| Previous | Next |
| SOC_CRITICAL_DEVICE_REMOVED | TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK |
PDC_WATCHDOG_TIMEOUT
Bug check PDC_WATCHDOG_TIMEOUT identifies a Power Dependency Coordinator client that failed to complete its power transition within the watchdog interval. Parameter 1 gives the client ID and parameter 2 identifies the kind of client that is hung.
Interpret parameter 2 before blaming the final power request: 0x1 is a notification client, 0x2 a resiliency client, 0x3 an activator holding a reference too long, and 0x100 a Win32k monitor-on request. Parameters 3 and 4 then point to the client or triage data for that branch.
PDC_WATCHDOG_TIMEOUT Parameters
| Parameter | Description |
|---|---|
| 1 | Client ID of the hung component. |
| 2 | Client type of the hung component. 0x1 : A notification client failed to respond. Parameter 3: Pointer to the notification client (PDC_NOTIFICATION_CLIENT). Parameter 4: Pointer to a pdc!PDC_14F_TRIAGE structure.0x2 : A resiliency client failed to respond. Parameter 3: Pointer to the resiliency client (PDC_RESILIENCY_CLIENT). Parameter 4: Pointer to a pdc!PDC_14F_TRIAGE structure.0x3 : An activator client held a reference for too long. Parameter 3: Pointer to the activation client (pdc!_PDC_ACTIVATOR_CLIENT). Parameter 4: Pointer to a pdc!PDC_14F_TRIAGE structure.0x100 : Win32k did not complete a monitor-on request in a timely manner. Parameter 3: The most recent POWER_MONITOR_REQUEST_REASON value for this request. Parameter 4: A value indicating the internal path taken to initiate the request. |
| 3 | See parameter 2 |
| 4 | See parameter 2 |
Resolution
Use the client type, client pointer or monitor-request reason, and the blocked stack to find the component that failed to acknowledge the transition. Validate the fix by repeating the same sleep, resume, display-on, or resiliency path without exceeding the watchdog interval.
Blue-screen reference
Looking for a different code? Search another status or error code.