Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by Reaping_Ant, Oct 1, 2009.
downclocking issue during 3d apps still exists with this set on w7 x64
186.91, while playing Half Life 2, I would get occasional pauses, like while I'm playing and the game would freeze, with a looping sound for 2 seconds, then loop in a different way for 1 adn restore itself. I', gonna test this one to see if the issue is still there. Anyone reporting something similar with these on a Source game? :biggun:
Has anyone tried running any game using the quake 3 engine with these drivers. If so do they work?
Reason I ask is when I tried 191.03 no games using the Quake 3 engine would run.
191.07 The best Win7 Drivers i ever used .
No lockups in High demanding Games.
Auto Fan working now.
Can AA in Game set on the highest setting now.
Looks like these drivers are more compatible With DX9 and 10.
Wating for DX11 Games
First 19x.xx driver I did not un-install after a few hours.
Looks very smooth in Grid, NFS Shift, COD waw, Wolfenstein and F.E.A.R.2.
Win7 Prof 32bit.
according to many replays i see that this drivers are very good
thanks ill give them a test drive
Good Driver for win7 x64!!!
Compared to 185.85 near same or better iq and performance.
Tested Far Cry 2, GTA IV, Battlefield 2, GTA: VC, COD4 and the old MOHAA Spearhead.
All games runs good without any error and with good performance.
Downclocking works also.
So i tested now for 6 hours gaming etc. i hope these drivers stay good, all other
19x.xx or any above 185.85 have some bugs here and there for me but this one
"Adjust screen size and position" is never working with s-video and 19x.xx drivers. I can use it with 18x.xx drivers. I tried every 19x.xx driver but no luck..
sticking with 186.91 driver.
You'll also have to wait for DX11 hardware too! :banana:
nvSCPAPISvr.exe was trying to reach web(3d vision), guess it has update feature
u need extension limit "on" to play old ogl
No you don't. the Profile in the driver forces Extension limit automatically.
EVGA Precision 1.8 Temp not work 191.07 Driver!
sof2mp wont open unless i put it on
edit: just looked at nvapps.xml, theres extension limit for jediacademy but not for ET or sof2
(PROPERTY Label="ogl_extension" Value="0x00004844" Default="0x00004844")
same with rtcw-sp...
the default profile does not have it on, and rtcw-sp errors on reading gl_caps it seems... forcing it on it will start.
squall: are you sure it's not a setting you previously made, carried over to this version? I did safemode sweep, and clean reg before installing this one and rtcw default profile has ext.lim. set to "use global...(off)" .
really cool drivers for me, no problems so far. NFS Shift smooth as hell now.
But..! is there a way nHancer 2.5.5 to work with this driver? i tried 2.5.3 also , no chance...
I just noticed you said quake 3 games, rather then quake 3, so the correct extension limit setting is 1b58, seems they've added it for the actual Quake game, but not for those using the quake 3 engine.
No it works but now it is little bit complicated to get EVGA to show temp properly. There are two ways you can try to get it work.
1. This one was posted by UNWINDER on NVIDIA forums:
"That's an internal issue of all currently available 190.xx series.
Since 190.xx series NVIDIA driver's internal resource manager is trying to precache thermal sensors information in the registry during the first startup after installation. This mechanism doesn't seem to work fine yet, under some conditions sensor detection and precaching algorithm can fail and store incorrect sensor type information in the registry causing temperatures to disappear till the ForceWare re-installation.
Until the problem is not fixed by NVIDIA, there are still some temporary tricks allowing to solve it. First, you may just perform complete Foreware re-install, this will also cause precached thermal sensor information to be removed from the registry and to be re-detected by ForceWare on the next start. Second, you may manually remove corrupted thermal sensor information from the registry and this way cause the ForceWare to re-detect it on the next reboot. To do it open regedit then search and delete all instances of RmThermalProviderInfo and RmThermalProviderNum entries in the registry. Then reboot."
Way number two I use and it is working. This is what you need to try:
1. Before driver update uninstall EVGA from your system completely. All files and the folder itselt.
2. Uninstall display driver.
3. Reboot in a safe mod and run Driver sweeper.
4. Reboot and install new display driver.
5. Reboot and install EVGA Precision.
Try to use the way number 1 or number two and you should get your TEMP back.
This has only started happening with sof2mp since 191.xxx drivers. In all previous drivers sof2mp would run quite happily with extension limit set to off.
Its because OpenGL 3.2's additional extensions have put increased the extension count past the apps detection capability, in nhancer add 1b58 or 4844 as that extension limit value for that app.
I'd go with 4844 though, it seems thats the value used on most of the starwars games including KOTOR.