If this is similar to the stuck tasks I 'used to' get, then there'll be no error messages, etc.. at all. It just sticks at zero progress. Restarting Boinc (service or boinc itself depending on installation type) should get them going normally. If so, then restarting boinc is the only way I found to make them 'un-stick' and happens to me every couple of days or so. To stop from having to manually handle this, I installed the VBScript from the other thread here, then, as I run as a service, made the modification described later in that thread to restart the service instead of terminating the tasks. I haven't had to do any manual intervention since, but noticed it automatically restarts boinc every couple of days or so. I was not able to pin the 'sticky tasks' to any particular angle range or other factor that I could determine.Jason
His picture shows that CUDA app still running ~4% CPU is normal ...
1) How you could know GPU is working - you already used right method - looked at GPU temp.If temp = idle temp - GPU idle, if temp increased - GPU working hard.2) If you have no work from SETI then you probably doing another non-CUDA enabled projects. So your CPU will do 5 CPU tasks and no CUDA ones.Try to get new tasks for SETI MultiBeam.