BSOD INTERNAL POWER ERROR After Hibernation Mode

I completed a MemTest86+ test overnight (18 passes), and all appears to be good...

Hello and sorry for the delay in any response - I think it was because you had added additional information in a new post and it looked as if someone had answered. I tend to look for unanswered posts and I had missed it.

Looking at the history you have had several recent bugchecks and they all occurred after a hibernation error.

Code:

2019-02-25T11:37:36.761  Windows failed to resume from hibernate with error status 0xC0000411.
2019-02-25T19:05:07.418  The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000a0 (0x0000000000000608, 0xffffde0cfcbd9018, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: fa1e3281-803b-441f-a79e-93a444a417bb.
2019-02-27T12:33:53.428  The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000a0 (0x0000000000000608, 0xffffbc822bfce018, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: e3a7139e-533c-4dab-af1d-7db6e1069105.
2019-03-01T11:52:50.739  Windows failed to resume from hibernate with error status 0xC0000001.
2019-03-01T11:53:12.922  The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000a0 (0x0000000000000608, 0xffffa002ba3d3018, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 36056ad4-3b68-49d8-a563-18fec8317096.
2019-03-01T16:35:59.733  Windows failed to resume from hibernate with error status 0xC0000001.
2019-03-01T16:36:20.043  The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000a0 (0x0000000000000608, 0xffff9702313d7018, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 8ea7344c-a9b0-4b97-a7c7-596d0da5c4df.
2019-03-03T19:55:24.949  Windows failed to resume from hibernate with error status 0xC0000001.
2019-03-03T19:55:53.076  The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000a0 (0x0000000000000608, 0xffffb4822afd0018, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 4aef4fca-149b-4812-80f0-205425248164.
2019-03-05T07:52:58.732  Windows failed to resume from hibernate with error status 0xC0000001.
2019-03-05T07:53:25.624  The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000a0 (0x0000000000000608, 0xffffab8ddf1cd018, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 1150a97f-f42f-4f58-8933-b5d9181c09a3.
2019-03-05T16:51:51.733  Windows failed to resume from hibernate with error status 0xC0000001.
2019-03-05T16:52:09.432  The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000a0 (0x0000000000000608, 0xffff82035f5d0018, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\030519-16625-01.dmp. Report Id: b5f8b51b-a8e8-4b3b-9029-71de58b340b9.

There have also been a number of Fast Startup failures:

Code:

2019-02-24T22:37:18.711        Windows failed fast startup with error status 0xC00000D4.
2019-02-24T23:18:13.759        Windows failed fast startup with error status 0xC00000D4.
2019-02-25T15:43:36.714        Windows failed fast startup with error status 0xC00000D4.
2019-02-25T19:04:45.723        Windows failed fast startup with error status 0xC0000001.
2019-02-26T06:19:36.761        Windows failed fast startup with error status 0xC00000D4.
2019-02-26T08:06:24.769        Windows failed fast startup with error status 0xC00000D4.
2019-02-27T12:33:25.717        Windows failed fast startup with error status 0xC0000001.
2019-02-27T15:17:40.726        Windows failed fast startup with error status 0xC00000D4.
2019-02-27T22:32:50.719        Windows failed fast startup with error status 0xC00000D4.
2019-02-28T08:33:26.719        Windows failed fast startup with error status 0xC00000D4.
2019-02-28T17:09:06.763        Windows failed fast startup with error status 0xC00000D4.
2019-02-28T17:16:48.767        Windows failed fast startup with error status 0xC00000D4.
2019-02-28T21:20:09.732        Windows failed fast startup with error status 0xC00000D4.
2019-03-02T01:06:37.771        Windows failed fast startup with error status 0xC00000D4.
2019-03-03T14:21:28.732        Windows failed fast startup with error status 0xC00000D4.
2019-03-03T14:46:27.739        Windows failed fast startup with error status 0xC00000D4.
2019-03-03T14:51:59.732        Windows failed fast startup with error status 0xC00000D4.
2019-03-04T16:44:53.779        Windows failed fast startup with error status 0xC00000D4.
2019-03-04T20:47:33.732        Windows failed fast startup with error status 0xC00000D4.
2019-03-05T06:13:40.732        Windows failed fast startup with error status 0xC00000D4.

All this suggests that there is something wrong with the hibernation mechanism. The simplest approach is to turn off hibernation and Fast Startup and see if things improve.

Turn On or Off Fast Startup in Windows 10

Enable or Disable Hibernate in Windows 10

If you need hibernation then please refer to:
https://support.microsoft.com/en-us/help/3211190/fast-startup-causes-hibernation-or-shutdown-to-fail-in-windows-10-wind


To actually fix this you may also need to reinstall the chipset drivers for your motherboard and check if there are any firmware updates for the new drives you have added.

Thanks for the reply Phil!

I will turn off hibernation and Fast Startup and report back with results...

Phil,

I have an update (below), but first--going back to your original reply--I want to inform you that I already reinstalled the chipset drivers for my motherboard and installed the latest firmware updates for my new Samsung drives. I did this during the initial upgrade before the BSODs.

Now for the update: I turned off Fast Startup and hibernation, but another issue has cropped up. And for the record, this same issue actually occurred this morning BEFORE I turned off Fast Startup and hibernation:

- I let the computer go to 'sleep.'
- Upon attempting to awake the computer it sounded like it was starting up (I could hear the fans crank up, etc. etc), however there was nothing on my screen; it was a black, blank screen. It wasn't a BSOD, but I noticed a mini-dump file was created. This is random and does not happen every time.

So, all together today I've had two of these occurrences and one INTERNAL_POWER_ERROR bsod.

I have attached a zip with all three mini dump files from today.

(Note: I managed to download and install the Beta Log Collector, but I still do not know how to read these files; as a result of my current issue, I'm hoping to delve in to this a little deeper--in the meantime, your time and assistance is greatly appreciated!)

These recent crashes are all Internal Power errors however, the two that did not create the blue screen are associated with the Samsung secnvme.sys driver. This might be a clue as to what the problem is, driver needs updating or possibly trying an older driver might work. Check on the Samsung forums in case there are any known problems with this drive.

Looking at the rawstack I can see this driver and one other that could be involved: ASMedia USB 3.0 driver. This gives you two drivers to work on updating.

Code:

10: kd> .load pde;!dpx
=========================================================================================
 PDE v11.3 - Copyright 2017 Andrew Richards
=========================================================================================
Start memory scan  : 0xffff8308024bf648 ($csp)
End memory scan    : 0xffff8308024c0000 (Kernel Stack Base)

               rsp : 0xffff8308024bf648 : 0xfffff8006a4e6a4c : nt!PopFxBugCheck+0x1c
0xffff8308024bf648 : 0xfffff8006a4e6a4c : nt!PopFxBugCheck+0x1c
0xffff8308024bf6a8 : 0xfffff8006a2d5862 : nt!KiChooseTargetProcessor+0x172
0xffff8308024bf6e8 : 0xfffff8006a34058e : nt!PoFxIdleComponent+0xe
0xffff8308024bf708 : 0xffff8308024bf840 :  !da "74371875"
0xffff8308024bf718 : 0xfffff8006a3a00d7 : nt!vsnprintf_l+0x5b
0xffff8308024bf730 : 0xffff8308024bf840 :  !da "74371875"
0xffff8308024bf748 : 0xfffff8006a28dc87 : nt!vDbgPrintExWithPrefixInternal+0x57
0xffff8308024bf758 : 0xfffff80cb9740a6a : storport!RaidAdapterPoFxIdleComponent+0x1a
0xffff8308024bf760 : 0xffff8308024bf840 :  !da "74371875"
*** WARNING: Unable to verify timestamp for secnvme.sys
0xffff8308024bf788 : 0xfffff80cb9753b2c : storport!RaidAdapterPoFxIdleComponentFromMiniport+0xc
0xffff8308024bf7b8 : 0xfffff80cb972299a : storport!StorPortExtendedFunction+0x97a
0xffff8308024bf7c8 : 0xfffff8006a4fc1a8 : nt!vDbgPrintExWithPrefix+0x18
0xffff8308024bf808 : 0xfffff80cb973fed0 : storport!StorPortDebugPrint+0xc0
0xffff8308024bf820 : 0xfffff80cb9771c50 :  !da ""%I64u - STORMINI: ""
0xffff8308024bf840 : 0x3537383137333437 :  !da "74371875"
0xffff8308024bf8c8 : 0xfffff80cb972b7bb : storport!StorportTimerDpc+0x4b
0xffff8308024bf918 : 0xfffff8006a2c8659 : nt!KiProcessExpiredTimerList+0x159
0xffff8308024bf968 : 0xfffff80cb972b770 : storport!StorportTimerDpc
0xffff8308024bfa08 : 0xfffff8006a2c95a7 : nt!KiRetireDpcList+0x4a7
Unable to load image asmtxhci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for asmtxhci.sys
0xffff8308024bfaf0 : 0xfffff80cb972b770 : storport!StorportTimerDpc
0xffff8308024bfc18 : 0xfffff8006a3c7ffa : nt!KiIdleLoop+0x5a

I updated the ASMedia USB 30 drivers and after a few wake up cycles had another INTERNAL_POWER_ERROR bsod. The new dump file is attached. I will now move onto the Samsung secnvme.sys driver to see if that helps.

OK, keep us posted.

philc43 said:

OK, keep us posted.

Will do, Phil--but I feel extremely confident that the Samsung secnvme.sys driver is the culprit. I just spent the last 30-40 minutes researching this over on a Samsung forum (per your suggestion), and this same BSOD was definitely a big problem with their earlier nvme drivers. AND (I feel like an idiot), I thought I had the latest driver version dated 12 Feb 2019. It turns out that I had version 3.0 from 12 Feb 2018! That was a complete mis-read on my part.

I updated to their latest driver, version 3.1 which is dated 17 Jan 2019. I will monitor tonight and tomorrow morning and come back with an update.

Phil,

I'm going to go ahead and call this one SOLVED! Since my email yesterday evening I have tracked all sleep/wake up cycles. There have been a total of 12 cycles with absolutely no issues. I checked the mini dump folder and there are no new files!

To summarize, the INTERNAL_POWER_ERROR Stop Codes that I received were caused by the Samsung 970 Pro SSD driver that I recently installed when adding two of these drives to my system. The driver was version 3.0 dated 12 Feb 2018. After exploring one of the Samsung forums, I found several other individuals who were experiencing the same exact issue. The problem appears to have been more prominent with users who installed more than one Samsung NVMe drive together in the same system. Samsung released a new driver, version 3.1 on 17 Jan 2019, and this appears to have fixed the problem.

For those of you who want to research this more, here's a link to the Samsung forum thread:
Solved: NVME driver causes "internal power error" on resum... - Samsung Community - 403634

I will continue to monitor this and will update this thread if there are any changes.

Phil, I can't thank you enough for you help and assistance! Thank you, thank you, thank you!!!