Looks like I have a problem loading AMD drivers on systems with multipole GPUs on risers.

Boinc does not see any GPUs and works only if I stop and restart it. Sometimes it works ok and sees all of them, other times none and I do a stop/start. At least it does not hang like GPUz.

GPU-z also has problems, I cannot configure GPU-z to start automatically with windows. Has to be started after windows has "stabilized" (for lack of a better word)

Read WiKi, there is a delay parameter in cc_config but it delays starting the projects, not the client
Read THIS over at WCG but I don't think that works on windows 10 as I recall a problem with GPUs and remote access when running boinc as a service.

It that still the case?

Also read this (last item)
https://www.thewindowsclub.com/set-delay-time-startup-programs-windows

QUOTE: If something runs as a service, just change it to delayed startup. If something runs from a startup group or registry key, just create a new scheduled task to start at login, set the delay to a minute or 2, and delete the original startup shortcut/run reg key. No need for more 3rd party bloat.

I think I can figure this out but was wondering if there is a walkthrough at the WiKi for boinc for something like the above.

[edit] want to mention that the client occasionally reports two times as many AMD GPUs as I actually have but I can fix this by editing that coproc_config file. This problem, counting drivers twice, really needs to be fixed. Maybe this is contributing to the problem even though I have "fixed" that config file so it cannot be re-written incorrectly.

[edit again]
Forgot to mention that I am not using BM but start boinc directly from the registry using

"D:\ProgramFiles\Boinc\boinc.exe" --detach --allow_remote_gui_rpc

Use Windows Task Manager to delay start any program.

If not figured out later, I will write a how to from my PC, am on my phone right now.

---

Sorry, Windows Task Scheduler.

Start Task Scheduler->Create Task

General: name BOINC
Security Options: When running the task, use the following user account *the account you normally use to run BOINC with*
Run only when user is logged on
Configure for: Windows N (your version)

Triggers
New
Begin the task: At startup
Delay task for: set a time, you can use presets but also state your own. Example given: 7 minutes.
Check 'Enabled'

Actions
New
Action: Start a program
Program/script: "D:\ProgramFiles\Boinc\boinc.exe" --detach --allow_remote_gui_rpc

And that should be it... OK/Save changes.

Thank Jord

Sill have problems but did make some progress

Unaccountably could not use my regular signing. I logged out and back in to make sure I had correct username / password as some time ago I used netplwiz to automate login.

Never got past the error "the account could not be used" or something like that. After poking and googling I used "administrators" with my password and was able to launch boinc.

Did not work, same problem. Tried 5 minutes then 7. I noticed I was using that old 7.12 as I forgot up restore to 7.14

Will do that in a bit.

I was watching the autologin and never saw the screen show the "cmd prompt" that is normal when running boinc.exe
Could this be a session problem? Maybe the GPUs cannot start properly but the CPU tasks work ok Could this be the "session 0" problem?

I set boinc to run after "log on" as I could not get the "at start" to use my account. After restore to 7.14 I will try again. I will also disable the autlogin and use a keyboard and monitor at the system instead of splashtop to access.

[edit] just when I thought things could not get any worse -- cannot uninstall 7.12.1 get error2503 "Called RunScript when not marked in progress" Just looked up that error - indicates a permission problem.

Will have to run revo uninstaller. Hope projects are not deleted.

Installed 7.14 and so far seems to be working. I did not lose any projects using revo uninstaller.

The uninstall got rid of the coproc file which I had set read-only but after putting in 7.14 and rebooting it was written out correctly for exactly 4 GPUs, not 8 like the previous.

All GPUs were recognized. if I have that problem again, I will enabled that task (in the task scheduler) and try again.