- Thread Author
- #1
Some weeks ago I made a reinstall of my Win7 Home Premium x64 (a Dell M1330 with 4gb RAM). After then, my machine starts having random BSOD errors when going or recovering from sleep or hibernate mode. The error is a DRIVER_POWER_STATE_FAILURE, with code 0x0000009f.
I attach here the info grabbed with W7F Diagnostic Tool, CPU z pictures and RAMmon html report. If it helps, here is the info I see with WinDbg looking the last minidump.
Tell me if you need something else, thanks in advance!
I attach here the info grabbed with W7F Diagnostic Tool, CPU z pictures and RAMmon html report. If it helps, here is the info I see with WinDbg looking the last minidump.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121412-26286-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`02589c32?
Symbol search path is: srv*C:\symbols2*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02a54000 PsLoadedModuleList = 0xfffff800`02c98670
Debug session time: Fri Dec 14 21:22:42.463 2012 (UTC - 3:00)
System Uptime: 2 days 8:31:41.018
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa80036dcb50, fffff800041a0510}
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80036dcb50, The thread currently holding on to the Pnp lock.
Arg4: fffff800041a0510
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 4
FAULTING_THREAD: fffffa80036dcb50
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LOCK_ADDRESS: fffff80002cceb80 -- (!locks fffff80002cceb80)
Resource @ nt!PiEngineLock (0xfffff80002cceb80) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff80002cceb80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002ac8a32 to fffff80002ad5e7a
STACK_TEXT:
fffff880`031e7660 fffff800`02ac8a32 : fffffa80`036dcb50 fffffa80`036dcb50 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`031e77a0 fffff800`02ad9d8f : fffff880`031e7c10 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`031e7830 fffff800`02b8aea5 : 00000000`00000000 00000000`00000000 fffffa80`036b1d00 fffff800`02d38500 : nt!KeWaitForSingleObject+0x19f
fffff880`031e78d0 fffff800`02e6ed9e : fffff800`02cce940 fffff880`031e79a4 00000000`00000000 00000000`00000001 : nt!PnpDeviceCompletionQueueGetCompletedRequest+0x35
fffff880`031e7920 fffff800`02ebbdd8 : fffffa80`036b1d10 fffffa80`036b1d10 00000000`00000002 00000000`00000000 : nt!PnpDeviceCompletionProcessCompletedRequests+0x5e
fffff880`031e7950 fffff800`02ebc288 : fffff800`02ccc500 00000000`00000000 00000000`00000001 fffff800`02d385e8 : nt!PipProcessDevNodeTree+0x378
fffff880`031e7bc0 fffff800`02bccee7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031e7c10 fffff800`02adc641 : fffff800`02bccbc0 fffff800`02dc5501 fffffa80`036dcb00 fffffa80`036dcb50 : nt!PnpDeviceActionWorker+0x327
fffff880`031e7cb0 fffff800`02d69e5a : 00000000`00000000 fffffa80`036dcb50 00000000`00000080 fffffa80`036cc5f0 : nt!ExpWorkerThread+0x111
fffff880`031e7d40 fffff800`02ac3d26 : fffff880`009e7180 fffffa80`036dcb50 fffff880`009f1f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031e7d80 00000000`00000000 : fffff880`031e8000 fffff880`031e2000 fffff880`031e74b0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .thread 0xfffffa80036dcb50 ; kb
FOLLOWUP_IP:
nt!KiSwapContext+7a
fffff800`02ad5e7a 488d8c2400010000 lea rcx,[rsp+100h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSwapContext+7a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
FAILURE_BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a
BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a
Followup: MachineOwner
---------Tell me if you need something else, thanks in advance!
