Hi,
if this Problem was already analysed in the deepness of this forum, maybe we should open a easier visualizable thread like this.

# Using CUDA device 0
Cuda error in file 'deviceQuery.cu' in line 59 : initialization error.

This error occured after more times of Remotedesktop usage. But first since the beginning a new workunit.
Maybe it's the similar issue like the Folding@home Remotedesktop issue.

I think this is caused by the display driver which is loaded at the time the remotedesktop is initialized.
If the Workunit is finished it is leaving the CUDA-Driver, starting a new WU, where the acemd-application can not longer allocate the CUDA ISA.
Maybe it will caused by useraccount-change?

After logging on via VNC, which is using and reloading the nvidia display driver, plus a boinc restart, the problem is gone. I killed 4 WU's in a short time, and there where no computation errors until now, except of an electrical power outage.

Any verifications?

You can not run windows remote desktop when running Folding@Home GPU. I would expect the same to be true of BOINC GPU. Microsoft replaces the video card driver with its own "virtual driver" which breaks the client -> GPU connection.

Thats just what raptOr wanted to say.

Some crunchers sure are not aware of that fact and get the "Cuda error in file 'deviceQuery.cu' in line 59 : initialization error."

You can not run windows remote desktop when running Folding@Home GPU. I would expect the same to be true of BOINC GPU. Microsoft replaces the video card driver with its own "virtual driver" which breaks the client -> GPU connection.

would programs like logmein do the same thing? They use a secondary video driver...

would programs like logmein do the same thing? They use a secondary video driver...