Computer goes blank, won't revive-cold reboot required

[MeeLee]

From my experience, folding or crunching WUs on GPUs is the best thing.
Feed that GPU with an Intel CPU, and you got a pretty solid performer.
Perhaps not 100% perfect, but many of my systems ran for months without intervention.
On AMD CPUs, especially Ryzen CPUs, I've had to hard reset the PCs from once a month, to once a day. Most of them would run roughly 1 week fine, before needing resetting.
especially the Ryzen CPUs with many cores (like the 8, 10, 12 or 16 core CPUs).

[gunnarre]

I've got a couple of 6-core AMD processors - Ryzen 5 3600 and Ryzen 5 5600G - feeding work to a couple an Nvidia GPU each. It works just fine, and sometimes they are used for CPU folding as well (when it's cold and power is cheap). The 5600 G seemed to be unstable at first, but it turned out to be an OS related issue. They're running Linux Mint and Debian, respectively.

[hrsetrdr]

Well I haven't as of yet determined the cause of the un-wakable display, but I can say with a degree of certainty that the folding progress continues uninterrupted. I'm looking at my PPD, and my GTX 1080 and GTX 1050 mobile GPUs alone are just not putting out the 3.7M PPD showing up on EOC.

[Neil-B]

Long Shot - Try switching from displayport/hdmi to the other if you can ... I have had issues in the past with certain monitors not reconnecting after monitor sleeping (not with FaH but with other programs) ... yours could possibly be some similar issue - machine was working fine but screen would not reconnect - in my case it was the combination of displayport and the particular monitor I was using.

[hrsetrdr]

Long Shot - Try switching from displayport/hdmi to the other if you can ... I have had issues in the past with certain monitors not reconnecting after monitor sleeping (not with FaH but with other programs) ... yours could possibly be some similar issue - machine was working fine but screen would not reconnect - in my case it was the combination of displayport and the particular monitor I was using.

Interesting idea, I'd have to get a display port adapter to test. I'm planning to migrate this RTX 2060 to my new build when my new RTX 3060 arrives next week. That should put this issue to rest, although I'd still like to answer the unwakable display question, as I've run into this in the distant past, around the beginning of the FAH v7 client, IIRC.

[bollix47]

Just as a test, have you tried disabling Monitor sleep and just turn off the monitor by using the power switch when you're not using the monitor?
When you turn it back on is it frozen?

[hrsetrdr]

Just as a test, have you tried disabling Monitor sleep and just turn off the monitor by using the power switch when you're not using the monitor?
When you turn it back on is it frozen?

Yes, that's what I've been doing. Strangely, there's no consistency, it would go a couple days without problem, then do the "un-wakable" blank thing a couple times.
A couple hours ago it blanked again, PSU didn't want to turn back on, so I pulled the RTX 2060 out of the machine and put it in my new build, which I intended to do this weekend anyway. The system in question is an old AM3 machine, it's getting retired from folding service, maybe do some light office duties before it eventually goes off to e-waste.