PC crashing overnight with v8.4.9; didn't with v7 client.

[Jeff7]

I'm pretty sure I haven't got overheating issues or anything like that. The system's not overclocked, and the CPU and GPU are pretty well-cooled. I had been running v7 for years, but it was prone to getting "stuck," with work slots either unable to download or unable to upload. I'd have to delete the stuck CPU or GPU slot and recreate it in order to clear it up. The system's also able to run the game Satisfactory without issue, which puts a fairly significant load on the entire PC.
So I wanted to try out the v8 client to see if that would deal with the issue of sticking work units.

Now whenever I leave it running overnight I find that the computer has rebooted at some point overnight. Not an issue with v7. I could easily have weeks of uptime with that. Now I can't seem to get even a day.
Windows Event Viewer gives nothing of value. There's a brief pause of logging, and then there's some things like, "Kernel-General: "The operating system started at system time..." and "The previous system shutdown at <time/date> was unexpected." It's as if the system dead-locked and rebooted, without even the ability to write out an event. Does Folding@Home itself have a logfile that might be useful?
v8.4.9 is the only v8 client I've tried, so I can't say if this problem would have started with 8.4.9 or not.
I have Folding@Home set to only use half of my available CPU cores.

Ryzen 9 5950
Asrock X570 Extreme4
Geforce GTX 1660 Super
96GB DDR4
Windows 10 Pro

[muziqaz]

FAHClient variation will not cause your computer to crash.
FAH will not be able to tell you what's wrong with your system stability in it's logs.
Please use 3rd party stability software to determine what is unstable on your system.
The only thing FAH can tell you, what hardware caused the crash, if you fold on GPU only and PC crashes, then your GPU is unstable. If you fold on CPU only and PC crashes, CPU is unstable. If you fold on both, finish work on one device and try each of them separately to see which one is causing the crashes.