You're right that the System log is showing WHAE hardware errors, like this one...
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 20/02/2024 01:34:35
Event ID: 1
Task Category: None
Level: Error
Keywords: WHEA Error Event Logs
User: LOCAL SERVICE
Computer: Lars_PC
Description:
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.
That doesn't tell you much, as you've noticed.
However, elsewhere in your System log I came across two BSODs, yet no dumps were uploaded. The bugcheck code was 0x101 - CLOCK_WATCHDOG_TIMEOUT...
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 20/02/2024 01:34:33
Event ID: 1001
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: Lars_PC
Description:
The description for Event ID 1001 from source Microsoft-Windows-WER-SystemErrorReporting cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
0x00000101 (0x0000000000000006, 0x0000000000000000, 0xfffff80037afb180, 0x0000000000000000) <==== This is the 0x101 bugcheck
C:\WINDOWS\Minidump\022024-30171-01.dmp <==== This is the minidump that was written and which wasn't uploaded
0b646711-59e7-4779-9ff5-c912ab6ecf92
The message resource is present but the message was not found in the message table
A minidump was written (022024-30171-01.dmp) but it was not in the upload. Are you running any kind of disk cleanup tool? These will often delete dump files. As it happens, with this bugcheck, we need the full kernel dump to fully debug the problem, that is the file C:\Windows\Memory.dmp so please upload that dump file (it will be large).
The bad news for you is that the 0x101 bugcheck is most usually a CPU error. It can, in rare cases, be caused by a rogue driver and that's why we need the kernel dump. Since the BSOD only seems to happen when playing one specific game it may be that this is one of those rare, driver-caused, cases. Without the kernel dump we cannot tell.
Edited by ubuysa, 20 February 2024 - 10:51 AM.