Share via

Wake from hibernation - BSOD - several stop codes - hardware issue?

Anonymous
2019-01-29T12:23:26+00:00

Hi community!

I hope someone can point me to the right direction. I'm tracking down a computer problem which existed for quiet a long time on this machine. This is my last approch to solve it.

The issue:

  1. the computer is put into hibernation (this kind of hibernation: "powercfg.exe /hibernate on", hybride sleep: off).
  2. when I wake up the computer after around 6 minutes, I get a BSOD, the stop codes vary from blue screen to blue screen

What I found out so far:

  • when hibernation period is shorter then 6 minutes, everything is fine
  • computer is running stable once booted, no BSOD during work time, even on heavy load
  • when PSU is switched off during hibernation (and hibernation period is under 6 minutes) BSOD occure on wake up
  • clean boot after shutdown is randomly affected, too
  • plug-in boot drive to another SATA port has no affect
  • resetting bios has no affect

BSOD stop codes I gathered so far:

0x000000fc (0xffff848c92aa6000, 0x8a00000608a008e3, 0xfffffe8a10059b90, 0x0000000000000003) >> ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

0x00000050 (0xfffff8041d0c3590, 0x0000000000000010, 0xfffff8041d0c3590, 0x0000000000000002) >> PAGE_FAULT_IN_NONPAGED_AREA

0x00000139 (0x0000000000000003, 0xfffff08d598ca8a0, 0xfffff08d598ca7f8, 0x0000000000000000) >> KERNEL_SECURITY_CHECK_FAILURE

0x0000004e (0x0000000000000099, 0x0000000000152945, 0x0000000000000001, 0x0000000000000000) >> PFN_LIST_CORRUPT

0x0000001a (0x000000000000**** 0xfffff00506459cf0) >> SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

0x00000021 (0x0000000000000000, 0x0000000000000001, 0x0000000080000400, 0x000000007d314c30) >> QUOTA_UNDERFLOW

0x00000050 (0xffffd6ffec6fb647, 0x0000000000000000, 0xfffff806483b5a91, 0x0000000000000002) >> PAGE_FAULT_IN_NONPAGED_AREA

0x0000003b (0x00000000c0000005, 0xfffffc1e49b031ba, 0xffffef88adb33970, 0x0000000000000000) >> SYSTEM_SERVICE_EXCEPTION

On BSOD a memory.dmp is generated. I opened it with WinDbg Preview, but I'm not really understanding, what is going on there or how to interprete the results (I hoped it points to a .dll or device, but all I see are registers, memory addresses and assembler code).

0x00000139 >> KERNEL_SECURITY_CHECK_FAILURE seems to occure more often then the others - 3 times so far.

System information:

  • Windows 10 Pro 17763 (freshly installed two weeks ago)
  • Gigabyte H77-D3H (latest Bios**** found nothing)
  • be quiet! Straigth Power BOT E9 400W
  • everything is unplugged from mainboard for trouble shooting, except SSD, CPU, RAM, 2 Fans, power

Suspicion:

I think the issue is related to power supply. The time periode, which seems to decide between successful or faulty wake, reminds me of a discharging capacitor on PSU or Mainboard. However, as far as I know, Windows hibernation is independend from power supply, so I'm not sure and posting this issue here.

Help!

  • Can someone tell me more in detail about the stop codes - I know about the Microsoft Bug Check Code Reference, but I'm not programmer enough, to fully understand or use thisfor troubleshooting
  • Can someone tell me how to use and interprete the memory.dmp files in order to find the faulty piece of driver or hardware, if even possible

!!Any tipps, references, knowledge, experiences or ideas to troubleshoot this are highly appreciated!!

Thank you in advance,

Martin

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

17 answers

Sort by: Most helpful
  1. Sumit D - IA 165.4K Reputation points Independent Advisor
    2019-01-30T16:55:38+00:00

    You did a quite lot of good troubleshooting. It is possible that both SSDs are faulty. Meanwhile, did you use a different cable for HDD or the same one?

    2 people found this answer helpful.
    0 comments No comments
  2. DaveM121 866.5K Reputation points Independent Advisor
    2019-01-29T12:44:19+00:00

    Hi Vogel

    The minidump files indicate storahci.sys, which it the HDD/SSD controller driver on your Motherboard

    Open Device Manager (accessible by right clicking your Start Button)

    Expand the IDE ATA/ATAPI controllers section

    Right click the device you will find there and choose uninstall

    Close Device Manager and restart your PC

    If that does not resolve this, go to the support page for your PC/Motherboard then download and install the chipset device driver they recommend . . .

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-01-29T12:35:00+00:00

    Hi Dave!

    Thank you very much, here we go:

    https://www.dropbox.com/s/ty4n6eyeysf56mo/VogelMoritz_Hibernation_BSOD_Minidumps.zip?dl=0

    Minidumps are from today, 5 only.

    0 comments No comments
  4. Sumit D - IA 165.4K Reputation points Independent Advisor
    2019-01-29T12:30:07+00:00

    Hi Vogel

    I am Sumit, an Independent Advisor and a 2-Year Windows Insider MVP here to help.

    We need log files(called dump files) that tell us what lead to crash.

    Please share them with us for a better analysis of the problem. Instructions can be found here:

    https://answers.microsoft.com/en-us/windows/for...

    Please let us know if you need any assistance about posting dump files.

    0 comments No comments
  5. DaveM121 866.5K Reputation points Independent Advisor
    2019-01-29T12:25:56+00:00

    Hi Vogel, most likely a device driver is not powering up correctly after your system wakes, please check to see if your system has produced any minidump files . . .

    Open Windows File Explorer

    Navigate to C:\Windows\Minidump

    Zip up the contents of that folder

    If you have problems zipping those files, copy them out onto your Desktop and zip them from there

    Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

    Then post a link here to the zip file, so we can take a look for you . . .

    0 comments No comments