The system abruptly stopped unexpectedly—no idea how to proceed?
The system abruptly stopped unexpectedly—no idea how to proceed?
Great! I'm glad to see these BIOS hard-reset instructions. I wasn't aware of them before. I'll try it after the next BSOD.
I regularly use Memtest86, Windows Memory diagnostics, Intel diagnostics, and any other tools I find useful!
Thanks! I'll update the thread in a few days or after another BSOD.
From what I've observed repeatedly, I suggest performing a full BIOS reset and then a clean Windows installation. Avoid installing Armory Crate at all costs. You won't need it because the manufacturer drivers can be downloaded manually from your motherboard's support page. I'm unsure how many discussions I've had about this issue, but many users reported problems like BSODs, freezing, errors, and overall poor performance when Armory Crate was involved. The same applies to most bundled motherboard utilities, no matter the manufacturer. It's best to steer clear of them altogether.
The recent 0x3B BSOD appears to be an unusual occurrence in your provided memory dumps, with other typical reasons also present. If your RAM has successfully completed two Memtest86 tests, it’s likely still functioning properly at this stage.
Turning off C States is a frequent solution for the 0x101 BSOD. It looks like certain CPUs may delay exiting the low-power mode, leading to missed clock synchronisation interrupts and resulting in this error. In all three dumps you shared, processor #5 failed to receive the clock synchronisation interrupt, making it a likely candidate for the issue. This pattern has been observed before with AMD chips, though less often with Intel.
Disabling C States is effective at preventing processors from entering low-power states, albeit with slightly higher power usage. If this is the root cause of your 0x101 BSODs, there may be limited alternatives. Also note that a malfunctioning driver can trigger a similar BSOD, so it’s not always the CPU itself.
If you encounter more CLOCK_WATCHDOG_TIMEOUT BSODs, please promptly move the C:\Windows\Memory.dmp file to a temporary location to avoid overwriting during subsequent errors. Uploading multiple kernel dumps afterward will help clarify the situation.
Just to inform you, the CPU unit had some issues. It seemed strange when I performed a stress test using Intel's XTU with the old CPU—no problems occurred, but the CPU usage stayed between 1 and 4 percent. The benchmark in XTU worked fine, yet the test caused constant thermal throttling within two seconds from start.
The new CPU handled the stress tests without any trouble, and the thermal readings improved significantly, mostly staying around 80-90 degrees. There were a few instances of thermal throttling at the end of the test, but only briefly to lower the temperature.
Additionally, the benchmark ran smoothly with a maximum temperature of 88 degrees. Hope you're all doing well, and thank you very much for your support!