2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8014dcbce13, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80267765138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000010
CURRENT_IRQL: 2
FAULTING_IP:
ndis!NdisGetReceivedPacket+f
fffff801`4dcbce13 488b7110 mov rsi,qword ptr [rcx+10h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
TRAP_FRAME: ffffd00023333090 -- (.trap 0xffffd00023333090)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe001e8325020 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffe001e4e946f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8014dcbce13 rsp=ffffd00023333220 rbp=0000000000000000
r8=ffffe001e9096046 r9=000000000000000e r10=ffffe001ec7e5600
r11=0000000000000173 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ndis!NdisGetReceivedPacket+0xf:
fffff801`4dcbce13 488b7110 mov rsi,qword ptr [rcx+10h] ds:00000000`00000010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8026755e7e9 to fffff80267552ca0
STACK_TEXT:
ffffd000`23332f48 fffff802`6755e7e9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`23332f50 fffff802`6755d03a : 00000000`00000000 ffffe001`eda77030 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd000`23333090 fffff801`4dcbce13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
ffffd000`23333220 fffff801`4e2edbfd : ffffe001`eda77030 00000000`0000000e 00000000`00000000 00000000`00000000 : ndis!NdisGetReceivedPacket+0xf
[COLOR=#ff0000]ffffd000`23333250 ffffe001`eda77030 : 00000000`0000000e 00000000`00000000 00000000`00000000 ffffe001`e53d16b8 : [/COLOR][COLOR=#ff0000]dne64x+0xdbfd[/COLOR]
ffffd000`23333258 00000000`0000000e : 00000000`00000000 00000000`00000000 ffffe001`e53d16b8 fffff801`4dc88ece : 0xffffe001`eda77030
ffffd000`23333260 00000000`00000000 : 00000000`00000000 ffffe001`e53d16b8 fffff801`4dc88ece 00000000`00000000 : 0xe
STACK_COMMAND: kb
FOLLOWUP_IP:
dne64x+dbfd
fffff801`4e2edbfd ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: dne64x+dbfd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dne64x
IMAGE_NAME: dne64x.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e3102e8
FAILURE_BUCKET_ID: AV_dne64x+dbfd
BUCKET_ID: AV_dne64x+dbfd
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_dne64x+dbfd
FAILURE_ID_HASH: {6c517f98-2074-2840-6de2-e46981375664}
Followup: MachineOwner
---------