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: fffff8a0016bc080, 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: fffff80002ce043e, address which referenced memory Debugging Details: ------------------ OVERLAPPED_MODULE: Address regions for 'VMMR0' and 'VMMR0.r0' overlap READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec7100 fffff8a0016bc080 CURRENT_IRQL: 2 FAULTING_IP: nt! ?? ::FNODOBFM::`string'+320c fffff800`02ce043e 8a0c1e mov cl,byte ptr [rsi+rbx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: VirtualBox.exe TRAP_FRAME: fffff88008a81310 -- (.trap 0xfffff88008a81310) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000002e rbx=0000000000000000 rcx=fffff88008a81500 rdx=fffffa80085cce10 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ce043e rsp=fffff88008a814a0 rbp=fffff880044a2038 r8=0000000000000001 r9=000000000000002e r10=fffffa8009455df4 r11=fffff88008a814c8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt! ?? ::FNODOBFM::`string'+0x320c: fffff800`02ce043e 8a0c1e mov cl,byte ptr [rsi+rbx] ds:e6fc:00000000`00000000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c89fe9 to fffff80002c8aa40 STACK_TEXT: fffff880`08a811c8 fffff800`02c89fe9 : 00000000`0000000a fffff8a0`016bc080 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`08a811d0 fffff800`02c88c60 : 00000000`00000000 fffff800`03213552 00000000`00000000 fffffa80`044ba830 : nt!KiBugCheckDispatch+0x69 fffff880`08a81310 fffff800`02ce043e : fffffa80`044ba428 fffff880`044896e0 fffff880`08a814d8 00000000`00000001 : nt!KiPageFault+0x260 fffff880`08a814a0 fffff880`04488492 : 00000000`00000000 fffffa80`044ba390 00000000`00000001 00000000`00000033 : nt! ?? ::FNODOBFM::`string'+0x320c fffff880`08a814d0 00000000`00000000 : fffffa80`044ba390 00000000`00000001 00000000`00000033 00000000`002f002e : VBoxNetLwf+0x4492 STACK_COMMAND: kb FOLLOWUP_IP: VBoxNetLwf+4492 fffff880`04488492 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: VBoxNetLwf+4492 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetLwf IMAGE_NAME: VBoxNetLwf.sys DEBUG_FLR_IMAGE_TIMESTAMP: 559e4840 FAILURE_BUCKET_ID: X64_0xA_VBoxNetLwf+4492 BUCKET_ID: X64_0xA_VBoxNetLwf+4492 Followup: MachineOwner