Got an error here and I think I've found what triggers it as well. I've got BOINC set to run only when the machine is inactive. Now before I didn't set windows to go to the login screen when coming out of screensaver mode (which come on for 5 minutes to show the BOINC graphics then sleeps the monitor), and everything would work just fine. As soon as I told windows to go to the login screen after screensaver, BOINC now fails to properly suspend computation.

It will say "Computation suspended", but a look in the tasks list in BOINC shows it to be still processing away. Oddly enough, the computer is being substantially slowed down by this, but the windows task manager doesn't show any CPU use out of the ordinary, but as soon as the BOINC process is killed, everything goes back to normal.

Everything runs fine up until screensaver mode starts. It's not an option for me to not have the computer lock after screensaver mode, so this is a killer error for me.

Which BOINC version?
Which project?
Are you running CUDA on that project?

---

-6.4.5
-SETI@Home
-No idea, whatever the default setting is.

The default setting is to run Seti Enhanced, Astropulse and if you have a CUDA capable Nvidia video card, CUDA.

The latter will not play nice on BOINC 6.4.5 when you suspend it in any way, as the task will stay in the video memory. It's even possible that it continues crunching as 6.4.5 was sort of a haste-job. CUDA will completely saturate the video card its GPU, while taking up at least 200MB of its VRAM.

You can recognize in BOINC Manager that you are running CUDA, by going BM->Advanced view->Tasks tab. In the Status column it should show CUDA + 0.03 CPU (the number can differ). Tasks done by CUDA on Seti run with the 6.08 application. Tasks solely done on the CPU are 6.03, Astropulse is by now 5.03

Please check all of that first. If you do not want to do certain Seti calculations, you can disable them in the Project Preferences. Any work still on the computer will continue to be crunched, though.

---

Hey, that was the problem, explains why things were being sluggish with no CPU use too! Thanks.