Windows 10: Driver Power State Failure on Sleep, Hibernate, Restart or Shutdown

Hi,

Every time I try to put put my laptop to sleep, hibernate, restart it or shutdown, it stalls for about 10 minutes before giving me a Driver Power State Failure.

Having installed "WhoCrashed" and "Windbg", I was able to determine it was related to "ntkrnlmp.exe", "ndis.sys", "raspppoe.sys" and a vpn driver at one point or another. I "believe" I managed to uninstall the offending vpn driver but of course still overall have the same issue.

This appeared to occur while trying to do a windows update last week but I can't be sure. I presume, there is a out of date or corrupt driver but just can't seem to determine which one.

Many thanks in advance,

Hob

:)

 

Microsoft cant shut down, sleep or hibernate.

fwiw

I have the same shutdown/sleep/hibernate issue.

In hibernate, even after holding the power button to force the shutdown, it still does its hibernate job here on restart.

 

Windows 10 fails to power off after ANY shutdown commands

There is no option in Windows 10 to put the computer into a "power down" mode (AKA shutdown).

The options are sleep, hibernate or "shutdown" which actually is a new "hybrid shutdown" state.

If the PC is in any of these states it will restart in response to keyboard and or mouse activity.

You CAN however create a shortcut to issue the "shutdown" command, and this DOES turn the PC OFF.

Full info on my site here skillbank : Customize Windows 10 and scroll down the page.

 

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.


Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

• Uninstall Daemon Tools
• Download the SPTD standalone installer and follow these steps:
  • Double click the executable to open it
  • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window



Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.
ONLY install the drivers from your manufacturer!

Please remove your VPN software.
Code: *** WARNING: Unable to verify timestamp for tap0901.sys *** ERROR: Module load completed but symbols could not be loaded for tap0901.sys[/quote]

 

Hi Axe0,

Thanks for the speedy reply!

I've uninstalled both Daemon Tools and Driver Booster 3. I've had Daemon Tools for a long time so I don't believe it would be the culprit but I'll take your good advice and remove it. I installed Driver Booster 3 after I experienced this issue - but I removed it as well.

I followed the link for the SPTD standalone installer and the "uninstall" button was greyed out so I can confirm it is not on my system.

My VPN software was still on my system and actually hanged when I attempted to uninstall (it appeared it couldn't remove the "TAP driver"). I removed the TAP driver directly, then uninstalled the VPN software and it did not hang on uninstallation.

After all that, I restarted and surprisingly it appeared to do a clean restart - no BSOD! However, upon a further attempt at "sleep mode" or "shutdown", another "ndis.sys" related BSOD. Same problem but some progress.

Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffe001bad887d0, Physical Device Object of the stack Arg3: fffff8011e154990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffe001ced29010, The blocked IRP Debugging Details: ------------------ Implicit thread is now ffffe001`b9775040 DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 10586.17.amd64fre.th2_release.151121-2308 SYSTEM_MANUFACTURER: LENOVO SYSTEM_PRODUCT_NAME: 20268 SYSTEM_SKU: LENOVO_MT_20268 SYSTEM_VERSION: IdeaPad U330 Touch BIOS_VENDOR: LENOVO BIOS_VERSION: 7CCN15WW BIOS_DATE: 07/24/2013 BASEBOARD_MANUFACTURER: LENOVO BASEBOARD_PRODUCT: Cherry 3A Touch BASEBOARD_VERSION: 31900003STD DUMP_TYPE: 1 BUGCHECK_P1: 3 BUGCHECK_P2: ffffe001bad887d0 BUGCHECK_P3: fffff8011e154990 BUGCHECK_P4: ffffe001ced29010 DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: b9775040 CPU_COUNT: 4 CPU_MHZ: 8f7 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 45 CPU_STEPPING: 1 CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 1D'00000000 (cache) 1D'00000000 (init) DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_SESSION_HOST: WEEN ANALYSIS_SESSION_TIME: 12-25-2015 08:47:00.0811 ANALYSIS_VERSION: 10.0.10586.567 amd64fre LAST_CONTROL_TRANSFER: from fffff8011be67dca to fffff8011bf5d1f6 STACK_TEXT: ffffd000`203df3a0 fffff801`1be67dca : ffffe001`b992f7f0 fffff800`fbd428e5 00000000`203df800 ffffd000`203df8d0 : nt!KiSwapContext+0x76 ffffd000`203df4e0 fffff801`1be67859 : ffffe001`b97587a0 ffffe001`cda6b740 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0x15a ffffd000`203df590 fffff801`1be674c5 : ffffe001`bdffe1a0 fffff800`fbd4bf52 ffffe001`bdffe101 00000000`00000000 : nt!KiCommitThreadWait+0x149 ffffd000`203df620 fffff800`fbdfe7b2 : ffffe001`bdfff618 fffff800`00000000 ffffd000`203df700 00000000`00000000 : nt!KeWaitForSingleObject+0x375 ffffd000`203df6e0 fffff800`fbde92fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!KWaitEventBase::Wait+0x22 ffffd000`203df720 fffff800`fbdc7f48 : ffffe001`bdffe1a0 ffffe001`bdffe1a0 00000000`00000000 fffff801`1c12aac8 : ndis!Ndis::BindEngine::ApplyBindChanges+0x16935 ffffd000`203df770 fffff800`fbd42588 : ffffe001`c4d6d380 ffffe001`bdffe1a0 00000000`00000004 00000000`00000004 : ndis!ndisIssueNetEventSetPowerEvent+0x60 ffffd000`203df870 fffff800`fbdc7cf9 : ffffe001`bdffe1a0 00000000`00000004 00000000`00000000 00000000`00000000 : ndis!ndisPrepForLowPower+0x38 ffffd000`203df940 fffff800`fbdc7bce : 00000000`00000000 00000000`00000004 ffffe001`ced29010 ffffe001`bdffe1a0 : ndis!ndisSetSystemPower+0x129 ffffd000`203df9c0 fffff800`fbd54528 : ffffe001`ced29010 ffffe001`bad8b490 ffffe001`ced29170 ffffe001`bdec4250 : ndis!ndisSetPower+0x96 ffffd000`203df9f0 fffff800`fad70e1d : ffffd000`203dfb10 ffffd000`203dfbf0 ffffe001`ced29010 ffffe001`bdec4250 : ndis!ndisPowerDispatch+0xa8 ffffd000`203dfa20 fffff800`fad504d8 : ffffe001`bdffb160 ffffd000`203dfb10 00000000`00000004 ffffd000`203dfae8 : Wdf01000!FxPkgFdo::_PowerPassDown+0x6d [d:\th\minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 86] ffffd000`203dfa50 fffff800`fad4dff2 : ffffe001`bdec4250 00000000`00000000 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgFdo:ispatchSystemSetPower+0x178 [d:\th\minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 292] ffffd000`203dfaa0 fffff800`fad411b1 : ffffe001`ced29010 ffffe001`be00d2b0 fffff801`1c0f0100 fffff801`1c0f0b80 : Wdf01000!FxPkgPnp:ispatch+0xb2 [d:\th\minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 654] ffffd000`203dfb10 fffff801`1bf275da : ffffd000`203dfbf0 fffff801`00000000 fffff801`1c0f0100 fffff801`1c0f0140 : Wdf01000!FxDevice:ispatchWithLock+0x111 [d:\th\minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1402] ffffd000`203dfb70 fffff801`1be1f125 : 00000000`00000000 fffff801`1bf273e4 00000000`00000000 00000000`000000b0 : nt!PopIrpWorker+0x1f6 ffffd000`203dfc10 fffff801`1bf5d906 : ffffd000`203e8180 ffffe001`b9775040 fffff801`1be1f0e4 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffffd000`203dfc60 00000000`00000000 : ffffd000`203e0000 ffffd000`203da000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: .thread 0xffffe001b9775040 ; kb THREAD_SHA1_HASH_MOD_FUNC: 85b437be74c36b81a4758d06eaca24e6a9562e93 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2bd0669205897cf980833bd36f1bef9f6fba191e THREAD_SHA1_HASH_MOD: 55e86ab040cf6f2789308dc90f2c9dc5acaff1e4 FOLLOWUP_IP: ndis!KWaitEventBase::Wait+22 fffff800`fbdfe7b2 4883c438 add rsp,38h FAULT_INSTR_CODE: 38c48348 SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: ndis!KWaitEventBase::Wait+22 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndis IMAGE_NAME: ndis.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5632d5d2 BUCKET_ID_FUNC_OFFSET: 22 FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ndis!KWaitEventBase::Wait BUCKET_ID: 0x9F_3_POWER_DOWN_ndis!KWaitEventBase::Wait PRIMARY_PROBLEM_CLASS: 0x9F_3_POWER_DOWN_ndis!KWaitEventBase::Wait TARGET_TIME: 2015-12-25T00:04:52.000Z OSBUILD: 10586 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 784 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2015-11-22 10:24:24 BUILDDATESTAMP_STR: 151121-2308 BUILDLAB_STR: th2_release BUILDOSVER_STR: 10.0.10586.17.amd64fre.th2_release.151121-2308 ANALYSIS_SESSION_ELAPSED_TIME: 1546 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_ndis!kwaiteventbase::wait FAILURE_ID_HASH: {87df8b85-0efe-97a8-ecf0-6fe565954fe3} Followup: MachineOwner ---------[/quote]

 

Run the dm log collector and upload a new zip.

Also run the command !irp on the address of the blocked irp
Thus
Code: !irp ffffe001ced29010[/quote] What do you get when you run that?

 

Uploaded a new dm log. Output of << !irp ffffe001ced29010 >> can be seen below:

Code: 0: kd> !irp ffffe001ced29010 Irp is active with 5 stacks 3 is current (= 0xffffe001ced29170) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. cmd flg cl Device File Completion-Context [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 0 ffffe001bdffe050 00000000 00000000-00000000 *** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys \Driver\NETwNb64 Args: 00014400 00000000 00000004 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffe001bdffb160 00000000 fffff8011c1b2b44-ffffe001c2bb92b0 Success Error Cancel pending \Driver\vwifibus nt!PopSystemIrpCompletion Args: 00014400 00000000 00000004 00000002 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffffe001c2bb92b0 Args: 00000000 00000000 00000000 00000000[/quote]

 

Upload a new zip, the current one is empty *Sad

 

Uploaded the zip in an edited post. My bad *Wink

 

The flagged driver is the driver for the Intel(R) Wireless-N 7260.
Check your manufacturer Lenovo for driver updates.
Code: 0: kd> !irp ffffe001ced29010 Irp is active with 5 stacks 3 is current (= 0xffffe001ced29170) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. cmd flg cl Device File Completion-Context [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 >[ 16, 2] 0 0 ffffe001bdffe050 00000000 00000000-00000000 Unable to load image \SystemRoot\System32\drivers\Netwbw02.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Netwbw02.sys *** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys \Driver\NETwNb64 Args: 00014400 00000000 00000004 00000002 [ 16, 2] 0 e1 ffffe001bdffb160 00000000 fffff8011c1b2b44-ffffe001c2bb92b0 Success Error Cancel pending \Driver\vwifibus nt!PopSystemIrpCompletion Args: 00014400 00000000 00000004 00000002 [ 0, 0] 0 0 00000000 00000000 00000000-ffffe001c2bb92b0 Args: 00000000 00000000 00000000 00000000 0: kd> lmvm Netwbw02 start end module name fffff800`fece0000 fffff800`ff069000 Netwbw02 T (no symbols) Loaded symbol image file: Netwbw02.sys Image path: \SystemRoot\System32\drivers\Netwbw02.sys Image name: Netwbw02.sys Timestamp: Tue Nov 03 15:30:10 2015 (5638C4F2) CheckSum: 003608BB ImageSize: 00389000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Hi Axe0,

Sorry for the late reply. I've been having a hard time finding an update for the Intel Wireless-N 7260 driver. I believe I updated it but still have a BSOD issue. I'll upload another dm log soon.

Off topic, recently it appears my screen's frame decided to pop off and continues to break each time I open the lid so this physical issue may have me a little distracted at the moment.

I'll keep you informed but for now, I really appreciate the help. Thanks!

 

Okay, uploaded a new dm_log zip. Managed to fix my hardware issues and installed the driver from my manufacturer's website. Thanks for your patience.Attachment 59639

 

Have you recently removed any program?
This driver is missing Driver Reference Table - npf_devolo.sys

Please uninstall AVG and use Windows Defender as alternative while troubleshooting
AVG - Uninstall Completely - Windows 7 Help Forums
Code: ffffd000`21c87ae0 fffff800`0dc92daaUnable to load image avgidsdrivera.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for avgidsdrivera.sys *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys avgidsdrivera+0x12daa[/quote]

 

npf_devolo must have been related to a program called Devolo Cockpit I had installed around the time the problem arose. It was used to set up Wifi in my home and hence it's problems related to the wireless drivers.

I uninstalled the program and attempted a restart afterwards to complete the uninstall. This restart crashed, however, the subsequent succeeded. I attempted a sleep and shutdown and no issues either. Uninstalling AVG was unnecessary at this point.

I'm pretty sure the problem's fixed and am delighted. It's the first time I can shut down my laptop properly in a month.

I really appreciate all your help axe0 - I couldn't have done it without you. Many many thanks! (I'll mark this post solved)

- Hob

 

I'm glad to hear that *Smile

Seems indeed that uninstalling AVG wasn't necessary, fortunately.