Windows 10: Driver_Power_State_Failure BSOD

My Alienware 17 R5 has been experiencing some problems lately. To begin with, I was sailing last year from Aug 2019 until Jan 2020. I didnt update anything in my laptop since internet signal was not that good at the middle of the sea. So the first thing I did when I came home was updating my laptop, Windows Update, Drivers, Games, etc.
I would often leave my laptop open overnight so that I could finish downloading my games. But I was surprised to see the next day my laptop in the log-in screen. Meaning it restarted sometime in the middle of the night. I didnt bother at first, but when it happened while I'm gaming, I dont know what to do. It showed me BSOD with the error Drive_Power_State_Failure. And when I checked Event Viewer, it would show me an error with the AWCC.exe.

So I checked forums why it is happening and I read it has something to do with drivers, so I checked my device manager to find 2 AWCC.exe drivers installed. So I thought the problem was solved, but maybe after a day or two, BSOD started happening again. Randomly. With the same error, withe same application. I asked help from my friends and suggested to remove AWCC to see if the problem is really coming from it. I uninstalled it but still BSOD keeps on happening.


So the last option they told me was to install a clean Windows 10 OS, to start from scratch everything new. Maybe something wrong with the update, we are not sure. Just yesterday I was able to make a clean install of WIn 10 in my laptop. But after a few hours, same BSOD error came with the same application. We are not sure anymore why this is happening. Maybe you guys have the same experience or have some idea. Thanks


Edit: I also tried reverting my GPU driver to the stock one but still I got BSOD'd.



I'll aslo add one of the minidump created from one of my BSOD.




Microsoft R Windows Debugger Version 10.0.18362.1 X86

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\evanj\Desktop\022820-11593-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 18362 MP 12 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff804`7e800000 PsLoadedModuleList = 0xfffff804`7ec48190

Debug session time: Fri Feb 28 01:45:45.381 2020 UTC + 8:00

System Uptime: 1 days 10:39:06.588

Loading Kernel Symbols

..



Press ctrl-c cdb, kd, ntsd or ctrl-break windbg to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.



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

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

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

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

Loading User Symbols

Loading unloaded module list

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

For analysis of this file, run !analyze -v

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

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

Arg4: ffff9d04cc97c980, The blocked IRP



Debugging Details:

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





KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 10.0.18362.657 WinBuild.160101.0800



DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump



DUMP_TYPE: 2



BUGCHECK_P1: 3



BUGCHECK_P2: ffff9d04b6793060



BUGCHECK_P3: ffffed87f102f7b0



BUGCHECK_P4: ffff9d04cc97c980



DRVPOWERSTATE_SUBCODE: 3



IMAGE_NAME: pci.sys



DEBUG_FLR_IMAGE_TIMESTAMP: 0



MODULE_NAME: pci



FAULTING_MODULE: fffff80480570000 pci



CPU_COUNT: c



CPU_MHZ: 8a0



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: a



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



BUGCHECK_STR: 0x9F



PROCESS_NAME: System



CURRENT_IRQL: 2



ANALYSIS_SESSION_HOST: DESKTOP-FU8DHJS



ANALYSIS_SESSION_TIME: 02-28-2020 01:48:56.0272



ANALYSIS_VERSION: 10.0.18362.1 x86fre



STACK_TEXT:

ffffed87`f102f778 fffff804`7eaee4d7 : 00000000`0000009f 00000000`00000003 ffff9d04`b6793060 ffffed87`f102f7b0 : nt!KeBugCheckEx

ffffed87`f102f780 fffff804`7eaee3e1 : ffff9d04`cfebdaa0 ffff9d04`cc4ba5f0 ffffaf80`05600100 ffffaf80`05600180 : nt!PopIrpWatchdogBugcheck+0xef

ffffed87`f102f7f0 fffff804`7e86ba89 : ffff9d04`cfebdad8 00000000`00000080 00000000`00000009 ffff9d04`00000002 : nt!PopIrpWatchdog+0x31

ffffed87`f102f840 fffff804`7e86a7e9 : 00000000`00000014 00000000`00989680 00000000`00489cb0 00000000`000000c8 : nt!KiProcessExpiredTimerList+0x169

ffffed87`f102f930 fffff804`7e9c5054 : ffffffff`00000000 ffffaf80`05600180 ffffaf80`05611340 ffff9d04`da3240c0 : nt!KiRetireDpcList+0x4e9

ffffed87`f102fb60 00000000`00000000 : ffffed87`f1030000 ffffed87`f1029000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84





THREAD_SHA1_HASH_MOD_FUNC: 418dcf5cc7a95525fe8ac8ffec7980c508fac304



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 380ee536789d4b77d82e9ab3a599c8d978e0118f



THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693



FOLLOWUP_NAME: MachineOwner



IMAGE_VERSION: 10.0.18362.628



STACK_COMMAND: .thread ; .cxr ; kb



FAILURE_BUCKET_ID: 0x9F_3_igdkmd64_IMAGE_pci.sys



BUCKET_ID: 0x9F_3_igdkmd64_IMAGE_pci.sys



PRIMARY_PROBLEM_CLASS: 0x9F_3_igdkmd64_IMAGE_pci.sys



TARGET_TIME: 2020-02-27T17:45:45.000Z



OSBUILD: 18362



OSSERVICEPACK: 657



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: 2005-04-23 09:40:32



BUILDDATESTAMP_STR: 160101.0800



BUILDLAB_STR: WinBuild



BUILDOSVER_STR: 10.0.18362.657



ANALYSIS_SESSION_ELAPSED_TIME: 6f47



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x9f_3_igdkmd64_image_pci.sys



FAILURE_ID_HASH: {286c55ea-1207-29ac-12e0-be8aeff9a0fd}



Followup: MachineOwner

---------

:)

 

BSOD : DRIVER_POWER_STATE_FAILURE

I have a laptop ASUS X550JK, I get the BSOD with DRIVER_POWER_STATE_FAILURE, it happens randomly, Before the BSOD occurs, I notice a rise in CPU temperature and the fan makes noise





When I check the dump file, I get this :





What I've tried:

1. I've tried to install Windows 10 with USB and CD/DVD Drive as
   well, but the same issue happened every time.
   
2. I've updated all drivers (using Driver Booster,Driver
   Reviver and DriverPack solution).
   
3. I've changed some Power settings.
   

NOTE: With Linux (Ubuntu 19.04 & Mint), everything works just fine, I've used Linux for 1 week, and I didn't face any issue with it.

Can anyone help me to get resolve this issue, I've spent a lot of time to solve it with no success

 

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.

 

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.