CLOCK_WATCHDOG_TIMEOUT
Code: 0x101 (257)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x0101 (257)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x0101 (257)
Parameters
| Parameter | Description |
|---|---|
| 1 | Clock interrupt time-out interval, in nominal clock ticks. |
| 2 | 0 |
| 3 | The address of the processor control block (PRCB) for the unresponsive processor. |
| 4 | The index of the hung processor. |
Description
The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This bug check indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, wasn't received within the allocated interval.
Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
Cause
The specified processor isn't processing interrupts. Typically, this bug check occurs when the processor is nonresponsive or is deadlocked.
Resolution
The following debugger commands can be used to investigate the processor states, IRQL level, and code that is running, to attempt to determine which piece of code is not allowing forward execution.
k, kb, kc, kd, kp, kP, kv (Display Stack Backtrace)
See Also
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| DevicePairing.dll | 0x101 | 7 | There are %1!d! file(s) open by %2!d! user(s) connected to %3. If you stop sharing %3, the files will close, which may cause these users to lose data. Do you want to continue? |
| ESENT.dll | 0x101 | 11 | %1 (%2) %3The internal database copy (for seeding or analysis purposes) of database %4 during recovery has been suspended. It took %5 seconds to wait for client to close the backup context. |
| EventCreate.exe | 0x101 | 78.11011 | %1 |
| crypt32.dll | 0x101 | 78.11011 | The Cryptographic Services service failed to initialize the Catalog Database. The ESENT error was: %1. |
| els.dll | 0x101 | 78.11011 | Security |
| mispace.dll | 0x101 | 1011 | Windows can't check the disk while it's in use. Do you want to check for hard disk errors the next time you start your computer? |
| ntdll.dll | 0x101 | 78.11011 | STATUS_ALERTED |
| ntlanui2.dll | 0x101 | 78.11011 | The server %1 could not be found on the network. |
| ntshrui.dll | 0x101 | 78.11011 | There are %1!d! file(s) open by %2!d! user(s) connected to %3. If you stop sharing %3, the files will close, which may cause these users to lose data. Do you want to continue? |
| pci.sys | 0x101 | 1011 | IDE Controller |
| storagewmi.dll | 0x101 | 8.11011 | Windows can't check the disk while it's in use. Do you want to check for hard disk errors the next time you start your computer? |
| webservices.dll | 0x101 | 78.11011 | The field type does not support an XML attribute mapping. |
| wevtapi.dll | 0x101 | 78.11011 | Security |
| 13 entries | |||