I recently purchased an ASUS G56JK for college (amongst other things). A couple of days after I received it, I got a BSOD which said "DRIVER_POWER_STATE_FAILURE". I figured I'd wait and see if I got it again to determine if it was serious enough to be bothered with. I might have waited too long, because what used to happen maybe once a week has happened twice so far in the two hours that I've used my laptop today. I'd love to hear any suggestions anyone has on this, because not only is this interfering with my gaming, it's also interfering with school, and that's not something to mess about with. The DMPs from today are below.
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: ffffe000939dd060, Physical Device Object of the stack Arg3: ffffd000ceb3f930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: ffffe00092f85b40, The blocked IRP Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4 MODULE_NAME: pci FAULTING_MODULE: fffff8002130e000 pci DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: ffffd000`ceb3f8f8 fffff800`2b806586 : 00000000`0000009f 00000000`00000003 ffffe000`939dd060 ffffd000`ceb3f930 : nt!KeBugCheckEx ffffd000`ceb3f900 fffff800`2b8064a6 : ffffe000`92f84f08 ffffe000`ffffffff ffffe000`92f84f48 fffff800`2b650190 : nt!PopIrpWatchdogBugcheck+0xde ffffd000`ceb3f960 fffff800`2b64c760 : 00000000`00000000 ffffd000`ceb3fab0 ffffe000`92f84f40 ffffd000`00000002 : nt!PopIrpWatchdog+0x32 ffffd000`ceb3f9b0 fffff800`2b7617ea : ffffd000`ceb15180 ffffd000`ceb15180 ffffd000`ceb213c0 ffffe000`999f4080 : nt!KiRetireDpcList+0x4f0 ffffd000`ceb3fc60 00000000`00000000 : ffffd000`ceb40000 ffffd000`ceb3a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys Followup: MachineOwner ---------
|
|
|
(Obvious attempt to separate the two DMPs is obvious)
|
|
|
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: ffffe001fd9d5880, Physical Device Object of the stack Arg3: ffffd001ad67c930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: ffffe001fd9e7680, The blocked IRP Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4 MODULE_NAME: pci FAULTING_MODULE: fffff801e8971000 pci DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: ffffd001`ad67c8f8 fffff803`9e606586 : 00000000`0000009f 00000000`00000003 ffffe001`fd9d5880 ffffd001`ad67c930 : nt!KeBugCheckEx ffffd001`ad67c900 fffff803`9e6064a6 : ffffe001`fd9e3f08 ffffe000`ffffffff ffffe001`fd9e3f48 fffff803`9e450190 : nt!PopIrpWatchdogBugcheck+0xde ffffd001`ad67c960 fffff803`9e44c760 : 00000000`00000000 ffffd001`ad67cab0 ffffe001`fd9e3f40 ffffd001`00000002 : nt!PopIrpWatchdog+0x32 ffffd001`ad67c9b0 fffff803`9e5617ea : ffffd001`ad667180 ffffd001`ad667180 ffffd001`ad6733c0 ffffe002`03f11080 : nt!KiRetireDpcList+0x4f0 ffffd001`ad67cc60 00000000`00000000 : ffffd001`ad67d000 ffffd001`ad677000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys Followup: MachineOwner ---------