| Previous | Next |
| TTM_FATAL_ERROR | CLUSTER_SVHDX_LIVEDUMP |
WIN32K_POWER_WATCHDOG_TIMEOUT
The WIN32K_POWER_WATCHDOG_TIMEOUT bug check has a value of 0x0000019C. This indicates that Win32k did not turn the monitor on in a timely manner.
WIN32K_POWER_WATCHDOG_TIMEOUT Parameters
| Parameter | Description |
|---|---|
| 1 | Failure type (win32kbase!POWER_WATCHDOG_TYPE)
0x10 : The power request queue is not making progress
2 - Pointer to the thread processing power requests, if any
3 - Pointer to the win32k user lock
4 - Pointer to the power request (win32kbase!PPOWERREQUEST) being
processed, if any
0x20 : Calling PO to set power state
2 - Pointer to the power request worker thread
3 - Reserved
4 - Reserved
0x30 : Calling GDI to power on
2 - Pointer to the power request worker thread
3 - Reserved
4 - Reserved
0x40 : Calling DWM to render
2 - Pointer to the power request worker thread
3 - Reserved
4 - Reserved
0x50 : Calling monitor driver to power on
2 - Pointer to the power request worker thread
3 - Reserved
4 - Reserved
|
| 2 | See parameter 1 |
| 3 | See parameter 1 |
| 4 | See parameter 1 |
Resolution and diagnostic sequence
Start with Parameter 1 because it identifies the stalled display-power boundary. For 0x10, inspect the power-request worker, the win32k user lock, and the request pointer from Parameters 2–4 to determine why the queue stopped making progress. Values 0x20, 0x30, 0x40, and 0x50 narrow the timeout respectively to the power manager transition, GDI, DWM rendering, or the monitor-driver power-on path.
Evidence to preserve
Keep the crash dump, Parameter 1 subtype, worker-thread stack, display adapter and monitor driver versions, connected-monitor topology, and the immediately preceding sleep, resume, lid, dock, or display-power transition. If the same failure repeats, compare dumps at the same subtype instead of applying unrelated USB, memory, storage, or CPU-watchdog remedies.
Correct recovery direction
After the dump identifies the stalled layer, test the smallest relevant change: the display miniport or monitor driver, DWM/display stack state, or platform power transition involved in that subtype. Reproduce the same power transition with the same monitor topology and confirm that the request queue completes; a generic reboot alone does not establish that the underlying display-power deadlock or timeout is fixed.
References
Looking for a different code? Search another status or error code.