WIN7 neue regelmäßige Bluescreens DRIVER_POWER_STATE_FAILURE (9f)
Hallo zusammen,
bin neu hier und hoffe, es ist ok, wenn ich einen neuen Thread mit meinem persönlichen Problem aufmache: Ich nutze seit einiger Zeit begeistert ein ASUS Ultrabook UX31A mit WIN7.
Seit einigen Wochen bekomme ich regelmäßige Bluescreens, die Maschine stürzt während des StandBy ab.
Habe daraufhin schließlich das Betriebssystem komplett neu aufgespielt, mühsam wieder auf den neuesten Stand gebracht - danach war es auch ne Weile gut, jetzt geht das wieder regelmäßig los.
Es scheint ein Treiber zu sein - die Dump-Analyse weist auf pci.sys hin. Aber was muß ich jetzt tun??? Die Minidumps weisen immer auf denselben Fehler hin.
Vielen Dank für den Fall, daß sich jemand erbarmt!!!
Olaf
-------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021915-11310-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00226892?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`15c91022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0238d022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0eeba592?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`044073c0?
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03a65000 PsLoadedModuleList = 0xfffff800`03ca9890
Debug session time: Wed Feb 18 17:31:32.201 2015 (UTC + 1:00)
System Uptime: 0 days 4:32:32.543
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
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80038aba10, fffff800044073d8, fffffa800a734010}
Probably caused by : pci.sys
Followup: MachineOwner
---------
0: 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: fffffa80038aba10, Physical Device Object of the stack
Arg3: fffff800044073d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800a734010, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000f59000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE: FFFFF8000440DFB0
STACK_TEXT:
fffff800`04407388 fffff800`03b4ab92 : 00000000`0000009f 00000000`00000003 fffffa80`038aba10 fffff800`044073d8 : nt!KeBugCheckEx
fffff800`04407390 fffff800`03ae5cfc : fffff800`044074c0 fffff800`044074c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`04407430 fffff800`03ae5b96 : fffffa80`03ec1c58 fffffa80`03ec1c58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`044074a0 fffff800`03ae5a7e : 00000026`12e01b2a fffff800`04407b18 00000000`000ffea9 fffff800`03c5a7a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04407af0 fffff800`03ae5867 : 00000008`e778f5ca 00000008`000ffea9 00000008`e778f529 00000000`000000a9 : nt!KiTimerExpiration+0x1be
fffff800`04407b90 fffff800`03ad1bca : fffff800`03c56e80 fffff800`03c64cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04407c40 00000000`00000000 : fffff800`04408000 fffff800`04402000 fffff800`04407c00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.1.7601.17514
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_Netwsw00_IMAGE_pci.sys
BUCKET_ID: X64_0x9F_3_POWER_DOWN_Netwsw00_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_netwsw00_image_pci.sys
FAILURE_ID_HASH: {89522579-be68-ffbe-efc9-652fde682f57}
Followup: MachineOwner
---------
Hallo zusammen,
bin neu hier und hoffe, es ist ok, wenn ich einen neuen Thread mit meinem persönlichen Problem aufmache: Ich nutze seit einiger Zeit begeistert ein ASUS Ultrabook UX31A mit WIN7.
Seit einigen Wochen bekomme ich regelmäßige Bluescreens, die Maschine stürzt während des StandBy ab.
Habe daraufhin schließlich das Betriebssystem komplett neu aufgespielt, mühsam wieder auf den neuesten Stand gebracht - danach war es auch ne Weile gut, jetzt geht das wieder regelmäßig los.
Es scheint ein Treiber zu sein - die Dump-Analyse weist auf pci.sys hin. Aber was muß ich jetzt tun??? Die Minidumps weisen immer auf denselben Fehler hin.
Vielen Dank für den Fall, daß sich jemand erbarmt!!!
Olaf
-------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021915-11310-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00226892?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`15c91022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0238d022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0eeba592?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`044073c0?
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03a65000 PsLoadedModuleList = 0xfffff800`03ca9890
Debug session time: Wed Feb 18 17:31:32.201 2015 (UTC + 1:00)
System Uptime: 0 days 4:32:32.543
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
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80038aba10, fffff800044073d8, fffffa800a734010}
Probably caused by : pci.sys
Followup: MachineOwner
---------
0: 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: fffffa80038aba10, Physical Device Object of the stack
Arg3: fffff800044073d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800a734010, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000f59000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE: FFFFF8000440DFB0
STACK_TEXT:
fffff800`04407388 fffff800`03b4ab92 : 00000000`0000009f 00000000`00000003 fffffa80`038aba10 fffff800`044073d8 : nt!KeBugCheckEx
fffff800`04407390 fffff800`03ae5cfc : fffff800`044074c0 fffff800`044074c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`04407430 fffff800`03ae5b96 : fffffa80`03ec1c58 fffffa80`03ec1c58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`044074a0 fffff800`03ae5a7e : 00000026`12e01b2a fffff800`04407b18 00000000`000ffea9 fffff800`03c5a7a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04407af0 fffff800`03ae5867 : 00000008`e778f5ca 00000008`000ffea9 00000008`e778f529 00000000`000000a9 : nt!KiTimerExpiration+0x1be
fffff800`04407b90 fffff800`03ad1bca : fffff800`03c56e80 fffff800`03c64cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04407c40 00000000`00000000 : fffff800`04408000 fffff800`04402000 fffff800`04407c00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.1.7601.17514
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_Netwsw00_IMAGE_pci.sys
BUCKET_ID: X64_0x9F_3_POWER_DOWN_Netwsw00_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_netwsw00_image_pci.sys
FAILURE_ID_HASH: {89522579-be68-ffbe-efc9-652fde682f57}
Followup: MachineOwner
---------
