BSOD problem with Dell Precision/Hibernation/Windows 11

P

pfabrice37

Member
Joined
Jul 27, 2023
Posts
15
Hi all,

Looking for some help with this one. I get a Green Screen of Death with Windows 11 (Insider Beta) on 2 Dell Precision laptops.
One is a Precision 5540 and the other a Precision 5570. Both have 64Gb ram.
They crash at random while getting out of hibernation.
What I get from the mindump with Windbg is:

Code: 
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 00000000000000f1, The system failed to complete(resume) a power transition in a timely manner.
Arg2: 0000000000000005, The system power state in transition.
Arg3: 0000000000000038, The sleep checkpoint most recently reached.
Arg4: ffffc08e046db040, A pointer to the thread currently processing the request.

STACK_TEXT: 
fffff404`315aeb00 fffff804`2ac5a365     : ffffaf81`dc051180 00000000`00000000 ffffc08d`c731f040 00000000`00000000 : nt!KiSwapContext+0x76
fffff404`315aec40 fffff804`2ac586c4     : ffffc08e`046db040 ffffc08d`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0xab5
fffff404`315aed90 fffff804`2ac57a46     : 00000000`00000000 00000000`00000001 00000000`00000015 00000029`7427f32d : nt!KiCommitThreadWait+0x134
fffff404`315aee40 fffff804`2acfc06b     : fffff804`2b63d2c0 fffff804`2b63d2c0 fffff404`315af2e0 00000000`00000000 : nt!KeWaitForSingleObject+0x256
fffff404`315af1e0 fffff804`2ac5d917     : fffff804`2b63d2c0 fffff404`315af2a8 00000000`00010224 fffff804`2adb0490 : nt!ExpWaitForResource+0x6b
fffff404`315af270 fffff804`2ac58508     : 00000000`00000005 fffff404`315af520 00000000`00000002 fffff404`315af480 : nt!ExpAcquireResourceExclusiveLite+0x317
fffff404`315af310 fffff804`2b4856c3     : fffff404`315af514 00000000`00000000 00000000`00000005 fffff404`315af480 : nt!ExAcquireResourceExclusiveLite+0x28
fffff404`315af350 fffff804`2b489849     : fffff404`315af500 fffff404`315af520 fffff404`315af3f9 00000000`00000000 : nt!PopAcquirePolicyLock+0x33
fffff404`315af380 fffff804`2b48726c     : 00000000`00000000 ffffc08d`c7359040 ffffc08d`f3992040 00000000`00000000 : nt!PopTransitionSystemPowerStateEx+0xae9
fffff404`315af460 fffff804`2ae465e5     : 00000000`00000005 fffff804`2b63f320 00000031`3176e8d3 00000031`3176cd23 : nt!NtSetSystemPowerState+0x4c
fffff404`315af630 fffff804`2ae370c0     : fffff804`2b1f5be6 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
fffff404`315af7c8 fffff804`2b1f5be6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff404`315af7d0 fffff804`2b1f6030     : 00000000`00000000 ffffc08d`c72dbc50 ffffc08e`046db040 fffff804`2ac0e2ff : nt!PopIssueActionRequest+0x25e
fffff404`315af880 fffff804`2ad1c518     : ffffc08e`046db000 00000000`00000002 00000000`ffffffff fffff804`2b749ac0 : nt!PopPolicyWorkerAction+0x80
fffff404`315af900 fffff804`2ac0dd25     : ffffc08d`00000001 ffffc08e`046db040 fffff404`315afa40 ffffc08d`c72dbc50 : nt!PopPolicyWorkerThread+0xa8
fffff404`315af940 fffff804`2acb6d67     : ffffc08e`046db040 00000000`00000206 ffffc08e`046db040 fffff804`2ac0dbd0 : nt!ExpWorkerThread+0x155
fffff404`315afb30 fffff804`2ae36794     : ffffaf81`dc851180 ffffc08e`046db040 fffff804`2acb6d10 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffff404`315afb80 00000000`00000000     : fffff404`315b0000 fffff404`315a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

The laptop is configured to do only hibernation: S1, S2, S3, S0, hybrid sleep and fast start are disabled.

I have tried many settings with the power options.
I have also run the driver verifier without finding any problem
(all drivers are up to date)

Any idea on a reason for these laptops to fail to resume from hibernation?
This has been a constant issue for more than 2 years, first with the 5540 and then with the 5570.
I can't believe that I am the only one with this issue.

Thanks for any clue or advice on how to avoid this annoying bugcheck.

Regards,

Fabrice
 
Unfortunately few of us read French, which makes reading your logs tricky. Would it be possible to change the system language to English and then run the log collector app again?
 
Please provide the following file if it exists:

Code: 
%systemroot\MEMORY.DMP

It's pretty much impossible to debug this bugcheck without it. It probably doesn't help that you're running an Insider build either.
 
Hi,

Thanks for the replies. I did not anticipated that all of the collected info would be localized in French :rolleyes:
Here is a link to an updated version of the SysnativeFileCollectionApp.zip archive
with Windows switched to US English
This is a wetransfer link because I have added the `%systemroot%\MEMORY.DMP` file which makes the archive too large for uploading here.

Regards,
 
It looks like your Intel Sound Technology driver is still in hibernation, those drivers have caused some problems in the past so it might be worthwhile checking for an update using the Intel DSA, otherwise I would disable the device and try and resume from hibernation again. It has an odd device instance path too.

Code: 
{DD8E82AE-334B-49A2-AEAE-AEB0FD5C40DD}\DetectionVerification\5&135027a5&0&0

Rich (BB code): 
5: kd> lmvm IntcOED
Browse full module list
start             end                 module name
fffff804`5a6e0000 fffff804`5a815000   IntcOED    (no symbols)          
    Loaded symbol image file: IntcOED.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\intcoed.inf_amd64_f21a18a53fedc854\IntcOED.sys
    Image name: IntcOED.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Mar  7 05:05:42 2023 (6406C626)
    CheckSum:         00138C89
    ImageSize:        00135000
    File version:     10.29.0.8719
    Product version:  10.29.0.8719
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.9 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Intel(R) Corporation
        ProductName:      Intel(R) Smart Sound Technology OED
        InternalName:     IntcOED.sys
        OriginalFilename: IntcOED.sys
        ProductVersion:   10.29.00.8719
        FileVersion:      10.29.00.8719
        FileDescription:  Intel(R) Smart Sound Technology OED
        LegalCopyright:    Intel(R) Corporation. All rights reserved.

Do you have any external peripherals connected when you go into hibernation? E.g. mouse or a keyboard
 
I disabled IntcOED and will see what happens.
This BSOD occurs at random: sometimes every wake up, sometimes I have to wait for ten wakeups.
Another clue : before going BSOD, I know that Windows is restoring because my headset tells me that Bluetooth is connected.

And yes I have a docking station with external keyboard and mouse connected most of the time.
 
Please enter the following commands from command prompt and then post the output:

Code: 
sc query IntcOED
sc qc IntcOED

There is a couple of similar devices to the one above, one of which related specifically to USB and I believe the other may have been Bluetooth, let's disable those devices too:

Code: 
sc config IntcUSB start= disabled
sc config IntcBTAu start= disabled
 
Here it is:
Code: 
C:\Windows\System32>sc query IntcOED

SERVICE_NAME: IntcOED
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 1077  (0x435)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

C:\Windows\System32>sc qc IntcOED
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: IntcOED
        TYPE               : 1  KERNEL_DRIVER
        START_TYPE         : 3   DEMAND_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : \SystemRoot\System32\DriverStore\FileRepository\intcoed.inf_amd64_f21a18a53fedc854\IntcOED.sys
        LOAD_ORDER_GROUP   : Extended Base
        TAG                : 49
        DISPLAY_NAME       : Technologie Intel® Smart Sound pour OED
        DEPENDENCIES       :
        SERVICE_START_NAME :

I disabled the other ones (IntcUSB, IntcBTAu).
These drivers are all installed by the Dell Realtek HD Audio driver package.
Let's see.
 
Unfortunately, it crashed again.
The stacktrace is the same:
Code: 
Implicit thread is now ffffcc04`5cee0040
  *** Stack trace for last set context - .thread/.cxr resets it
 # RetAddr               : Args to Child                                                           : Call Site
00 fffff800`73a5a365     : ffff9600`b8d97180 00000000`00000000 ffffcc04`17b98040 00000000`00000000 : nt!KiSwapContext+0x76
01 fffff800`73a586c4     : ffffcc04`5cee0040 ffffcc04`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0xab5
02 fffff800`73a57a46     : 00000000`00000000 00000000`00000001 00000000`000000f3 0000001b`0f70b09f : nt!KiCommitThreadWait+0x134
03 fffff800`73afc06b     : fffff800`7443d2c0 fffff800`7443d2c0 fffff989`96ac72e0 00000000`00000000 : nt!KeWaitForSingleObject+0x256
04 fffff800`73a5d917     : fffff800`7443d2c0 fffff989`96ac72a8 00000000`00010224 fffff800`73bb0490 : nt!ExpWaitForResource+0x6b
05 fffff800`73a58508     : 00000000`00000005 fffff989`96ac7520 00000000`00000002 fffff989`96ac7480 : nt!ExpAcquireResourceExclusiveLite+0x317
06 fffff800`742856c3     : fffff989`96ac7514 00000000`00000000 00000000`00000005 fffff989`96ac7480 : nt!ExAcquireResourceExclusiveLite+0x28
07 fffff800`74289849     : fffff989`96ac7500 fffff989`96ac7520 fffff989`96ac73f9 00000000`00000000 : nt!PopAcquirePolicyLock+0x33
08 fffff800`7428726c     : 00000000`00000000 ffffcc04`17b57040 ffffcc04`5c7e5040 00000000`00000000 : nt!PopTransitionSystemPowerStateEx+0xae9
09 fffff800`73c465e5     : 00000000`00000005 fffff800`7443f320 00000025`3a089d34 00000025`3a08885d : nt!NtSetSystemPowerState+0x4c
0a fffff800`73c370c0     : fffff800`73ff5be6 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0b fffff800`73ff5be6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
0c fffff800`73ff6030     : 00000000`00000000 ffffcc04`17acbcf0 ffffcc04`5cee0040 fffff800`73a0e2ff : nt!PopIssueActionRequest+0x25e
0d fffff800`73b1c518     : ffffcc04`5cee0000 00000000`00000002 00000000`fffffffb fffff800`74549ac0 : nt!PopPolicyWorkerAction+0x80
0e fffff800`73a0dd25     : ffffcc04`00000001 ffffcc04`5cee0040 fffff989`96ac7a40 ffffcc04`17acbcf0 : nt!PopPolicyWorkerThread+0xa8
0f fffff800`73ab6d67     : ffffcc04`5cee0040 00000000`00000158 ffffcc04`5cee0040 fffff800`73a0dbd0 : nt!ExpWorkerThread+0x155
10 fffff800`73c36794     : ffff9600`b8fd1180 ffffcc04`5cee0040 fffff800`73ab6d10 00000000`00000000 : nt!PspSystemThreadStartup+0x57
11 00000000`00000000     : fffff989`96ac8000 fffff989`96ac1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

The !powertriage does not report anything abnormal (AFAICS):

Code: 
6: kd> !powertriage

System Capabilities :
  Machine is not AOAC capable.

Power Capabilities:
PopCapabilities @ 0xfffff8007443d600
  Misc Supported Features:  PwrButton SlpButton Lid S4 S5 HiberFile VideoDim
  Processor Features:     
  Disk Features:           
  Battery Features:         BatteriesPresent
    Battery 0 - Capacity:        0  Granularity:        0
    Battery 1 - Capacity:        0  Granularity:        0
    Battery 2 - Capacity:        0  Granularity:        0
  Wake Caps
    Ac OnLine Wake:         Sx
    Soft Lid Wake:          Sx
    RTC Wake:               S4
    Min Device Wake:        Sx
    Default Wake:           Sx



Power Action:

PopAction :fffff8007443c9a0
    Current System State..: Hibernate
    Target System State...: Hibernate
    State.................: Set System State in progress(3)

Devices with allocated Power IRPs:

    +  PCI\VEN_8086&DEV_466E&SUBSYS_0B1A1028&REV_02\3&11583659&0&38
       0xffffcc041d2f0360 pci D3 !podev FxDevice: !fxdevice  WAIT_WAKE_IRP !irp Related Threads !rcdrlogdump
         Upper DO 0xffffcc041d0edd50 ACPI !podev
***Error in InitTypeRead for WppTraceControlBlock

           Upper DO 0xffffcc042a2f27d0 pci !podev !rcdrlogdump

    +  PCI\VEN_8086&DEV_463F&SUBSYS_0B1A1028&REV_02\3&11583659&0&39
       0xffffcc041d5e8360 pci D3 !podev FxDevice: !fxdevice  WAIT_WAKE_IRP !irp Related Threads !rcdrlogdump
         Upper DO 0xffffcc041d0efd50 ACPI !podev
***Error in InitTypeRead for WppTraceControlBlock

           Upper DO 0xffffcc0426dc6100 pci !podev !rcdrlogdump

    +  USB4\ROOT_DEVICE_ROUTER&VID_8086&PID_463E\4&300946ec&4&0
       0xffffcc042a3e45f0 Usb4HostRouter D3 !podev FxDevice: !fxdevice  WAIT_WAKE_IRP !irp Related Threads !rcdrlogdump !wdfdriverinfo !wdflogdump
         Upper DO 0xffffcc0428edadc0 Usb4DeviceRouter !podev !rcdrlogdump !wdfdriverinfo !wdflogdump

    +  USB4\VID_8087&PID_0B26\5&35a80c50&1&1
       0xffffcc042a3e9b00 Usb4DeviceRouter D3 !podev FxDevice: !fxdevice  WAIT_WAKE_IRP !irp Related Threads !rcdrlogdump !wdfdriverinfo !wdflogdump
         Upper DO 0xffffcc0428ec9db0 Usb4DeviceRouter !podev !rcdrlogdump !wdfdriverinfo !wdflogdump

And the !pnptriage reports only the devices that have been forcibly disabled:

Code: 
6: kd> !pnptriage

********************************************************************************
Dumping PnP DeviceAction Queue @ 0xfffff8007445b060
********************************************************************************


Dumped 0 entries

********************************************************************************
Dumping PnP DeviceEvent Queue @ 0xffffcc0417aa07e0
********************************************************************************

List = 0xffffcc0417aa0858, 0xffffcc0417aa0858
Event list is empty

********************************************************************************
Dumping PnP DeviceCompletion Queue @ 0xfffff8007445c5e0
********************************************************************************

0 Pnp operation(s) dispatched (IRP pending) currently.

Dumping pending asynchronous request list...

Dumping completed asynchronous request list...

********************************************************************************
Dumping devnodes with problems...
********************************************************************************

Dumping IopRootDeviceNode (= 0xffffcc0417b51860)
DevNode 0xffffcc04192efaa0 for PDO 0xffffcc0417df2df0
  InstancePath is "ROOT\NET\0001"
  ServiceName is "tapexpressvpn"
  State = DeviceNodeInitialized (0x304)
  Previous State = DeviceNodeUninitialized (0x301)
  Problem = CM_PROB_DISABLED
  Problem Status = 0x00000000
DevNode 0xffffcc041d1eea20 for PDO 0xffffcc041d1ee060
  InstancePath is "PCI\VEN_10EC&DEV_5260&SUBSYS_0B1A1028&REV_01\00000001004CE00000"
  ServiceName is "RTSPER"
  State = DeviceNodeInitialized (0x304)
  Previous State = DeviceNodeUninitialized (0x301)
  Problem = CM_PROB_DISABLED
  Problem Status = 0x00000000
DevNode 0xffffcc042a0d7b60 for PDO 0xffffcc042a3e6d60
  InstancePath is "INTELAUDIO\DSP_CTLR_DEV_51C8&VEN_8086&DEV_0222&SUBSYS_0B1A1028&REV_0001\4&30b8d0cf&8&0800"
  ServiceName is "IntcOED"
  State = DeviceNodeInitialized (0x304)
  Previous State = DeviceNodeUninitialized (0x301)
  Problem = CM_PROB_DISABLED
  Problem Status = 0x00000000

********************************************************************************
Dumping PnP locks...
********************************************************************************


Resource @ nt!PiEngineLock (0xfffff8007445c680)    Available
    Contention Count = 63
1 total locks

Resource @ nt!IopDeviceTreeLock (0xfffff8007445c780)    Available
    Contention Count = 3
1 total locks

Resource @ nt!PnpRegistryDeviceResource (0xfffff8007445c8e0)    Available
    Contention Count = 1865
1 total locks

********************************************************************************
If one or more of above are NOT available, do !thread on the owner thread to find the thread hung in PnP
********************************************************************************


********************************************************************************
Dumping currently active PnP thread (if any)...
********************************************************************************

No active Pnp thread found!
 
Could you please provide the latest MEMORY.DMP file?

It might be worthwhile enabling Driver Verifier using these instructions but I would only recommend enabling the following settings: Force Pending I/O Request and DDI Compliance Checking.
 
Here is the link to the memory.dmp file (zipped)
memory.dmp.zip
I will try the driver verifier. I did it before posting it but without any result. I set DDI Compliance Checking. Don't remember about Force Pending I/O though.
 
Forgive my intrustion, but since this is an insider build should this issue not be reported to Microsoft via the Feedback Hub? Catching these kinds of problems is what insider builds are for, isn't it?
 
I have reported the problem on the MS feedback hub with no answer.
I have reported the problem to Dell with the usual answer: make sure your drivers are up to date :-/
Maybe I should ask them to escalate this issue.
I am quite convinced that it is something else than drivers and that it would be the same with a regular Windows 11.
I am running Insiders beta 22H2, this is the 22000 series which is out for quite some time now, not the 23000 nor 25000.
But more importantly: I had already the exact same issue 2 years ago with a Precision 5540, and the windows version from 2 years back.
So I was quite surprised to find this issue again with this new hardware and new Windows 11.

My hope in looking for help here was that someone with a good (better than mine) knowledge of windbg and Windows internals could help
tracing what's happening, assuming that memory.dmp would be enough for that. And possibly finding a workaround.
 
Last edited:
Fair enough, but we generally assume that Microsoft modules are perfect. With an insider build it's not possible to be that certain.
 
I will add some observations to my problem:
- the stack trace may be irrelevant to the problem. Especially the call to nt!NtSetSystemPowerState+0x4c is a call to *shutdown* the system while it should be resuming. So is this stack trace about entering the BSOD? Am I wrong?
- the problem could well happen when the system is hibernating and not when it is resuming. How to trace that?
 
A trace wouldn't be particularly helpful here unfortunately because your crashes are too inconsistent. It would be worthwhile if it was consistently crashing when you tried to resume from sleep/hibernation. Most bugchecks don't have a straightforward answer unless a driver has a very blatant bug with it. If you wanted to do a trace then you could use xbootmgr from the WPA (Windows Performance Toolkit) but I'm not sure what the configuration settings are for it.

pfabrice37 said:
Especially the call to nt!NtSetSystemPowerState+0x4c is a call to *shutdown* the system while it should be resuming. So is this stack trace about entering the BSOD? Am I wrong?
Click to expand...
Hmm sort of, the call stack will always lead to the bugcheck, you read it from the bottom up, with the nt!KeBugCheckEx being the last call.

Rich (BB code): 
6: kd> knL
 # Child-SP          RetAddr               Call Site
00 fffff989`99c1f898 fffff800`73da663a     nt!KeBugCheckEx << BSOD is issued to the operating system
01 fffff989`99c1f8a0 fffff800`73a0dd25     nt!PopStateTransitionTimeoutDispatch+0xea << Throws a timeout exception
02 fffff989`99c1f940 fffff800`73ab6d67     nt!ExpWorkerThread+0x155
03 fffff989`99c1fb30 fffff800`73c36794     nt!PspSystemThreadStartup+0x57
04 fffff989`99c1fb80 00000000`00000000     nt!KiStartSystemThread+0x34

It would seem to be that way if you look at the documentation for that function you mentioned, however, looking at the code from ReactOS it seems that it takes a power action object and then decides the power transition based on that. Additionally, much of the dump file appears to be contrary to a possible shutdown as well.

It looks like the third parameter is actually an enumeration too which describes the checkpoint:

Rich (BB code): 
6: kd> dt _POP_SLEEP_CHECKPOINT
nt!_POP_SLEEP_CHECKPOINT
   PopSleepCheckpointInvalid = 0n0
   PopSleepCheckpointPowerTransitionStart = 0n1
   PopSleepCheckpointSuspendAppsBefore = 0n2
   PopSleepCheckpointSuspendAppsAfter = 0n3
   PopSleepCheckpointSuspendServicesBefore = 0n4
   PopSleepCheckpointSuspendServicesAfter = 0n5
   PopSleepCheckpointNotifySuperfetchBefore = 0n6
   PopSleepCheckpointNotifySuperfetchAfter = 0n7
   PopSleepCheckpointNotifyCallbacksBefore = 0n8
   PopSleepCheckpointNotifyCallbacksAfter = 0n9
   PopSleepCheckpointSleepTransactionCommitted = 0n10
   PopSleepCheckpointQueryDriversBefore = 0n11
   PopSleepCheckpointQueryDriversAfter = 0n12
   PopSleepCheckpointAllocatingHiberContext = 0n13
   PopSleepCheckpointSuspendDriversBefore = 0n14
   PopSleepCheckpointPreSleepNotification = 0n16
   PopSleepCheckpointInterruptsDisabledBegin = 0n17
   PopSleepCheckpointInvokeHandlerBefore = 0n18
   PopSleepCheckpointSaveHiberContextBegin = 0n19
   PopSleepCheckpointInitializeDumpStackFailed = 0n20
   PopSleepCheckpointHiberWriteFailed = 0n21
   PopSleepCheckpointHiberFileTooSmall = 0n22
   PopSleepCheckpointSaveHiberContextFailed = 0n23
   PopSleepCheckpointSaveHiberContextEnd = 0n24
   PopSleepCheckpointHiberKernelHandoff = 0n25
   PopSleepCheckpointInvokeHandlerAfter = 0n26
   PopSleepCheckpointReadHiberfileBefore = 0n27
   PopSleepCheckpointInitializeDumpStackForReadFailed = 0n28
   PopSleepCheckpointHiberReadFailed = 0n29
   PopSleepCheckpointChecksumFailure = 0n30
   PopSleepCheckpointDecompressionFailed = 0n31
   PopSleepCheckpointReadHiberfileAfter = 0n32
   PopSleepCheckpointInterruptsDisabledEnd = 0n33
   PopSleepCheckpointWakeDriversAfter = 0n36
   PopSleepCheckpointResumeAppsBefore = 0n37
   PopSleepCheckpointResumeAppsAfter = 0n38
[...]

None of these values are properly documented by Microsoft so it would be difficult to say what exactly it means but presumbly, it suggests that any application threads should be resumed after this checkpoint is reached.

If you look at the power action structure too, then it seems we are certainly waking from hibernation, which does fit with the situation you've described of having a BSOD when resuming from hiberation.

Rich (BB code): 
6: kd> dt _POP_POWER_ACTION fffff8007443c9a0
nt!_POP_POWER_ACTION
   +0x000 Updates          : 0 ''
   +0x001 State            : 0x3 ''
   +0x002 Shutdown         : 0 '' << FALSE
   +0x004 Action           : 2 ( PowerActionSleep )
   +0x008 LightestState    : 5 ( PowerSystemHibernate )
   +0x00c Flags            : 0x80000004
   +0x010 Status           : 0n0
   +0x014 DeviceType       : 7 ( PolicySystemIdle )
   +0x018 DeviceTypeFlags  : 0
   +0x01c IrpMinor         : 0x2 ''
   +0x01d Waking           : 0x1 ''
   +0x020 SystemState      : 5 ( PowerSystemHibernate )
   +0x024 NextSystemState  : 1 ( PowerSystemWorking )
   +0x028 EffectiveSystemState : 5 ( PowerSystemHibernate )
   +0x02c CurrentSystemState : 5 ( PowerSystemHibernate )
   +0x030 ShutdownBugCode  : (null)
   +0x038 DevState         : (null)
   +0x040 HiberContext     : 0xffffcc04`1e7fdd70 _POP_HIBER_CONTEXT
   +0x048 WakeTime         : 0x0000002d`abc17024
   +0x050 SleepTime        : 0x00000025`3a244439
   +0x058 WakeFirstUnattendedTime : 0
   +0x060 WakeAlarmSignaled : 3 ( PoConditionMaximum )
   +0x068 WakeAlarm        : [3] <unnamed-tag>
   +0x0b0 WakeAlarmPaused  : 0x1 ''
   +0x0b8 WakeAlarmLastTime : 0
   +0x0c0 DozeDeferralStartTime : 0
   +0x0c8 FilteredCapabilities : SYSTEM_POWER_CAPABILITIES
   +0x118 WatchdogLock     : 0
   +0x120 WatchdogDpc      : _KDPC
   +0x160 WatchdogTimer    : _KTIMER
   +0x1a0 WatchdogInitialized : 0x1 ''
   +0x1a4 WatchdogState    : 2 ( PopPowerActionWatchdogStateResuming )
   +0x1a8 WatchdogStartTime : 0x00000025`3a4475c6
   +0x1b0 WatchdogTimeout  : 0x12c
   +0x1b8 ActionWorkerThread : 0xffffcc04`5cee0040 _KTHREAD
   +0x1c0 PromoteActionWorkerThread : (null)
   +0x1c8 UnlockAfterSleepWorkerThread : (null)



It might be worth not using the docking station with the mouse and keyboard and see if the issue persists. Unfortunately, these types of bugchecks can be a matter of trial and error but usually !devpowerstate complete can be useful in examing which power states individual devices were in at the time of the crash.
 
Well, I did quite many tests. I even reinstalled a clean image of my current OS Windows 11 beta.
I had tens of resume from hibernation without a glitch, and I got 2 crashes today.

I used the RecentEvents.ps1 script (from EventID 28 error - Microsoft Q&A) to gather
all events logged into a single listing and found this:

8/14/2023 20:03 158 Microsoft-Windows-Kernel-Boot/Operational Error "Error: BL_LOG_ERROR_RES_INVALID_PAGEFILE: Page file is invalide for hibernate resume. Status: {Operation Failed}
The requested operation was unsuccessful."
8/14/2023 20:03 32 System Information The bootmgr spent 0 ms waiting for user input.
8/14/2023 20:03 18 System Information There are 0x1 boot options on this system.
8/14/2023 20:03 16 System Error Windows failed to resume from hibernate with error status 0xC0000001.

Unfortunately, I can't find any reference to BL_LOG_ERROR_RES_INVALID_PAGEFILE anywhere.
I did a scan of the drive (SSD M2) with chkdsk but there were no error. The pagefile is 1.5x th RAM size.

I guess my next try will be to stop Windows Insiders updates at the next release and use a stable image for some time.

Thanks for your help.
I will be listening if anybody comes with a clue.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top