Merhabalar, win32k_power_ watchdog_timeout (19c) error nasıl düzelteceğim?

Question

Merhabalar, win32k_power_ watchdog_timeout (19c) error nasıl düzelteceğim?

Anonymous

1: 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: ffff800763293240, Pointer to the power request worker thread.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1483

    Key  : Analysis.Elapsed.mSec
    Value: 2396

    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: 328

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

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

    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.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    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: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    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: ni_release_svc_prod3

    Key  : WER.OS.Version
    Value: 10.0.22621.2506

BUGCHECK_CODE:  19c

BUGCHECK_P1: 50

BUGCHECK_P2: ffff800763293240

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  050924-13687-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe

FAULTING_THREAD:  ffff800763293240

STACK_TEXT:  
ffffcd87`a968ede0 fffff802`72a3aa05     : 00000000`00000020 00000000`00000000 ffff8007`61ff74c0 00000000`ffffffff : nt!KiSwapContext+0x76
ffffcd87`a968ef20 fffff802`72a3cbe7     : ffff8007`63293240 ffffcd87`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0xab5
ffffcd87`a968f070 fffff802`72a3eb06     : 00000000`00000000 ffffffff`00000001 ffff8007`00000011 00000000`60440c84 : nt!KiCommitThreadWait+0x137
ffffcd87`a968f120 fffff802`72a90b9b     : ffffcd87`a968f5d0 ffff8007`61911a90 00000000`00000000 fffff802`78bab9c8 : nt!KeWaitForSingleObject+0x256
ffffcd87`a968f4c0 fffff802`72a36347     : ffff8007`61911a90 ffffcd87`a968f588 00000000`00010224 fffff802`72ab66a0 : nt!ExpWaitForResource+0x6b
ffffcd87`a968f550 fffff802`72a7af61     : 00000000`00000000 ffffa585`1b7e41a0 00000000`00000002 00000000`00000000 : nt!ExpAcquireResourceExclusiveLite+0x317
ffffcd87`a968f5f0 ffffcd4b`8c8dc38b     : 00000000`00000002 ffff8007`632a7e10 00000000`00000000 ffff8007`4e493330 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0xf1
ffffcd87`a968f630 ffffcd4b`8c8dc05f     : ffffcd87`a968f8e0 00000000`706d7447 00000000`00000000 00000000`00000000 : win32kbase!DrvSetWddmDeviceMonitorPowerState+0x30b
ffffcd87`a968f7a0 ffffcd4b`8c8a0a9b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!DrvSetMonitorPowerState+0x2f
ffffcd87`a968f7d0 ffffcd4b`8c89f99f     : 00000000`00000000 ffffcd87`a968f909 00000000`00000103 ffffcd87`00000001 : win32kbase!PowerOnMonitor+0x21b
ffffcd87`a968f840 ffffcd4b`8c89e974     : ffff8007`567129e0 ffff8007`567129e0 00000000`00000001 00000000`00000001 : win32kbase!xxxUserPowerEventCalloutWorker+0x35b
ffffcd87`a968f970 ffffcd4b`8cc58742     : ffff8007`63293240 00000000`00000000 00000000`00000020 fffff802`72ec1a0e : win32kbase!xxxUserPowerCalloutWorker+0x264
ffffcd87`a968fa40 ffffcd4b`8d016ed5     : 00000000`00000000 00000000`00050213 00000000`00000000 00000000`00000018 : win32kfull!NtUserUserPowerCalloutWorker+0x22
ffffcd87`a968fa70 fffff802`72c2d538     : ffff8007`000005a2 580bfd71`50550000 00000000`00000000 00000000`00000000 : win32k!NtUserUserPowerCalloutWorker+0x15
ffffcd87`a968faa0 00007fff`104dc8f4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000003f`b697f998 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`104dc8f4

SYMBOL_NAME:  win32kbase!DrvSetWddmDeviceMonitorPowerState+30b

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.22621.3527

STACK_COMMAND:  .process /r /p 0xffff80076316b180; .thread 0xffff800763293240 ; kb

BUCKET_ID_FUNC_OFFSET:  30b

FAILURE_BUCKET_ID:  0x19C_DRVSETMONITORPOWERSTATE_HANG_win32kbase!DrvSetWddmDeviceMonitorPowerState

OS_VERSION:  10.0.22621.2506

BUILDLAB_STR:  ni_release_svc_prod3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c2f3b63e-5f94-8af7-1fec-e562548bc885}

Followup:     MachineOwner
---------

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.

0 comments

1 answer

Answer 1

Hello Yuiyao, welcome to the Microsoft Community!

According to your feedback, you are experiencing a blue screen issue

Analyzing your blue screen logs, we know that

Your blue screen is caused by a win32kbase.sys error via csrss.exe.

You can try to repair your system:

Search for CMD, find the command prompt and select Run as administrator.
Enter the following commands one by one, making sure to execute the next command only after the previous one completes:

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /RestoreHealth

SFC /Scannow

After the scan is complete, you can check the scan information to see if any problems were detected and fixed.

Also csrss.exe is a virus, you can try the following methods to remove it

   Step 1, end the virus process csrss.exe, note that it is Windowscsrss.exe not WindowsSystem32csrss.exe.

　　Step 2, find the following files and delete them. (Not all of these files are there, there may only be a few, but as long as they are there, delete them!)

　　Code:

　　>> Systemdxdiag.com

　　>> Systemfinder.com

　　>> Systemmsconfig.com

　　>> C:autorun.inf

　　>> ProgramfilesInternet Exploreriexplore.com

　　>> ProgramfilesCommon Filesiexplore.pif

　　>> Windows.com

　　>> Windowscsrss.exe

　　>> WindowsExERoute.exe

　　>> Windowsexplorer1.com

　　>> Windowsfinder.com

　　>> WindowsDebugDebugProgram.exe

　　>> systemcommand.pif

　　>> Systemregedit.

　　>> Systemrundll32.com

　　At the same time, check "Start" --- "Programs" for the following connection security test.lnk, computer security center.lnk, system information manager.ink, delete them if there are any!

　　Step 3, open the registry editor:

　　(1) Find the information of "finder.com", "rundll32.com", "command.pif" respectively, and put the found value of "finder.com", "rundll32.com", "command.pif" to " rundll32.exe";

　　(2) Find the information of "iexplore.com", change "iexplore.com" to "iexplore.exe" in the found value. "; look for the information of "iexplore.pif", change the information of "%ProgramFiles%Common Filesiexplore.pif" to "%ProgramFiles%Common Filesiexplore.pif" in the found value. information to something like "%ProgramFiles%Internet Exploreriexplore.exe";

　　(3) Look for the information of "explorer1.com", and change "explorer1.com" to "explorer.exe" in the found value. ";

　　Step 4: Remove the virus startup items:

　　Code:

　　[HKEL_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run]

　　"Torjan Program"="%Windows%CSRSS.exe"

　　In [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon].

　　Restore "Shell"="Explorer.exe 1" to "Shell"="Explorer.exe".

　　Delete the entries [HKEY_CLASSES_ROOT\Applicationsiexplore.com] and [HKEY_CLASSES_ROOT\winfiles].

　　Step 5: Restart your computer and you're done.

　　Although the above operation is a bit complicated and cumbersome, but it is the most effective way to kill csrss.exe virus!

I hope the above information is helpful to you!

Kirito|Microsoft Community Support Specialist