0: kd> !analyze -v
*******************************************************************************
*
*
* 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: fffffa80054ca050, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the
Functional Device Object of the stack
Arg4: fffffa8007e37010, The blocked IRP
Debugging Details:
*** ERROR: Module load completed but symbols could not be loaded for
ahcix64.sys
TRIAGER: Could not open triage file : C:\Debuggers\x64\triage\modclass.ini,
error 2
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: fffffa8003accc90
IMAGE_NAME: ahcix64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c9b227e
MODULE_NAME: ahcix64
FAULTING_MODULE: fffff88001039000 ahcix64
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
fffff80000b9bd58 fffff80002bb8d92 : fffffa800738cea0 0000000000000000
0000000000000000 fffffa8007a6d000 : nt!RtlpBreakWithStatusInstruction
fffff80000b9bd60 fffff80002bba158 : fffff80000000004 fffff80002cc9b80
000000000000000f fffff80002c51cc0 : nt!KiBugCheckDebugBreak+0x12
fffff80000b9bdc0 fffff80002ad1744 : fffffa8008021260 fffff80002b7e054
fffff80000000068 0000000000000004 : nt!KeBugCheck2+0xcf8
fffff80000b9c490 fffff80002b3db52 : 000000000000009f 0000000000000003
fffffa80054ca050 fffff80000b9c518 : nt!KeBugCheckEx+0x104
fffff80000b9c4d0 fffff80002add062 : fffff80000b9c600 fffff80000b9c600
0000000000000001 0000000000000001 : nt! ?? ::FNODOBFM::string'+0x34a90 fffff80000b9c570 fffff80002adcf06 : fffff80002c79740 0000000000025385 0000000000000000 0000000000000000 : nt!KiProcessTimerDpcTable+0x66 fffff80000b9c5e0 fffff80002adcdee : 0000000589921c88 fffff80000b9cc58 0000000000025385 fffff80002c47328 : nt!KiProcessExpiredTimerList+0xc6 fffff80000b9cc30 fffff80002adcbd7 : 00000002150b0fc1 0000000200025385 00000002150b0f37 0000000000000085 : nt!KiTimerExpiration+0x1be fffff80000b9ccd0 fffff80002ac936a : fffff80002c43e80 fffff80002c51cc0 fffff80000000001 fffff88000000000 : nt!KiRetireDpcList+0x277 fffff80000b9cd80 0000000000000000 : fffff80000b9d000 fffff80000b97000 fffff80000b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
0: kd> !stacks
Proc.Thread .Thread Ticks ThreadState Blocker
[fffff80002c521c0 Idle]
0.000000 fffff80002c51cc0 0000000 RUNNING
nt!RtlpBreakWithStatusInstruction
0.000000 fffff880009fe040 0000000 RUNNING amdppm!ReadIoMemRaw+0x30
0.000000 fffff88002f6f040 0000000 RUNNING amdppm!ReadIoMemRaw+0x30
0.000000 fffff88002fe0040 0000000 RUNNING amdppm!ReadIoMemRaw+0x30
0.000000 fffff880009bd040 0000000 RUNNING amdppm!ReadIoMemRaw+0x30
0.000000 fffff88003093040 ffffdd5b RUNNING amdppm!ReadIoMemRaw+0x30
[… rest of the threads are BLOCKED]
Yes I know the structure, and am going to try to peel off the infos…
-pro
On Thu, Apr 5, 2012 at 6:21 AM, Scott Noone wrote:
> I don?t have this data type in my symbols either, I filed a bug against
> the documentation at least.
>
> Luckily the article provides output of the command working with private
> symbols though, so you know the structure layout:
>
> 0: kd> dt nt!TRIAGE_9F_POWER 82b5dae0
> +0x000 Signature : 0x8000
> +0x002 Revision : 1
> +0x004 IrpList : 0x82b78480 _LIST_ENTRY
> +0x008 ThreadList : 0x82b77f28 _LIST_ENTRY
> +0x00c DelayedWorkQueue : 0x82b715bc _TRIAGE_EX_WORK_QUEUE
>
> What’s the bugcheck information for the new crash?
>
>
> -scott
>
> –
> Scott Noone
> Consulting Associate and Chief System Problem Analyst
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> “Prokash Sinha” wrote in message news:xxxxx@windbg…
> One thing I was trying to find is the type nt!TRIAGE_9F_POWER this is for
> a different crash ( after modifying the hiberfile size configuration, now
> it is 100% of the memory installed ).
>
>
> But on 64bit Win 7, and I understand I’ve stripped os files.
>
> kd> 0: kd> dt nt!TRIAGE_9F_POWER fffff80000b9c518
> Symbol nt!TRIAGE_9F_POWER not found
>
>
> http://msdn.microsoft.com/en- us/library/windows/hardware/
> ff559329(v=vs.85).aspxhttp:tells how to use it…
>
> -pro
>
>
>
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.**cfm?name=ListServerhttp:
></http:></http:>