Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\062009-23228-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*
Symbol information
Executable search path is: SRV*C:\symbols*
http://msdl.microsoft.com/download/symbol
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02a66000 PsLoadedModuleList = 0xfffff800`02c9fe90
Debug session time: Sat Jun 20 19:34:53.566 2009 (GMT+2)
System Uptime: 0 days 8:48:40.806
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 A, {1e0, 2, 1, fffff80002aeffc4}
Unable to load image \SystemRoot\system32\DRIVERS\lpx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for lpx.sys
*** ERROR: Module load completed but symbols could not be loaded for lpx.sys
Probably caused by : lpx.sys ( lpx+933b )
Followup: MachineOwner
---------
1: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
...........
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000001e0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002aeffc4, address which referenced memory
Debugging Details:
------------------
Unable to load image \SystemRoot\system32\DRIVERS\lpx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for lpx.sys
*** ERROR: Module load completed but symbols could not be loaded for lpx.sys
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0a0e0
00000000000001e0
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeReleaseSpinLock+14
fffff800`02aeffc4 f048832100 lock and qword ptr [rcx],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88003dff070 -- (.trap 0xfffff88003dff070)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000000001e0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aeffc4 rsp=fffff88003dff200 rbp=fffffa8006eea452
r8=0000000000000006 r9=0000000000000000 r10=fffff880009e6ac0
r11=fffffa800790e809 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeReleaseSpinLock+0x14:
fffff800`02aeffc4 f048832100 lock and qword ptr [rcx],0 ds:00000000`000001e0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ae44e9 to fffff80002ae4f80
STACK_TEXT:
fffff880`03dfef28 fffff800`02ae44e9 : 00000000`0000000a 00000000`000001e0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03dfef30 fffff800`02ae3160 : fffffa80`06ed9c70 00000000`00000000 0000000c`00f80000 fffff8a0`08620400 : nt!KiBugCheckDispatch+0x69
fffff880`03dff070 fffff800`02aeffc4 : fffff880`03dff218 00000000`00000018 fffff880`016131c0 fffff880`03dff2e0 : nt!KiPageFault+0x260
fffff880`03dff200 fffff880`0160933b : 00000000`c0010022 00000000`00000000 fffffa80`0860b258 fffffa80`0860b060 : nt!KeReleaseSpinLock+0x14
fffff880`03dff230 00000000`c0010022 : 00000000`00000000 fffffa80`0860b258 fffffa80`0860b060 00000000`00000000 : lpx+0x933b
fffff880`03dff238 00000000`00000000 : fffffa80`0860b258 fffffa80`0860b060 00000000`00000000 0000f880`0161317e : 0xc0010022
STACK_COMMAND: kb
FOLLOWUP_IP:
lpx+933b
fffff880`0160933b ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: lpx+933b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: lpx
IMAGE_NAME: lpx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4685a421
FAILURE_BUCKET_ID: X64_0xA_lpx+933b
BUCKET_ID: X64_0xA_lpx+933b
Followup: MachineOwner
