PDA

View Full Version : 190.40 beta

namuk
07-27-09, 08:16 AM
http://www.fudzilla.com/content/view/14797/1/
LitHiuM
07-27-09, 11:14 AM
Downloaded but gonna hang fire on installing until I see some more feedback.
B0ne
07-27-09, 11:38 AM
Just installed em, played a couple of games, performance seems to be better; could just be placebo effect.
betterdan
07-27-09, 11:47 AM
I'll try these when I get home. I hate how the 190.38 drivers make my card get stuck at 3d speeds all the time even when not playing a game.
Silverbak
07-27-09, 04:13 PM
Just installed em, played a couple of games, performance seems to be better; could just be placebo effect.

I've just tested this out in World of Warcraft and certain places that had previously (against version .38) abysmal framerates have now dramatically improved with the .40 drivers.
shilk
07-27-09, 05:06 PM
I couldn't even get these to install. It would just hang while it's installing, and I was sitting there looking at the progress bar for a good 20 minutes before I decided to kill it and reinstall the 190.38's.
ATi
07-27-09, 11:11 PM
any one tried Arma2 with the 190.40 ?:o
betterdan
07-28-09, 12:14 AM
Installed these drivers and just like the 190.38 drivers they make my card get stuck at 3d speeds while idling in Windows which puts off more heat than it needs to. :thumbdwn: Is anyone else having this problem?

3D Mark Vantage score is about the same.
shilk
07-28-09, 12:51 AM
Tried reinstalling and they didn't install the Control Panel. Got a black screen which went to "monitor not detected mode" a few seconds later. Rebooted in safe mode, got the same thing and then it automatically rebooted again by itself. Back in regular desktop and the drivers didn't even show up but they were listed as being installed in the windows control panel. Tried to fire up Firefox and even IE and it would crash upon launch.

Uninstalled to make sure and rebooted and no more issues. Frakkin weird drivers. Staying away from these even if they went WHQL.
betterdan
07-28-09, 01:53 AM
They installed fine for me but they don't uninstall fine. They leave a couple of files which when I installed older drivers (190.15 and 190.38) the 190.40 files show up in the driver information still. The files are NVGameSR.dll, NVDispSR.dll, NVViTvSR.dll and NVWSSR.dll
The are extra files it seems with just an "R" added at the end. For example 190.38 installs NVGameS.dll and 190.40 installed that plus NVGameSR.dll No idea what the R file is supposed to be for.

Anyways I reinstalled 190.38
LitHiuM
07-28-09, 08:40 AM
These still give terrible frame rates in WoW. Back to 186's
FlakMagnet
07-28-09, 08:40 AM
Maybe the 'R' means Release as in non-Debug build? Where 'D' always meant Debug when developing C++.

Probably not though.
betterdan
07-28-09, 09:36 AM
Here's an example of the driver info.

http://img.photobucket.com/albums/v296/betterdan/Capture-10.jpg

Notice the extra NVGameSR.dll and the NVDispSR.dll files these were left over after uninstalling 190.40 and reinstalling 190.38 drivers.
The driver download was bigger than previous ones and I am betting it's because they had those extra files in the installer.
Skinner
07-28-09, 10:00 AM
Here's an example of the driver info.

http://img.photobucket.com/albums/v296/betterdan/Capture-10.jpg

Notice the extra NVGameSR.dll and the NVDispSR.dll files these were left over after uninstalling 190.40 and reinstalling 190.38 drivers.
The driver download was bigger than previous ones and I am betting it's because they had those extra files in the installer.

Ik have this also once in a while.
Sometimes you need to manually uninstall everything (with drivercleaner or somthing like this) to let them install right.
B0ne
07-28-09, 01:26 PM
any one tried Arma2 with the 190.40 ?:o

Yup, fired up the demo just now, seems like there was a nice improvement; again, I don't have FRAPS or anything installed at the moment so it could be placebo.
qube
07-31-09, 06:59 AM
any one tried Arma2 with the 190.40 ?:o

Arma 2 works fine whit 190.40
badboy64
08-02-09, 02:55 PM
Here's an example of the driver info.

http://img.photobucket.com/albums/v296/betterdan/Capture-10.jpg

Notice the extra NVGameSR.dll and the NVDispSR.dll files these were left over after uninstalling 190.40 and reinstalling 190.38 drivers.
The driver download was bigger than previous ones and I am betting it's because they had those extra files in the installer.
I just installed the this driver over the 190.38 and all of mine say 190.40. I didn't even uninstall the 190.38 at all and I am using Win 7. too.
betterdan
08-02-09, 05:32 PM
I just installed the this driver over the 190.38 and all of mine say 190.40. I didn't even uninstall the 190.38 at all and I am using Win 7. too.

Ok.
When I installed the 190.40 over the 190.38 I did not uninstall the older driver either and everything said 190.40 in the driver information too.
What I was saying is I then uninstalled 190.40 and reinstalled 190.38 and that is when I came across the problem of having 2 different drivers listed.
Yaboze
08-03-09, 09:10 PM
This happened to me going to 190.38. I removed the 190.38's and rebooted. Windows 7 decided to install the Windows Update drivers of 185.85. I didn't realize it was doing this on that reboot. I had a mix of .85 and .38. I had to go into Device Manager, uninstall the graphics card and reboot. This put the base WDM driver up that ships with Windows 7. Then I was able to install the 190.38's.