Win32K_POWER_WATCHDOG_TIMEOUT BSOD-FILECHAD PRO 5

私たちのSurface Pro 5の過去数日の2日間にawin32k_power_watchdog_timeout bsod

* *

* BugCheck Analysis *

* *

win32k_power_watchdog_timeout(19c)

Win32kは、タイムリーにモニターをオンにしませんでした.

引数:

arg1:0000000000000020、電源状態を設定するためにPOを呼び出します.

ARG2:FFFFA7061E3C3080、電源リクエストワーカースレッドへのポインタ

arg3:0000000000000000

arg4:0000000000000000

<強力>デバッグの詳細:

key_values_string:1

キー:Analysis.cpu.sec

値:3

キー:Analysis.DebuganalysisProvider.cpp

値:作成:8007007Eアレックスsurface

キー:Analysis.debugData

値:CreateObject

キー:Analysis.DebugModel

値:CreateObject

key:Analysis.elapsed.sec

値:40

キー:Analysis.Memory.commitpeak.mb

値:96

キー:Analysis.System

値:CreateObject

bugcheck_code:19c

bugcheck_p1:20

bugcheck_p2:FFFFA7061E3C3080

bugcheck_p3:0

bugcheck_p4:0

ブラックボックスBSD:1(！BlackBoxBSD)

blackboxntfs:1(！blackboxntfs)

ブラックボックスPnp:1(！BlackBoxPnp)

ブラックボックスウィンロゴン:1

customer_crash_count:1

process_name:csrss.exe

Faulting_Thread:FFFFA7061E3C3080

stack_text:

FFFFA385`7cc4e7a0fffff804 `7e27da0:FFFFD480FFFFFFE 00000000`FFFFFFFFFE 00000000`00000000000000:NT！KiswapContext + 0x76

FFFFA385`7cc4e8507cc4e807072cf:FFFFA706`0000000 FFFFA385`7CC4EaA00000000 00000000:NT！Kiswapthread + 0x500

ffffa385`7cc4e990 FFFFF804 '7e26b73:00000000`00000000 00000000 00000000 FFFFA706`1E3C31C0:NT！KICOMMITTHREADWAIT + 0x14F

FFFFA385`7cc4ea30fffff804 `7e29a4d:FFFFA385`7CC4EC00000000000000000000000 00000000 00000000:NT！KewaitForsingleObject + 0x233

FFFFA385 `7CC4EB207CC4EB20 FFFFF804` 7e2331:FFFFA385 `7CC4EBE8 00000000 `00010224 FFFFF804`7ef4fca0:NT！ExpWaitForResource + 0x6D

ffffa385`7cc4eba0fffff804 '7f59c352:ffffa385`7cc4a0000000000000000000000000000000000000000000000000000000000000000000:NT！ExacquireResourceExclusiveLite + 0x1FE

ffffa385`7cc4ec30fffff804`7f3de372:00000000 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000:NT！Popacquirepolicylock + 0x32

FFFFA385 '7cc4ec60fffff8046:00000000 $ 100000000000000000000:NT！NTPowerInformation + 0x1F8A42

FFFFA385 `7CC4F3B07CC4F3B0 FFFFF804 `7efe1da0:FFFFA706`27A37B48 FFFFA706`27A37B48 00000000 00000000:NT！KisystemServiceCopyend + 0x25

FFFFA385「7CC4F5B8 FFFFD294」FFFFD294`78CCAE9A:FFFFA706`27A37B48 00000000 00000000 00000000 00000000:NT！kiservic誘発

FFFFA385`7CC4F5C07CC4F5C0 FFFFD294`78CCAB62:FFFFA706`27A37B20 00000000 00000001 00000000 00000000:Win32KBase！XXXUSUSERPOWEREVERCALLOUjpORKER + 0X1AA

FFFFA385`7cc4f9307cc4f930788b1251:FFFFA706`1E3C3080 00000000 0000000025:Win32KBase！XXXUSERPOWERCALLOUjpORKER + 0XE2

FFFFA385 `7CC4F9A0 FFFFD294` 786B474E:FFFFA706`1E3C3080 FFFFF804`7efef731 00000000 00000010 00000000 $ 100040287:Win32Kfull！NtuserCallNoParam + 0x71

ffffa385`7cc4f9d0fffff804`7efef875:ffffa706`000000000000000000000000000000000000000000000000000000000:Win32k！NtuserCallNoParam + 0x16

ffffa385`7cc4fa000000000000000000000000000000000000000000000000000000000000000000000000000000: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}

フォローアップ: 機関所有者