Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff80003525c06, 2, 0, fffff800032ae7a2}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
Followup: MachineOwner
---------
2: 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: fffff80003525c06, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800032ae7a2, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b90e0
fffff80003525c06
CURRENT_IRQL: 2
FAULTING_IP:
nt!RtlDispatchException+122
fffff800`032ae7a2 410fb60c24 movzx ecx,byte ptr [r12]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880033628d0 -- (.trap 0xfffff880033628d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800034a11ec rbx=0000000000000000 rcx=fffff80003525c44
rdx=fffff80003525bac rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032ae7a2 rsp=fffff88003362a60 rbp=fffff88003363908
r8=0000000000002029 r9=0000000000002029 r10=fffff88003363d40
r11=fffff88003362aa8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!RtlDispatchException+0x122:
fffff800`032ae7a2 410fb60c24 movzx ecx,byte ptr [r12] ds:f000:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003280ca9 to fffff80003281740
STACK_TEXT:
fffff880`03362788 fffff800`03280ca9 : 00000000`0000000a fffff800`03525c06 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03362790 fffff800`0327f920 : 00000000`00000000 00000000`0000005a 00000000`00000000 fffff880`066215a5 : nt!KiBugCheckDispatch+0x69
fffff880`033628d0 fffff800`032ae7a2 : fffff800`03525c06 fffff880`03362aa8 fffff880`03363908 fffff800`03211000 : nt!KiPageFault+0x260
fffff880`03362a60 fffff800`032bb9ef : fffff880`03363908 fffff880`03363170 fffff880`00000000 00000000`0000ffff : nt!RtlDispatchException+0x122
fffff880`03363140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!RtlDispatchException+122
fffff800`032ae7a2 410fb60c24 movzx ecx,byte ptr [r12]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!RtlDispatchException+122
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xA_VRF_nt!RtlDispatchException+122
BUCKET_ID: X64_0xA_VRF_nt!RtlDispatchException+122
Followup: MachineOwner