After installing the driver 190.38 I have some heavy screen lags while playing games on my GTX295 with and without SLI mode. I've not seen this behavior in the last months.

---

Am I correct in that Cuda 2.3 has to have the 190.. drivers but Cuda 2.2 "as we are going to" works with the 185..186.. series drivers? I dont believe 190 drivers are necessary for Cuda 2.2 only for Cuda 2.3..
According to Nvidia release highlights.

I know the Mod. said 190.. was necessary but I wonder if he was mistaken.

If it was a Mistake it's cost me over 24 hours already on 4 200 Series NVIDIA Cards because all they've done since installing the 190.38 Drivers is Toast the Wu's after about 1/2 hour of running ... I've had both Dual GPU Core Box's shut down for the last 4 hr's cause didn't know what else to do with them and was tired of seeing all the errors come off them.

Am I correct in that Cuda 2.3 has to have the 190.. drivers but Cuda 2.2 "as we are going to" works with the 185..186.. series drivers? I dont believe 190 drivers are necessary for Cuda 2.2 only for Cuda 2.3..
According to Nvidia release highlights.

You're correct.

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

Sure, you can install the CUDA2.2 drivers as well. They will work, that's the reason to release the new application as cuda2.2.
On the other hand, we have tested here 190.xx and they seem to work.

gdf

Sure, you can install the CUDA2.2 drivers as well. They will work, that's the reason to release the new application as cuda2.2.
On the other hand, we have tested here 190.xx and they seem to work.

gdf

So far they've seemed to have worked on 4 Box's of mine with around 10 GPU Cores in them but on 3 Box's they haven't with 7 GPU Cores. 2 of those Box's with 4 Cores have turned in nothing but errors for about the last 40 hr's now. Not 1 good Wu has been returned off them since going to the 190.xx Drivers. The other Box has 3 GPU Cores in it & 1 of the cores or 2 will turn in an error every now & then since updating to the 190.38 Drivers.

I've tried Marks RivaTuner Fix for the Cards dropping their Speed but that hasn't worked. They keep resetting themselves to lower speeds within an hour or so after getting them back up to speed again. I reinstalled the 186.18 Drivers too on both those Boxes but they continue to get the errors now where they weren't getting any before I updated them to the 190.38 Drivers.

When you refer to the CUDA2.2 Drivers & the 190.xx Drivers are you refering to different Drivers or the same thing. All I have installed is the NVIDIA Drivers but not CUDA2.2 Drivers. Do you think it would help to install the CUDA2.2 Drivers if they are different from the 190.xx Drivers ???

[When you refer to the CUDA2.2 Drivers & the 190.xx Drivers are you refering to different Drivers or the same thing. All I have installed is the NVIDIA Drivers but not CUDA2.2 Drivers. Do you think it would help to install the CUDA2.2 Drivers if they are different from the 190.xx Drivers ???

Nvidia drivers gives your card the capability to run 2.2 apps but GPUGRID has to compile their apps with 2.2 to enable you to run GPUGRID using 2.2 runtime.
Same goes for 190.xxx drivers they give you capability to run 2.3 runtime but only on apps that have been compiled to do so.

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

Has everyone tried upgrading to BOINC 6.6.37 so that we're all singing from the same hymn sheet?

This has a significant fix for CUDA apps especially the use of video ram. I am running it no problems for days now.

XP32

XP64

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

Has everyone tried upgrading to BOINC 6.6.37 so that we're all singing from the same hymn sheet?

This has a significant fix for CUDA apps especially the use of video ram. I am running it no problems for days now.

XP32

XP64

I'll give the 6.6.37 a try on those Box's in awhile, right now their useless to me to run the Grid Project so anythings worth a try.

I'll give the 6.6.37 a try on those Box's in awhile, right now their useless to me to run the Grid Project so anythings worth a try.

I would also recommend that anyone having trouble with the 190.xxx drivers uninstalls all Nvidia drivers including PhysX REBOOT and then installing the new drivers as a clean install ensuring you have anti virus turned off. I appologise to anyone who has already done this.

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

I'll give the 6.6.37 a try on those Box's in awhile, right now their useless to me to run the Grid Project so anythings worth a try.

I would also recommend that anyone having trouble with the 190.xxx drivers uninstalls all Nvidia drivers including PhysX REBOOT and then installing the new drivers as a clean install ensuring you have anti virus turned off. I appologise to anyone who has already done this.

Did all that & installed the 6.6.37 Client along with the 190.38 Drivers and have 2 Wu Errors already on 2 different Box's, the same 2 Box's that have been giving 100% errors for the last 48 hours now. This all started with the original installation of the 190.38 Drivers, up until that time none of the Cards was giving errors but now that they've started there's been no way to stop them so far

Not ever reverting back to the 185.18 Drivers has helped, so I'm out 6 GPU Cards because of a Driver Change, just great. Now the one Box won't even get anymore Wu's because it's used up it's Daily Quota so I can't try anything else until tonight when the Quota's reset ...

Hi, is that the dual-GTX295 box that has the 01 error ? I noticed that you still have them overclocked (Clock rate: 1476000 kilohertz). What I find strange with the nvidia drivers and the 'precision' tool from evga is that you can test a speed and it will say "*DRIVER* has passed speed check". This makes me suspicious of whether the *driver* is a serious bottleneck for overclocking. I would expect a message like "New speed accepted by *CARD*) or similar to make it clear that overclocking does not depend on a driver revision.

So... You might want to try the stock clocks and see how that works and clock up from there. Good luck.

---

Join team Bletchley Park, the innovators.

Which hostid is out of quota? I will clear it.

gdf

ID: 17909 ... Thanks GDF, I'm going to set the clock back to default & see what happens, if that doesn't work I'll try each card seperatly. Usually it's just one of the Cards hats causing both of them to get errors or so thats what I've found in the past ...

Hi, is that the dual-GTX295 box that has the 01 error ? I noticed that you still have them overclocked (Clock rate: 1476000 kilohertz). What I find strange with the nvidia drivers and the 'precision' tool from evga is that you can test a speed and it will say "*DRIVER* has passed speed check". This makes me suspicious of whether the *driver* is a serious bottleneck for overclocking. I would expect a message like "New speed accepted by *CARD*) or similar to make it clear that overclocking does not depend on a driver revision.

So... You might want to try the stock clocks and see how that works and clock up from there. Good luck.

Yes, I didn't know it was getting that many errors though until I just looked at it. It must be going down hill fast as it wasn't getting that many before. I'll go drop that back to stack speeds too & see what happens.

'precision' tool from evga is that you can test a speed and it will say "*DRIVER* has passed speed check"

This test only finds out if the GPU can handle the Overclock.
It doesn't test for the actual stability.
Bob

Not even reverting back to the 186.18 Drivers has helped, so I'm out 6 GPU Cards because of a Driver Change, just great.

We had cases before where people upgraded the driver to some version, got only errors and upon reverting to the previously working drivers they still got only errors.

MrS

---

Scanning for our furry friends since Jan 2002

@MrS: I would then presume that in those cases there were remains of the new drivers in there. I nowadays make ghost images of my system before I change anything major. It just takes too much time and hassle to revert in case of issues otherwise. Now at least I can play back the ghost onto the drive and go.

@popandbob: I realize it doesn't test actual stability, I was more putting the focus on the word DRIVER. It seems illogical to me to refer to testing a driver if in fact you are testing the GPU, unless one actually means to indicate that the driver was tested and not (only) the GPU. I can imagine that a driver has influence on the way the GPU can handle high command speeds (from my haydays of direct I/O assembly programming on ATI cards).

---

Join team Bletchley Park, the innovators.

Hello Admin,
Would it be possible to do as Seti and have it to where the 2 DLL files for Cuda 2.3 could be " dropped " into the GPU folder and replace the 2.2 files?
This is possible on the Seti optimized apps. and works great.
For the people that 190.. drivers are running problem free this could give a small added boost.
I tried it one time and it would not work because the "file size " was incorrect and it errored out.
If the software did not look at the file size it would maybe work.
It may also help the developers get a jump on any issues with 2.3 also.

Just a question.
Thanks

Hello Admin,
Would it be possible to do as Seti and have it to where the 2 DLL files for Cuda 2.3 could be " dropped " into the GPU folder and replace the 2.2 files?
This is possible on the Seti optimized apps. and works great.
For the people that 190.. drivers are running problem free this could give a small added boost.
I tried it one time and it would not work because the "file size " was incorrect and it errored out.
If the software did not look at the file size it would maybe work.
It may also help the developers get a jump on any issues with 2.3 also.

Just a question.
Thanks

That sounded like an interesting question, so I'm giving it a try on two hosts.

Preliminary observation - makes no difference at all, but both tasks are still below 10% - it'll be tomorrow morning (UTC) before I get a definitive answer. I'm running this on my two Q6600/9800GT hosts (XP SP3), if anyone wants to watch.

I can only presume that GPUGrid relies much less on Fourier Transforms than SETI - it was fft that made the difference at SETI.

Gentlemen, I am new to gpugrid having folded for some months...May I ask...when you are talking of these errors since upgrading drivers ...are you getting the driver failed and recovered message??