I was in the middle of playing Diablo IV when my system crashed without a blue screen—it just froze for a few seconds and then restarted. I've been gaming for a while, so this is a new issue for me. I'm running Windows 11 Home with the following specs:
- Motherboard: ASUS ROG Maximus XII Hero Z490
- CPU: Core i7 10700K
- GPU: 5090 FE (new hardware, other components are older)
- RAM: G.SKILL Trident Z RGB Series 32GB (2x16GB) 3600MT/s
- BIOS Version: American Megatrends Inc. 1003, 11/30/2020
All my drivers are up to date, and I've run systems checks like sfc /scannow and dism. I found a BugCheck error, which I believe usually indicates a hardware issue, but I'm unsure how to interpret the dump file to figure out what went wrong. I also found this Event Viewer error:
"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff83028b19d028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:WINDOWSMinidump50825-14468-01.dmp. Report Id: cc446d8c-57dd-423c-903a-87a60f221f81."
I really hope I don't have to reinstall Windows!
3 Answers
To analyze BugCheck errors properly, you'll need to look at the dump files created during the crash. Just open File Explorer and navigate to C:WindowsMinidump. If you find any dump files there, zip them up and upload them to a file-sharing site like mediafire or catbox.moe for others to examine. If you only have one dump file or none, you might be limited in what you can analyze. To improve the situation, follow guides to set your system to create a Small Memory Dump, which will save useful crash data without overwriting past dumps.
Thanks for the advice! I’ll update the BIOS and check for those dump files. Fingers crossed it does the trick!
First things first, you need to update your BIOS—you’re several versions behind. The 124 error you're encountering indicates a hardware issue. If you can update the BIOS to the latest version (which should be 3201 or higher), that could resolve some underlying problems. Once that's done, recheck if the crash issue persists. Also, if you need to pinpoint what triggered the BugCheck, research the WHEA_UNCORRECTABLE_ERROR; the error parameters can help isolate the hardware fault.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures