BSOD After SSD Failure. (Power driver state failure)

[Thomas James]

Im absolutely stumped over this one. Recently i believe my SSD crapped the bed, might have been due to a recent power outage, but it was weeks before. Afterwards, one day i noticed my computer was in black screen, but the peripherals were powered so i forced a shut down. After that it wouldnt boot. Acted like it wasnt recognizing the SSD at all. Looked in the case, light was on the SSD but wouldnt work. Unplugged things, tried different sata ports etc etc decided it was dead. Installed windows on a HDD did updates yadda etc. Started getting blue screens on start up. driver power state failure over and over. constantly gave me the ntoskrnl.exe module error. Eventually it started saying it was a RAZER driver, So i tried to uninstall all those drivers, even in safe mode, it just wasnt having it, and the blue screens persisted. So, i went back to windows 7. Worked fine. but the
noticeable loss in performance while gaming started to bother me. so i decided to try windows 10 again. Upgraded, everything installed fine, everything worked fine. A week or so later, im starting to have the same BSOD only when im starting the computer for the first time of the day. Lets say that every time i shut down the pc, then try to start it, it will BSOD while loading all the programs at startup. It will restart, then everything will work fine???? Im typing this on the pc in question. Im kind of at a loss at this point. Im wondering if maybe this Razer Black widow that i spilled water on a couple months ago, and then tore apart to blow dry and clean out is somehow causing this? The one thing i noticed, back when i got that black screen, the leds on the mouse were on, but the keyboard was not. im gonna add the data from Whocrashed in case that is helpful to someone more experienced with all this than i.

System Information (local)
--------------------------------------------------------------------------------

Computer name: BEAST-PC
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH Z77
CPU: GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17119100928 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 9/5/2017 12:36:15 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\090517-29984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x9F (0x3, 0xFFFFD50E6E3DB060, 0xFFFFF803B025B8F0, 0xFFFFD50E757985C0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 9/5/2017 12:36:15 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFD50E6E3DB060, 0xFFFFF803B025B8F0, 0xFFFFD50E757985C0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 9/4/2017 4:23:11 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\090417-28781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x9F (0x3, 0xFFFFBB07889C7060, 0xFFFFCB01A50788F0, 0xFFFFBB078AAD1B40)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/2/2017 2:44:51 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\090217-26796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x9F (0x3, 0xFFFFB8001CC0E600, 0xFFFFF80278C5B8F0, 0xFFFFB800200A1320)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[scout_03]

this razer black widows got water in could you try another for test you might have short something if it was under power .

 

[johnbl]

generally, for DRIVER_POWER_STATE_FAILURE bugcheck, you would update the BIOS and any motherboard drivers. (some motherboards have a special utility for controlling the power, old hardware drivers might not respond to the low power state transitions. IE they turn off (sleep) but don't wake up when the should.)

This error is more common on windows 7 systems that have been upgraded to windows 10.
(windows 7 had low power links turned off by default, windows 8 and above turn them on by default)

if you can not get a fix via the bios and driver updates you can go into control panel and set the system to high performance mode so the devices do not sleep. (not the best option)

you can also start cmd.exe as an admin and run
powercfg.exe /energy
and look at the report it generates. It might indicate what is not working correctly.
(common for some usb wireless cards to not wake up after sleep states.)

you can also put your memory dump from c:\window\minidump directory on to a cloud server like Microsoft onedrive, share the files for public access and post a link.
Someone with a debugger can take a quick look for old drivers.

Note: some hardware might have firmware that has to be updated (old solid state drives, some fancy mice)

if you can not get it working, you might change the memory dump type to kernel and put up the kernel dump. It will contain more info about your hardware.


some SSD "die" because they fill up and do not get to run their firmware garbage collection. You can plug the device into power without the data cable and the firmware should run its garbage collection routines after 5 minutes. I would leave it powered for a few hours then plug in the data cable and see if the system can see the drive.

 

[Thomas James]

generally, for DRIVER_POWER_STATE_FAILURE bugcheck, you would update the BIOS and any motherboard drivers. (some motherboards have a special utility for controlling the power, old hardware drivers might not respond to the low power state transitions. IE they turn off (sleep) but don't wake up when the should.)

This error is more common on windows 7 systems that have been upgraded to windows 10.
(windows 7 had low power links turned off by default, windows 8 and above turn them on by default)

if you can not get a fix via the bios and driver updates you can go into control panel and set the system to high performance mode so the devices do not sleep. (not the best option)

you can also start cmd.exe as an admin and run
powercfg.exe /energy
and look at the report it generates. It might indicate what is not working correctly.
(common for some usb wireless cards to not wake up after sleep states.)

you can also put your memory dump from c:\window\minidump directory on to a cloud server like Microsoft onedrive, share the files for public access and post a link.
Someone with a debugger can take a quick look for old drivers.

Note: some hardware might have firmware that has to be updated (old solid state drives, some fancy mice)

if you can not get it working, you might change the memory dump type to kernel and put up the kernel dump. It will contain more info about your hardware.


some SSD "die" because they fill up and do not get to run their firmware garbage collection. You can plug the device into power without the data cable and the firmware should run its garbage collection routines after 5 minutes. I would leave it powered for a few hours then plug in the data cable and see if the system can see the drive.

Thanks for the reply! I'll try everything you listed here in the morning and post my results. The one thing I have not been doing lately has been installing the Asus utility suite that came with the sabertooth board. I haven't updated my bios in at least a couple years but I know it's not on the same version as it originally came with. I feel like they stopped releasing updates around 2012.

 

[Thomas James]

I ran the CMD and did the energy report as you suggested, does this tell you anything? Looks like some usb device is causing issues, no doubt either my mouse or keyboard...

https://drive.google.com/file/d/0B_VpiTzWGwHxUFZvclByRmMyejQ/view?usp=sharing

edit: oh i guess uploading that to drive that way really jacked it up...

 

[scout_03]

i would carefully inspect the board with a magnifier the power outage could have blow a parts use a magnifier to do it also if you could try to test cpu in another system .