Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\ DOWNLOADS\ DUMPS\adamski\021411-19546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`8078ada4?
Symbol search path is: SRV*C:\XSymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82e4f000 PsLoadedModuleList = 0x82f97810
Debug session time: Mon Feb 14 18:45:56.142 2011 (UTC + 0:00)
System Uptime: 0 days 1:22:56.060
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.......
0: kd> !analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, 855aeec8, 8078adb0, 85d1f9f8}
Unable to load image \SystemRoot\system32\DRIVERS\appliand.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for appliand.sys
*** ERROR: Module load completed but symbols could not be loaded for appliand.sys
Probably caused by : ntkrpamp
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 855aeec8, Physical Device Object of the stack
Arg3: 8078adb0, Functional Device Object of the stack
Arg4: 85d1f9f8, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: ntkrpamp
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: ntkrpamp
FAULTING_MODULE: 963c8000 appliand
IRP_ADDRESS: 85d1f9f8
DEVICE_OBJECT: 8761f028
DRIVER_OBJECT: 8733be90
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: fssm32.exe
CURRENT_IRQL: 2
STACK_TEXT:
8078ad64 82e8b044 0000009f 00000003 855aeec8 nt!KeBugCheckEx+0x1e
8078add0 82e8a8d8 8078ae7c 00000000 858e9bd8 nt!PopCheckIrpWatchdog+0x1f5
8078ae08 82eb916d 82f90a20 00000000 69fb11fb nt!PopCheckForIdleness+0x73
8078ae4c 82eb9111 82f78d20 8078af78 00000001 nt!KiProcessTimerDpcTable+0x50
8078af38 82eb8fce 82f78d20 8078af78 00000000 nt!KiProcessExpiredTimerList+0x101
8078afac 82eb734e 0004de00 bdee8d34 00000000 nt!KiTimerExpiration+0x25c
8078aff4 82eb6b1c bdee8ce4 00000000 00000000 nt!KiRetireDpcList+0xcb
8078aff8 bdee8ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82eb6b1c 00000000 0000001a 00d6850f bb830000 0xbdee8ce4
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_ntkrpamp
BUCKET_ID: 0x9F_3_IMAGE_ntkrpamp
Followup: MachineOwner
