PDC_WATCHDOG_TIMEOUT_LIVEDUMP
Code: 0x15c (348)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x015c (348)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x015c (348)
Parameters
| Parameter | Description |
|---|---|
| 1 | Client ID of the hung component. |
| 2 | Client type of the hung component. 0x1 : A notification client failed to respond.3 - Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT). 4 - Pointer to a pdc!PDC_14F_TRIAGE structure. 0x2 : A resiliency client failed to respond.3 - Pointer to the resiliency client (pdc!_PDC_RESILIENCY_CLIENT). 4 - Pointer to a pdc!PDC_14F_TRIAGE structure. 0x3 : An activator client held a reference for too long3 - Pointer to the activation client (pdc!_PDC_ACTIVATOR_CLIENT). 4 - Pointer to a pdc!PDC_14F_TRIAGE structure. |
| 3 | See parameter 2 |
| 4 | See parameter 2 |
Description
The PDC_WATCHDOG_TIMEOUT_LIVEDUMP live dump has a value of 0x0000015C. This indicates that a system component failed to respond within the allocated time period, preventing the system from entering or exiting connected standby.
(This code can never be used for a real bug check; it is used to identify live dumps.)
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 |
|---|---|---|---|
| EventCreate.exe | 0x15c | 78.11011 | %1 |
| kernel32.dll | 0x15c | 1011 | The requested operation failed because the file stream is marked to disallow writes. |
| webservices.dll | 0x15c | 78.11011 | The maximum number of namespaces in scope of %1 for the document was exceeded. |
| 3 entries | |||