Hi,

my card has been doing CUDA fine for about 1-2 weeks. I recently updated to BOINC manager v6.6.20, and initially CUDA worked fine. However after some time I had about 2-3 CUDA workunits that were stuck in status Waiting to run (0.31 CPUs, 1 CUDA), and the manager started getting CPU workunits instead.

Since all tips I found here (suspend/resume, restart BOINC, restart machine, etc.) didn't help, I just reset the SETI project. Now it no longer downloads CUDA workunits.

The log shows:

4/17/2009 7:55:53 AM Starting BOINC client version 6.6.20 for windows_x86_64
4/17/2009 7:55:53 AM log flags: task, file_xfer, sched_ops
4/17/2009 7:55:53 AM Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
4/17/2009 7:55:53 AM Data directory: C:\ProgramData\BOINC
4/17/2009 7:55:53 AM Running under account Torsten
4/17/2009 7:55:53 AM Processor: 2 GenuineIntel Intel(R) Pentium(R) D CPU 2.80GHz [Intel64 Family 15 Model 6 Stepping 2]
4/17/2009 7:55:53 AM Processor features: fpu tsc pae nx sse sse2 pni mmx
4/17/2009 7:55:53 AM OS: Microsoft Windows Vista: Ultimate x64 Editon, Service Pack 1, (06.00.6001.00)
4/17/2009 7:55:53 AM Memory: 4.00 GB physical, 5.91 GB virtual
4/17/2009 7:55:53 AM Disk: 39.05 GB total, 3.27 GB free
4/17/2009 7:55:53 AM Local time is UTC +2 hours
4/17/2009 7:55:53 AM CUDA device: GeForce 9800 GTX+ (driver version 18250, CUDA version 1.1, 512MB, est. 84GFLOPS)
4/17/2009 7:55:53 AM Not using a proxy
4/17/2009 7:55:53 AM SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 4867638; location: home; project prefs: default
4/17/2009 7:55:53 AM GPUGRID URL: http://www.gpugrid.net/; Computer ID: 32881; location: (none); project prefs: default
4/17/2009 7:55:53 AM SETI@home General prefs: from SETI@home (last modified 17-Apr-2009 07:35:49)
4/17/2009 7:55:53 AM SETI@home Computer location: home
4/17/2009 7:55:53 AM SETI@home General prefs: no separate prefs for home; using your defaults
4/17/2009 7:55:53 AM Preferences limit memory usage when active to 2046.79MB
4/17/2009 7:55:53 AM Preferences limit memory usage when idle to 3684.22MB
4/17/2009 7:55:53 AM Preferences limit disk usage to 0.31GB
4/17/2009 7:55:53 AM Preferences limit # CPUs to 1
4/17/2009 8:04:00 AM SETI@home Resetting project
4/17/2009 8:04:04 AM SETI@home Sending scheduler request: To fetch work.
4/17/2009 8:04:04 AM SETI@home Requesting new tasks
4/17/2009 8:04:09 AM SETI@home Scheduler request completed: got 1 new tasks
4/17/2009 8:04:11 AM SETI@home Started download of setiathome_6.03_windows_intelx86.exe
4/17/2009 8:04:11 AM SETI@home Started download of setigraphics_6.03_windows_intelx86.exe
4/17/2009 8:04:15 AM SETI@home Finished download of setiathome_6.03_windows_intelx86.exe
4/17/2009 8:04:15 AM SETI@home Finished download of setigraphics_6.03_windows_intelx86.exe
4/17/2009 8:04:15 AM SETI@home Started download of libfftw3f-3-1-1a_upx.dll
4/17/2009 8:04:15 AM SETI@home Started download of setiathome-6.03_AUTHORS
4/17/2009 8:04:17 AM SETI@home Finished download of setiathome-6.03_AUTHORS
4/17/2009 8:04:17 AM SETI@home Started download of setiathome-6.03_COPYING
4/17/2009 8:04:19 AM SETI@home Finished download of setiathome-6.03_COPYING
4/17/2009 8:04:19 AM SETI@home Started download of setiathome-6.03_COPYRIGHT
4/17/2009 8:04:20 AM SETI@home Finished download of libfftw3f-3-1-1a_upx.dll
4/17/2009 8:04:20 AM SETI@home Finished download of setiathome-6.03_COPYRIGHT
4/17/2009 8:04:20 AM SETI@home Started download of setiathome-6.03_README
4/17/2009 8:04:20 AM SETI@home Started download of seti_603.jpg
4/17/2009 8:04:22 AM SETI@home Finished download of setiathome-6.03_README
4/17/2009 8:04:22 AM SETI@home Finished download of seti_603.jpg
4/17/2009 8:04:22 AM SETI@home Started download of 06fe09ac.11771.1299.5.8.26
4/17/2009 8:04:22 AM SETI@home Started download of arecibo_181.png
4/17/2009 8:04:25 AM SETI@home Finished download of arecibo_181.png
4/17/2009 8:04:25 AM SETI@home Started download of sah_40.png
4/17/2009 8:04:26 AM SETI@home Finished download of 06fe09ac.11771.1299.5.8.26
4/17/2009 8:04:26 AM SETI@home Finished download of sah_40.png
4/17/2009 8:04:26 AM SETI@home Started download of sah_banner_290.png
4/17/2009 8:04:26 AM SETI@home Started download of sah_ss_290.png
4/17/2009 8:04:27 AM SETI@home Starting 06fe09ac.11771.1299.5.8.26_0
4/17/2009 8:04:27 AM SETI@home Starting task 06fe09ac.11771.1299.5.8.26_0 using setiathome_enhanced version 603
4/17/2009 8:04:28 AM SETI@home Finished download of sah_banner_290.png
4/17/2009 8:04:28 AM SETI@home Finished download of sah_ss_290.png

Any ideas what this might be, and how I might be able to get CUDA running again?

Thanks,
Torsten

Hi,

Just a thought, but when you updated Boinc, did you enable gpu usage in Boinc Manager? I believe that would be in the Advanced Menu> Preferences> under porcessor usage.

There's also info in this thread about an app_info.xml file that you may find of interest.

---

Hm, under Advanced Preferences, Processor I only found the option to use the GPU while the computer is in use, and in my SETI profile GPU usage is activated. I activated the "while computer in use" checkbox, and somehow this seems to have done the trick. However I'm fairly convinced that it also didn't do CUDA when the computer was not in use, because the screensaver showed the same behaviour. Whatever it was, since it is now processing CUDA WUs again it's fine for me.

Thanks for the pointer!

Hm, under Advanced Preferences, Processor I only found the option to use the GPU while the computer is in use, and in my SETI profile GPU usage is activated. I activated the "while computer in use" checkbox, and somehow this seems to have done the trick. However I'm fairly convinced that it also didn't do CUDA when the computer was not in use, because the screensaver showed the same behaviour. Whatever it was, since it is now processing CUDA WUs again it's fine for me.

Thanks for the pointer!

Glad to hear it helped. I only used a 6.6x version of Boinc for CUDA for a limited time a while back, and my memory on it is a little fuzzy, so I was under the impression there was more to it than allowing gpu use "while in use", but I can't swear by it, since I don't have a 6.6x version on my pc's ATM. I had thought I'd had a similar experience, and wasn't able to get CUDA to start up until I enabled that function. Of course, I could well be confusing it with something else, but as long as it's working for you now, it's all good. It's probable that one of the other crunchers will be able to clarify it in more detail in a while.

---