kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pagable (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: fc71f004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 81efade4, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  fc71f004 

CURRENT_IRQL:  2

FAULTING_IP: 
+ffffffff81efade4
81efade4 ??               ???

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  f8950dc4 -- (.trap fffffffff8950dc4)
ErrCode = 00000002
eax=00000000 ebx=8217a608 ecx=81efaca6 edx=822b5b10 esi=fc71ef68 edi=f80c27dc
eip=81efade4 esp=f8950e38 ebp=fc71ef68 iopl=0         nv up ei pl zr na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
81efade4 ??               ???
Resetting default context

LAST_CONTROL_TRANSFER:  from f80c27dc to 81efade4

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
f8950e34 f80c27dc fc71ef68 8217a608 f80c27dc 0x81efade4
fc71ef68 00000000 00000000 00000000 00000000 0xf80c27dc


FOLLOWUP_IP: 
axvscsi+3bf4
f7fd2bf4 ??               ???

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  axvscsi+3bf4

MODULE_NAME:  axvscsi

IMAGE_NAME:  axvscsi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3e00a1e0

STACK_COMMAND:  .trap fffffffff8950dc4 ; kb

BUCKET_ID:  0xD1_W_axvscsi+3bf4

Followup: MachineOwner
---------