- Software and digital services
- Operating system
CLOCK_WATCHDOG_TIMEOUT
CLOCK_WATCHDOG_TIMEOUT (0x101) on Windows: a secondary processor stops responding
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
One of the PC's processors did not service the expected clock interrupt in time and Windows stopped. Start by removing new hardware, checking Device Manager and installing pending updates.
Safety first
Stop and check this first
- A code that mentions a processor does not prove the CPU is faulty: it says the processor did not respond, not why. Ask for dump analysis before agreeing to a CPU or motherboard swap.
Safe checks you can perform
- Hardware added before the crash
- Device Manager and updates
- Free space and restore
Leave these tasks to a qualified professional
- Do not attempt this professional task: Analyse processor state in the dump
- Do not attempt this professional task: BIOS, firmware and hardware tests
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Analyse processor state in the dump
What they doIT support uses !analyze, the stack (k), !pcr, !prcb and !irql on the processor named in parameter 4.
They must show youthe output with the hung processor and the code running.
In writingwhich module was identified and what was changed.
BIOS, firmware and hardware tests
What they doThey check BIOS and firmware are current and run the relevant hardware and memory tests.
They must show youinstalled versions and the test report.
In writingthe result and, if a part is replaced, its reference and reason.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Hardware added before the crash
- Who:
- you, with the PC off.
- How:
- remove the external hardware you connected before the first blue screen and start again.
- Result that matters:
- whether the error goes away without it.
- If it does:
- that device or its driver is the likely source.
- If not:
- reconnect it and continue.
- Evidence to keep:
- what you removed and the result.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Device Manager and updates
- Who:
- you.
- How:
- open Device Manager, look for devices with an exclamation mark and choose Update driver; then go to Settings, Windows Update, Check for updates.
- Result that matters:
- whether any device was flagged or updates were pending.
- If so and the error stops after updating:
- the driver or update resolved the hang.
- If nothing was pending:
- go to restore or to IT support.
- Evidence to keep:
- dated list of drivers and updates installed.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Free space and restore
- Who:
- you.
- How:
- check the system drive has 10% to 15% free and, if the error began after a change, use an earlier system restore point.
- Result that matters:
- whether the error stops after freeing space or restoring.
- If it stops:
- the undone change was the cause.
- If not:
- keep the dumps for IT support.
- Evidence to keep:
- free space before and after and the date of the restore point.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x00000101
- 0x101
- CLOCK WATCHDOG TIMEOUT
- STOP 0x00000101
- stop code CLOCK_WATCHDOG_TIMEOUT
What it means
Microsoft defines 0x00000101 as an expected clock interrupt on a secondary processor, in a multiprocessor system, not arriving within the allocated interval. That processor is not processing interrupts, typically because it is unresponsive or deadlocked. Parameter 4 gives the index of the hung processor. Microsoft does not tie the code to a part: finding the code that blocks progress requires analysing the dump in the debugger.
Warnings and stop conditions
- Mediumeditorial warning
A code that mentions a processor does not prove the CPU is faulty: it says the processor did not respond, not why. Ask for dump analysis before agreeing to a CPU or motherboard swap.
Evidence: Bug Check 0x101 CLOCK_WATCHDOG_TIMEOUT
Symptoms and causes
Probable causes · in order
- Code blocking a processorPossible
Microsoft steers the investigation to finding which code prevents forward execution; it may be a driver. Only the dump identifies it.
Evidence: Bug Check 0x101 CLOCK_WATCHDOG_TIMEOUT
- New hardware or outdated firmwarePossible
Microsoft's general guidance is to remove new hardware and keep BIOS and firmware current; if the crash stops after doing so, that was the source.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Virtual technician
Does CLOCK_WATCHDOG_TIMEOUT still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Bug Check 0x101 CLOCK_WATCHDOG_TIMEOUT
Microsoft · 2026 · official_doc
- 2
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 3
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
Was this entry useful?