Question

Q: Driver Power State Failure (Windows 64_bit)

For the past 3 weeks now I have been getting the DPSF error every time I start my computer and use it for around 10 or 15 minutes, after the computer has restarted it is suddenly fine. I get no errors for the session and it won't happen until I restart my computer. I have attached the minidumps that pertain to my issue.
 
Minidumps
https://skydrive.live.com/redir?resid=97B96974B5000DD3!299&authkey=!ACsrFQ8muDV-kFI&ithint=folder%2c.dmp


* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

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.

By default, the fault of the crash is labeled as atapi.sys which is the ATAPI IDE Miniport Driver (not the true cause and is being driven to fault by something else). If we go ahead and run an !irp on the 4th parameter of the bug check (blocked IRP address), we get the following:

 [ 16, 2]   0 e1 fffffa800778eb10 00000000 fffff8024a198410-fffffa8009cac760 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\fltsrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fltsrv.sys
*** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys

^^ fltsrv.sys is a the Acronis Storage Filter Management Driver. Acronis has been known to cause issues, especially if performing regular backups, so I would go ahead and definitely uninstall it for troubleshooting purposes.

Regards,

Patrick
Debugger/Reverse Engineer.

Did this solve your problem?

Sorry this didn't help.


I uninstalled but still received the error additional minidump attached.

https://skydrive.live.com/redir?resid=97B96974B5000DD3!299&authkey=!ACsrFQ8muDV-kFI&ithint=folder%2c.dmp

I read something about the drivers still being even after an uninstall if that is any help.

Thank You for your response.

Did this solve your problem?

Sorry this didn't help.


Correct, the driver is still listed and loaded. Let's manually remove it:

Navigate to C:\Windows\System32\Drivers and find and rename fltsrv.sys to fltsrv.old.

Restart.

Regards,

Patrick
Debugger/Reverse Engineer.

Did this solve your problem?

Sorry this didn't help.


I was looking for fltsrv.sys however could not find it.

Did this solve your problem?

Sorry this didn't help.


Strange, it was listed and loaded in the DMP you linked. Since you're still crashing, please enable Driver Verifier.

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 -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・    Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

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
Debugger/Reverse Engineer.

Did this solve your problem?

Sorry this didn't help.


I ran the BSOD and as soon as I logged in I got BSOD'd, I tried to run a command prompt to turn off the verifier and it didn't work, I was able to get back to a restore point.

If the minidump in question was not the BSOD I will try the verifier again.

EDIT: looking at that article you sent it said verifier.exe/reset wheras I was trying verifier/reset. I will try to BSOD again.

EDIT: Got those BSOD minidumps.
https://skydrive.live.com/redir?resid=97B96974B5000DD3!299&authkey=!ACsrFQ8muDV-kFI&ithint=folder%2c.dmp

Did this solve your problem?

Sorry this didn't help.


All of the attached DMP files are of the DRIVER_VERIFIER_DETECTED_VIOLATION (c4) bug check.

This is the general bug check code for fatal errors found by Driver Verifier.

However, despite its name, it's failing to detect a device driver within violation in ALL dumps, therefore this is likely a hardware issue, or the system is crashing so fast verifier has no time to find the cause.

How new is this system?

Regards,

Patrick
Debugger/Reverse Engineer.

Did this solve your problem?

Sorry this didn't help.


I built it last summer it was first operational sometime in July 2013.

Did this solve your problem?

Sorry this didn't help.


Would you be willing to back up any important documents and do a CLEAN install of Windows with nothing but the latest drivers to rule out hardware as the issue?

Regards,

Patrick
Debugger/Reverse Engineer.

Did this solve your problem?

Sorry this didn't help.


I will do so, it may take me a few days though. After I do my wipe I will get back to you.

Did this solve your problem?

Sorry this didn't help.


* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
Question Info

Views: 1,513 Last updated: March 24, 2018 Applies to: