Crashing after booting from hibernate

Page 1 of 2 12 LastLast

  1. Posts : 31
    Windows 10 Education x64
       #1

    Crashing after booting from hibernate


    Sorry if this is not in the correct place since I'm not exactly seeing bluescreens when this issue happens. Though I am getting .dmp files from this issue.

    I had this PC built last month so it's relatively new. It seemed everything is working fine until I started doing hibernation. I first thought that there was a pattern of after every 3rd hibernation, the computer would crash on bootup but it seemed random. Sometimes it takes fewer hibernations, sometimes more before it happens. After pressing the power button, the computer would reach this part (just pretend the Windows logo is an MSI logo).

    Crashing after booting from hibernate-img_5a387c400a760.png

    Then it would suddenly shut down and I have to press the power button again to make it boot. Afterwards, it would bootup normally. When checking the .dmp files with BlueScreenView, it's say it's because of INTERNAL_POWER_ERROR.

    Crashing after booting from hibernate-bluescrenview1.png

    Interestingly enough, it says that the crash time happened when I initiated the hibernate. But if that was the case, then wouldn't the computer just boot up normally when powered it since it has 'already crashed'?

    For reference, I do not have this issue when booting from a shut down (with fast startup).

    I'm on the latest Windows version (22H2/19045.2728) and updates, and BIOS (7E06v14).
    Crashing after booting from hibernate Attached Files
      My Computers


  2. Posts : 43,418
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, presumably this is System 1 as you mention MSI.

    First thought- disable Fast Startup, then retry. Some people experience weird issues when using Fast Startup, although that shouldn't be in play when resuming from hibernation of course.

    Note: when cold booting using a SSD you will barely notice any benefit from Fast Startup, which primarily benefits HDDs

    Second thought- although it's a new PC so hardware should be fine- and following the text of the message- suggest you try with only the system disk in place- disconnect the others.

    There are more suggestions in the error message too.
      My Computers


  3. Posts : 885
    10 Pro/11 Pro Dual Boot
       #3

    Rain08 said:
    Sorry if this is not in the correct place since I'm not exactly seeing bluescreens when this issue happens. Though I am getting .dmp files from this issue.

    I had this PC built last month so it's relatively new. It seemed everything is working fine until I started doing hibernation. I first thought that there was a pattern of after every 3rd hibernation, the computer would crash on bootup but it seemed random. Sometimes it takes fewer hibernations, sometimes more before it happens. After pressing the power button, the computer would reach this part (just pretend the Windows logo is an MSI logo).

    Crashing after booting from hibernate-img_5a387c400a760.png

    Then it would suddenly shut down and I have to press the power button again to make it boot. Afterwards, it would bootup normally. When checking the .dmp files with BlueScreenView, it's say it's because of INTERNAL_POWER_ERROR.

    Crashing after booting from hibernate-bluescrenview1.png

    Interestingly enough, it says that the crash time happened when I initiated the hibernate. But if that was the case, then wouldn't the computer just boot up normally when powered it since it has 'already crashed'?

    For reference, I do not have this issue when booting from a shut down (with fast startup).

    I'm on the latest Windows version (22H2/19045.2728) and updates, and BIOS (7E06v14).
    all dump files are identical. its not actually a power issue. I/O or disk issue. Please see highlighted below:

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    INTERNAL_POWER_ERROR (a0)
    The power policy manager experienced a fatal error.
    Arguments:
    Arg1: 000000000000010e, The disk subsystem returned corrupt data while reading from the
    hibernation file.

    Arg2: 000000000000000a
    Arg3: 0000000000009b37, Incorrect checksum
    Arg4: 00000000000084f6, Previous disk read's checksum


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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 1671

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 1692

    Key : Analysis.Init.CPU.mSec
    Value: 171

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

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


    DUMP_FILE_ATTRIBUTES: 0x9
    Hiber Crash Dump
    Kernel Generated Triage Dump

    BUGCHECK_CODE: a0

    BUGCHECK_P1: 10e

    BUGCHECK_P2: a

    BUGCHECK_P3: 9b37

    BUGCHECK_P4: 84f6

    CUSTOMER_CRASH_COUNT: 1

    STACK_TEXT:
    fffff18a`1f90f588 fffff802`6e5a4082 : 00000000`000000a0 00000000`0000010e 00000000`0000000a 00000000`00009b37 : nt!KeBugCheckEx
    fffff18a`1f90f590 fffff802`6e5b1a31 : 00000000`00000001 ffffc10f`9a849a90 00000003`87df7000 ffffc10f`c9fae000 : nt!PopHiberChecksumHiberFileData+0xf632
    fffff18a`1f90f5f0 fffff802`6e5a365b : 00000000`00000000 ffff9903`7c35a058 00000000`00000001 00000000`00000001 : nt!PopRequestRead+0x7d
    fffff18a`1f90f660 fffff802`6e593b61 : 00011cde`57e25a17 ffff9903`7c35a058 fffff18a`1f90f880 00000000`00000000 : nt!PopRestoreHiberContext+0xf923
    fffff18a`1f90f6f0 fffff802`6e59386e : fffff802`6e8503a0 fffff18a`1f90f870 fffff802`6e8503a0 00000000`00000100 : nt!PopHandleNextState+0x241
    fffff18a`1f90f740 fffff802`6e5935eb : 00000000`00000100 fffff802`6e8503a0 00000106`d9456dd6 00000000`00989680 : nt!PopIssueNextState+0x1a
    fffff18a`1f90f770 fffff802`6e596499 : fffff18a`1f90f988 00000000`00000018 00000000`00000000 fffff802`6e59621f : nt!PopInvokeSystemStateHandler+0x33b
    fffff18a`1f90f970 fffff802`6e590a6a : ffffffff`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!PopEndMirroring+0x1e9
    fffff18a`1f90fa30 fffff802`6e590755 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff802`6de0dfa9 : nt!MmDuplicateMemory+0x2be
    fffff18a`1f90fac0 fffff802`6de55485 : ffffc10f`c10f8500 ffffc10f`c10f8580 fffff802`6e590620 00000000`00000002 : nt!PopTransitionToSleep+0x135
    fffff18a`1f90fb50 fffff802`6e002cc8 : ffff8281`b4880180 ffffc10f`c10f8580 fffff802`6de55430 ffffc10f`ffffffff : nt!PspSystemThreadStartup+0x55
    fffff18a`1f90fba0 00000000`00000000 : fffff18a`1f910000 fffff18a`1f909000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


    SYMBOL_NAME: nt!PopHiberChecksumHiberFileData+f632

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    IMAGE_VERSION: 10.0.19041.2604

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: f632

    FAILURE_BUCKET_ID: 0xa0_10e_nt!PopHiberChecksumHiberFileData

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {28ba2091-a476-6f77-2dec-6241bccd4685}

    Followup: MachineOwner
    ---------
      My Computers


  4. Posts : 31
    Windows 10 Education x64
    Thread Starter
       #4

    dalchina said:
    Hi, presumably this is System 1 as you mention MSI.

    First thought- disable Fast Startup, then retry. Some people experience weird issues when using Fast Startup, although that shouldn't be in play when resuming from hibernation of course.

    Note: when cold booting using a SSD you will barely notice any benefit from Fast Startup, which primarily benefits HDDs

    Second thought- although it's a new PC so hardware should be fine- and following the text of the message- suggest you try with only the system disk in place- disconnect the others.

    There are more suggestions in the error message too.
    Yeah, the computer in concern is System 1. Sorry if that was not clear in the post.

    I will try checking the behavior with just the boot drive installed.



    tomdsr said:
    all dump files are identical. its not actually a power issue. I/O or disk issue. Please see highlighted below:
    If I'm understanding this correctly, the hiberfil.sys could potentially be corrupted? Do I just recreate the file and see if this would help alleviate the issue?
      My Computers


  5. Posts : 43,418
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #5

    Try with Fast Startup off too.

    You can use the powercfg command to remove and reinstate hiberfl.sys.
    Enable or Disable Hibernate in Windows 10
      My Computers


  6. Posts : 885
    10 Pro/11 Pro Dual Boot
       #6

    Rain08 said:
    Yeah, the computer in concern is System 1. Sorry if that was not clear in the post.

    I will try checking the behavior with just the boot drive installed.





    If I'm understanding this correctly, the hiberfil.sys could potentially be corrupted? Do I just recreate the file and see if this would help alleviate the issue?
    no, it is written when it hibernates.

    its like storing your partially done homework while you nap, except your brother changed your homework, and when you noticed, you got mad (blue screen).

    disable fast startup like was asked, and check your disks
      My Computers


  7. Posts : 31
    Windows 10 Education x64
    Thread Starter
       #7

    I forgot to mention it in the other reply, but I have already disabled fast boot as well.
      My Computers


  8. Posts : 43,418
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #8

    Fast Boot??
    Fastboot is a communications protocol used primarily with Android devices. It is implemented in a command-line interface tool of the same name and as a mode of the bootloader of Android devices.
    And use of powercfg?
      My Computers


  9. Posts : 31
    Windows 10 Education x64
    Thread Starter
       #9

    Got confused with the term, but yes, Fast Startup has been disabled.

    I have also used powercfg to disable then enable hibernate.

    I did my first hibernation with those things done last night. I shall see if this would help fix the issue.

    - - - Updated - - -

    Unfortunately, neither recreating hiberfil.sys nor disabling fast startup fixed the issue. I just had a crash again when booting the computer earlier.

    If it's going to do any further help, I have attached the .dmp file and also Power Efficiency Diagnostic Reports (which I kept doing after a hibernation issue too with my other PC back in 2018)

    The 2023-03-29--0600 one is booting from the crashed hibernation. The others were clean hibernation/boots for reference.
    Crashing after booting from hibernate Attached Files
      My Computers


  10. Posts : 885
    10 Pro/11 Pro Dual Boot
       #10

    Rain08 said:
    Got confused with the term, but yes, Fast Startup has been disabled.

    I have also used powercfg to disable then enable hibernate.

    I did my first hibernation with those things done last night. I shall see if this would help fix the issue.

    - - - Updated - - -

    Unfortunately, neither recreating hiberfil.sys nor disabling fast startup fixed the issue. I just had a crash again when booting the computer earlier.

    If it's going to do any further help, I have attached the .dmp file and also Power Efficiency Diagnostic Reports (which I kept doing after a hibernation issue too with my other PC back in 2018)

    The 2023-03-29--0600 one is booting from the crashed hibernation. The others were clean hibernation/boots for reference.
    same issue
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    INTERNAL_POWER_ERROR (a0)
    The power policy manager experienced a fatal error.
    Arguments:
    Arg1: 000000000000010e, The disk subsystem returned corrupt data while reading from the
    hibernation file.

    Arg2: 000000000000000a
    Arg3: 000000000000974a, Incorrect checksum
    Arg4: 000000000000b123, Previous disk read's checksum

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 1859

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 2598

    Key : Analysis.Init.CPU.mSec
    Value: 171

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

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

    Key : Memory.System.Errors.ScrubErrors
    Value: 6


    DUMP_FILE_ATTRIBUTES: 0x9
    Hiber Crash Dump
    Kernel Generated Triage Dump

    BUGCHECK_CODE: a0

    BUGCHECK_P1: 10e

    BUGCHECK_P2: a

    BUGCHECK_P3: 974a

    BUGCHECK_P4: b123

    CUSTOMER_CRASH_COUNT: 1

    BAD_PAGES_DETECTED: 6

    STACK_TEXT:
    ffff9606`e1037228 fffff807`405a5086 : 00000000`000000a0 00000000`0000010e 00000000`0000000a 00000000`0000974a : nt!KeBugCheckEx
    ffff9606`e1037230 fffff807`405b2a31 : 00000000`00000001 ffffa98a`142715f0 00000005`30508000 ffffa98a`509de000 : nt!PopHiberChecksumHiberFileData+0xf636
    ffff9606`e1037290 fffff807`405b23e6 : 00000000`00000000 ffffbd0c`eccaa058 ffff9606`e1037390 00000000`00000002 : nt!PopRequestRead+0x7d
    ffff9606`e1037300 fffff807`3ff87d24 : ffffbd0c`ecca9ef0 00000000`00000000 00000000`00000000 fffff807`57719110 : nt!PopDecompressCallback+0x16
    ffff9606`e1037330 fffff807`4018f6b2 : ffffa98a`50c43259 00000000`0000ff13 ffffa98a`50c3e000 ffffe501`024c0000 : nt!RtlpMakeXpressCallback+0x24
    ffff9606`e1037360 fffff807`4018f4ec : ffffe501`024c0000 ffff9606`e1037540 00000000`00010000 00031932`b87a19a3 : nt!RtlDecompressBufferXpressHuffProgress+0x1b2
    ffff9606`e10373e0 fffff807`405a540b : 00000000`00000001 ffff9606`e1037540 00000000`00000000 00000000`00010000 : nt!RtlDecompressBufferProgress+0xbc
    ffff9606`e1037440 fffff807`405a467c : 00000003`181e9000 ffffbd0c`eccaa058 00000000`00000001 00000000`00000001 : nt!PopDecompressHiberBlocks+0xf347
    ffff9606`e1037660 fffff807`40594b61 : 00031931`d0c130eb ffffbd0c`eccaa058 ffff9606`e1037880 00000000`00000000 : nt!PopRestoreHiberContext+0xf944
    ffff9606`e10376f0 fffff807`4059486e : fffff807`408505a0 ffff9606`e1037870 fffff807`408505a0 00000000`00000100 : nt!PopHandleNextState+0x241
    ffff9606`e1037740 fffff807`405945eb : 00000000`00000100 fffff807`408505a0 000002ea`aa9d4840 00000000`00989680 : nt!PopIssueNextState+0x1a
    ffff9606`e1037770 fffff807`40597499 : 00000000`00000001 ffff9606`e1037a80 00000000`00000000 fffff807`4059721f : nt!PopInvokeSystemStateHandler+0x33b
    ffff9606`e1037970 fffff807`40591a6a : ffffffff`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!PopEndMirroring+0x1e9
    ffff9606`e1037a30 fffff807`40591755 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff807`3fe0dfa9 : nt!MmDuplicateMemory+0x2be
    ffff9606`e1037ac0 fffff807`3fe55485 : ffffa98a`229d3000 ffffa98a`229d3040 fffff807`40591620 00000000`00000002 : nt!PopTransitionToSleep+0x135
    ffff9606`e1037b50 fffff807`40002d48 : ffffe500`c2b63180 ffffa98a`229d3040 fffff807`3fe55430 ffffa98a`14c47b70 : nt!PspSystemThreadStartup+0x55
    ffff9606`e1037ba0 00000000`00000000 : ffff9606`e1038000 ffff9606`e1031000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


    SYMBOL_NAME: PAGE_NOT_ZERO

    MODULE_NAME: hardware

    IMAGE_NAME: hardware_ram


    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: PAGE_NOT_ZERO_0xa0_10e

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {510b7dc8-b7df-06b0-3746-0f9e36384025}

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

    *** Memory manager detected 6 instance(s) of page corruption, target is likely to have memory corruption.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:40.
Find Us




Windows 10 Forums