said by Neil A in another thread-

I access one of my home crunching computers a lot by MS Terminal Services. I have a feeling that if I access the computer remotely from my work laptop, that when it finishes completing the current work unit on my CPU (8800GT) that the next one doesn't start correctly and errors out. IF it connect to the computer directly at its console again before the work unit completes, then the next work unit starts. This is a theory at this point only.

I can only guess that since I have connected from a laptop that doesn't have a valid GPU to process this type of work, and if I remain connected to it, that when the current WU completes and the next WU starts, it sees the GPU card on my laptop instead and errs out?

This is only a guess on my part, and I'm still trying to prove this theory. Does anybody else access their crunching home computer a lot via terminal services and see this behavior?

Does anybody know what should happen to a crunching computer if you access it remotely from a non-compatible laptop via terminal services?

I looked in the NVIDIA CUDA forum regarding various posts and found one that explained that when you terminal service from one non-cuda PC to a CUDA pc running GPU work and remain connected when the current task ends and tries to start a new one, it will fail. This is a result of the terminal services session setting itself up with a non cuda driver/configuration so GPU work fails. Seems silly to me when GPU capable graphics cards on the CUDA capable PC, but this is the way the application works.

A suggestion was to use VNC or similar alternate product to perform remote connections to CUDA pc's. I'll look for the post again on the NVIDIA CUDA forum and post it here for those who may be interested.

Here it is: link

Neil
____________
Crunching for the benefit of humanity and in memory of my dad and other family members.

thanks for the replies. MrS, now that I think about it, it probably was Seti wu's taking a dump while in a RDP session. Neil A., I would be using tightVNC, save for it doesn't work with XP64. I believe the latest pay VNC version does. Thanks for the link, I'll check it out.

MrS, Neil, etc:

NVidia driver 181.22 released about a week ago seems to have cured this problem. Our driver guy has confirmed the bug in previous nvidia drivers, has seen it cleared up with this latest version. I installed it alongside BOINC 6.5.0, might be a bit early to tell, but (knock on wood) I'm running RDP without issues now, even with seti gpu work.