WIN32K_POWER_WATCHDOG_TIMEOUT Crash Trying to Wake Computer

Question

I am frequently getting the error WIN32K_POWER_WATCHDOG_TIMEOUT followed by a crash when trying to wake my laptop. Analysis results from a recent dump file are below. What does this mean?

I have mini-dump files available: https://drive.google.com/file/d/1NNyjFK5N-AsLwCe7wP\_5A8DAb9ksXt84/view?usp=sharing

Thanks,

NM

For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`23bfa090 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffffd0b`5a367360=000000000000019c
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WIN32K_POWER_WATCHDOG_TIMEOUT (19c)
Win32k did not turn the monitor on in a timely manner.
Arguments:
Arg1: 0000000000000050, Calling monitor driver to power on.
Arg2: ffff818374343080, Pointer to the power request worker thread.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2296

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 16816

    Key  : Analysis.IO.Other.Mb
    Value: 10

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 39

    Key  : Analysis.Init.CPU.mSec
    Value: 1577

    Key  : Analysis.Init.Elapsed.mSec
    Value: 35846

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 117

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x19c

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x19c

    Key  : Bugcheck.Code.Register
    Value: 0x19c

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  19c

BUGCHECK_P1: 50

BUGCHECK_P2: ffff818374343080

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  csrss.exe

FAULTING_THREAD:  ffff818374343080

STACK_TEXT:  
fffffd0b`51d295e0 fffff802`23a7e370     : fffff802`1f40d180 ffff8183`74343080 fffffd0b`00000001 ffff8183`acd94158 : nt!KiSwapContext+0x76
fffffd0b`51d29720 fffff802`23a7d89f     : 00000000`00000000 00000000`00000000 fffffd0b`51d298e0 00000000`00000000 : nt!KiSwapThread+0x500
fffffd0b`51d297d0 fffff802`23a7d143     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8183`743431c0 : nt!KiCommitThreadWait+0x14f
fffffd0b`51d29870 fffff802`399de50e     : ffff8183`686e4178 00000000`00000000 ffff8183`686e3100 00000000`00000000 : nt!KeWaitForSingleObject+0x233
fffffd0b`51d29960 fffff802`39b325a2     : ffff8183`686e3180 00000000`00000000 fffff802`1f40d100 00000000`00000000 : dxgkrnl!DpiCheckForOutstandingD3Requests+0x6e
fffffd0b`51d299c0 fffff802`39addce6     : ffffa6a2`00200340 ffffa6a2`00201c40 ffffa6a2`00201e00 fffff802`23ef0960 : dxgkrnl!DxgkPowerOnOffMonitor+0x10e
fffffd0b`51d29ae0 fffff802`39ae5170     : ffff8183`ffffffff ffff8183`8ea19ac0 ffff8183`736adde0 00000000`00000000 : dxgkrnl!DpiGdoDispatchInternalIoctl+0x586
fffffd0b`51d29b90 fffff802`23a954d5     : 00000000`00000000 ffff8183`00000000 00000000`c0000002 00000000`00000010 : dxgkrnl!DpiDispatchInternalIoctl+0x100
fffffd0b`51d29cc0 ffffa6d0`b9885211     : fffffd0b`51d29d90 00000000`00000000 ffffa6a2`07fe0070 ffffa6d0`b98c7daa : nt!IofCallDriver+0x55
fffffd0b`51d29d00 ffffa6d0`b98c8022     : ffffa6a2`07fe0070 fffffd0b`51d29ea0 00000000`00000000 ffff8183`00000000 : win32kbase!GreDeviceIoControlImpl+0xed
fffffd0b`51d29da0 ffffa6d0`b98c7def     : fffffd0b`51d2a0f0 00000000`00000000 00000000`00000001 00000000`00000050 : win32kbase!DrvSetWddmDeviceMonitorPowerState+0x212
fffffd0b`51d29f10 ffffa6d0`b987aa9f     : 00000000`00000050 00000000`c00000bb 00000000`c00000bb 00000000`00000001 : win32kbase!DrvSetMonitorPowerState+0x2f
fffffd0b`51d29f40 ffffa6d0`b98132eb     : 00000000`00000000 fffffd0b`51d2a0c0 00000000`00000000 00000000`00000001 : win32kbase!PowerOnMonitor+0x1cf
fffffd0b`51d29fc0 ffffa6d0`b9812f52     : ffff8183`9a784d40 ffff8183`9a784d40 00000000`00000001 00000000`00000000 : win32kbase!xxxUserPowerEventCalloutWorker+0x20b
fffffd0b`51d2a330 ffffa6d0`b9b2e9f1     : ffff8183`74343080 00000000`00000000 00000000`00000025 00000000`00000025 : win32kbase!xxxUserPowerCalloutWorker+0xe2
fffffd0b`51d2a3a0 ffffa6d0`ba6e476e     : ffff8183`74343080 fffff802`23c0d7b1 00000000`00000000 00000000`00040287 : win32kfull!NtUserCallNoParam+0x71
fffffd0b`51d2a3d0 fffff802`23c0d8f5     : 00000000`0000016c 00000000`00000025 00000000`00000000 00000000`00000000 : win32k!NtUserCallNoParam+0x16
fffffd0b`51d2a400 00007fff`345010e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000bb`adeff8a8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`345010e4

SYMBOL_NAME:  dxgkrnl!DpiCheckForOutstandingD3Requests+6e

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

STACK_COMMAND:  .process /r /p 0xffff8183738a72c0; .thread 0xffff818374343080 ; kb

BUCKET_ID_FUNC_OFFSET:  6e

FAILURE_BUCKET_ID:  0x19C_DRVSETMONITORPOWERSTATE_HANG_dxgkrnl!DpiCheckForOutstandingD3Requests

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b953a24d-00f1-7e05-510d-44334608bc78}

Followup:     MachineOwner

Answer 1

Your dump file shows that DirectX is causing the crash.
This could be caused by a faulty graphics card or a corrupt driver. It is recommended to uninstall the graphics driver and then perform a system repair. Open PowerShell as administrator and enter the following command.

Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-image /RestoreHealth
sfc /scannow

Then download the latest version of the driver from the device manufacturer's official website and reinstall it.

I didn't see the software to be uninstalled from the add/remove programs list but I did "uninstall device" and began running the provided commands. During the first command though, Windows automatically reinstalled the device driver though. I went through the three commands still and was successful. I reinstalled the driver from the device manufacturer's website which was updated but I got another minidump this morning at 1:40am while the laptop lid was closed and in standby. Here is the dump file: https://drive.google.com/file/d/1XTj8qitP8cTCY3zRReVU41RxUI6dHinD/view?usp=sharing

Thanks for your help

Answer 2

Your dump file shows that DirectX is causing the crash.

This could be caused by a faulty graphics card or a corrupt driver. It is recommended to uninstall the graphics driver and then perform a system repair. Open PowerShell as administrator and enter the following command.

Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-image /RestoreHealth
sfc /scannow

Then download the latest version of the driver from the device manufacturer's official website and reinstall it.