View Full Version : Nvidia Geforce 191.07 WHQL drivers

10-05-09, 09:12 AM
New official WHQL drivers from Nvidia.



10-06-09, 01:28 PM
Risen Demo stopped working, when I upgraded from Forceware 186.18 WHQL to the new 191.07 WHQL, furthermore the program Refresh Rate Patcher 1.0.1 no longer allowed forcing 2048x1536 at 85Hz making it impossible to use this mode (since Nvidia seems to have forgotten that we a still a few hanging on to the king of CRTs like the Sony 21" F520). So a quick system restore sent me back to the great and trouble-free 186.18... For now... :-)

10-11-09, 08:26 PM
I loved these drivers, all my newer games worked great, HD video and BluRay was superb. I loved them, until I tried to play Call of Duty (the first one) and CoD:United Offensive. Both would crash to desktop.

I got the buffer overflow errors the Extension Limit off, and this error message with it on. I went back to my tried and true 186.18's. Hopefully this will be cleared up with the next release.

COD 1.3 build win-x86 Mar 2 2004
----- FS_Startup -----
Current language: english
Current search path:
C:\PROGRA~1\CALLOF~1\main\pakb.pk3 (60 files)
C:\PROGRA~1\CALLOF~1\main\paka.pk3 (41 files)
C:\PROGRA~1\CALLOF~1\main\pak9.pk3 (149 files)
C:\PROGRA~1\CALLOF~1\main\pak8.pk3 (235 files)
C:\PROGRA~1\CALLOF~1\main\pak6.pk3 (3 files)
C:\PROGRA~1\CALLOF~1\main\pak5.pk3 (4858 files)
C:\PROGRA~1\CALLOF~1\main\pak4.pk3 (1668 files)
C:\PROGRA~1\CALLOF~1\main\pak3.pk3 (1992 files)
C:\PROGRA~1\CALLOF~1\main\pak2.pk3 (694 files)
C:\PROGRA~1\CALLOF~1\main\pak1.pk3 (2642 files)
C:\PROGRA~1\CALLOF~1\main\pak0.pk3 (12816 files)
C:\PROGRA~1\CALLOF~1\main\localized_english_pak5.p k3 (46 files)
localized assets pak file for english
C:\PROGRA~1\CALLOF~1\main\localized_english_pak3.p k3 (7 files)
localized assets pak file for english
C:\PROGRA~1\CALLOF~1\main\localized_english_pak2.p k3 (9 files)
localized assets pak file for english
C:\PROGRA~1\CALLOF~1\main\localized_english_pak1.p k3 (3736 files)
localized assets pak file for english
C:\PROGRA~1\CALLOF~1\main\localized_english_pak0.p k3 (1204 files)
localized assets pak file for english

File Handles:
30160 files in pk3 files
execing default.cfg
couldn't exec language.cfg
execing config.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
...detecting CPU, found Intel Pentium III
Measured CPU speed is 2.66 GHz
System memory is 1024 MB (capped at 1 GB)
Video card memory is 2048 MB
Streaming SIMD Extensions (SSE) supported

----- Client Initialization -----
----- Initializing Renderer ----
----- Client Initialization Complete -----
----- R_Init -----
Initializing OpenGL subsystem
...initializing QGL
...calling LoadLibrary( 'C:\Windows\system32\opengl32.dll' ): succeeded
...setting mode -1: 1680 1050 FS
...using colorbits of 32
...calling CDS: ok
...registered window class
...created window@0,0 (1680x1050)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD( 32, 24, 8 )
...125 PFDs found
...hardware acceleration found
...PIXELFORMAT 9 selected
...creating GL context: succeeded
...making context current: succeeded
Initializing OpenGL extensions

----- CL_Shutdown -----
RE_Shutdown( 1 )
Shutting down OpenGL subsystem
...wglMakeCurrent( NULL, NULL ): success
...deleting GL context: success
...releasing DC: success
...destroying window
...resetting display
...shutting down QGL
...unloading OpenGL DLL
Hunk_Clear: reset the hunk ok
Your video card appears to be missing one or more features required to run Call of Duty.

You should install the latest drivers for your video card, being sure to uninstall the old drivers first. If you already have the latest drivers, you should completely uninstall the drivers and then reinstall them. This fixes most problems. If the game still doesn't work, it may be that your video card does not have the minimum features required. Please check the readme for more information, including a list of supported video cards

10-15-09, 10:35 PM
After installation I noticed that Vsync is stuttering in TF2. Once I disable it the stuttering is gone. I didn't get this with the last driver set. Any ideas? Any one else get this problem? I hate tearing I might go back to the last driver set.

10-16-09, 07:31 PM
These drivers are terrible even though the performance is better. I crashed two times so far. I ended up going back to the 190.62 for vista 64.

Elvin Presler
10-16-09, 07:59 PM
These are pure crap.

1. When I tried to make any custom resolutions...like 1024x768@60, 1280x960@60 (or any others) they promptly informed me my Samsung 205BW did not support that resolution and refused to create the custom res, which I do ALL THE TIME to fix the broken fixed aspect ratio scaling in all the latest drivers since Vista came out.

2. After uninstalling them, upon reboot, Windows popped up the new hardware found wizard, then proceeded to AUTOMATICALLY without any input from me search for and attempt install a driver...fortunately, there was none for it to find and I block Windows Updates. So these drivers made system changes (I wouldn't even know how to undo) that basically allowed Windows to just hijack installing new hardware and go to town without allowing me to stop it.

These drivers felt like I was installing Windows 7 drivers on XP (which they weren't of course) like they just hacked in the Windows XP check into something made for Windows 7.

Audio drivers bundled in there? WTF? Trash. Pure trash! It looks like 182.50 will be as far as real XP support is going to go. Anything later is loaded with crap and breaks resolutions, etc, etc. Damn I miss the old control panel and a working temperature monitor right in it. :thumbdwn::thumbdwn::thumbdwn:

10-22-09, 03:48 PM
had Nvlddmkm stopped responding while playing operation flashpoint dragon rising on windows 7

saw this further down in the event viewer= "The NVIDIA Display Driver Service service has reported an invalid current state 32"

any ideas anyone?


10-31-09, 07:40 AM
With these drivers setting in UT2004 AA to forced 4x or 8x any setting doesnt have effect.
AF works but AA does not have effect. It worked fine with older drivers, any idea?

Weird now it works... anyway with the earlier driver set setting AA in newer games only worked after setting it in CP, and restarting the game. While usually it works just by alt - tabbing back to the game.

How is it in these drivers?