Question Computer crashing twice a day for 10 days in a row

[Tinchote]

Desktop computer

• ASUS TUF Gaming X570-Plus (Wi-Fi), BIOS 4802
• AMD Ryzen 9 5900X
• 32GB DDR4 PC4-17000
• RX6600
• SSD Samsung 860 EVO 1TB
• Windows 11 Pro 23H2 Build 22631.3296

Since ten days ago, computer started crashing about twice day, most often when its idle. Things I've tried, without any success:

• Dusted and vaccumed all fans
• Replaced all RAM
• Replaced video card
• Updated drivers
• Uninstalled latest Windows updates
• Checked SMART status with CrystalDiskInfo ("all good")
• Checked the crash dumps, I see no pattern:
  

I own another computer with the same specs. Checking with HWInfo64, the only difference I noted is that the crashing computer shows a higher CPU Package temp. This temp is at 66C now (with a peak of 85C), while on the healthy computer it shows 56C with a peak of 72C. I don't know if this is relevant at all.

At this state I don't know what else to try. Should I replace the motherboard? Is there anything else I should check?

 

[Ralston18]

Look in Reliability History/Monitor.

Much more end user friendly and the timeline format may reveal some pattern with respect to the crashes.

Another place to look is Event Viewer. However Event Viewer requires more time and effort to navigate and to understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

One immediate thought is that "idle" time is invoking some power/screen saver that may be buggy or corrupted.

Disable all such settings and determine if the crashes continue.

If so then try "dism" and "sfc /scannow" to find and fix problems.

FYI:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Post accordingly.

 

[Tinchote]

Thanks. I've used the reliability monitor, but not sure what I should get from it? It only seems to show me when the crashes happened.

I'm also not sure what I could get from the Event Viewer. The last event after each crash is a Distributed COM warning, but there are hundreds of those, many at times that have nothing to do with a crash. But the crash dumps shows the crashes happening at different modules, and with very different stack traces.

As for the idle, that seems to be a red herring, as I had the system just crash when I was typing this.

Both DISM and SFC report no problems.