Questions and Answers :
Win7 Open CL - Not using GPU if not logged on
Message board moderation
Joined: 12 Dec 08
I currently run 7 machines to do my crunching for SETI. The one machine I am having issues with is my Win7 machine.
It currently has an H81 M/B running the on-board Intel GPU + an ASUS GT210 GPU.
If I setup BOINC/SETI on this machine in non-protected mode both GPU's will not do any work until I log onto the machine. If I logon to the machine it gets work for both GPU's and crunches away happily.
If I setup the machine in protected-mode so that the BOINC client starts without having to logon to the machine neither of the GPU's do any work. It doesnt matter whether I logon to the machine or not.
Would this have to do with the way Open CL starts? I am thinking that OPEN CL will only work when I logon to the machine.
I am asking this as I have 5 machines grouped together in the cupboard without a monitor/KB/Mouse and I would like to take advantage of the extra power the GPU's bring to the table. Currently this particular machine is sitting on my work desk and I want to put it back into the cupboard with the other four.
Any insight would be helpful.
"I know I am insignificant...Just look how many stars their are...!"
Joined: 9 Apr 02
I assume by "protected mode" you are actually referring to the Service Install. Please read the text on the installer window:
Joined: 9 Jun 99
If I setup BOINC/SETI on this machine in non-protected mode both GPU's will not do any work until I log onto the machine.
Additionally, this is normal as well. Only services run when no one is logged in, normal programs do not.
As to the why on that GPUs don't do work when BOINC is installed as a service, that's all down to drivers. When BOINC is installed as a service, it runs under a limited privilege account. This account does not have access to the videocard drivers, which run under the user's account. And so BOINC will not be able to read that these drivers are installed, thus is not able to detect any GPU.
BOINC runs the programs also from a sandboxed directory, meaning that the privileged account can only read from, write to and execute programs in this directory, and therefore it and possible programs are not allowed to search specific directories on the system to see if certain drivers are there.
This is a security measure Microsoft thought up, so if it needs to change it's up to MS, not up to BOINC to fix that.
©2023 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.