In the last week or two I've started having a really weird Windows crash, sometimes when I'm using the machine, always over night when my session is locked with no foreground apps, F@H being allowed to run full tilt. This same behavior has happened during VR (Star Wars: Squadrons), but in that case it is a consistently repeatable crash and is also a full system restart, as opposed to what happens when the computer is idling, less F@H, is running overnight.
When actively using my computer I generally set Folding to "On Idle" and then turn that option off whenever I'm done. Even if I don't, it kicks into high gear when I lock my computer of course. Over the last week or so when I come back to my computer it's asleep, and when I turn it on and put in my pin I'm logged in. Nothing had been running since some point overnight, not my ever-present processes (Steam, GoG), not F@H, nothing.
Thinking Blue Screens were happening I turned 'Automatically restart' in Windows settings off, but that's not the case, I've never seen one. Windows boots fast nowadays via UEFI and all that, but I *never* see that screen, I don't think my system is rebooting. So it seems to me like Windows is crashing pretty badly, so bad that it ends my session, but isn't a Blue Screen, it isn't entirely fatal. My Windows process knowledge is lacking, but in Linux terms I would call this a "Window Server" or "Desktop Environment" crash.
When these crashes happen the display goes black, and even the power light on my system goes out. It's as if it is forced into some sort of sleep state, the power down behavior is particularly weird considering that I believe Windows never actually goes away. But this is more than a sleep / hibernate due to the nature of my account getting logged out.
In the event viewer there are some errors under 'Application' that I raise my eye at. Fahcore is listed in all of them, and strangely Rocket League is listed too. I just finished playing it but the crash has never kicked me out mid-RL. As previously stated it has happened mid-Star Wars: Squadrons, but consistently and I don't believe the behavior to be related.
I see a cluster of 5 of these errors pretty often in the "Application" logs:
Code: Select all
Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0
Problem signature:
P1: FahCore_a7.exe
P2: 0.0.0.0
P3: 5dde687c
P4: FahCore_a7.exe
P5: 0.0.0.0
P6: 5dde687c
P7: 0000000000f161e7
P8: c0000409
P9: 0000000000000005
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8FEF.tmp.WERInternalMetadata.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FahCore_a7.exe_d3a07ecd28195878f6fcb1b80c5a41937fbf981_b9fa5d94_9125c930-d9b7-4f61-ba88-e96a417bb390
Analysis symbol:
Rechecking for solution: 0
Report Id: bdf19f7c-7879-4090-98ca-78e8e25d6143
Report Status: 4196
Hashed bucket:
Cab Guid: 0
I'm at a bit of a loss on what else to look at. What I'm going to do tonight is quit F@H and see if I still get the 'logged out' behavior overnight, or just a normal sleep, wake, unlock behavior. If F@H is catalyzing these crashes / bad behavior, any suggestions of what to do?