Windows 10: DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe during sleep

Hello

After upgrading to windows 10 My computer seems has started randomly auto rebooting when it's asleep. I can "wake up" the computer, but it has a clean desktop etc, and upon checking both the administrative events and dmp files (using bluescreenview), find that it rebooted to prevent damage.

In general, it has many more errors in the event viewer than it did running w7

I have done the following:

Done a complete removal of the NVIDIA drivers using DDU and clean re-install
Updated the MB BIOS to the latest
Used the intel driver update utility and it found that all of my chipset drivers are up to date. There is a more recent version, but the utility did not recommend it
Ran driver verifier, which caused the system to crash and not reboot (recovered using safe mode) - dmp file is included
Rrun SFCmany times and it has always found no issue
Ran DISM /scanhealth and the result was "no component store corruption detected"

In any case, I have done all can can figure out by scanning forums etc. Any suggestion would be very appreciated.

Thank you

D




:)

 

Blue Screen of Death (DRIVER_POWER_STATE_FAILURE)

Hello

My laptop has been facing issues lately, whenever I were to use the battery and charged my laptop, my laptop would just crash and showed me a blue screen. I did some digging and used BlueScreenView and turns out it was caused by ntoskrnl.exe.

Bug Check String: DRIVER_POWER_STATE_FAILURE

Bug Check Code: 0x0000009f

Parameter 1: 00000000`00000003

Parameter 2: ffffc581`165a6060

Parameter 3: fffff800`569267f0

Parameter 4: ffffc581`1db404f0

Caused By Driver: ntoskrnl.exe

Caused By Address: ntoskrnl.exe+1640e0

Processor: x64

Crash Address: ntoskrnl.exe+1640e0

Moved from Windows / Windows 10 / Devices & drivers )

 

Having bluescreen called DRIVER POWER STATE FAILURE when i plugged in the adapter for my laptop in Win10

Crash List

Created by using
BlueScreenView

Dump File
Crash Time
Bug Check String
Bug Check Code
Parameter 1
Parameter 2
Parameter 3
Parameter 4
Caused By Driver
Caused By Address
File Description
Product Name
Company
File Version
Processor
Crash Address
Stack Address 1
Stack Address 2
Stack Address 3
Computer Name
Full Path
Processors Count
Major Version
Minor Version
Dump File Size
Dump File Time

012817-24078-01.dmp
28/01/2017 10:37:04 PM
DRIVER_POWER_STATE_FAILURE
0x0000009f
00000000`00000003
ffffc208`3bd6e060
fffff801`58b20960
ffffc208`3e355b80
ntoskrnl.exe
ntoskrnl.exe+149f90




x64
ntoskrnl.exe+149f90




C:\Windows\Minidump\012817-24078-01.dmp
8
15
14393
1,479,396
28/01/2017 10:39:02 PM

012417-18921-01.dmp
24/01/2017 8:35:10 AM
DRIVER_POWER_STATE_FAILURE
0x0000009f
00000000`00000003
ffffb984`78a68060
ffffdf80`21262cb0
ffffb984`779ecb40
ntoskrnl.exe
ntoskrnl.exe+149f90




x64
ntoskrnl.exe+149f90




C:\Windows\Minidump\012417-18921-01.dmp
8
15
14393
2,022,204
24/01/2017 8:37:05 AM

012417-27625-01.dmp
24/01/2017 12:46:51 AM
DRIVER_POWER_STATE_FAILURE
0x0000009f
00000000`00000003
ffffa501`1f5dd840
ffff8880`f11f9960
ffffa501`21ecc170
ntoskrnl.exe
ntoskrnl.exe+149f90




x64
ntoskrnl.exe+149f90




C:\Windows\Minidump\012417-27625-01.dmp
8
15
14393
1,330,780
24/01/2017 12:49:58 AM

 

Hello 200qa200k and welcome to the forum. I looked at the last 5 or 6 dump files. They all seemed to be blaming either yout Graphics drivers or Acronis.

Code: Use !analyze -v to get detailed debugging information. BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+1af427 ) Followup: MachineOwner[/quote] Code: BugCheck 9F, {4, 12c, ffffe0008f54d040, fffff802169059b0} *** WARNING: Unable to verify timestamp for fltsrv.sys *** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys *** WARNING: Unable to verify timestamp for snapman.sys *** ERROR: Module load completed but symbols could not be loaded for snapman.sys Implicit thread is now ffffe000`8f54d040 Probably caused by : partmgr.sys ( partmgr!PmRemoveDevice+c7 )[/quote] snapman- Acronis True Image Snapshot Manager driver also included in Seagate DiscWizard


fltsrv- Acronis Storage Filter Management

Code: Use !analyze -v to get detailed debugging information. BugCheck 9F, {4, 12c, ffffe0008f54d040, fffff802169059b0} *** WARNING: Unable to verify timestamp for fltsrv.sys *** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys *** WARNING: Unable to verify timestamp for snapman.sys *** ERROR: Module load completed but symbols could not be loaded for snapman.sys Implicit thread is now ffffe000`8f54d040 Probably caused by : partmgr.sys ( partmgr!PmRemoveDevice+c7 )[/quote] There is Acronis again and farther into the dump it blames

Code: fffd000`2181ee88 fffff801`f2781822Unable to load image \SystemRoot\system32\DRIVERS\vidsflt.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for vidsflt.sys *** ERROR: Module load completed but symbols could not be loaded for vidsflt.sys vidsflt+0x11822[/quote] That is the Acronis Virtual Disk driver for the Virtual Disk Storage Filter.

Due to the fact that you have already done several installs of the Nvidia Driver, I would suggest you uninstall Acronis. It is not easy to completely remove Acronis. Uninstall it from add/remove programs then use this Acronis KB article to completely get rid of it, or as much of it as you can. Acronis Cleanup Utility | Knowledge Base

Try that and see if you get better results.

 

Essenbe


Thank you for your quick and detailed response. I removed WD Acronis True Image AND Seatools using the Apps and Features in Settings and then followed up with the Acronis removal utility. We should see fairly soon if it was successful, as it usually rebooted overnight.

Thanks again

D

 

OK, great. Just let me know and if you do have another BSOD, please upload the DM Log collector again. I also did some checking after my post and it looks like you are getting several errors from Windows Live Photo Gallery. WLXPipeTran.dll to be exact. I would caution you not to use any of the 'fix it' programs offered on the net.

 

Hmm - Should I just remove windows live essentials? Cant find a way to just remove Live Photo Gallery...

D

 

Just wait and see if Acronis fixes it. If you uninstall Live Essentials, you will get a menu of which one or all of them. You could just select Photo Gallery. But, I'd wait first.

 

Alas no joy. It crashed while not being used, though it is a different failure from the Driver Power State failure. This time its watchdog.sys that casued the problem.

Plus, as is sometimes the case, windows search did work after the computer reboot. I need to run the following command to get search to work (from MS) : Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}


I have attached an updated debug file. Should I go ahead ad delete live photo?

 

And evidently, the DRIVER POWER STATE FAILURE issue is not resolved either. Last night the system crashed 3 times. I will try removing the photo-viewer

 

Your bsods are pretty much the same.

Code: Use !analyze -v to get detailed debugging information. BugCheck 119, {1, 3b1e07, 3b1e16, ffffe0016d9ba3b0} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiVerifyDriverReportedFenceId+78eb ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_SCHEDULER_INTERNAL_ERROR (119) The video scheduler has detected that fatal violation has occurred. This resulted in a condition that video scheduler can no longer progress. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000001, The driver has reported an invalid fence ID. Arg2: 00000000003b1e07 Arg3: 00000000003b1e16 Arg4: ffffe0016d9ba3b0 Debugging Details:[/quote] Code: DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: 0000000000000000 Debugging Details:[/quote] You still have a lot of errors with Windows Live Photo Gallery. Uninstall Live Essentials. You will get a dialogue box and be asked which part of it you want to install. Select photo gallery. And try that.

 

Essenbe

Bummer, but I removed photo viewer and 6 hours later the power state failure error occurred again, and as usual, while the computer was not being used....

I really appreciate you patience with this one...

D

 

I appreciate your patience with me. This seems to not be an easy one. When you say the computer is not being used, do you mean it is in Sleep or Hibernation? It is naming you graphics card/or drivers. The device is a pcie device. Do you have any other pci/pcie devices installed?

Code: !devobj ffffe000632ca060Device object (ffffe000632ca060) is for: Cannot read info offset from nt!ObpInfoMaskToOffset \Driver\pci DriverObject ffffe0006328a060 Current Irp 00000000 RefCount 0 Type 00000023 Flags 00001040 DevExt ffffe000632ca1b0 DevObjExt ffffe000632ca7a8 DevNode ffffe000632cb4f0 ExtensionFlags (0000000000) Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN AttachedDevice (Upper) ffffe000632cc3b0 \Driver\ACPI[/quote] If you would, please run Furmark, but make sure you watch the temps closely and stop the test if they get too high. Temps will rise rapidly and very high. After a few minutes they will level off. Let it run, if temps are not too high, until the temps level off. Watch for artifacts while the test is running.

After that I would like you to remove all wireless devices and any cards or dongles you use and see if that improves things any.

 

Also, are you running Nvidia driver 355.98? if not download it here. http://www.nvidia.com/download/drive...px/91812/en-us . Then, uninstall all Nvidia graphics drivers, making sure that you uninstall the Graphics driver last. Yes, Windows Update will give you a hard time. But, when you install, select custom install and install only the Graphics driver and PhysX driver. Nothing else. Make sure you have the clean install box checked.

 

Yes - the computer is either asleep or idle (ie - it may still be running), but its usually several hours after it was last used. One thing you said about the video drivers may be relevant - I had already done a clean, "minimal" install of 355.98, but had ONLY installed the graphic drivers, but had NOT installed the physx drivers. I used DDU to remove everything and did a clean install of 355.98, but this time included the physx...

The only pci/pcie card I have is the graphics card

I can run frurmark, but the system is not running "hot" when it fails - ie - the fans are either off or running slowing.

Dhanks again for your persistance

D