SYNTHETIC_WATCHDOG_TIMEOUT
Code: 0x1ca (458)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x01ca (458)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x01ca (458)
Parameters
| Parameter | Description |
|---|---|
| 1 | The time since the watchdog was last reset, in interrupt time. |
| 2 | The current interrupt time. |
| 3 | The current QPC timestamp. |
| 4 | The index of the clock processor. |
Description
The SYNTHETIC_WATCHDOG_TIMEOUT bug check has a value of 0x000001CA. A system wide watchdog has expired. This indicates that the system is hung and not processing timer ticks.
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
A system wide watchdog has expired. This indicates that the system is hung and not processing timer ticks.
Resolution
The !analyze debugger extension displays information about the bug check and can be helpful in determining the root cause. For more information about WinDbg and !analyze, see Using the !analyze extension and !analyze.
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 |
|---|---|---|---|
| ESENT.dll | 0x1ca | 8.11011 | %1 (%2) %3The logfiles %4 and %5 are not in a valid sequence. Logfile replay cannot succeed if there are gaps in the sequence of available logfiles. |
| EventCreate.exe | 0x1ca | 78.11011 | %1 |
| kernel32.dll | 0x1ca | 1011 | The custom capability's SCCD failed to parse. |
| webservices.dll | 0x1ca | 78.11011 | The text type (%1) is not valid. |
| 4 entries | |||