Windows 10: Windows 10 BSOD - DRIVER_POWER_STATE_FAILURE

I have a Dell Inspiron 5379 Laptop that keep blue screening randomly!


It always happens when left to go to sleep or hibernate, but not every time. Did not happen for 2 days then again this morning.


I get the following message in the event log


The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f 0x0000000000000003, 0xffff8583566c6870, 0xffff80077303f750, 0xffff858369fb7860. A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: eb34b479-c4b6-4649-873d-2960e316e97f.


Just before the blue screen there is an error in the Event log


Miniport Dell Giga Ethernet, {a2b388e7-513a-49f2-a28d-ee30b57ab892}, had event Fatal error: The miniport has failed to start by returning an error code from MiniportRestart


But not always


This started after installing Windows 10 feature update "20H2"


All Windows updates have been installed and all Dell drivers are the latest


I have run


sfc /scannow


and


dism /online /cleanup-image /restorehealth


I have tried removing the NIC and reinstalling


I removed the feature update and all was ok for a few days but installed again 3 days ago and got the blue screen again this morning.


I think it must be a driver problem, but identifying which one.


I have analysed memory.dmp file, but that is where I run out of ideas.





Microsoft R Windows Debugger Version 10.0.19041.685 AMD64

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.





************* Path validation summary **************

Response Time ms Location

Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 19041 MP 8 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff803`2a000000 PsLoadedModuleList = 0xfffff803`2ac2a490

Debug session time: Tue Mar 23 17:25:55.238 2021 UTC + 0:00

System Uptime: 1 days 5:12:10.382

Loading Kernel Symbols

...............................................................

................................................................

................................................................

...................................................

Loading User Symbols



Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

2: kd> !analyze -v

*******************************************************************************

* *

* 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: ffff8583566c6870, Physical Device Object of the stack

Arg3: ffff80077303f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

Arg4: ffff858369fb7860, The blocked IRP



Debugging Details:

------------------



Implicit thread is now ffff8583`39ab6040



KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 2



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-LTB5D1K



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 11



Key : Analysis.Memory.CommitPeak.Mb

Value: 77



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 9f



BUGCHECK_P1: 3



BUGCHECK_P2: ffff8583566c6870



BUGCHECK_P3: ffff80077303f750



BUGCHECK_P4: ffff858369fb7860



DRVPOWERSTATE_SUBCODE: 3



FAULTING_THREAD: ffff858339ab6040



ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.



IRP_ADDRESS: ffff858369fb7860



DEVICE_OBJECT: ffff85835a8bf030



DRIVER_OBJECT: ffff858347850310



IMAGE_NAME: IndirectKmd.sys



MODULE_NAME: IndirectKmd



FAULTING_MODULE: fffff8034e880000 IndirectKmd



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



PROCESS_NAME: System



STACK_TEXT:

ffff8007`730173a0 fffff803`2a265850 : 00000028`00000008 00000000`ffffffff 00000050`00000000 ffff8583`3baf0558 : nt!KiSwapContext+0x76

ffff8007`730174e0 fffff803`2a264d7f : ffff8583`39e36000 ffff8583`39ab6040 ffff8007`730176a0 00000000`00000000 : nt!KiSwapThread+0x500

ffff8007`73017590 fffff803`2a264623 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8583`39ab6180 : nt!KiCommitThreadWait+0x14f

ffff8007`73017630 fffff803`41b6339e : ffff8007`73017780 ffff8007`00000000 ffff8583`5a8bf100 ffff8583`52813100 : nt!KeWaitForSingleObject+0x233

ffff8007`73017720 fffff803`41b62486 : 00000000`00000003 00000000`00000010 ffff8583`5a8c0050 ffff8583`5a8c0050 : dxgkrnl!DpiRequestIoPowerState+0xbe

ffff8007`730177c0 fffff803`41b63024 : 00000000`00000000 ffff8583`69fb7860 00000000`00000004 00000000`00000004 : dxgkrnl!DpiFdoSetAdapterPowerState+0x336

ffff8007`73017880 fffff803`41b62631 : 00000000`00000001 00000000`00000000 ffff8007`7307ff00 ffff8583`69fb7f18 : dxgkrnl!DpiFdoHandleDevicePower+0x134

ffff8007`73017920 fffff803`41b63b81 : ffff8583`69fb7860 ffff8583`5a8bf180 ffff8583`5a8bf030 ffff8007`73017a40 : dxgkrnl!DpiFdoDispatchPower+0x21

ffff8007`73017950 fffff803`2a39cb29 : ffff8583`69fb7908 ffff8583`00000000 ffff8583`39ab6040 ffff8583`39ab6000 : dxgkrnl!DpiDispatchPower+0xe1

ffff8007`73017a70 fffff803`2a317e85 : 00000000`00000000 fffff803`2a39c950 00000000`00000000 00000000`0000009e : nt!PopIrpWorker+0x1d9

ffff8007`73017b10 fffff803`2a3fd2a8 : ffffc001`e8080180 ffff8583`39ab6040 fffff803`2a317e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55

ffff8007`73017b60 00000000`00000000 : ffff8007`73018000 ffff8007`73011000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28





STACK_COMMAND: .thread 0xffff858339ab6040 ; kb



SYMBOL_NAME: IndirectKmd!VIDPN_TARGET_INFO::~VIDPN_TARGET_INFO <PERF> IndirectKmd+0x0+0



BUCKET_ID_FUNC_OFFSET: 0



FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_DXG_POWER_IRP_TIMEOUT_IndirectKmd!VIDPN_TARGET_INFO::_VIDPN_TARGET_INFO__PERF__IndirectKmd+0x0



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {e7010bde-1525-fe49-08c6-f896c6d75436}



Followup: MachineOwner

---------




Any help, would be appreciated.

Thanks in advance.

Kevan

:)

 

BSOD: DRIVER_POWER_STATE_FAILURE Windows 10

Hello,

Thank you for contacting Microsoft Community.

We understand the inconvenience you have experienced.

I would suggest you to refer to the following suggestion provided by SpiritX MS MVP replied on January 25, 2016 and check if it helps. Refer to the below link:

BSoD: DRIVER_POWER_STATE_FAILURE | Windows 10

BSoD: DRIVER_POWER_STATE_FAILURE | Windows 10

Hope this information is helpful. If you need any further assistance, please feel free to reply.

 

Windows 10 BSOD - DRIVER_POWER_STATE_FAILURE

Hi,



Thank you for writing to Microsoft Community Forums.



I understand that you are receiving Blue Screen error with DRIVER_POWER_STATE_FAILURE on your computer. I’ll certainly assist you with the issue.



However, please let us know:

• When exactly do you receive the Blue Screen error?
  
• Are you aware of any changes made to the computer recently?
  
• Which build version of Windows 10 is installed on the computer? To check type:
  winver in the search bar on the Taskbar and hit
  Enter.
  
• What is the make and model of the computer?
  

I have tried to access the link for dump files shared by you. However, I was unable to access the link. I would suggest you to upload the files in OneDrive and share the link.



The DRIVER_POWER_STATE_FAILURE error occurs when the driver is in an inconsistent or invalid power state. You may want to refer the troubleshooting steps mentioned in the Remarks section of the
article Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE
and see if that helps.



Note: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting
from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.



You may also want to refer the steps mentioned in the article Troubleshoot
blue screen errors.



We await your response.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

BSOD when running on battery - driver_power_state_failure

***Merged***

Hello,

Since a few months my laptop - MSI GS60 2PE running Windows 10 Home - started giving BSOD's with the DRIVER_POWER_STATE_FAILURE after a seemingly random time when running on the battery. As I'm using it every day for work,
I depend on the machine and managed by just plugging it in.

While that works, I know it should be possible to make it work on the battery...

I've recently "reset this pc" using the build in option in Windows 10, after which I installed all "latest" drivers from the MSI site. I also re-installed all programs required to do my job and play some games.

Yesterday, Windows wanted to install the Fall Creators Update: I did. Booting the laptop while unplugged now gave me another BSOD, though with a different message: VIDEO_DXGKRNL_FATAL_ERROR. This seems to point to the Intel HD 4600 or Nvidia
GTX 870M.

To sum up some other issues I was starting out with...

Syptoms

• When unplugged, a BSOD occurs after a seemingly random time. (driver_power_state_failure)
  • After updating to the fall creators version, it also throws video_dxgkrnl_fatal_error; feels like a coin flip which one it will show.
    
• Bluetooth was failing after a couple of minutes, regardless whether I used it or not and whether the laptop was plugged in or not.
  
• Shutting down Windows would sometimes just heat up the CPU, make the fan go haywire and do nothing but turning the screen off.

I've tried / did:

• All drivers are up to date. This was verified by using DriverView and manually going over all of the non-Microsoft drivers.
  • This step fixed symptom 2 described above. Next to the latest version there was some patch (or 3 major versions ago) that couldn't be removed by conventional means. The build in troubleshooter actually removed it and bluetooth is now working
    as it should.
  • The HD4600 drivers were removed from the device management and I installed the latest according to the Intel site.
  • DDU was used in safe mode to remove the Nvidia driver and the latest one was installed.
• BlueScreenViewer shows the minidumps and lots of drivers.
  
  • The one created when the driver_power_state_failure occurred is useless, as nothing is marked but the ntoskrnl.
  • The one created when the video_dxgkrnl_fatal_error occurred shows ntoskrnl, watchdog and dxgkrnl.
    
• A clean boot (disabling all non-Microsoft services and disabling all startup programs) still results in the BSOD.
  
• Booting the laptop while plugged in, letting it run for a couple of minutes so everything is started and then unplugging it also seems to work.
  • Yesterday, I unplugged it and could work with it for about 2.5 hours before it called out for power: I doubt the battery is the issue.
  • I was asked to run a battery check (powercfg -energy -output ...) but that doesn't seem to show any issues. (design capacity '55031' Last full
    charge '38556'. The laptop is over three years old.)
    
• Starting in safe mode with networking will not result in a BSOD. (At least not within the hour I left it on.)
  
• Unchecking 'turn on fast startup' - as suggested in so many posts - in the power settings only causes issues.
  • When unchecked, windows won't shut down properly.
  • When checked, it does shut down normally. This seems to be the
    fix for symptom 3.
    
• Running various Windows troubleshooters didn't do much. Only the 'Windows Update' said it had some fixes regarding the database and 'fixed' it.
  
• The bios is up to date. (Version E16H2IMS.112)

Any help would be welcome.

Cheers!

PS: yes this post looks a lot like my
previous post, but that was marked answered because a moderator thinks all checks suggested can be performed within three days, next to a daily routine.