Seti@Home optimized science apps and information

Optimized Seti@Home apps => Windows => GPU crunching => Topic started by: michael37 on 01 Feb 2010, 03:53:43 pm

Title: Cuda 3.0 / Nvidia 196.21
Post by: michael37 on 01 Feb 2010, 03:53:43 pm
I just upgraded my nvidia driver to 196.21 to get a HW-accelerated playback in Flash.  The driver provides OpenCL 1.0 and Cuda 3.0.    I am running Windows 7 64-bit.

How should I use the GPU app?



Title: Re: Cuda 3.0 / Nvidia 196.21
Post by: Raistmer on 01 Feb 2010, 07:09:06 pm
If you really need new driver then just continue with it and CUDA 2.3.
But it seems best speed will be with 190 or 191.xx + CUDA 2.3
Title: Re: Cuda 3.0 / Nvidia 196.21
Post by: Gizbar on 05 Feb 2010, 07:02:37 pm
Haven't tried 196.21, but was testing 195.62 on win7-64HP. Worked well for a while, but then started failing on the driver - 'Nvidia driver has stopped responding but has successfully recovered'.

Every time this happens, it seems to 'forget' the current GPU WU, and start another. I have a GTX260 and an 8800GTX in this machine. When it failed 3 times in less than an hour today, I went back to version 191.07. No problems since, and I was using BBC iPlayer to watch recorded TV as well.

My other machine is a Vista32HP. That one didn't seem to be failing in the same way, but I still went back to 191.07 on that one too. It only has one 9800GTX+ in it.

If you really need H/W Flash acceleration, then try it. I got fed up of the increasing unfinished work units. I may try 196.21 in a while if it seems to be stable for others.

195.62 just wasn't stable enough for me.

regards, Gizbar.
Title: Re: Cuda 3.0 / Nvidia 196.21
Post by: MarkJ on 06 Feb 2010, 09:16:53 am
I have 196.21 on 4 machines. The only issues i've seen are with the GPUgrid beta app on the old (65nm) GTX260's where it rebooted once and got a heap of "app has stopped responding" popup messages. :o

Two machines have a GTX295, one has a GTX275 and one with dual (65nm) GTX260's. I don't mix different cards. Still running the cuda 2.3 DLL's, along with the 64bit multibeam.