New
#21
No dump files again. I notice that there is only 9.5GB of free space on your paging file, are you allowing Windows to manage the paging file or do you have the values set manually? If the latter please allow Windows to manage the paging file. Crash dumps are written at the time of the event to the paging file, they are only moved to the minidump folder on the next boot.
In the System log there is only one WHEA error message...
However, this is immediately preceded by an informational message concerning the starting of the WLAN Extensibility Module (for your Intel Ax210 WiFi card, which I note you're not using)...Code:Event[782]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2023-04-11T13:14:26.3410000Z Event ID: 1 Task: N/A Level: Error Opcode: Info Keyword: WHEA Error Event Logs User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-31HHLHG Description: A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.
You can see that the WHEA occurs 0.172 seconds after the WLAN module is loaded. I have no idea whether the two events are connected though.Code:Event[781]: Log Name: System Source: Microsoft-Windows-WLAN-AutoConfig Date: 2023-04-11T13:14:26.1690000Z Event ID: 10001 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-31HHLHG Description: WLAN Extensibility Module has successfully started. Module Path: C:\Windows\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_9ba233fff172b953\IntelIHVRouter10.dll
I did ask earlier if you could boot into Safe Mode and you said that you don't think it's ever failed in Safe Mode. Can we confirm that please? Please boot into Safe Mode with networking and run with it in Safe Mode for as long as you can. In Safe Mode only Windows drivers are loaded so this is the easiest way to see whether your problem is with a third-party driver (because none of them are loaded).
Many of your devices will not have full functionality, some may not work at all. Your display for example, will be at a very low resolution because you'll be using the Windows basic display driver. However, despite these difficulties it is extremely useful for you to run in Safe Mode for long enough for you to have normally had a BSOD. Ideally you want to be running for twice the time it normally takes to BSOD, you want to give it every opportunity to BSOD in Safe Mode.
If you can be absolutely certain that it does not BSOD in Safe Mode then we can be reasonably confident that your problem is related to a third-party driver - that will be VERY important information - so please persevere with Safe Mode for as long as you can stand it.