The system abruptly stopped unexpectedly—no idea how to proceed?
The system abruptly stopped unexpectedly—no idea how to proceed?
Hello,
I’m experiencing some issues with my computer over the past few days (it was purchased in April this year). To give you a clear picture, the problem started after a game session with my brother. The screen suddenly froze and a severe BSOD appeared. After restarting, it would happen again shortly after. I went back into the game after a short wait, but the issue persisted.
I followed several troubleshooting steps: I reinstalled Windows, used Armoury Crate from ASUS to install the latest drivers, and even performed a clean installation of Windows with driver updates. Still, the BSOD returned each time. Eventually, I reinstalled the PC again.
I paid more attention to the process, letting Windows update itself and then updating drivers one by one. After installing the newest drivers, everything functioned properly except for a strange reading from one of the memory sticks (DRAM 0 slot) showing a temperature of 0.5 degrees in the BIOS. I thought it might be related to the RAM contact, so I swapped the sticks and checked if the temperature changed. It didn’t. I then ran Prime95 for three hours without any crashes.
Next, I tried debugging tools like Event Viewer and searched online. I discovered that the HyperX Cloud 7.1 USB sound card was causing problems, so I updated its firmware. After that, I continued investigating and found two types of BSOD errors: CLOCK_WATCHDOG_TIMEOUT and MACHINE_CHECK_EXCEPTION. I checked for RAM issues and ran Memtest86 on both memory modules—no errors detected. The DRAM 1 slot still showed an unusual temperature, but it was normal afterward.
I have the latest drivers installed and updates applied. Everything seems fine except for that one memory stick issue. I’m unsure what to do next. Help is needed. This PC has been perfect since purchase, but these last few days have been challenging.
HW INFO:
- MB: ASUS ROG STRIX B660-I GAMING WIFI
- CPU: Intel Core i5-13600KF
- RAM: Corsair 32GB KIT DDR5 5600MHz CL36 Vengeance
- SSD: Kingston KC3000 NVMe 2TB
- PSU: Corsair RM850 White (2021)
- Windows: Windows 11 Pro
TL;DR: My computer suddenly displays two kinds of BSOD errors. One is CLOCK_WATCHDOG_TIMEOUT and the other MACHINE_CHECK_EXCEPTION. A memory stick reported an abnormal temperature, but no overclocking was performed. All other components appear to be functioning normally.
I’ve reinstalled Windows twice, runned Prime95 stress tests, and done multiple Memtest86 runs—no crashes. I have the latest drivers and updates installed everywhere. I’ve consulted manufacturers and checked online resources.
I also saved dump files in a Google Drive folder.
If you’d like, I can provide those files for further analysis.
I understand it’s inconvenient, but I’m hoping you can assist me.
Welcome to the forums, newcomer!
Where did you obtain the installer for the OS? Did you set up the installation without internet access and manually add all the latest drivers via the elevated command prompt, such as right-clicking the installer and selecting Run as Administrator?
I'm currently lagging in updates. I'd update to version 2802 and then check if the problems persist.
Thanks for the reply! I changed the BIOS yesterday and experienced a BSOD twice. I concentrated on the CPU, Intel Diagnostics showed everything normal, and stress tests were fine. However, after some research, I found that for users with similar PC configurations and similar issues, disabling CPU C States Support in the BIOS helped. I'm currently testing the system. It's an unusual problem, but many 13600K(F)s seem to face it unexpectedly.
First things first; four of the dumps are (as you say) 0x101, CLOCK_WATCHDOG_TIMEOUT and these can only be fully analysed with the full kernel dump. Unfortunately there is only one of those recorded and it's always for the most recent BSOD, which isn't a 0x101 in your case. Sod's law of course!
If/when you get another 0x101 BSOD please copy the file C:\Windows\Memory.dmp to a temp folder somewhere to prevent it being overwritten by a subsequent BSOD. Then upload it to the cloud - it will be large.
The 0x101 BSOD is almost always a CPU issue, so if you're overclocking that K series CPU please remove it and run at stock frequencies until your problem is resolved. Same with your RAM, please disable XMP and run at stock frequencies. Any overclocking introduces instability, and 0x101 is the common excessive overclock BSOD (so too is the 0x9C, MACHINE_CHECK_EXCEPTION).
The latest dump is a 0x3B, SYSTEM_SERVICE_EXCEPTION which means that some sort of exception occurred whilst running in kernel mode. In the call stack you can see that virtual memory operations were in progress...
Code:
STACK_TEXT:
fffff086`a3fff490 fffff806`28749be4 nt!MiGetProtoPteAddress+0x38
fffff086`a3fff4e0 fffff806`2874ba2b nt!MiQueryAddressState+0x564
fffff086`a3fff700 fffff806`28bda75f nt!MiQueryAddressSpan+0x24b
fffff086`a3fff7c0 fffff806`28bda005 nt!MmQueryVirtualMemory+0x73f
fffff086`a3fff960 fffff806`288274e5 nt!NtQueryVirtualMemory+0x25
fffff086`a3fff9b0 00007ffb`43c0f854 nt!KiSystemServiceCopyEnd+0x25
00000039`95fffd58 00000000`00000000 0x00007ffb`43c0f854
The error occurred in the last call there (the top one)...
Code:
CONTEXT: ffffe001ddf7e900 -- (.cxr 0xffffe001ddf7e900)
rax=ffffcc8720a80b20 rbx=00000007ffaef9ee rcx=ffffcc8720a80aa0
rdx=ffffcc8721a44520 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8062874a948 rsp=fffff086a3fff490 rbp=fffff086a3fff5e0
r8=0000000000000004 r9=fffff086a3fff568 r10=00000007ffaebae0
r11=ffffcc8721a44568 r12=0000000000000004 r13=fffff43ffd77cf70
r14=fffff086a3fff568 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!MiGetProtoPteAddress+0x38:
fffff806`2874a948 f7413800000008 test dword ptr [rcx+38h],8000000h ds:002b:ffffcc87`20a80ad8=????????
Resetting default scope
You can see the failing instruction is a TEST instruction using the RCX register as a memory pointer. However, the resulting memory address is invalid (=????????) meaning that the memory location was either not allocated, was paged-out (which is not allowed since we're running at an elevated IRQL), or the RAM page was bad.
When you tested the RAM what tester did you use? If that 32GB kit is 2x16GB then try running on just one stick for a day or two (or until you get a BSOD) and then swap RAM sticks and run on just the other for a day or two (or until you get a BSOD). That is the 'gold standard' RAM test.
I really would like to see the kernel dump for the next 0x101 BSOD however...
I don't know if it's considered the "gold standard RAM test," but it remains a useful approach for identifying which memory stick might be the culprit, especially if the issue is rooted in physical memory problems. Should it be a configuration, firmware, or motherboard-related concern, these factors won't provide much clarity.
Regarding memory testing, although not entirely reliable, it's important to verify each stick by performing all 11 tests in full on Memtest86. If they pass every single pass, repeat the test together for another four passes. This process will require significant time if you decide to carry it out thoroughly.
Additionally, running advanced Windows memory diagnostics could be beneficial.
After updating the BIOS, consider performing a hard reset to eliminate any persistent settings. It's common for such issues to occur.
BIOS Hard Reset Steps
Turn off the device, power down the power supply, and disconnect the PSU cable from the wall or power source.
Remove the CMOS battery on the motherboard for three to five minutes. In some instances, you may need to take out the graphics card to access it.
While the battery is removed, keep pressing the case power button continuously for 15–30 seconds to drain any remaining charge in the CMOS circuit. Once the time is up, reinstall the battery, ensuring it's oriented correctly.
If you had to remove the graphics card, you can reinstall it afterward, but make sure to reconnect any connected power cables and display cable.
Reconnect the PSU power cable, turn it back on, and restart the system. It should show the POST screen with options for CMOS/BIOS setup. Enter the BIOS configuration, adjusting boot settings for Windows or legacy systems as needed.
Save your changes and exit. If the system successfully boots, proceed further—this may involve resetting hardware tables in the BIOS and configuring settings like Memory XMP, A-XMP, or D.O.C.P profiles, fan profiles, or other custom parameters that were lost during the reset.
In certain situations, after resetting the BIOS, it might be necessary to load default or optimal values to restore hardware tables properly in the boot manager.
It's also advisable to consider alternative displays if the issue involves a video signal problem. A different type of display, such as HDMI, may work better, especially if your system struggles with standard connections or lacks visual feedback during BIOS access.
If you're unable to enter the BIOS due to display issues, trying another monitor can be helpful. This is often a viable solution when display problems are present.
I value the thorough explanation you provided! I’m still unsure about fixing these .dmp files, so thank you for your assistance.
I tried using memtest86 (free) and noticed some missing tests in the free version. I performed two full tests per stick and one combined test. I also ran them on separate days—one with each stick—and still experienced BSODs, which was frustrating.
However, after disabling CPU C States Support in the BIOS, I no longer encountered BSODs. I completed several stress tests, including Counter Strike for two hours. Good luck! I hope this points to the problem. I’ve detailed more about it in earlier replies.
My next steps will be to upload the full Memory.dmp file if another BSOD occurs, so you can investigate further. Also, turn off XMP as recommended, and I’ll keep working on resolving it.