Windows 10: Ramdom BSODs DRIVER_POWER_STATE_FAILURE on Windows 10

This problem has been plaguing me since last November. The BSOD occurs randomly, and with a interval from once per week to multiple times a day. It happens during all types of activities gaming, web browsing, youtube, even when idle while I afk.


There are no signs indicates when it would happen. When it does happen, the computer would freeze both image and audio for brief second then go to the BSOD screen; or the image would freeze while audio continue to play as normal then go to the BSOD screen after a while about 30 seconds, sometimes I even have to force shutdown because the system just stuck there forever.


I would greatly appreciate your help.


DMP file here https://1drv.ms/u/s!AqVDdsCn5gF0ow9aTVrL57tKF-oR?e=Ad6Rlh



Microsoft R Windows Debugger Version 10.0.18362.1 AMD64

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\031220-11375-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 = 0xfffff806`6b400000 PsLoadedModuleList = 0xfffff806`6b848150

Debug session time: Thu Mar 12 14:16:50.595 2020 UTC + 8:00

System Uptime: 0 days 18:54:37.704

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

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

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

Arg4: ffff9b853fe80820, The blocked IRP



Debugging Details:

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



Implicit thread is now ffff9b85`3787f040

*** WARNING: Unable to verify timestamp for igdkmd64.sys



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.719 WinBuild.160101.0800



DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump



DUMP_TYPE: 2



BUGCHECK_P1: 3



BUGCHECK_P2: ffff9b853b080060



BUGCHECK_P3: fffffa8c6f83f7b0



BUGCHECK_P4: ffff9b853fe80820



DRVPOWERSTATE_SUBCODE: 3



FAULTING_THREAD: ffff9b853787f040



IMAGE_NAME: pci.sys



DEBUG_FLR_IMAGE_TIMESTAMP: 0



MODULE_NAME: pci



FAULTING_MODULE: fffff8066ff70000 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-7JI65JU



ANALYSIS_SESSION_TIME: 03-12-2020 14:28:35.0632



ANALYSIS_VERSION: 10.0.18362.1 amd64fre



STACK_TEXT:

fffffa8c`6f815c30 fffff806`6b51508d : ffffab80`db680180 66c3c085`fffffffe ffffab80`ffffffff 00000000`00000001 : nt!KiSwapContext+0x76

fffffa8c`6f815d70 fffff806`6b513f14 : ffff9b85`3787f040 fffff806`00000000 fffff806`00000000 ffff9b85`00000000 : nt!KiSwapThread+0xbfd

fffffa8c`6f815e10 fffff806`6b5136b5 : 00000000`00000000 ffff800a`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x144

fffffa8c`6f815eb0 fffff806`6fe82a9a : fffffa8c`6f815ff8 00000000`00000000 00000000`00000000 ffff9b85`3aa8af00 : nt!KeWaitForSingleObject+0x255

fffffa8c`6f815f90 fffff806`6fe91797 : fffffa8c`00000000 ffff9b85`3aa8af90 00000000`00000004 00000000`00000028 : ACPI!SyncEvalObject+0x29a

fffffa8c`6f816040 fffff806`6fe9135a : 00000000`00000000 ffff800a`5a5ed890 00000000`00000000 ffff800a`56d85710 : ACPI!AMLIEvalNameSpaceObject+0xab

fffffa8c`6f8160a0 fffff806`6fe81586 : ffff9b85`51416b00 fffff806`00000004 ffff800a`5a5ed890 ffff9b85`3aa8b008 : ACPI!ACPIIoctlEvalControlMethod+0xa6

fffffa8c`6f816130 fffff806`6fe810d8 : ffff9b85`378998a0 00000000`00000007 ffff9b85`51416c60 0000647a`a6ded528 : ACPI!ACPIIrpDispatchDeviceControl+0x186

fffffa8c`6f816170 fffff806`6b50a939 : 00000000`00000007 00000000`c00000bb fffffa8c`6f816330 00000000`00000000 : ACPI!ACPIDispatchIrp+0xc8

fffffa8c`6f8161f0 fffff806`836a1e26 : ffff9b85`3d195900 ffff9b85`401f9101 ffff9b85`00000000 fffff806`00000000 : nt!IofCallDriver+0x59

fffffa8c`6f816230 fffff806`8354366a : 00000000`00000000 ffff9b85`3dc05030 00000000`00000000 ffff9b85`3dc05030 : dxgkrnl!DpiFdoDispatchIoctl+0x6f6

fffffa8c`6f816d50 fffff806`6b50a939 : ffff800a`58ec70b0 fffff806`00000014 00000000`00000000 fffffa8c`6f816f28 : dxgkrnl!DpiDispatchIoctl+0xda

fffffa8c`6f816e70 fffff806`83541fb2 : 00000000`00000000 ffff9b85`3dc05180 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59

fffffa8c`6f816eb0 fffff806`87e86e78 : ffffffff`fe363c00 ffff9b85`ffffffff fffff806`83541e50 00000000`0000003c : dxgkrnl!DpEvalAcpiMethod+0x162

fffffa8c`6f816f80 ffffffff`fe363c00 : ffff9b85`ffffffff fffff806`83541e50 00000000`0000003c ffff800a`58ec70b0 : igdkmd64+0x56e78

fffffa8c`6f816f88 ffff9b85`ffffffff : fffff806`83541e50 00000000`0000003c ffff800a`58ec70b0 fffff806`00000014 : 0xffffffff`fe363c00

fffffa8c`6f816f90 fffff806`83541e4f : 00000000`0000003c ffff800a`58ec70b0 fffff806`00000014 00000000`ffffffff : 0xffff9b85`ffffffff

fffffa8c`6f816f98 00000000`0000003c : ffff800a`58ec70b0 fffff806`00000014 00000000`ffffffff 00000000`00000000 : dxgkrnl!_BtlPreAcquireSharedAccess<&CCD_BTL_ACTIVE_PATHS_COLLECTOR::_CollectActiveAdaptersCallback,1,0>+0x1ff

fffffa8c`6f816fa0 ffff800a`58ec70b0 : fffff806`00000014 00000000`ffffffff 00000000`00000000 fffffa8c`6f8170b0 : 0x3c

fffffa8c`6f816fa8 fffff806`00000014 : 00000000`ffffffff 00000000`00000000 fffffa8c`6f8170b0 00000000`00000000 : 0xffff800a`58ec70b0

fffffa8c`6f816fb0 00000000`ffffffff : 00000000`00000000 fffffa8c`6f8170b0 00000000`00000000 00000000`c0000001 : 0xfffff806`00000014

fffffa8c`6f816fb8 00000000`00000000 : fffffa8c`6f8170b0 00000000`00000000 00000000`c0000001 fffff806`87e870da : 0xffffffff





STACK_COMMAND: .thread 0xffff9b853787f040 ; kb



THREAD_SHA1_HASH_MOD_FUNC: 50b1b41d315e034f5b0c27fe86566c735ded73e5



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 59c13f0ce03043f433b56bba7142d72041e3cd64



THREAD_SHA1_HASH_MOD: 524583d6c711df47da664c7ebe202a87e763e740



FOLLOWUP_NAME: MachineOwner



IMAGE_VERSION: 10.0.18362.628



FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys



BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys



PRIMARY_PROBLEM_CLASS: 0x9F_3_ACPI_IMAGE_pci.sys



TARGET_TIME: 2020-03-12T06:16:50.000Z



OSBUILD: 18362



OSSERVICEPACK: 719



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: unknown_date



BUILDDATESTAMP_STR: 160101.0800



BUILDLAB_STR: WinBuild



BUILDOSVER_STR: 10.0.18362.719



ANALYSIS_SESSION_ELAPSED_TIME: 657f



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x9f_3_acpi_image_pci.sys



FAILURE_ID_HASH: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}



Followup: MachineOwner

---------

:)

 

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.

 

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