Windows 10: win32k_power_watchdog_timeout BSOD - Surface Pro 5

Over the past few days 2 of our Surface Pro 5's have had a win32k_power_watchdog_timeout BSOD

I have gathered the minidump file results as shown below: It looks like it's related to the monitor taking to turn on after restart/sleep, but can anyone confirm if this is actually the case and what can we do to resolve this.
*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



WIN32K_POWER_WATCHDOG_TIMEOUT 19c

Win32k did not turn the monitor on in a timely manner.

Arguments:

Arg1: 0000000000000020, Calling PO to set power state.

Arg2: ffffa7061e3c3080, Pointer to the power request worker thread.

Arg3: 0000000000000000

Arg4: 0000000000000000



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 3



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on ALEX-SURFACE



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 40



Key : Analysis.Memory.CommitPeak.Mb

Value: 96



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 19c



BUGCHECK_P1: 20



BUGCHECK_P2: ffffa7061e3c3080



BUGCHECK_P3: 0



BUGCHECK_P4: 0



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: csrss.exe



FAULTING_THREAD: ffffa7061e3c3080



STACK_TEXT:

ffffa385`7cc4e7a0 fffff804`7ee27da0 : ffffd480`fffffffe 00000000`ffffffff 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x76

ffffa385`7cc4e8e0 fffff804`7ee272cf : ffffa706`00000002 fffff804`00000000 ffffa385`7cc4eaa0 00000000`00000000 : nt!KiSwapThread+0x500

ffffa385`7cc4e990 fffff804`7ee26b73 : 00000000`0000000f 00000000`00000000 00000000`00000000 ffffa706`1e3c31c0 : nt!KiCommitThreadWait+0x14f

ffffa385`7cc4ea30 fffff804`7ee29a4d : ffffa385`7cc4ec00 00000000`0000001b ffffa385`7cc4f600 00000000`00000000 : nt!KeWaitForSingleObject+0x233

ffffa385`7cc4eb20 fffff804`7ee2331e : fffff804`7f823c20 ffffa385`7cc4ebe8 00000000`00010224 fffff804`7ef4fca0 : nt!ExpWaitForResource+0x6d

ffffa385`7cc4eba0 fffff804`7f59c352 : ffffa385`7cc4f4a0 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x1fe

ffffa385`7cc4ec30 fffff804`7f3de372 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PopAcquirePolicyLock+0x32

ffffa385`7cc4ec60 fffff804`7efef875 : 00000000`00040246 fffff804`7ee3e821 000f0003`00000000 00000000`00000000 : nt!NtPowerInformation+0x1f8a42

ffffa385`7cc4f3b0 fffff804`7efe1da0 : ffffd294`78ccae9a ffffa706`27a37b48 ffffa706`27a37b48 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

ffffa385`7cc4f5b8 ffffd294`78ccae9a : ffffa706`27a37b48 ffffa706`27a37b48 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage

ffffa385`7cc4f5c0 ffffd294`78ccab62 : ffffa706`27a37b20 ffffa706`27a37b20 00000000`00000001 00000000`00000000 : win32kbase!xxxUserPowerEventCalloutWorker+0x1aa

ffffa385`7cc4f930 ffffd294`788b1251 : ffffa706`1e3c3080 00000000`00000000 00000000`00000025 00000000`00000025 : win32kbase!xxxUserPowerCalloutWorker+0xe2

ffffa385`7cc4f9a0 ffffd294`786b474e : ffffa706`1e3c3080 fffff804`7efef731 00000000`00000010 00000000`00040287 : win32kfull!NtUserCallNoParam+0x71

ffffa385`7cc4f9d0 fffff804`7efef875 : ffffa706`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : win32k!NtUserCallNoParam+0x16

ffffa385`7cc4fa00 00007ffd`763110e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

00000085`1093fd68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`763110e4





STACK_COMMAND: .thread 0xffffa7061e3c3080 ; kb



SYMBOL_NAME: win32kbase!xxxUserPowerEventCalloutWorker+1aa



MODULE_NAME: win32kbase



IMAGE_NAME: win32kbase.sys



IMAGE_VERSION: 10.0.19041.423



BUCKET_ID_FUNC_OFFSET: 1aa



FAILURE_BUCKET_ID: 0x19C_MONITORINVOCATION_HANG_win32kbase!xxxUserPowerEventCalloutWorker



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {6ea5508c-0d96-6a05-ac55-f2e01cd0139a}



Followup: MachineOwner

:)

 

WIN32K_POWER_WATCHDOG_TIMEOUT

I started to get the "WIN32K_POWER_WATCHDOG_TIMEOUT" blue screen a few weeks ago. I have a Surface Pro 4 and a Dell U3415W monitor. They were connected via the Surface Dock with a mini-port cable. When I finally go
through the blue screen restart, the Dell can not be found when it's plugged into the dock. I have been plugging it into the mini-port slot on the Surface.



Sometimes the system starts without a problem and other times the timeout happens. In my normal operations, I would have the Surface closed and only use the Dell. Now it's 50/50 as to whether the Surface is open.

I could use some help getting rid of the "WIN32K_POWER_WATCHDOG_TIMEOUT. "

 

Problem updating Windows Surface Pro 4 with Windows 10 feature updates

Hi,

I have manage to install image for Microsoft Surface Pro 4 by going to https://support.microsoft.com/en-us/...erecoveryimage and download a recovery image for Microsoft Surface Pro 4.

What I did to reset your Surface from a USB recovery drive was:
Step 1: Make sure your Surface is turned off and plugged in (hold down the power
button for 30 seconds).
Step 2: Insert the USB recovery drive into the USB port on your Surface.
Step 3: Press and hold the volume-down button while you press and release the
power button on your Surface.
Step 4: When the Surface logo appears, release the volume button.
Step 5: When prompted, select the language and keyboard layout you want.
Step 6: Select Troubleshoot > Reset your PC.
If prompted for a recovery key, select Skip this drive at the bottom of the
screen.
Step 7: Select the target operating system you wish to reset. This
refers to the current operating system installed on your Surface.
Step 8: Select Yes, repartition the drives, and on the next page, select Next.
Step 9: Choose Just remove my files.
Step 10: Select Reset.
Surface restarts and the Surface logo displays while the reset process continues
(this can take a while).

This always fails and I have to do the below which continues installation.
Windows 10 Installation Media:

1. Insert the Media (DVD/USB) in your PC and restart.
2. Boot from the media.
3. Select Repair Your Computer.

Select Troubleshoot.

1. Choose Command Prompt from the menu:

Type in the command:
Diskpart
Type in the command:
List disk (Note which disk is your Boot drive number mine is 0)
Type in the command:
Sel disk 0
Type in the command:
List vol (Note which volume is the EFI partition mine is 4)
Type in the command:
Sel vol 4
Type in the command:
assign letter=V:
Type in the command:
Exit
Type in the command:
V:
After you have assigned a drive letter Using Diskpart You can format the EFI partition:
Example: if you assigned a letter V to the partition the command would be:
format V: /FS:FAT32
Type in the command:
bcdboot C:\windows /s V: /f UEFI


Now I have an issue that I cannot install Feature Updates. They keep failing to install.
Any ideas how to resolve issue?

 

Surface Pro 3

Hi ChrisWaters3,

Thank you for writing to Microsoft Community Forums.

Could you please help me with the below information:

1. Does the battery drain out, if the tablet is not connected to peripherals?
   
   
2. Which version of Windows you are using? (To check, type: winver in start menu and hit enter.)
   

I understand how something like this can try your patience. This issue is an indication of faulty drivers or incompatible driver.
However, I suggest you to follow the troubleshooting steps mentioned below:

Method 1: Check the drivers.

Step1: Battery driver

1. Press Windows andR
   key together on your Keyboard.
2. Type devmgmt.msc and hit enter.
   
3. Click on view on top > Select Show hidden devices.
   
4. Expand the Batteries option from the list.
   
5. Select the ACPI Compliant Control Method Battery> right click on the driver and click on
   Properties.
6. Click on Driver tab > check if you have the option to
   Roll Back Driver.
7. If yes, Roll back the driver or uninstall it and restart the computer.
   

Uninstalling the driver will be automatically installed after the system is restarted. Check if the issue is fixed.

Step 2: Keyboard driver.

1. In the Device manager, go to ‘Other devices’, you will find
   Unknown devices.
   
2. Double tap on the unknown device > click on
   Driver tab> click on update driver.
   
3. Select browse my computer for driver software> Click on Let me pick from a list of device drivers
   
4. Select keyboard, then click ‘Next’.
   
5. Select HID Keyboard device and click finish.
   

Method 2: Run the toolkit.


Note: If your Surface is managed by your work or school, check with your organization's IT department before running the tool.

I would suggest you to run the toolkit provided by Microsoft on
Fix common Surface
problems using the Surface Diagnostic Toolkit

If the above steps, doesn’t fix the issue. I would suggest you to follow the steps mentioned in the article on
Surface Pro 3 Battery
FAQ for the Surface Pro Embedded Controller Firmware update.


Hope it helps.

Roohi Taj S

Microsoft Community - Moderator