New
#1
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 .
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 !