I’m getting the same thing. However it’s only happening to me as I am gaming. It happens 2-3 times a week.
BSOD with STOP Code - WIN32K POWER WATCHDOG TIMEOUT
Hello everyone,
I am hoping someone can help me to identify the real issue here. We are getting lots of (every week at least 5/6 users if not more) BSOD with WIN32K POWER WATCHDOG TIMEOUT, error.
I've downloaded and installed the Windbg utility and analysed the dump files from the users and all of them shows the same error. The details of the analysed dump file is below:
*******************************************************************************
* *
* 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: ffffba8dec384080, Pointer to the power request worker thread.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5796
Key : Analysis.Elapsed.mSec
Value: 8607
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 1312
Key : Analysis.Init.Elapsed.mSec
Value: 6567
Key : Analysis.Memory.CommitPeak.Mb
Value: 105
Key : Bugcheck.Code.LegacyAPI
Value: 0x19c
Key : Bugcheck.Code.TargetModel
Value: 0x19c
Key : Failure.Bucket
Value: 0x19C_DRVSETMONITORPOWERSTATE_HANG_win32kbase!DrvSetWddmDeviceMonitorPowerState
Key : Failure.Hash
Value: {c2f3b63e-5f94-8af7-1fec-e562548bc885}
Key : Hypervisor.Enlightenments.Value
Value: 68673420
Key : Hypervisor.Enlightenments.ValueHex
Value: 417df8c
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 21631230
Key : Hypervisor.Flags.ValueHex
Value: 14a10fe
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 19c
BUGCHECK_P1: 50
BUGCHECK_P2: ffffba8dec384080
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 072424-13296-01.dmp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csrss.exe
FAULTING_THREAD: ffffba8dec384080
STACK_TEXT:
fffffc8c419b7ed0 fffff8010dc38a30 : ffffe401ffffffff 0000000000000000 ffffffffffffff01 0000000000000000 : nt!KiSwapContext+0x76
fffffc8c419b8010 fffff8010dc37f5f : 0000000700000007 fffff80100000005 fffffc8c419b81d0 fffffc8c00000000 : nt!KiSwapThread+0x500
fffffc8c419b80c0 fffff8010dc37803 : 00000000000000b0 ffffcb0900000000 0000000000000000 ffffba8dec3841c0 : nt!KiCommitThreadWait+0x14f
fffffc8c419b8160 fffff8010dc3404d : fffffc8c419b8348 fffff8010000001b ffffba8dec384000 ffffba8de306af00 : nt!KeWaitForSingleObject+0x233
fffffc8c419b8250 fffff8010dc3edd0 : ffffba8dea877a90 fffffc8c419b8330 0000000000010224 fffff8010dd53820 : nt!ExpWaitForResource+0x6d
fffffc8c419b82d0 fffff8010dc3dfdc : 0000000100000594 0000000000000003 000000000000005b 0000000000000000 : nt!ExpAcquireResourceExclusiveLite+0x320
fffffc8c419b83a0 fffffd8c312c5a3a : 0000000000000001 0000000000989680 0000000000000000 ffffba8dec315a00 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x3c
fffffc8c419b83e0 fffffd8c312c576f : fffffc8c419b8730 0000000000000000 0000000000000001 0000000000000050 : win32kbase!DrvSetWddmDeviceMonitorPowerState+0x2aa
fffffc8c419b8550 fffffd8c3126a67f : 0000000000000050 00000000c00000bb 00000000c00000bb 0000000000000001 : win32kbase!DrvSetMonitorPowerState+0x2f
fffffc8c419b8580 fffffd8c31269c4b : 0000000000000000 fffffc8c419b8700 0000000000000000 0000000000000001 : win32kbase!PowerOnMonitor+0x1cf
fffffc8c419b8600 fffffd8c312698b2 : ffffba8df57c4d80 ffffba8df57c4d80 0000000000000001 0000000000000000 : win32kbase!xxxUserPowerEventCalloutWorker+0x20b
fffffc8c419b8970 fffffd8c31ad89f1 : ffffba8dec384080 0000000000000000 0000000000000025 0000000000000025 : win32kbase!xxxUserPowerCalloutWorker+0xe2
fffffc8c419b89e0 fffffd8c316e474e : ffffba8dec384080 0000000000040246 0000000000000000 0000000000000018 : win32kfull!NtUserCallNoParam+0x71
fffffc8c419b8a10 fffff8010de11d05 : 0000000000000164 0000000000000025 0000000000000000 0000000000000000 : win32k!NtUserCallNoParam+0x16
fffffc8c419b8a40 00007ffdb0b410e4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000b971bffb88 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd`b0b410e4
SYMBOL_NAME: win32kbase!DrvSetWddmDeviceMonitorPowerState+2aa
MODULE_NAME: win32kbase
IMAGE_NAME: win32kbase.sys
IMAGE_VERSION: 10.0.19041.4648
STACK_COMMAND: .process /r /p 0xffffba8debb1a140; .thread 0xffffba8dec384080 ; kb
BUCKET_ID_FUNC_OFFSET: 2aa
FAILURE_BUCKET_ID: 0x19C_DRVSETMONITORPOWERSTATE_HANG_win32kbase!DrvSetWddmDeviceMonitorPowerState
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c2f3b63e-5f94-8af7-1fec-e562548bc885}
Followup: MachineOwner
Can anyone please help me to identify the real issue here? I have done loads of research already and whatever I have found so far have tried but it didn't stop it from reoccurring. So far I have tried the following:
1. SFC
2. DISM Tool
3. Rolled back Graphics card driver
4. Updated Graphics card driver
Any help is appreciated. Thank you very much in advance.
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
4 answers
Sort by: Most helpful
-
Anonymous
2024-11-09T16:45:58+00:00 -
Anonymous
2024-08-07T08:45:50+00:00 Hi, Suranjan
Thanks for your reply!
I noticed that your blue screen problem occurs indirectly. This may be related to the software you are running. Have you noticed which software you used when the blue screen appeared?
The minidump file usually points out the program that caused the blue screen. As I mentioned in my first reply, the minidump file you provided pointed out that the blue screen was caused by win32kbase.sys, which is a system-related component. This means that your system components may be damaged. You can follow the solutions I provided step by step. The last solution will guide you to repair the system. You can follow the last solution if the first two solutions cannot solve it.
If you have any progress, you are welcome to contact us at any time.
Best Regards
Nicholas.Z - MSFT | Microsoft Community Support Specialist
-
Anonymous
2024-08-05T16:22:02+00:00 Hi, Suranjan
Welcome to Microsoft Community.
We understand that you are experiencing a blue screen issue and that WIN32K_POWER_WATCHDOG_TIMEOUT reports an error stating that Win32k did not turn on the monitor in time. We understand that you have tried using DISM, the SFC scan command, and the option of rolling back the graphics card driver.Has the computer with the problem downloaded any third-party programs recently?We suggest you try Clean Boot first:The method is as follows1. Tap Windows+R and type msconfig.2. Open System Configuration and select General tab - Selective Boot.3. Remove the checkmark of Load startup items.4. Go to the Services tab - click Hide all microsoft services in the lower left corner, and then click Disable all.5. Click OK and restart your computer. (Be sure to select Hide all Microsoft services first and then click Disable all, otherwise it may cause unforeseen problems such as not being able to access the system.)Check to see if the problem will reoccur.*Disclaimer: A “clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background service is interfering with your game or program and to isolate the cause of a problem.**These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get back on track.*If you it did not work ,you can try entering WinRE to repair your system:- Start your PC as if Windows is trying to load (spinning point), hold the power button for 5-10 seconds to perform a hard shutdownDo this twice- On the third boot, Windows will boot into the recovery environment from which you can access System Repair, Safe Mode, Command Prompt ...... Click on "Advanced".-Click on "Advanced Options".- Go to Troubleshooting - Advanced Options - Startup Repair- See if Windows startup can be repaired on its ownIf you can't repair your system in WinRE, then you can use Media Creation Tool to repair your system, you can upgrade/repair your system using Microsoft's MediaCreationTool20H2 tool:Download Windows 10 (microsoft.com)After opening the above link, click the second button "Download Tool Now" (the first button downloads Easy Upgrade, please click the second button).Double click to run it after downloading.Select the first option to upgrade this computer immediately.If the system is installed in an unsupported directory or other unusual circumstances, it may not be possible to repair without damage.It is also recommended to backup important data to prevent accidents.For detailed instructions on the above steps, check out the video tutorials at the link below:Video Player (microsoft.com) Disclaimer: Let’s try performing an in-place install or in-place upgrade which will refresh your Windows files and operating system without removing files or applications. That being said, we always recommend that if you have important data, you should back it up before making large system changes. If you want to back up your data first, please do so. Once you are done backing up, you can follow the steps in the following guides: How to perform an In-place Upgrade with Windows 10 Step-by-Step Guide - Microsoft Community If you have any progress, please feel free to contact us.
Best Regards
Nicholas.Z - MSFT | Microsoft Community Support Specialist
Hi Nicholas,
Many thanks for your response with the things to try. I will give it a go but the problem is, the use is getting BSOD very intermittently., e.g.1 week no BSOD and next week couples.
One question, from the Minidump analysis are you able pinpoint the cause of the issue?
Thank you
-
Anonymous
2024-08-03T03:41:20+00:00 Hi, Suranjan
Welcome to Microsoft Community.
We understand that you are experiencing a blue screen issue and that WIN32K_POWER_WATCHDOG_TIMEOUT reports an error stating that Win32k did not turn on the monitor in time. We understand that you have tried using DISM, the SFC scan command, and the option of rolling back the graphics card driver.Has the computer with the problem downloaded any third-party programs recently?We suggest you try Clean Boot first:The method is as follows1. Tap Windows+R and type msconfig.2. Open System Configuration and select General tab - Selective Boot.3. Remove the checkmark of Load startup items.4. Go to the Services tab - click Hide all microsoft services in the lower left corner, and then click Disable all.5. Click OK and restart your computer. (Be sure to select Hide all Microsoft services first and then click Disable all, otherwise it may cause unforeseen problems such as not being able to access the system.)Check to see if the problem will reoccur.*Disclaimer: A “clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background service is interfering with your game or program and to isolate the cause of a problem.**These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get back on track.*If you it did not work ,you can try entering WinRE to repair your system:- Start your PC as if Windows is trying to load (spinning point), hold the power button for 5-10 seconds to perform a hard shutdownDo this twice- On the third boot, Windows will boot into the recovery environment from which you can access System Repair, Safe Mode, Command Prompt ...... Click on "Advanced".-Click on "Advanced Options".- Go to Troubleshooting - Advanced Options - Startup Repair- See if Windows startup can be repaired on its ownIf you can't repair your system in WinRE, then you can use Media Creation Tool to repair your system, you can upgrade/repair your system using Microsoft's MediaCreationTool20H2 tool:Download Windows 10 (microsoft.com)After opening the above link, click the second button "Download Tool Now" (the first button downloads Easy Upgrade, please click the second button).Double click to run it after downloading.Select the first option to upgrade this computer immediately.If the system is installed in an unsupported directory or other unusual circumstances, it may not be possible to repair without damage.It is also recommended to backup important data to prevent accidents.For detailed instructions on the above steps, check out the video tutorials at the link below:Video Player (microsoft.com) Disclaimer: Let’s try performing an in-place install or in-place upgrade which will refresh your Windows files and operating system without removing files or applications. That being said, we always recommend that if you have important data, you should back it up before making large system changes. If you want to back up your data first, please do so. Once you are done backing up, you can follow the steps in the following guides: How to perform an In-place Upgrade with Windows 10 Step-by-Step Guide - Microsoft Community If you have any progress, please feel free to contact us.
Best Regards
Nicholas.Z - MSFT | Microsoft Community Support Specialist