BSOD - INTERNAL_POWER_ERROR

NKVD · March 11, 2025

Hello all,

I've recently downgraded back from Windows 11 to Windows 10 on my desktop PC, as I'm not fond of the whole Copilot/Recall direction Microsoft is going in, however I've been facing a lot of blue screens ever since.

OS: Windows 10 x64 (retail)

System: Intel Core i9-9900k / NVIDIA RTX 2070 SUPER / MSI MPG Z390 (MS 7B17) / Corsair HX750 PSU / Corsair Vengeance LPX 32GB DDR4

Hardware age: Everything is about six years old except the NVME drive (3 years old) and the RAM (4 years old).

The minidump files indicate a fault in the NVME driver, so if it helps, my system is installed on a Samsung 970 EVO 1TB. I've attached the most recent one. Analyzing it using WinDbg yields the following:

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: 00000000000022df, Incorrect checksum
Arg4: 00000000000067f4, Previous disk read's checksum

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2687

    Key  : Analysis.Elapsed.mSec
    Value: 7015

    Key  : Analysis.IO.Other.Mb
    Value: 10

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 18

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa0

    Key  : Dump.Attributes.AsUlong
    Value: 9

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0xa0_10e_0xa_HIBERSTACK_INIT_FAILED_IMAGE_stornvme.sys

    Key  : Failure.Hash
    Value: {5bbb5214-9d0b-5c7e-b2af-cfd7d39c2848}


BUGCHECK_CODE:  a0

BUGCHECK_P1: 10e

BUGCHECK_P2: a

BUGCHECK_P3: 22df

BUGCHECK_P4: 67f4

FILE_IN_CAB:  031025-6843-01.dmp

DUMP_FILE_ATTRIBUTES: 0x9
  Hiber Crash Dump
  Kernel Generated Triage Dump

ERROR_CODE: (NTSTATUS) 0xa - The environment is incorrect.

IMAGE_NAME:  stornvme.sys

MODULE_NAME: stornvme

FAULTING_MODULE: fffff80216230000 stornvme

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:  
ffff8007`2aa271e8 fffff802`145a7f1c     : 00000000`000000a0 00000000`0000010e 00000000`0000000a 00000000`000022df : nt!KeBugCheckEx
ffff8007`2aa271f0 fffff802`145b5ad1     : 00000000`00000001 ffff8902`17899d70 00000001`2c4e1000 ffff8902`3b5c8000 : nt!PopHiberChecksumHiberFileData+0xfd1c
ffff8007`2aa27250 fffff802`145b5486     : 00000000`00000000 ffff990b`3e895a58 ffff8007`2aa27350 00000000`00000002 : nt!PopRequestRead+0x7d
ffff8007`2aa272c0 fffff802`13f89274     : ffff990b`3e8958f0 00000000`00000000 00000000`00000000 fffff802`299c9270 : nt!PopDecompressCallback+0x16
ffff8007`2aa272f0 fffff802`14193752     : ffff8902`3b6ddace 00000000`0000ffda ffff8902`3b6d8000 ffffae01`0be40000 : nt!RtlpMakeXpressCallback+0x24
ffff8007`2aa27320 fffff802`1419358c     : ffffae01`0be40000 ffff8007`2aa27500 00000000`00010000 00005538`5d637615 : nt!RtlDecompressBufferXpressHuffProgress+0x1b2
ffff8007`2aa273a0 fffff802`145a82a1     : 00000000`00000001 ffff8007`2aa27500 00000000`00000000 00000000`00010000 : nt!RtlDecompressBufferProgress+0xbc
ffff8007`2aa27400 fffff802`145a7512     : 00000003`22d04000 ffff990b`3e895a58 00000000`00000001 00000000`00000001 : nt!PopDecompressHiberBlocks+0xfa2d
ffff8007`2aa27620 fffff802`14597311     : 00005538`50bdd53f ffff990b`3e895a58 ffff8007`2aa27840 00000000`00000000 : nt!PopRestoreHiberContext+0x1002a
ffff8007`2aa276b0 fffff802`14597026     : fffff802`148506a0 ffff8007`2aa27830 fffff802`148506a0 00000000`00000100 : nt!PopHandleNextState+0x241
ffff8007`2aa27700 fffff802`14596da3     : 00000000`00000100 fffff802`148506a0 000000ac`92aa233b 00000000`00989680 : nt!PopIssueNextState+0x1a
ffff8007`2aa27730 fffff802`1459a439     : ffff8007`2aa27a20 00000000`00000000 00000000`00000000 fffff802`1459a1bf : nt!PopInvokeSystemStateHandler+0x33b
ffff8007`2aa27930 fffff802`14599dda     : ffffffff`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!PopEndMirroring+0x1e9
ffff8007`2aa279f0 fffff802`14599ac5     : 00000000`00000000 00000000`00000000 00000000`00000001 ffff8902`0f8bf040 : nt!MmDuplicateMemory+0x2be
ffff8007`2aa27a80 fffff802`13f5a2b5     : ffff8902`1a47b000 ffff8902`1a47b040 fffff802`14599990 00000000`00000000 : nt!PopTransitionToSleep+0x135
ffff8007`2aa27b10 fffff802`14007728     : ffffae00`f9fec180 ffff8902`1a47b040 fffff802`13f5a260 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff8007`2aa27b60 00000000`00000000     : ffff8007`2aa28000 ffff8007`2aa21000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


IMAGE_VERSION:  10.0.19041.5553

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0xa0_10e_0xa_HIBERSTACK_INIT_FAILED_IMAGE_stornvme.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5bbb5214-9d0b-5c7e-b2af-cfd7d39c2848}

PROCESS_NAME:  Unknown

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

I tried reinstalling Windows 10 a second time, but the results are the exact same. My system blue screens when waking from sleep or when booted up. Any help is appreciated!

031025-6843-01.dmp

Bjoolz · March 11, 2025

If you wiped the drive when reinstalling, the SSD being faulty is the main suspect. We do often see issues with proper seating with M.2 drives so please re-seat it and make sure it's properly in there. Also check Samsung Magician for any firmware updates and make sure that it's not overheating. Because this is a an error reading from the hibernation file, I doubt it's heat related, but it's worth checking.

NKVD · March 12, 2025

I reseated the SSD, but have since encountered a different BSOD crash (which I've attached). Online research suggested running Windows Memory Diagnostics, which didn't turn up any issues.

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the BugCheck.
Arg2: ffffba0000202000
Arg3: 0000000000000009
Arg4: fffff8868c1c9d60

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2359

    Key  : Analysis.Elapsed.mSec
    Value: 4222

    Key  : Analysis.IO.Other.Mb
    Value: 11

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 18

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key  : Failure.Bucket
    Value: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

    Key  : Failure.Hash
    Value: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1a

BUGCHECK_P1: 61941

BUGCHECK_P2: ffffba0000202000

BUGCHECK_P3: 9

BUGCHECK_P4: fffff8868c1c9d60

FILE_IN_CAB:  031225-8250-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:  
fffff886`8c1c9bb8 fffff800`272331aa     : 00000000`0000001a 00000000`00061941 ffffba00`00202000 00000000`00000009 : nt!KeBugCheckEx
fffff886`8c1c9bc0 fffff800`2720df6d     : 00000000`00000000 fffff800`27094f61 ffffd180`178863f0 ffff70db`92c175ed : nt!MmAccessFault+0x1f9e1a
fffff886`8c1c9d60 fffff800`27038d58     : fffff886`8c1ca360 fffff800`270d752f fffff886`8c1ca460 00000000`00000000 : nt!KiPageFault+0x36d
fffff886`8c1c9ef0 fffff800`2703882f     : 00000000`00000004 00000000`00000000 ffff8383`ecf799c0 85000004`9b068821 : nt!MiComputePxeWalkAction+0x8
fffff886`8c1c9f40 fffff800`2703892b     : ffffba5d`00001010 ffff8383`ecf799c0 00000000`00000000 fffff886`8c1ca4b0 : nt!MiWalkPageTablesRecursively+0x78f
fffff886`8c1c9fe0 fffff800`2703892b     : ffffba5d`2e800008 ffff8383`ecf799c0 00000000`00000001 fffff886`8c1ca4c0 : nt!MiWalkPageTablesRecursively+0x88b
fffff886`8c1ca080 fffff800`2703892b     : ffffba5d`2e800000 ffff8383`ecf799c0 00000000`00000002 fffff886`8c1ca4d0 : nt!MiWalkPageTablesRecursively+0x88b
fffff886`8c1ca120 fffff800`2703592b     : 00000000`00000002 ffff8383`ecf799c0 fffff886`00000003 fffff886`8c1ca4e0 : nt!MiWalkPageTablesRecursively+0x88b
fffff886`8c1ca1c0 fffff800`27035211     : fffff886`8c1ca460 00000000`00000000 00000000`00000002 00000000`00000001 : nt!MiWalkPageTables+0x36b
fffff886`8c1ca2c0 fffff800`27034919     : 00000000`00000000 00000000`00000000 ffffd47f`ffffd840 00000000`00000000 : nt!MiAgeWorkingSet+0x3d1
fffff886`8c1ca7d0 fffff800`27034127     : 00000000`00000000 fffff886`8c1ca980 fffff886`8c1ca940 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x3c9
fffff886`8c1ca8c0 fffff800`270eb8c0     : fffff800`27a50cc0 fffff886`8c1ca980 00000000`00003513 ffff9980`00000200 : nt!MiProcessWorkingSets+0x227
fffff886`8c1ca960 fffff800`271bae57     : 00000000`00000002 00000000`00000002 00000000`ffffffff ffff9980`717c0180 : nt!MiWorkingSetManager+0x110
fffff886`8c1caa20 fffff800`27129935     : ffff8383`e049a040 00000000`00000080 fffff800`271bad00 00000000`00000000 : nt!KeBalanceSetManager+0x157
fffff886`8c1cab10 fffff800`27206e08     : ffff9980`717c0180 ffff8383`e049a040 fffff800`271298e0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff886`8c1cab60 00000000`00000000     : fffff886`8c1cb000 fffff886`8c1c4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

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

031225-8250-01.dmp

Bjoolz · March 13, 2025

7 hours ago, NKVD said:

I reseated the SSD, but have since encountered a different BSOD crash (which I've attached). Online research suggested running Windows Memory Diagnostics, which didn't turn up any issues.

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the BugCheck.
Arg2: ffffba0000202000
Arg3: 0000000000000009
Arg4: fffff8868c1c9d60

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2359

    Key  : Analysis.Elapsed.mSec
    Value: 4222

    Key  : Analysis.IO.Other.Mb
    Value: 11

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 18

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key  : Failure.Bucket
    Value: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

    Key  : Failure.Hash
    Value: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1a

BUGCHECK_P1: 61941

BUGCHECK_P2: ffffba0000202000

BUGCHECK_P3: 9

BUGCHECK_P4: fffff8868c1c9d60

FILE_IN_CAB:  031225-8250-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:  
fffff886`8c1c9bb8 fffff800`272331aa     : 00000000`0000001a 00000000`00061941 ffffba00`00202000 00000000`00000009 : nt!KeBugCheckEx
fffff886`8c1c9bc0 fffff800`2720df6d     : 00000000`00000000 fffff800`27094f61 ffffd180`178863f0 ffff70db`92c175ed : nt!MmAccessFault+0x1f9e1a
fffff886`8c1c9d60 fffff800`27038d58     : fffff886`8c1ca360 fffff800`270d752f fffff886`8c1ca460 00000000`00000000 : nt!KiPageFault+0x36d
fffff886`8c1c9ef0 fffff800`2703882f     : 00000000`00000004 00000000`00000000 ffff8383`ecf799c0 85000004`9b068821 : nt!MiComputePxeWalkAction+0x8
fffff886`8c1c9f40 fffff800`2703892b     : ffffba5d`00001010 ffff8383`ecf799c0 00000000`00000000 fffff886`8c1ca4b0 : nt!MiWalkPageTablesRecursively+0x78f
fffff886`8c1c9fe0 fffff800`2703892b     : ffffba5d`2e800008 ffff8383`ecf799c0 00000000`00000001 fffff886`8c1ca4c0 : nt!MiWalkPageTablesRecursively+0x88b
fffff886`8c1ca080 fffff800`2703892b     : ffffba5d`2e800000 ffff8383`ecf799c0 00000000`00000002 fffff886`8c1ca4d0 : nt!MiWalkPageTablesRecursively+0x88b
fffff886`8c1ca120 fffff800`2703592b     : 00000000`00000002 ffff8383`ecf799c0 fffff886`00000003 fffff886`8c1ca4e0 : nt!MiWalkPageTablesRecursively+0x88b
fffff886`8c1ca1c0 fffff800`27035211     : fffff886`8c1ca460 00000000`00000000 00000000`00000002 00000000`00000001 : nt!MiWalkPageTables+0x36b
fffff886`8c1ca2c0 fffff800`27034919     : 00000000`00000000 00000000`00000000 ffffd47f`ffffd840 00000000`00000000 : nt!MiAgeWorkingSet+0x3d1
fffff886`8c1ca7d0 fffff800`27034127     : 00000000`00000000 fffff886`8c1ca980 fffff886`8c1ca940 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x3c9
fffff886`8c1ca8c0 fffff800`270eb8c0     : fffff800`27a50cc0 fffff886`8c1ca980 00000000`00003513 ffff9980`00000200 : nt!MiProcessWorkingSets+0x227
fffff886`8c1ca960 fffff800`271bae57     : 00000000`00000002 00000000`00000002 00000000`ffffffff ffff9980`717c0180 : nt!MiWorkingSetManager+0x110
fffff886`8c1caa20 fffff800`27129935     : ffff8383`e049a040 00000000`00000080 fffff800`271bad00 00000000`00000000 : nt!KeBalanceSetManager+0x157
fffff886`8c1cab10 fffff800`27206e08     : ffff9980`717c0180 ffff8383`e049a040 fffff800`271298e0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff886`8c1cab60 00000000`00000000     : fffff886`8c1cb000 fffff886`8c1c4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

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

031225-8250-01.dmp 3.45 MB · 0 downloads

This is a memory error, but memory doesn't have to mean RAM. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

With just two dump files to go by, it doesn't really narrow down the suspects. Would need like five to spot any patterns.

And if you want to test the RAM, I don't trust memory testers with DDR4 and newer. They miss bad RAM too often. Just use the PC normally with one stick at a time.