Any update on this? Did that fix it? What was your solution?
Start you own thread, with the link to the dump files included, and someone will be happy to help you.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
My computer has crash 3 times this week, two of those today. I get a blue screen and an error message of "Driver Power State Failure".
https://www.dropbox.com/s/a2o1btmboh8jmut/122713-11484-01.dmp
https://www.dropbox.com/s/sljr94irb8ab1oi/011414-29187-01.dmp
Here are the two files I found in my minidump folder. Any help would be greatly appreciated.
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.
Any update on this? Did that fix it? What was your solution?
Start you own thread, with the link to the dump files included, and someone will be happy to help you.
Any update on this? Did that fix it? What was your solution?
My pleasure, I look forward to your update.
Regards,
Patrick
Thanks for the reply. I set up the Driver Verifier, but after a restart and a few hours of usage there have been no crashes yet. I guess time will tell.
Hi,
The attached DMP file is of the DRIVER_POWER_STATE_FAILURE (9f) bug check.
*This bug check indicates that the driver is in an inconsistent or invalid power state.*If we run an !irp on the 4th parameter of the bug check (blocked IRP address), we get the following:
>[ 16, 2] 0 e1 ffffe00000f02610 00000000 fffff80000808ff0-ffffe00001406cb0 Success Error Cancel pending Unable to load image \SystemRoot\System32\drivers*ataport.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for ataport.SYS*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS \Driver*atapi* CLASSPNP!ClasspPowerUpCompletion*
^^
atapi.sys = ATAPI IDE Miniport Driver
ataport.sys = ATAPI Driver Extension
Both system drivers, not the true cause and being faulted by something else. Please go ahead and enable Driver Verifier to see what driver(s) are causing corruption:
Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
Important information regarding Driver Verifier:
If this happens, do not panic, do the following:
・ Restart and boot into normal Windows.
If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in %systemroot%\Minidump
Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617
Regards,
Patrick