Windows 10: Driver_power_state_failure

After upgrading to windows 10 I can't stop having BSOD such as " DRIVER_POWER_STATE_FAILURE "
It's driving me crazy, the PC isn't new but it isn't old either.
Driver as far as I know are up to date.
Can someone kindly please help me *Sad.

Minidump.

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Unique Expertise, Guaranteed Results)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`0820a000 PsLoadedModuleList = 0xfffff802`085b8170
Debug session time: Mon Aug 27 06:00:22.347 2018 (UTC - 4:00)
System Uptime: 0 days 11:25:52.170
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffa78ab283f060, Physical Device Object of the stack
Arg3: fffff8020a65d7d0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffa78ab2836010, The blocked IRP

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffa78ab2682580

IMAGE_NAME: xusb22.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: xusb22

FAULTING_MODULE: fffff80af4a50000 xusb22

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff802`0a65d798 fffff802`0847bb79 : 00000000`0000009f 00000000`00000003 ffffa78a`b283f060 fffff802`0a65d7d0 : nt!KeBugCheckEx
fffff802`0a65d7a0 fffff802`0847ba82 : ffffa78a`b2837560 ffffa78a`b40e41f0 00000000`0000003e fffff802`06ecb180 : nt!PopIrpWatchdogBugcheck+0xed
fffff802`0a65d810 fffff802`08259909 : ffffa78a`b2837598 0000005f`d09aee00 ffffa78a`b28375d8 00000000`00000002 : nt!PopIrpWatchdog+0x22
fffff802`0a65d860 fffff802`08258847 : 00000000`00000016 fffff802`0820f04a 00000000`003bb94b 00000000`00000019 : nt!KiProcessExpiredTimerList+0x159
fffff802`0a65d950 fffff802`083b63da : 00000000`00000000 fffff802`06ecb180 00000000`001a6570 fffff802`08674400 : nt!KiRetireDpcList+0x4c7
fffff802`0a65db60 00000000`00000000 : fffff802`0a65e000 fffff802`0a657000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_xusb22.sys

BUCKET_ID: X64_0x9F_3_IMAGE_xusb22.sys

Followup: MachineOwner
---------

THANK YOU SO MUCH !

:)

 

recurring Driver_power_state_failure with Windows 10

Latest update #2: bad news! Driver_power_state_failure error occurred again yesterday, so the latest nVidia driver update does not appear to have been the solution. So I shifted my focus to ZigZags suggestion to update the NW1900.sys driver, but I cannot
find an update anywhere online. My PC display driver is provided by NextWindow, but I think they are no longer in business. I have version 1.4.0.0, which was released in 2012-5-17. Any suggestions.

 

DRIVER_POWER_STATE_FAILURE on Windows 10

Hi,

Thank you for the response! After your words about Atapi driver - I've checked out all my hard drives (I have 4 HDDs in 6 partitions) and figured that I have only 5 partitions now. One HDD is missing in this list and looks like it broken.

I disconnected broken HDD from my PC and DRIVER_POWER_STATE_FAILURE doesn't appear anymore.

Thank you for help.

 

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.