Uploaded Oct 5 (codesigned Oct 1). The fix list (below) looks minor.

I installed, rebooted, and back to crunching no problems, no perf change either way.

nVIDIA DL site is here.

-------------------------------

New in Version 191.07

•Adds support for OpenGL 3.2 for GeForce 8, 9, 100, and 200-series GPUs and ION GPUs.
•Accelerates performance in several gaming applications. The following are examples of improvements measured with version 191.07 drivers vs. version 190.62 drivers (results will vary depending on your GPU, system configuration, and game settings):


â—¦Up to 12% performance increase in ARMA 2
â—¦Up to 8% performance increase in Batman: Arkham Asylum with GPU PhysX enabled
â—¦Up to 50% performance increase in Call of Juarez: Blood in Bound with SLI enabled
â—¦Up to 14% performance increase in Fallout 3 (indoor scenes) with antialiasing enabled
â—¦Up to 10% performance increase in Far Cry 2 (DX9 version) with antialiasing enabled
â—¦Up to 34% performance increase in Prototype with antialiasing enabled



•Adds SLI support for Aion, Darkfall, Dawn of Magic 2: Time of Shadows, Dreamkiller, Fuel, Majesty 2: The Fantasy Kingdom Sim, Need for Speed: Shift and more.
•Includes numerous bug fixes, including the following key fix (additional bug fixes can be found in the release notes on the documentation tab): For graphics cards supporting multiple clock states, 3D clocks correctly return to 2D clocks after exiting a 3D application

Unfortunately this upgrade killed CPUID ability to monitor CUDA temps.
Bummer!!!

---

When we finally figure it all out, all the rules will change and we can start all over again.

Unfortunately this upgrade killed CPUID ability to monitor CUDA temps.
Bummer!!!

run registry and look for all instances of RmThermalProviderNum and RmThermalProviderInfo and delete them.

---

Hi, doesn't seem a good idea to mix 2, totally different GPU's, on 1 host.
Has to be possible, but IMHO, it's asking for trouble (instabillity)

How does BOINC react to that, in terms of workfetch and flow?
Maybe too early to tell?

---

Hi, doesn't seem a good idea to mix 2, totally different GPU's, on 1 host.
Has to be possible, but IMHO, it's asking for trouble (instabillity)

Instability from 2 different GPU means you have badly made OS.

---

This updated driver still does not fix the fact that if you have 2 GTX295's,
in a Vista os rig that only 3 GPU's are seen.
Still Waiting on Nvidia to fix it.

Dave

---

Unfortunately this upgrade killed CPUID ability to monitor CUDA temps.
Bummer!!!

run registry and look for all instances of RmThermalProviderNum and RmThermalProviderInfo and delete them.

Big thanks, that did the trick:)

---

When we finally figure it all out, all the rules will change and we can start all over again.

And it's worth to go from 190.x to 191.x if only CUDA crunching?

Speed up?

---

My i7 with two different GPUs (8800GTS & 9800+) just froze up with 191.07. I went back to driver 190.38, no such issues since.

/Anton

And it's worth to go from 190.x to 191.x if only CUDA crunching?

Speed up?

I doubt there would be any speedup for Cuda crunching, as I do not see any new DLL's above 2.3 being offered at the moment.

---

"Time is simply the mechanism that keeps everything from happening all at once."

And it's worth to go from 190.x to 191.x if only CUDA crunching?

Speed up?

I doubt there would be any speedup for Cuda crunching, as I do not see any new DLL's above 2.3 being offered at the moment.

I don't see any mesurable speed up as yet, but other task running at the same time do seem to be a bit smoother.

---

When we finally figure it all out, all the rules will change and we can start all over again.

I have had a screw up here with these drivers.
A job got hung or stoped showing progress at about 60% done and stayed that way for about 2 hours untill I aborted it.
Then it started haveing Comp errors on all the rest of the jobs untill I stopped BOINC and rebooted my system.
The problems were for only the CUDA jobs as the rest of the WU ran normally during this time.
So far all is back to normal now.

---

When we finally figure it all out, all the rules will change and we can start all over again.

Think I'll stay with 190.62 until this gets sorted....

---

"Time is simply the mechanism that keeps everything from happening all at once."

@ Pilot

Maybe this new driver version isn't very well for your new OS (Win7) ?


If I wouldn't have speed up with the new 191.07 , I will stay with 190.38 , it work fine with WinXP Home.

---

@ Pilot

Maybe this new driver version isn't very well for your new OS (Win7) ?


If I wouldn't have speed up with the new 191.07 , I will stay with 190.38 , it work fine with WinXP Home.

Before the Download and update I checked and it said that it was good for Windows 7. However I am still running RC which could have a funny or two in it.
If it hangs again, or starts giving massive errors, I will back down to earlier version of the drivers.

---

When we finally figure it all out, all the rules will change and we can start all over again.

I meant also - maybe it's because of..

190.38 came out and then they saw that it's not well for WinVista, then they published 190.62 .

Maybe soon they will publish > 191.07 which will work better with Win7 ..


All AFAIK and IIRC.. :-)

---

191.07 caused my 9500gt to slow wayyyy down. cuda work units took about 10 times longer then when i was using the 190.62 drivers.

i gave the new drivers about 24 hours to see if things would fix themselves , but they had not so i uninstalled them and went back to the 190.62's and my cuda workunit time is back where it suppose to be.

I got 191.07 for my GTS250 but the nvidia site only has up to 186.81 for my mobile-based 9600M GS.

Stange...

I got 191.07 for my GTS250 but the nvidia site only has up to 186.81 for my mobile-based 9600M GS.

Stange...

Beta 190.38 Notebook drivers are available in the second post in this thread:

CUDA Toolkit and SDK 2.3 released

Been using 190.38 for the last couple of weeks, managed to get my under spec GPU (for Seti) crunching on Collatz with it,
and managed to get Collatz to lower their Server's Cuda memory requirements down to 126Mb, so no app_info required anymore. :)

Claggy

---