I'm running Windows XP 32 bit and the only hints I can find seem to be issues with Vista and Windows 7. I've reset the project, restarted BOINC, and keep getting the error message:

6/18/2009 2:27:44 PM GPUGRID Message from server: Can't use CUDA app for Full-atom molecular dynamics: Your computer has no CUDA device


I'm running some optimized apps with a customized app_info.xml for SETI. Would that have anything to do with it? Any help is appreciated.

GPU is an Nvidia GTX 260 and works fine with SETI.

I started playing with optimized apps yesterday and it was working CUDA units after that. My GPU was pushing 80c and it idles @ 55c normally. I've been out of work units all day today and yesterday for SETI so no way to verify that I know of.

edit: I do see there may be a problem with my setup after screwing with it...
6/18/2009 2:22:12 PM SETI@home [error] No app version for result: windows_intelx86 608 cuda
6/18/2009 2:22:12 PM SETI@home [error] No app version for result: windows_intelx86 608 cuda

6/18/2009 2:22:12 PM GPUGRID [error] No app version for result: windows_intelx86 664 cuda
6/18/2009 2:22:12 PM GPUGRID [error] No app version for result: windows_intelx86 664 cuda

Any recommendations? Maybe it's the optimizations somehow or custom app_info.xml?

Nvidia drivers are pretty recent. Within the last month I think 6.14.11.8250 but can't remember how to decipher that into Nvidia's driver version.

Edit: Again: Ok maybe it has to do with me trying to attach to the project via RDP. I notice dxdiag doesn't want to give me the driver version via rdp. This thing is really giving me hell.

Cuda wont work with RDP. That's your problem.

What method of remote controlling the machine is supported? I'm thinking I probably broke it by restarting boinc via rdp. Once I have it going maybe it will stay going even if I remote in.

I don't ever recall having this problem before and I've been using BOINC and RDP for a long while, but not necessarily CUDA apps. Guess I'll have to try a few things. Even using RDP to directly control the console doesn't allow them to run.

The second you log onto a system with RDP it loads its own drivers which dont support cuda. There is no way around that except finding some other program which works.
You can reboot the cuda machine after you've accessed it via rdp to get it to run again but every time you log in it will dump all cuda tasks.

Bob

I confirm Windows 7 Ultimate and 185.85 and Boinc 6.6.36 does not see CUDA device....
See THIS movie at 6:10....
____________
POLISH NATIONAL TEAM - Join! Crunch! Win!

Ochadd, try VNC instead, it's been reported to work. BOINC without CUDA and RDP is fine, as it does not depend on the video driver. Your driver is 182.50, which is fine. This

6/18/2009 2:22:12 PM GPUGRID [error] No app version for result: windows_intelx86 664 cuda

tells us something is wrong with your app_info. It looks for some alternative GPU-Grid app, which you can not have. Did you place an app_info into the GPU-Grid folder? Remove it an try again. Otherwise.. might help to post the contents of your app_info.

MrS