|  | | nVidia ForceWare 163.44 | Nvidia has released a new beta ForceWare driver. This beta driver is optimized for the BioShock Demo and has support for the GeForce 6-8 families. This driver is available for Windows 2000/XP/2003/MCE/Vista and their 64-bit versions as well. You can also grab the BioShock Demo directly from our file server too.
Download for Windows 2000/XP/2003 Download for Windows XP/2003 x64 Edition Download for Windows Vista x32 Download for Windows Vista x64
Last edited by Regeneration; August 20th, 2007 at 11:51 PM..
| | | | 13 Comments | | | this driver sucks nutzzzzzz and the game crashes before it even goes up with those or without and benchmarked crappier then the previous ones so even if you say they are Bioshock oriented they dont even run that for alof of nvidia cards owners G7 and G8 | | | | or maybe something sucks in your system, or maybe you didn't remve drivers properly.. or maybe alot of things..
all i know is i run the drivers without an issue at all and only punks have problems | | | | Update! Important!
This driver apparently fixes the Texture Eviction bug that many sites have reported | | | | this one is working just fine here
i like it | | | | My system works fine with v158 drivers running, but if I install 162.22 I get all sorts of problems. mainly with the nvlddmkm driver failing to respond then the screen goes blank, then comes back for 20 seconds then goes blank, etc....
The same happened with the beta 163.34 drivers, although not as bad. I am going to give newer 163.44 drivers a try and see if this is the cure I have been waiting for. In the meantime I wish Nvidia would get a move on. | | | | Ok, break it up you two. Flaming is not allowed here, squall - you should know it already.
nvlddmkm is a known ForceWare Vista issue. |
Last edited by Regeneration; August 26th, 2007 at 04:05 AM..
| Quote | | | | | i wasn't flaming him, i was letting him know that only noobs or antinvidia propagandists are having issues with the drivers.
the general experts have worked out how now to get such issues. | | | | refering to people as "noobs or antinvidia propagandists" is not needed, we dont all have the same skill levels so you are in fact insulting users with your terms | | | | meh, anyone who isn't a member of ngohq is a noob. period. | | | | chaos i dont protect squall but i can say that he dident say anything wrong this time (only a punk and that is not big insult and he dident say that directly to anyone) | | | | Any plans to bring up a modified version of these with the old control panel? That stupid new cp is giving me quite a headache... | | | | Quote:
Originally Posted by RojBlake My system works fine with v158 drivers running, but if I install 162.22 I get all sorts of problems. mainly with the nvlddmkm driver failing to respond then the screen goes blank, then comes back for 20 seconds then goes blank, etc....
The same happened with the beta 163.34 drivers, although not as bad. I am going to give newer 163.44 drivers a try and see if this is the cure I have been waiting for. In the meantime I wish Nvidia would get a move on. | After a lot of hair pulling, screaming, shouting and generally throwing toys out of pram, I stumbled on the problem. It was nothing to do with the video drivers, as such. The problem was caused by my motherboard choosing a safe speed for my memory, instead of running it at 4-4-4-12 the correct speed, it was running it at 5-5-5-15. Having manually set the memory timings, I have had no further problems. Give it a try what have you got to lose, I am sure your sanity is hiding in the corner somewhat like mine, lol. | | | | Quote:
Originally Posted by schadenfreude Any plans to bring up a modified version of these with the old control panel? That stupid new cp is giving me quite a headache... |
Maybe use nHancer  | | |