STOP 0x00000101
CLOCK_WATCHDOG_TIMEOUT
One of your CPU's cores stopped responding to the others. This is usually a hardware-side problem: an unstable overclock or undervolt, insufficient power, overheating, or a genuinely faulty CPU — with BIOS/microcode bugs as the software exception.
Worth knowing: This code leans hardware. Software fixes are worth a try, but recurring 0x101 with stock settings and a current BIOS usually means the CPU, board or PSU needs attention.
Likely causes, most common first
- An unstable CPU overclock or undervolt
- Overheating or a failing CPU cooler
- An outdated BIOS / CPU microcode
- A degrading or faulty CPU, or failing power delivery (PSU/VRM)
How to fix it
1. Return the CPU to stock settings moderate
- In the BIOS, load optimized defaults (this clears overclocks, undervolts and XMP/EXPO).
- Use the PC normally and see if the crashes stop.
- If they do and you want your tuning back, reapply it in small steps.
2. Update the BIOS and check cooling moderate
- Install the newest BIOS from your motherboard or PC maker's support page — microcode fixes for exactly this crash ship in BIOS updates.
- Check CPU temperatures with the maker's tool or HWMonitor; clean dust and verify the cooler is seated if it runs hot.
- If you have an Intel 13th/14th-gen K-series CPU with recurring 0x101/0x124 crashes, make sure you're on the latest BIOS (degradation-mitigation microcode) and consider a warranty claim.
The four parameters on the blue screen
Windows shows four hex numbers with this stop code. Here's what each means — our analyzer decodes them automatically from your dump file.
| Parameter 1 | Timeout interval |
| Parameter 2 | Reserved |
| Parameter 3 | The processor block of the stuck core |
| Parameter 4 | Index of the stuck core |
Got a crash dump? Get your verdict in seconds
Drop the .dmp file into our analyzer — it runs entirely in your browser. No upload, no size limit, no account.
Analyze my dump file →