Crash in sleep mode

ax h 21 Reputation points
2022-11-05T02:14:31.127+00:00

When my computer enters the hibernation mode, it will shut down immediately. I use the MSI motherboard, which has turned off all energy saving methods. The power on the computer is set to the default balance mode. I have been meeting this problem since I assembled the computer. And T tried to find reason using WinDbg, however I cannot understand this report.

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64  
Copyright (c) Microsoft Corporation. All rights reserved.  
  
  
Loading Dump File [C:\Windows\MEMORY.DMP]  
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.  
  
  
************* Path validation summary **************  
Response                         Time (ms)     Location  
Deferred                                       srv*  
Symbol search path is: srv*  
Executable search path is:   
Windows 10 Kernel Version 19041 MP (16 procs) Free x64  
Product: WinNt, suite: TerminalServer SingleUserTS  
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406  
Machine Name:  
Kernel base = 0xfffff805`74000000 PsLoadedModuleList = 0xfffff805`74c2a270  
Debug session time: Sat Nov  5 02:10:43.091 2022 (UTC + 8:00)  
System Uptime: 0 days 0:12:48.773  
Loading Kernel Symbols  
...............................................................  
.......Page 217727 not present in the dump file. Type ".hh dbgerr004" for details  
.........................................................  
................................................................  
..........  
Loading User Symbols  
  
Loading unloaded module list  
........  
For analysis of this file, run !analyze -v  
nt!KeBugCheckEx:  
fffff805`743f90f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc089`b74df7e0=00000000000000a0  
12: kd> !analyze -v  
*******************************************************************************  
*                                                                             *  
*                        Bugcheck Analysis                                    *  
*                                                                             *  
*******************************************************************************  
  
INTERNAL_POWER_ERROR (a0)  
The power policy manager experienced a fatal error.  
Arguments:  
Arg1: 00000000000000f0, The system failed to complete(suspend) a power transition in a timely manner.  
Arg2: 0000000000000004, The system power state in transition.  
Arg3: 000000000000000e, The sleep checkpoint most recently reached.  
Arg4: ffff87881c048040, A pointer to the thread currently processing the request.  
  
Debugging Details:  
------------------  
  
  
KEY_VALUES_STRING: 1  
  
    Key  : Analysis.CPU.mSec  
    Value: 1562  
  
    Key  : Analysis.DebugAnalysisManager  
    Value: Create  
  
    Key  : Analysis.Elapsed.mSec  
    Value: 1566  
  
    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: 1202  
  
    Key  : Analysis.Init.Elapsed.mSec  
    Value: 2520  
  
    Key  : Analysis.Memory.CommitPeak.Mb  
    Value: 96  
  
    Key  : Bugcheck.Code.DumpHeader  
    Value: 0xa0  
  
    Key  : Bugcheck.Code.KiBugCheckData  
    Value: 0xa0  
  
    Key  : Bugcheck.Code.Register  
    Value: 0xa0  
  
    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:  a0  
  
BUGCHECK_P1: f0  
  
BUGCHECK_P2: 4  
  
BUGCHECK_P3: e  
  
BUGCHECK_P4: ffff87881c048040  
  
FAULTING_THREAD:  ffff87881c048040  
  
BLACKBOXBSD: 1 (!blackboxbsd)  
  
  
BLACKBOXNTFS: 1 (!blackboxntfs)  
  
  
BLACKBOXPNP: 1 (!blackboxpnp)  
  
  
BLACKBOXWINLOGON: 1  
  
PROCESS_NAME:  System  
  
STACK_TEXT:    
ffffc089`b986f5f0 fffff805`742130b0     : 00000000`00000000 00000000`00000000 fffff805`00000000 00000000`389d7180 : nt!KiSwapContext+0x76  
ffffc089`b986f730 fffff805`742125df     : 00000000`28ed5540 00000000`00000000 ffffc089`b986f8f0 00001f80`00000000 : nt!KiSwapThread+0x500  
ffffc089`b986f7e0 fffff805`74211e83     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8788`1c048180 : nt!KiCommitThreadWait+0x14f  
ffffc089`b986f880 fffff805`74994351     : ffffc089`bb23f720 ffffc089`00000000 fffff805`74c02b00 ffff8788`1ab4e100 : nt!KeWaitForSingleObject+0x233  
ffffc089`b986f970 fffff805`74993d83     : 00000000`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!PopEndMirroring+0x91  
ffffc089`b986fa30 fffff805`74993b35     : 00000000`00000000 00000000`00000000 00000000`00000001 fffff805`74308939 : nt!MmDuplicateMemory+0x1f7  
ffffc089`b986fac0 fffff805`74271d25     : ffff8788`1c048000 ffff8788`1c048040 fffff805`74993a00 00000000`00000000 : nt!PopTransitionToSleep+0x135  
ffffc089`b986fb50 fffff805`74400778     : ffffc201`389d7180 ffff8788`1c048040 fffff805`74271cd0 00000000`00000246 : nt!PspSystemThreadStartup+0x55  
ffffc089`b986fba0 00000000`00000000     : ffffc089`b9870000 ffffc089`b9869000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28  
  
  
SYMBOL_NAME:  nt!KiSwapContext+76  
  
MODULE_NAME: nt  
  
IMAGE_NAME:  ntkrnlmp.exe  
  
STACK_COMMAND:  .process /r /p 0xffff8788060ba040; .thread 0xffff87881c048040 ; kb  
  
BUCKET_ID_FUNC_OFFSET:  76  
  
FAILURE_BUCKET_ID:  0xa0_f0_nt!KiSwapContext  
  
OS_VERSION:  10.0.19041.1  
  
BUILDLAB_STR:  vb_release  
  
OSPLATFORM_TYPE:  x64  
  
OSNAME:  Windows 10  
  
FAILURE_ID_HASH:  {168f8d2f-e77e-7dcf-020c-035a9129b0ab}  
  
Followup:     MachineOwner  
---------  
  
12: kd> !blackboxbsd  
Version: 0xb0  
Product type: 1  
  
Auto advanced boot: FALSE  
Advanced boot menu timeout: 30  
Last boot succeeded: TRUE  
Last boot shutdown: FALSE  
Sleep in progress: FALSE  
  
Power button timestamp: 0x0  
System running: TRUE  
Connected standby in progress: FALSE  
User shutdown in progress: FALSE  
System shutdown in progress: FALSE  
Sleep in progress: 4  
Connected standby scenario instance id: 0  
Connected standby entry reason: 0  
Connected standby exit reason: 0  
System sleep transitions to on: 1  
Last reference time: 0x1d8f0775c58642e  
	2022-11-04T18:00:44.850Z  
Last reference time checksum: 0x96d3fbdf  
Last update boot id: 59  
  
Boot attempt count: 1  
Last boot checkpoint: TRUE  
Checksum: 0x35  
Last boot id: 59  
Last successful shutdown boot id: 58  
Last reported abnormal shutdown boot id: 58  
  
Error info boot id: 0  
Error info repeat count: 0  
Error info other error count: 0  
Error info code: 0  
Error info status: 0x0  
  
Power button last press time: 0x0  
Power button cumulative press count: 0  
Power button last press boot id: 0  
Power button last power watchdog stage: 0  
Power button watchdog armed: FALSE  
Power button shutdown in progress: FALSE  
Power button last release time: 0x0  
Power button cumulative release count: 0  
Power button last release boot id: 0  
Power button error count: 0  
Power button current connected standby phase: 0  
Power button transition latest checkpoint id: 0  
Power button transition latest checkpoint type: 0  
Power button transition latest checkpoint sequence number: 0  
  
Power transition Shutdown Device Type: 0  
Power transition Setup In Progress: FALSE  
Power transition OOBE In Progress: FALSE  
Power transition Sleep Checkpoint Source: 0  
Power transition Sleep Checkpoint: 0  
Power transition Connected Standby Entry Reason Category: 0  
Power transition Connected Standby Exit Reason Category: 0  
Power transition Connected Standby Entry Scenario Instance Id: 0x0  
  
Feature Configuration State : Uninitialized  
  
12: kd> !blackboxntfs  
  
NTFS Blackbox Data  
  
Record 0:  
  Record type:    1 (Slow I/O Timeout)  
  Record length:  32  
        Irp:      ffff87881a9f8a20  
        Scb:      ffff9f0efbccf170  
        Thread:   ffff87881ab61040  
  
Record 1:  
  Record type:    1 (Slow I/O Timeout)  
  Record length:  32  
        Irp:      ffff87880d9b5950  
        Scb:      ffff9f0eff7e9470  
        Thread:   ffff87881ab63040  
  
Record 2:  
  Record type:    1 (Slow I/O Timeout)  
  Record length:  32  
        Irp:      ffff87881faee520  
        Scb:      ffff9f0f01291170  
        Thread:   ffff87881ab92040  
  
Record 3:  
  Record type:    1 (Slow I/O Timeout)  
  Record length:  32  
        Irp:      ffff87881e5a7010  
        Scb:      ffff87880e89c060  
        Thread:   ffff87881ab91040  
  
Record 4:  
  Record type:    1 (Slow I/O Timeout)  
  Record length:  32  
        Irp:      ffff87881e67a010  
        Scb:      ffff9f0f090e0700  
        Thread:   ffff87881fe91080  
  
Record 5:  
  Record type:    1 (Slow I/O Timeout)  
  Record length:  32  
        Irp:      ffff87881c9ef970  
        Scb:      ffff87880e89cd40  
        Thread:   ffff87881ab8c040  
  
6 Slow I/O Timeout Records Found  
0 Oplock Break Timeout Records Found  
12: kd> !kdexts.thread ffff87881ab61040  
THREAD ffff87881ab61040  Cid 0004.1da4  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable  
    ffffc089bb306f38  NotificationEvent  
IRP List:  
    ffff87881a9f8a20: (0006,04c0) Flags: 00060043  Mdl: ffff87881c1292d0  
Not impersonating  
DeviceMap                 ffff9f0efb6358a0  
Owning Process            ffff8788060ba040       Image:         System  
Attached Process          N/A            Image:         N/A  
Wait Start TickCount      11580          Ticks: 37621 (0:00:09:47.828)  
Context Switch Count      18574          IdealProcessor: 13  NoStackSwap  
UserTime                  00:00:00.000  
KernelTime                00:00:00.031  
Win32 Start Address nt!ExpWorkerThread (0xfffff80574252a60)  
Stack Init ffffc089bb307bd0 Current ffffc089bb306650  
Base ffffc089bb308000 Limit ffffc089bb301000 Call 0000000000000000  
Priority 13 BasePriority 13 PriorityDecrement 0 IoPriority 2 PagePriority 5  
Child-SP          RetAddr               : Args to Child                                                           : Call Site  
ffffc089`bb306690 fffff805`742130b0     : ffffc201`38863180 fffff805`ffffffff ffffd09d`843212a5 fffff805`74299e0c : nt!KiSwapContext+0x76  
ffffc089`bb3067d0 fffff805`742125df     : ffff8788`00000003 00000000`00000002 ffffc089`bb306990 fffff805`00000000 : nt!KiSwapThread+0x500  
ffffc089`bb306880 fffff805`74211e83     : ffff8788`00000000 fffff805`00000000 ffff8788`1a9f8a00 ffff8788`1ab61180 : nt!KiCommitThreadWait+0x14f  
ffffc089`bb306920 fffff805`784f3928     : ffffc089`bb306f38 00000000`00000000 ffff8788`1ee0ad00 00000000`00001000 : nt!KeWaitForSingleObject+0x233  
ffffc089`bb306a10 fffff805`784dce2f     : ffff8788`00000000 ffff8788`1ee0ad78 ffffc089`bb306b60 ffffffff`fa0a1f00 : Ntfs!NtfsWaitOnIo+0x84  
ffffc089`bb306a60 fffff805`784ea5f8     : 00000000`00000000 ffff8788`1cf147e8 ffff8788`0d95c3d0 00000000`00000000 : Ntfs!NtfsNonCachedIo+0x9bf  
ffffc089`bb306cf0 fffff805`784eed02     : ffff8788`1ee0ad78 ffff8788`1a9f8a20 ffff9f0e`fbccf170 00000000`00000000 : Ntfs!NtfsNonCachedUsaWrite+0x10c  
ffffc089`bb306db0 fffff805`784eb123     : ffff8788`1ee0ad78 ffff8788`1a9f8a20 ffffc089`bb307070 00000000`00000000 : Ntfs!NtfsCommonWrite+0x3772  
ffffc089`bb307000 fffff805`7422a6b5     : ffff8788`1c07c920 ffff8788`1a9f8a20 ffff8788`1a9f8a20 ffff8788`0d958920 : Ntfs!NtfsFsdWrite+0x1d3  
ffffc089`bb3070d0 fffff805`722270cf     : 00000000`00000006 00000000`00000000 00000000`00000000 fffff805`7421f636 : nt!IofCallDriver+0x55  
ffffc089`bb307110 fffff805`72224a03     : ffffc089`bb3071a0 ffffc089`bb307410 00000000`00000000 ffffc089`bb307448 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f  
ffffc089`bb307180 fffff805`7422a6b5     : ffff8788`1a9f8a20 fffff805`7422a6f7 00000000`0000000d fffff805`742b5804 : FLTMGR!FltpDispatch+0xa3  
ffffc089`bb3071e0 fffff805`742e4d03     : ffffc089`bb307410 ffff8788`1a9f8a20 ffff8788`21674670 ffffc089`bb3072a0 : nt!IofCallDriver+0x55  
ffffc089`bb307220 fffff805`7433def4     : 00000000`00000000 ffffc089`bb3072c0 ffff8788`21674670 fffff805`742e0555 : nt!IoSynchronousPageWriteEx+0x13b  
ffffc089`bb307260 fffff805`74247022     : 00000000`00000011 ffff9f0f`0f24f010 00000000`00000000 00000000`00000000 : nt!MiIssueSynchronousFlush+0x70  
ffffc089`bb3072e0 fffff805`742e3ce5     : ffffc089`bb3079c8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushSectionInternal+0x862  
ffffc089`bb3075b0 fffff805`74259a4d     : 00000000`00000001 ffff8788`1ab61040 00000000`00001000 00000000`00000000 : nt!MmFlushSection+0xbd  
ffffc089`bb307660 fffff805`7425a444     : ffff8788`20f248c8 00000000`00000000 00000000`00000001 ffffc089`bb307808 : nt!CcFlushCachePriv+0x6cd  
ffffc089`bb3077b0 fffff805`74260145     : ffff8788`2007f080 00000000`00000000 ffff8788`060b0b00 ffff8788`00000000 : nt!CcWriteBehindInternal+0x1f4  
ffffc089`bb307890 fffff805`74261a29     : 00000000`00000000 00000000`00000000 ffff8788`2007f080 00000000`00000000 : nt!CcWriteBehind+0x91  
ffffc089`bb307980 fffff805`74252b65     : ffff8788`1ab61040 ffff8788`1ab61040 ffff8788`060acc20 00000000`00000000 : nt!CcWorkerThread+0x259  
ffffc089`bb307ab0 fffff805`74271d25     : ffff8788`1ab61040 00000000`00000080 ffff8788`060ba040 002fe47f`bd9bbfff : nt!ExpWorkerThread+0x105  
ffffc089`bb307b50 fffff805`74400778     : ffffc201`390d9180 ffff8788`1ab61040 fffff805`74271cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55  
ffffc089`bb307ba0 00000000`00000000     : ffffc089`bb308000 ffffc089`bb301000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28  
  

Also I upload the MEMORY.Dump to onedrive, this is the url: https://1drv.ms/u/s!AjCcF1RJM1h-iXOoRr9wWkIr0Diy?e=JcZPVO.
I have been troubled by this problem for a long time, hope someone can help me solve the problem.

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,938 questions
{count} votes

Accepted answer
  1. Gary Nebbett 5,751 Reputation points
    2022-11-15T18:48:41.073+00:00

    Hello All,

    My suggestion that killing all instances of EpicWebHelper.exe before entering hibernation might be an effective measure against this bug check probably sounds rather implausible. In case it is of any use to someone, here is the (rather lengthy) explanation of why I came to that conclusion.

    INTERNAL_POWER_ERROR (a0)  
    The power policy manager experienced a fatal error.  
    Arguments:  
    Arg1: 00000000000000f0, The system failed to complete (suspend) a power transition in a timely manner.  
    Arg2: 0000000000000004, The system power state in transition. 0x4 = PowerSystemSleeping3  
    Arg3: 000000000000000e, The sleep checkpoint most recently reached. 0xE = PopSleepCheckpointSuspendDriversBefore  
    Arg4: ffffaa094b147040, A pointer to the thread currently processing the request.  
    

    The stack of the thread that initiated the bug check is:

    nt!KeBugCheckEx
    nt!PopPowerActionWatchdog+0xa5
    nt!KiProcessExpiredTimerList+0x172
    nt!KiRetireDpcList+0x5dd
    nt!KiIdleLoop+0x9e

    The stack of the thread processing the request (Arg4) is:

    nt!KiSwapContext+0x76
    nt!KiSwapThread+0x500
    nt!KiCommitThreadWait+0x14f
    nt!KeWaitForSingleObject+0x233
    nt!PopEndMirroring+0x91
    nt!MmDuplicateMemory+0x1f7
    nt!PopTransitionToSleep+0x135
    nt!PspSystemThreadStartup+0x55
    nt!KiStartSystemThread+0x28

    The “Wait Start TickCount” of this thread is 7622 and the TickCount at the time of the crash is 45937; (45937 – 7622) / 64 = 598.7 seconds. The PopPowerActionWatchdog is set at 600 seconds; the crash happens 10 minutes after initiating hibernation.

    The stack of the “ActionWorkerThread” (POP_POWER_ACTION.ActionWorkerThread, !poaction) is:

    nt!KiSwapContext+0x76
    nt!KiSwapThread+0x500
    nt!KiCommitThreadWait+0x14f
    nt!KeWaitForSingleObject+0x233
    nt!ExpWaitForResource+0x6d
    nt!ExAcquireResourceExclusiveLite+0x1fe
    nt!ExAcquireTimeRefreshLock+0x22
    nt!PoBroadcastSystemState+0x310
    nt!PopSetDevicesSystemState+0x87
    nt!PopTransitionSystemPowerStateEx+0xbfe
    nt!NtSetSystemPowerState+0x4c
    nt!KiSystemServiceCopyEnd+0x25 (TrapFrame @ ffffa90d`eaba87c0)
    nt!KiServiceLinkage
    nt!PopIssueActionRequest+0x216
    nt!PopPolicyWorkerAction+0x79
    nt!PopPolicyWorkerThread+0x94
    nt!ExpWorkerThread+0x105
    nt!PspSystemThreadStartup+0x55
    nt!KiStartSystemThread+0x28

    This thread is blocked, waiting for the “TimeRefresh” lock. Examining that lock shows:

    Resource @ nt!ExpTimeRefreshLock (0xfffff8024ce194c0)    Exclusively owned  
        Contention Count = 24  
        NumberOfExclusiveWaiters = 14  
         Threads: ffffaa094e32f580-01<*>  
      
         THREAD ffffaa094e32f580  Cid 2fac.329c  Teb: 0000002ad2aed000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable  
             ffffa90df0b16a18  NotificationEvent  
         IRP List:  
             ffffaa094dd9c570: (0006,04c0) Flags: 00060043  Mdl: ffffaa094e5d25b0  
         Not impersonating  
         DeviceMap                 ffffbd8220944db0  
         Owning Process            ffffaa0950216080       Image:         EpicWebHelper.exe  
         Attached Process          N/A            Image:         N/A  
         Wait Start TickCount      8273           Ticks: 37664 (0:00:09:48.500)  
         Context Switch Count      14             IdealProcessor: 13  
         UserTime                  00:00:00.000  
         KernelTime                00:00:00.000  
         Win32 Start Address 0x00007ffaaf11f460  
         Stack Init ffffa90df0b17bd0 Current ffffa90df0b16200  
         Base ffffa90df0b18000 Limit ffffa90df0b11000 Call 0000000000000000  
         Priority 12 BasePriority 8 PriorityDecrement 48 IoPriority 2 PagePriority 5  
         Child-SP          RetAddr               Call Site  
         ffffa90d`f0b16240 fffff802`4c4130b0     nt!KiSwapContext+0x76  
         ffffa90d`f0b16380 fffff802`4c4125df     nt!KiSwapThread+0x500  
         ffffa90d`f0b16430 fffff802`4c411e83     nt!KiCommitThreadWait+0x14f  
         ffffa90d`f0b164d0 fffff802`4e8f38b8     nt!KeWaitForSingleObject+0x233  
         ffffa90d`f0b165c0 fffff802`4e8dce2f     Ntfs!NtfsWaitOnIo+0x84  
         ffffa90d`f0b16610 fffff802`4e8d88d0     Ntfs!NtfsNonCachedIo+0x9bf  
         ffffa90d`f0b168a0 fffff802`4e8d926c     Ntfs!NtfsCommonRead+0x1eb0  
         ffffa90d`f0b16ab0 fffff802`4c42a6b5     Ntfs!NtfsFsdRead+0x1fc  
         ffffa90d`f0b16b80 fffff802`485a70cf     nt!IofCallDriver+0x55  
         ffffa90d`f0b16bc0 fffff802`485a4a03     FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f  
         ffffa90d`f0b16c30 fffff802`4c42a6b5     FLTMGR!FltpDispatch+0xa3  
         ffffa90d`f0b16c90 fffff802`4c4e4b27     nt!IofCallDriver+0x55  
         ffffa90d`f0b16cd0 fffff802`4c4f1d4a     nt!IoPageReadEx+0x1d7  
         ffffa90d`f0b16d40 fffff802`4c4ef3cd     nt!MiIssueHardFaultIo+0xb6  
         ffffa90d`f0b16d90 fffff802`4c439a48     nt!MiIssueHardFault+0x29d  
         ffffa90d`f0b16ea0 fffff802`4c60715e     nt!MmAccessFault+0x468  
         ffffa90d`f0b17040 fffff802`4c47932b     nt!KiPageFault+0x35e (TrapFrame @ ffffa90d`f0b17040)  
         ffffa90d`f0b171d0 fffff802`4c47889e     nt!RtlpLookupFunctionEntryForStackWalks+0xcb  
         ffffa90d`f0b17250 fffff802`4c47851c     nt!RtlpWalkFrameChain+0x34e  
         ffffa90d`f0b17960 fffff802`4c84f18d     nt!RtlWalkFrameChain+0x11c  
         ffffa90d`f0b179b0 fffff802`4c84f530     nt!PoDiagCaptureUsermodeStack+0x45  
         ffffa90d`f0b179e0 fffff802`4c60a9b5     nt!NtSetTimerResolution+0x1a0  
         ffffa90d`f0b17a40 00007ffb`142106b4     nt!KiSystemServiceCopyEnd+0x25 (TrapFrame @ ffffa90d`f0b17a40)  
         0000002a`d4daf458 00000000`00000000     0x00007ffb`142106b4  
      
         Threads Waiting On Exclusive Access:  
                  ffffaa094eed10c0       ffffaa094be65080       ffffaa093b47a040       ffffaa094b76d600  
                  ffffaa094c440040       ffffaa094b781040       ffffaa094b678040       ffffaa094c6f7080  
                  ffffaa094b80d080       ffffaa094b815040       ffffaa094d79a080       ffffaa094c3e4080  
                  ffffaa094d68f080       ffffaa094d79c080  
    

    The thread incurred a hard page fault while holding the lock and has now held the lock for at least 588.5 seconds while it waits for the page I/O to complete; in the meantime, 14 other threads have begun to wait to acquire it.

    The IRP looks like this:

    Irp is active with 12 stacks 5 is current (= 0xffffaa094dd9c760)  
     Mdl=ffffaa094e5d25b0: No System Buffer: Thread ffffaa094e32f580:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context  
     [N/A(0), N/A(0)]  
                0  0 00000000 00000000 00000000-00000000  
      
                            Args: 00000000 00000000 00000000 00000000  
     [N/A(0), N/A(0)]  
                0  0 00000000 00000000 00000000-00000000  
      
                            Args: 00000000 00000000 00000000 00000000  
     [N/A(0), N/A(0)]  
                0  0 00000000 00000000 00000000-00000000  
      
                            Args: 00000000 00000000 00000000 00000000  
     [N/A(0), N/A(0)]  
                0  0 00000000 00000000 00000000-00000000  
      
                            Args: 00000000 00000000 00000000 00000000  
    >[IRP_MJ_READ(3), N/A(34)]  
               10 e0 ffffaa093f4da0a0 00000000 fffff8024e4a2ff0-00000000 Success Error Cancel  
                   \Driver\disk     partmgr!PmIoCompletion  
                            Args: 00004000 00000000 2895d39b400 00000000  
     [IRP_MJ_READ(3), N/A(3)]  
               10 e0 ffffaa093f3a78d0 00000000 fffff8024e4a3f10-00000000 Success Error Cancel  
                   \Driver\partmgr  partmgr!PartitionIoCompletion  
                            Args: 4718a9b5 00000000 2895d39b400 00000000  
     [IRP_MJ_READ(3), N/A(0)]  
               10 e0 ffffaa093f43b060 00000000 fffff8024e591160-ffffaa093f3c0a40 Success Error Cancel  
                   \Driver\partmgr  volmgr!VmpReadWriteCompletionRoutine  
                            Args: 00004000 00000000 955d29b400 00000000  
     [IRP_MJ_READ(3), N/A(0)]  
                0 e0 ffffaa093f3c08f0 00000000 fffff8024f1d52c0-ffffaa093f518180 Success Error Cancel  
                   \Driver\volmgr   fvevol!FvePassThroughCompletionRdpLevel2  
                            Args: 00004000 00000000 4718a9ac 00000000  
     [IRP_MJ_READ(3), N/A(0)]  
                0 e0 ffffaa093f518030 00000000 fffff8024f3a5200-00000000 Success Error Cancel  
                   \Driver\fvevol   iorate!IoRateReadWriteCompletion  
                            Args: 00004000 00000000 955d29b400 00000000  
     [IRP_MJ_READ(3), N/A(0)]  
                0 e0 ffffaa093f3718d0 00000000 fffff8024e8f3790-ffffa90df0b16a10 Success Error Cancel  
                   \Driver\iorate   Ntfs!NtfsMasterIrpSyncCompletionRoutine  
                            Args: 00004000 00000000 955d29b400 00000000  
     [IRP_MJ_READ(3), N/A(0)]  
                0 e0 ffffaa0940c0f030 ffffaa0950133c80 fffff802485a44e0-ffffaa094ef5b010 Success Error Cancel  
                   \FileSystem\Ntfs FLTMGR!FltpPassThroughCompletion  
                            Args: 00004000 00000000 08f88400 00000000  
     [IRP_MJ_READ(3), N/A(0)]  
                0  1 ffffaa0940c395a0 ffffaa0950133c80 00000000-00000000    pending  
                   \FileSystem\FltMgr  
                            Args: 00004000 00000000 08f88400 00000000  
    

    Identifying the target storage device with !storagekd.storclass:

    Storage Class Devices  
      
    Usage Legend: B = Boot, P = Paging, D = Dump, H = Hiber, R = Removable  
      
    FDO                      # Device ID                        Usage   UP   DN  FL  
    -------------------------------------------------------------------------------  
    ffffaa093f4da0a0 [1,2]   0 WDC WD42EJRX-89BFNY0                      ?    ?   0  
    ffffaa093f408080 [1,2]   1 Samsung SSD 980 1TB              BPDH     ?    ?   1  
      
    kd>  !storagekd.storclass ffffaa093f4da0a0 2  
    Storage class device ffffaa093f4da0a0 with extension at ffffaa093f4da1f0  
      
    Classpnp Internal Information at ffffaa093f40e040  
      
        Transfer Packet Engine:  
      
         Packet          Status  DL Irp          Opcode  Sector/ListId   UL Irp  
        --------         ------ --------         ------ --------------- --------  
        ffffaa093f3e43d0  Free  ffffaa0938fced20  
        ffffaa094cf023d0  Free  ffffaa094bebb060  
        ffffaa094cf02710  Free  ffffaa094c9c1a20  
        ffffaa094cf02a50  Free  ffffaa094cd27a20  
        ffffaa094cf06cf0 Queued ffffaa094ba21b50   00   ffffaa094dce8010 \Epic Games\Launcher\Engine\Binaries\ThirdParty\CEF3\Win64\libcef.dll  
        ffffaa094cf07030  Free  ffffaa094a5b0a20  
        ffffaa094cf086f0  Free  ffffaa094d10ea20  
        ffffaa094cf08210 Queued ffffaa094d10dd00   00   ffffaa094dd9c570 \Epic Games\Launcher\Engine\Binaries\ThirdParty\CEF3\Win64\libcef.dll  
        ffffaa094cf076b0  Free  ffffaa094b8e8a60  
        ffffaa094e286710  Free  ffffaa094e0b6a70  
        ffffaa094e286090  Free  ffffaa094e241a70  
        ffffaa094e288930  Free  ffffaa094d0ab920  
        ffffaa094e287750 Queued ffffaa094d722dd0   00   ffffaa094ebcf010 \Steam\logs\steamui_system.txt  
        ffffaa094e287270  Free  ffffaa094df7ad70  
        ffffaa094cdf73f0 Queued ffffaa094e07fa70   00   ffffaa094ebe28c0 \Steam\logs\connection_log.txt  
        ffffaa094cdf7a70 Queued ffffaa094c394de0   00   ffffaa094ee65a70 \$LogFile  
        ffffaa09408ac720 Queued ffffaa094d54fde0   00   ffffaa094e2a2a30 \Epic Games\Launcher\Portal\Binaries\Win64\EpicGamesLauncher.exe  
    

    The read request is in a queue, waiting to be sent to the storage device; the storage device is not used for boot, paging, dump or hibernation; as we can see (!fxdevice), it is in a lower-power (D3) state:

            Device Object: 0xffffaa093b475050  
            DevNode: 0xffffaa093b33c780  
            UniqueId: "\_SB.PC00.SAT0.PRT5"  
            InstancePath: "SCSI\Disk&Ven_WDC&Prod_WD42EJRX-89BFNY0\4&35b87281&0&050000"  
            Device Power State: PowerDeviceD3  
            Component Count: 1  
                    Component 0: Current:F0/Deepest:F0 - ACTIVE (RefCount = 8)  
    

    libcef.dll (The Chromium Embedded Framework (CEF)) is a very large DLL (more than 100 megabytes) and has a very large PE “Exception Directory”; it also imports the routines timePeriodBegin/timePeriodEnd (which call NtSetTimerResolution) and RegisterPowerSettingNotification (which enables the DLL to learn of events like hibernation). NtSetTimerResolution walks the stack and needs to read the Exception Directory to do this on the x64 architecture.

    All of the above factors combine to cause the bug check. Killing all instances of EpicWebHelper.exe before entering hibernation would help to verify the correctness of the analysis. Moving the installation of the software that uses/includes EpicWebHelper to the system disk would be a medium term workaround.

    There is no easy “good” fix for this problem, but it is also not easy to exploit the issue to create an unprivileged tool to crash Windows; the difficulties include:

    • Patience is needed; the crash would happen 10 minutes after initiating hibernation.
    • A “non-system” disk is required to hold some DLLs.
    • The timing of the call to timePeriodBegin/timePeriodEnd has to be finely judged – after requests to the storage device have been paused but while the thread can still run.
    • Access to the exception table needs to cause a hard page fault.

    Gary


3 additional answers

Sort by: Most helpful
  1. Dillon Silzer 54,926 Reputation points
    2022-11-05T03:53:41.22+00:00

    Hi @ax h

    From looking around at similar issues (example is https://www.bleepingcomputer.com/forums/t/738781/crash-on-sleep-or-shutdown-internal-power-error-caused-by-ntoskrnlexe/) the fix usually ends up being a factory reset of Windows.

    These issues are usually driver/software related and are very time consuming to pinpoint. I'd recommend you download the "Create Windows 10 installation media" and install it to a USB drive (minimum 8 GB requirement):

    https://www.microsoft.com/en-ca/software-download/windows10

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

    If this is helpful please accept answer.


  2. Gary Nebbett 5,751 Reputation points
    2022-11-09T21:12:03.873+00:00

    Hello axh,

    This link seems particularly relevant to your issue: "Debugging Stop 0xA0 – INTERNAL_POWER_ERROR (Part 2)" (the bug check args 1 - 3 match your values). It starts with the text:

    This is quite an easy bugcheck to debug if you know [...]

    That said, and having read the link contents carefully, I downloaded your most recent dump and am still puzzling about the cause :-(

    There are however plenty of interesting ideas to follow up. I will let you know if I make any useful progress.

    Gary


  3. ax h 21 Reputation points
    2022-11-11T10:50:35.003+00:00

    Thank everyone, now I set harddisk never sleep and it works normally 3 days.

    0 comments No comments