Deleted GPU Slots Return After Reboot

[AlanD2]

I'm running 7.6.21 on Windows 10. I use the Client Advanced Control => Configure => Slots to delete 2 GPU slots and set the CPU slot to use 6 threads.

After a reboot, the CPU slot is still using 6 threads, but both GPU slots are back, which leads to the GPU overheating.

I searched and found a similar problem back in 2014, but I'm assuming a lot has changed since then.

[Neil-B]

Pause the slots and add the pause on start = true flag

[bruce]

The client's CPU setting allows you to overcommit the number of CPUs. If you configure it for -1, it will choose the recommended number, which in this case, probably isn't what you want since there's no point in allocating a CPU thread for each GPU if you're not going to be running the GPU(s).

Have you tried setting an extra client option to gpu=false in FAHControl's EXPERT tab?

[AlanD2]

I used bruce's suggestion. It worked perfectly!

Definitely not something I would have figured out on my own (I'm certainly no expert!).

Thanks, bruce!

If somebody can close this problem or mark in solved, I would appreciate it.

P.S. I always allocate 6 of my processor's 8 threads to F@H. I've done this for years without any problems.

[bruce]

Thanks for the feedback, AlanD2. My suggestion was based on a hunch --- I had not had the opportunity to test it yet.

For everybody who has been recommending the pause-on-start method, we can now recommend turning off the GPU reconfiguration step that runs on every client restart. It will only create a new problem if somebody adds or replaces one GPU with another type.