2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 9b868096, The address that the exception occurred at
Arg3: 9b29fb40, Exception Record Address
Arg4: 9b29f720, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt.
FAULTING_IP:
lvrs+3096
9b868096 395e24 cmp dword ptr [esi+24h],ebx
EXCEPTION_RECORD: 9b29fb40 -- (.exr 0xffffffff9b29fb40)
ExceptionAddress: 9b868096 (lvrs+0x00003096)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0037fd4c
Attempt to read from address 0037fd4c
CONTEXT: 9b29f720 -- (.cxr 0xffffffff9b29f720)
eax=0037fd28 ebx=00000000 ecx=00000000 edx=00000000 esi=0037fd28 edi=86d2d644
eip=9b868096 esp=9b29fc08 ebp=9b29fc58 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
lvrs+0x3096:
9b868096 395e24 cmp dword ptr [esi+24h],ebx ds:0023:0037fd4c=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 0037fd4c
READ_ADDRESS: GetPointerFromAddress: unable to read from 82db484c
Unable to read MiSystemVaType memory at 82d93f00
0037fd4c
FOLLOWUP_IP:
lvrs+3096
9b868096 395e24 cmp dword ptr [esi+24h],ebx
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 9b8684bb to 9b868096
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9b29fc58 9b8684bb 00000002 86d1ce24 0037fd28 lvrs+0x3096
9b29fc88 9b865f52 86d1ce24 00000002 0037fd28 lvrs+0x34bb
9b29fcb0 9b870ee6 86d1ce24 00000002 0037fd28 lvrs+0xf52
9b29fd50 82e5400f 00000000 bcc17211 00000000 lvrs+0xbee6
9b29fd90 82cfa699 9b870c3c 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: lvrs+3096
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: lvrs
IMAGE_NAME: lvrs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f16687f
STACK_COMMAND: .cxr 0xffffffff9b29f720 ; kb
FAILURE_BUCKET_ID: 0x7E_lvrs+3096
BUCKET_ID: 0x7E_lvrs+3096
Followup: MachineOwner
---------
2: kd> lmvm lvrs
start end module name
9b865000 9b8af200 lvrs T (no symbols)
Loaded symbol image file: lvrs.sys
Image path: \SystemRoot\system32\DRIVERS\lvrs.sys
Image name: lvrs.sys
Timestamp: Wed Jan 18 07:36:47 2012 (4F16687F)
CheckSum: 00052086
ImageSize: 0004A200
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
