F5F Stay Refreshed Hardware Desktop Error code BSOD with internal power issue detected.

Error code BSOD with internal power issue detected.

Error code BSOD with internal power issue detected.

M
Mr_Floobiful
Posting Freak
890
09-16-2021, 08:50 PM
#1
Hello everyone, I recently switched back to Windows 10 on my desktop after downgrading from Windows 11. I’m not comfortable with the Copilot/Recall features Microsoft is promoting, but I’ve been seeing a lot of blue screens now. My setup is Windows 10 x64 (official) with Intel Core i9-9900k / NVIDIA RTX 2070, MSI MPG Z390 (MS 7B17), Corsair HX750 PSU, and Corsair Vengeance LPX 32GB DDR4. The hardware is around six years old except for the NVME drive (about three years) and RAM (four years). According to the minidump files, there’s a driver issue in the NVME module, and WinDbg analysis shows:

- Power policy manager failed with corrupt disk data during hibernation.
- Checksum mismatch detected.
- Kernel generated a hibersterror image.

The crash dump points to a hiberstack initial failure in the stornvme.sys module. I’ve attached the latest dump for reference.

Analyzing it further reveals:
- CPU and memory performance metrics.
- A legacy API bug (code.lifecycle).
- Kernel-generated triage data indicating a system instability.

If you need more details, just let me know!
M
Mr_Floobiful
09-16-2021, 08:50 PM #1

Hello everyone, I recently switched back to Windows 10 on my desktop after downgrading from Windows 11. I’m not comfortable with the Copilot/Recall features Microsoft is promoting, but I’ve been seeing a lot of blue screens now. My setup is Windows 10 x64 (official) with Intel Core i9-9900k / NVIDIA RTX 2070, MSI MPG Z390 (MS 7B17), Corsair HX750 PSU, and Corsair Vengeance LPX 32GB DDR4. The hardware is around six years old except for the NVME drive (about three years) and RAM (four years). According to the minidump files, there’s a driver issue in the NVME module, and WinDbg analysis shows:

- Power policy manager failed with corrupt disk data during hibernation.
- Checksum mismatch detected.
- Kernel generated a hibersterror image.

The crash dump points to a hiberstack initial failure in the stornvme.sys module. I’ve attached the latest dump for reference.

Analyzing it further reveals:
- CPU and memory performance metrics.
- A legacy API bug (code.lifecycle).
- Kernel-generated triage data indicating a system instability.

If you need more details, just let me know!

X
xX_Verdy_Xx
Junior Member
17
09-16-2021, 11:34 PM
#2
If you cleared the drive during reinstallation, the faulty SSD is likely the issue. We frequently encounter problems with correct placement of M.2 drives—re-seat it and confirm it’s firmly installed. Also, verify Samsung Magician for any firmware updates and ensure the device isn’t overheating. Since this appears as an error in the hibernation file, heat probably isn’t the cause, but it’s worth investigating.
X
xX_Verdy_Xx
09-16-2021, 11:34 PM #2

If you cleared the drive during reinstallation, the faulty SSD is likely the issue. We frequently encounter problems with correct placement of M.2 drives—re-seat it and confirm it’s firmly installed. Also, verify Samsung Magician for any firmware updates and ensure the device isn’t overheating. Since this appears as an error in the hibernation file, heat probably isn’t the cause, but it’s worth investigating.

Y
Yoshix
Member
228
09-19-2021, 01:11 AM
#3
I replaced the SSD again, but now faced another BSOD (attached). Research online suggested using Windows Memory Diagnostics, though it didn’t find any problems. At 8: kd> !analyze -v ******************************************************************** Bugcheck Analysis MEMORY_MANAGEMENT (1a) – Additional checks needed. Parameters: Arg1: 0000000000061941, Bugtype: ffffba0000202000, Arg2: 0000000000000009, Arg4: fffff8868c1c9d60 Debugging info: Key values: CPU mSec 2359, Elapsed mSec 4222, IO.Other.Mb 11, Init.CPU.mSec 1015, Init.Elapsed.mSec 24001, Memory commit peak 88 MB. Other details include debug codes and file paths. No issues detected in diagnostics. * * * Online advice: ran memory tests but no faults appeared. * * * Machine status: crash occurred once; process name svchost.exe. Stack trace fffff886`8c1c9bb8.*
Y
Yoshix
09-19-2021, 01:11 AM #3

I replaced the SSD again, but now faced another BSOD (attached). Research online suggested using Windows Memory Diagnostics, though it didn’t find any problems. At 8: kd> !analyze -v ******************************************************************** Bugcheck Analysis MEMORY_MANAGEMENT (1a) – Additional checks needed. Parameters: Arg1: 0000000000061941, Bugtype: ffffba0000202000, Arg2: 0000000000000009, Arg4: fffff8868c1c9d60 Debugging info: Key values: CPU mSec 2359, Elapsed mSec 4222, IO.Other.Mb 11, Init.CPU.mSec 1015, Init.Elapsed.mSec 24001, Memory commit peak 88 MB. Other details include debug codes and file paths. No issues detected in diagnostics. * * * Online advice: ran memory tests but no faults appeared. * * * Machine status: crash occurred once; process name svchost.exe. Stack trace fffff886`8c1c9bb8.*

R
Royalsalt
Junior Member
16
09-23-2021, 07:27 AM
#4
Memory issues can occur due to misinterpretation of storage types. Windows moves data from RAM to the page file when needed, making it appear as memory. The CPU handles the memory controller, and failure here may seem like a memory problem. With only two dump files, identifying patterns is challenging. For testing RAM, avoid relying on testers for DDR4 and newer models—they often miss faults. Use the PC normally with one stick at a time.
R
Royalsalt
09-23-2021, 07:27 AM #4

Memory issues can occur due to misinterpretation of storage types. Windows moves data from RAM to the page file when needed, making it appear as memory. The CPU handles the memory controller, and failure here may seem like a memory problem. With only two dump files, identifying patterns is challenging. For testing RAM, avoid relying on testers for DDR4 and newer models—they often miss faults. Use the PC normally with one stick at a time.