Windows 10: BSOD after installing new HDD.. DRIVER_POWER_STATE_FAILURE upon wake Solved

  1.    28 Dec 2016 #1

    BSOD after installing new HDD.. DRIVER_POWER_STATE_FAILURE upon wake


    I recently swapped out an old 300gb HDD for a new WD Black 5tb drive. I'm running a 1000w PSU and currently have windows loaded on a 256gb Samsung 850 EVO SSD and have 4 other HDD's connected (500gb, 1tb, 2tb, and new 5tb). Everything is working fine after a fresh start / restart, but if I put the computer to sleep it will crash upon wake. It will wake up and I can perform some tasks in windows, but it will crash soon after. After wake, none of the hard drives will read, and I can initiate the BSOD if I try to open one in windows explorer. This began happening after I installed the new 5tb WD Black.

    I have updated all drivers, turned off link state power management, uninstalled NVIDIA drivers and programs & reinstalled current display drivers, performed sfc / DISM scan, scanned for malware, etc but cannot find a solution.

    Thank you for any and all help!
    Last edited by nikko; 02 Jan 2017 at 12:58.
      My ComputerSystem Spec

  2.    28 Dec 2016 #2

    The crashdumps you posted are showing atapi.sys as the probable cause for the crashes. This is the driver that controls your SATA interface, so your hunch about the new hard drive seems to be on the money.

    Here are some steps to take to help us see what's wrong:

    1. If your motherboard has new firmware and drivers available, update to the latest and see if you still are getting crashes. I couldn't tell what model your motherboard was, but if you can't find the driver/firmware page let us know.

    2. Plug the new hard drive into a different SATA port, see if it blue screens again.

    3. Outright unplug the hard drive from the motherboard, and again, see if the crashes continue.
      My ComputerSystem Spec


  3. Posts : 11,816
    Windows 10 Pro
       29 Dec 2016 #3

    Please remove all pirated programs and such from your system before we can start troubleshooting.
    The Forum Rules is meant for everything regarding piracy
    • Discussing it,
    • Asking for guidance,
    • Asking for a crack,
    • The use of it,
    • Etc.

    4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).
      My ComputersSystem Spec

  4.    29 Dec 2016 #4

    Spectrum said: View Post
    The crashdumps you posted are showing atapi.sys as the probable cause for the crashes. This is the driver that controls your SATA interface, so your hunch about the new hard drive seems to be on the money.

    Here are some steps to take to help us see what's wrong:

    1. If your motherboard has new firmware and drivers available, update to the latest and see if you still are getting crashes. I couldn't tell what model your motherboard was, but if you can't find the driver/firmware page let us know.

    2. Plug the new hard drive into a different SATA port, see if it blue screens again.

    3. Outright unplug the hard drive from the motherboard, and again, see if the crashes continue.

    Thank you for the advice, Spectrum. My MOBO is a Asus Sabertooth 990fx, and I have the latest firmware (unless I'm missing something, the Asus page says the latest firmware is build 1604 back in 2012).

    Before this started happening, I was using the same SATA port for a Seagate 300gb HDD (the same total number of HDD's and Windows on SSD). All I did was swap the 300gb for a 5tb. Could I be looking at a hardware issue here? It seems unlikely that the PSU or new WD Black 5tb drive is faulty, as it works just fine from a fresh boot. This only happens when resuming from sleep.

    Every SATA port is currently being used, but I will try switching the drive when I get home from work. I will also try removing it outright to see if that solves the problem.

    Thanks again for the help, I will research atapi.sys crashes and see what I can find.
      My ComputerSystem Spec


  5. Posts : 11,816
    Windows 10 Pro
       29 Dec 2016 #5

    Atapi.sys is a driver from Windows, searching for it mostly results in search results that are nowhere close to trustworthy results. (Mainly because there are lots of results from Solvusoft, Reviversoft and similar companies who post nothing more than crap on there sites in an attempt to sell their useless software.)
      My ComputersSystem Spec

  6.    29 Dec 2016 #6

    axe0 said: View Post
    Atapi.sys is a driver from Windows, searching for it mostly results in search results that are nowhere close to trustworthy results. (Mainly because there are lots of results from Solvusoft, Reviversoft and similar companies who post nothing more than crap on there sites in an attempt to sell their useless software.)

    Thank you, I noticed that! I was moreso searching for atapi.sys related BSOD errors in windows 10, along with DRIVER_POWER_STATE_FAILURE but haven't found anything very helpful yet. I plan on trying out Driver Verifier later on tonight, and perhaps running chkdsk /r. Another post suggested changing "Transfer Mode" in device manager from DMA to PIO.

    I also tried a full system restore back to a point before I had installed the HDD, but am still getting the BSOD. This is very unusual as my computer has been running fine for some time now, and it was only a simple HDD swap that caused this to start happening.

    Thanks again.
      My ComputerSystem Spec


  7. Posts : 11,816
    Windows 10 Pro
       29 Dec 2016 #7

    As soon as you've done post #3 we'll continue.
      My ComputersSystem Spec

  8.    29 Dec 2016 #8

    axe0 said: View Post
    As soon as you've done post #3 we'll continue.
    Thank you for your time/responses, but I'm not comfortable removing anything from this computer as I share it with others who use it for work. Also, I'm not exactly sure which software is pirated and which is legitimate. This all started with replacing one of the HDD's--everything appeared to be working fine before that.

    Thanks again, and I will continue my search!
      My ComputerSystem Spec

  9.    02 Jan 2017 #9

    Just wanted to follow up on this thread to potentially help anyone else having this problem. It ended up being an issue with the way the SATA devices were connected. I moved the new 5tb HDD to a different SATA port and the BSOD's have ceased--now all drives & disc burners are connected and working 100%. I'm still not exactly sure where the conflict happened, but the good thing is after all the troubleshooting and driver updates my computer is running faster than it was before the problems began!
      My ComputerSystem Spec


 

Related Threads
Bsod driver_power_state_failure in BSOD Crashes and Debugging
I've been getting a BSOD that the windows diplays as driver power state failure when shutting down. I've tried updating every important driver that I can think of (Graphics, Chipset, BIOS, VGA, audio, ATK), and when the problem seems solved it...
BSOD driver_power_state_failure in BSOD Crashes and Debugging
Hi, My computer runs into BSOD driver_power_state_failure every time I resume from sleep mode or turning on the computer after turning it off (I have the quick boot enabled). I just did a refresh on my machine to get rid of all the bloatwares...
BSOD: Driver_Power_State_Failure in BSOD Crashes and Debugging
Hello, I came across a BSOD crash from system file ntoskrnl.exe I need your help to interpret minidump files. Kind regards!
Driver_Power_State_Failure BSOD in BSOD Crashes and Debugging
So ive spend multiple hours a night the last week or so trying to resolve this problem. The BSOD is a repeatable one for me, as far as i know ive not had and random ones, only crashes due to the repeatable offense. When i play a game, if i alt tab...
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 05:41.
Find Us