3/29/2009 2:47:20 PM||Starting BOINC client version 6.4.7 for windows_x86_64
3/29/2009 2:47:20 PM||log flags: task, file_xfer, sched_ops
3/29/2009 2:47:20 PM||Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
3/29/2009 2:47:20 PM||Data directory: K:\BOINC_DATA
3/29/2009 2:47:20 PM||Running under account x
3/29/2009 2:47:20 PM||Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz [Intel64 Family 6 Model 23 Stepping 6]
3/29/2009 2:47:20 PM||Processor features: fpu tsc pae nx sse sse2 pni
3/29/2009 2:47:20 PM||OS: Microsoft Windows Vista: Ultimate x64 Editon, Service Pack 1, (06.00.6001.00)
3/29/2009 2:47:20 PM||Memory: 4.00 GB physical, 8.17 GB virtual
3/29/2009 2:47:20 PM||Disk: 50.00 GB total, 49.04 GB free
3/29/2009 2:47:20 PM||Local time is UTC -5 hours
3/29/2009 2:47:20 PM||Not using a proxy
3/29/2009 2:47:20 PM||No CUDA devices found
3/29/2009 2:47:20 PM||No coprocessors
3/29/2009 2:47:20 PM|rosetta@home|URL: http://boinc.bakerlab.org/rosetta/; Computer ID: ; location: home; project prefs: default
3/29/2009 2:47:20 PM|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: ; location: home; project prefs: default
3/29/2009 2:47:20 PM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: ; location: home; project prefs: default
3/29/2009 2:47:20 PM||General prefs: from SETI@home (last modified 16-Jul-2006 00:05:26)
3/29/2009 2:47:20 PM||Computer location: home
3/29/2009 2:47:20 PM||General prefs: no separate prefs for home; using your defaults
3/29/2009 2:47:20 PM||Preferences limit memory usage when active to 2046.79MB
3/29/2009 2:47:20 PM||Preferences limit memory usage when idle to 3684.22MB
3/29/2009 2:47:20 PM||Preferences limit disk usage to 1.00GB
3/29/2009 2:47:20 PM||[error] Missing a CUDA coprocessor
   "....and continues."

I am assuming "Missing a CUDA coprocessor" are the SETI jobs complaining about it as BOINC appears not to want to run anything from SETI now, and the message repeats a million times.

I have tried everything I can think of. (Disabling Screen saver. Aero. etc.)
I have: (1) nVidia 8800GT.
I have checked the video card for overheating. It isn't.


I received this error for quite awhile the last time, but then read about re-installing newer nVidia driver. I cleaned the driver files out and installed newest driver. BOINC then started seeing the CUDA device, again. In the last few days it has started the above behavior once again. I have not touched anything or installed anything since 're-newing' the driver. Any help appreciated.

---

One thought. I am using remote desktop to get into the computer/reboot/etc. Of course this is through terminal services so there is no option for nVidia control panel, etc. Could it be by starting Boinc/seti@home in this way somehow interferes with the graphic processor/cuda availability?

---

One thought. I am using remote desktop to get into the computer/reboot/etc. Of course this is through terminal services so there is no option for nVidia control panel, etc. Could it be by starting Boinc/seti@home in this way somehow interferes with the graphic processor/cuda availability?

That is most likely your problem. Remote Desktop uses its own graphics drivers for the RDP and not the nVidia ones installed. Many users in the Number Crunching forum have stated that RDP is not compatible with CUDA.

---

Indeed this was the case. When I got back home I rebooted, and works like a charm.

Thanks for the response. Resolved, but shouldn't Boinc be made to grab the cuda device (especially in this case since card isn't even running anything?) when it runs regardless of use of device elsewhere? I guess since the nVidia card isn't 'initialized' for user, it won't function at all?

---

Indeed this was the case. When I got back home I rebooted, and works like a charm.

Thanks for the response. Resolved, but shouldn't Boinc be made to grab the cuda device (especially in this case since card isn't even running anything?) when it runs regardless of use of device elsewhere?I guess since the nVidia card isn't 'initialized' for user, it won't function at all?

Its not BOINC that can be changed to correct this from where I sit. BOINC simply looks for CUDA within the video driver, and if RDP is using a generic driver that's different from the video card in the system, then this driver is not going to report CUDA capabilities to BOINC. You would have to look to Microsoft to update their Remote Desktop feature to include all of the originating card's driver features, which isn't really Microsoft's intent when designing and offering Remote Desktop in the first place (not to mention making Remote Desktop exponentially more difficult to test and troubleshoot to make sure it works with the plethora of video cards and drivers on the market).

---

I have recently been having this same problem as well.
I have found that if I just uninstall boinc and reinstall
all is well and working again