Hab mich schon ein bisschen eingelesen hier im Forum, weiß aber nicht wie ich meinen Fehler behebe.
Ich hab ein Asus S56, nachdem ich windows neu installiert habe kommt nach jedem zuklappen (energie sparen) beim aufklappen ein bluescreen (driver_power_state_failure).
Das hier habe ich über den bluescreen auswerten lassen:
Also müsste usbhub.sys das Problem sein, oder? Wie werde ich das los? in den USB-Ports steckt nichts, Bluescreen kommt trotzdem. Wäre SEHR dankbar über Hilfe, da sogar nach einschicken zu ASUS nur die Festplatte gewechselt wurde und der Fehler immer noch da ist. Habe einfach keine Lust nochmal 2 Wochen ohne Laptop in die Uni zu gehen und dann schon wieder den Fehler zu haben. Danke!
Ich hab ein Asus S56, nachdem ich windows neu installiert habe kommt nach jedem zuklappen (energie sparen) beim aufklappen ein bluescreen (driver_power_state_failure).
Das hier habe ich über den bluescreen auswerten lassen:
*******************************************************************************
* *
* 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: fffffa80074513c0, Physical Device Object of the stack
Arg3: fffff803b708b7e0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800a52e010, The blocked IRP
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: USBHUB!_DEVICE_EXTENSION_PDO ***
*** ***
*************************************************************************
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5010ab53
MODULE_NAME: usbhub
FAULTING_MODULE: fffff88005b81000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF803B7091FB0
STACK_TEXT:
fffff803`b708b7a8 fffff803`b579f41e : 00000000`0000009f 00000000`00000003 fffffa80`074513c0 fffff803`b708b7e0 : nt!KeBugCheckEx
fffff803`b708b7b0 fffff803`b579f451 : fffffa80`09d589b0 fffffa80`0dc771f0 fffff803`b708b939 fffff803`b56b5686 : nt!PopIrpWatchdogBugcheck+0xe2
fffff803`b708b810 fffff803`b56b68b4 : fffffa80`0dc771f0 fffffa80`0dc77080 fffff803`b708bb18 fffff880`02e75180 : nt!PopIrpWatchdog+0x32
fffff803`b708b860 fffff803`b56b6ed5 : 00000000`00000000 00000000`00002fa2 00000000`00140001 00000000`00000002 : nt!KiProcessExpiredTimerList+0x214
fffff803`b708b9a0 fffff803`b56b6d88 : fffff803`b5905180 fffff803`b5907f80 00000000`00000005 00000000`002f6bea : nt!KiExpireTimerTable+0xa9
fffff803`b708ba40 fffff803`b56b0e76 : fffffa80`00000000 00001f80`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff803`b708baf0 fffff803`b56b557a : fffff803`b5905180 fffff803`b5905180 00000000`00183db0 fffff803`b595f880 : nt!KiRetireDpcList+0x1f6
fffff803`b708bc60 00000000`00000000 : fffff803`b708c000 fffff803`b7086000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_btfilter_IMAGE_usbhub.sys
BUCKET_ID: 0x9F_3_btfilter_IMAGE_usbhub.sys
Followup: MachineOwner
---------
* *
* 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: fffffa80074513c0, Physical Device Object of the stack
Arg3: fffff803b708b7e0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800a52e010, The blocked IRP
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: USBHUB!_DEVICE_EXTENSION_PDO ***
*** ***
*************************************************************************
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5010ab53
MODULE_NAME: usbhub
FAULTING_MODULE: fffff88005b81000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF803B7091FB0
STACK_TEXT:
fffff803`b708b7a8 fffff803`b579f41e : 00000000`0000009f 00000000`00000003 fffffa80`074513c0 fffff803`b708b7e0 : nt!KeBugCheckEx
fffff803`b708b7b0 fffff803`b579f451 : fffffa80`09d589b0 fffffa80`0dc771f0 fffff803`b708b939 fffff803`b56b5686 : nt!PopIrpWatchdogBugcheck+0xe2
fffff803`b708b810 fffff803`b56b68b4 : fffffa80`0dc771f0 fffffa80`0dc77080 fffff803`b708bb18 fffff880`02e75180 : nt!PopIrpWatchdog+0x32
fffff803`b708b860 fffff803`b56b6ed5 : 00000000`00000000 00000000`00002fa2 00000000`00140001 00000000`00000002 : nt!KiProcessExpiredTimerList+0x214
fffff803`b708b9a0 fffff803`b56b6d88 : fffff803`b5905180 fffff803`b5907f80 00000000`00000005 00000000`002f6bea : nt!KiExpireTimerTable+0xa9
fffff803`b708ba40 fffff803`b56b0e76 : fffffa80`00000000 00001f80`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff803`b708baf0 fffff803`b56b557a : fffff803`b5905180 fffff803`b5905180 00000000`00183db0 fffff803`b595f880 : nt!KiRetireDpcList+0x1f6
fffff803`b708bc60 00000000`00000000 : fffff803`b708c000 fffff803`b7086000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_btfilter_IMAGE_usbhub.sys
BUCKET_ID: 0x9F_3_btfilter_IMAGE_usbhub.sys
Followup: MachineOwner
---------
Also müsste usbhub.sys das Problem sein, oder? Wie werde ich das los? in den USB-Ports steckt nichts, Bluescreen kommt trotzdem. Wäre SEHR dankbar über Hilfe, da sogar nach einschicken zu ASUS nur die Festplatte gewechselt wurde und der Fehler immer noch da ist. Habe einfach keine Lust nochmal 2 Wochen ohne Laptop in die Uni zu gehen und dann schon wieder den Fehler zu haben. Danke!