I have this sporadic BSOD issue with a hyperV guest OS and the publisher is telling me its drivers but the system is using default hyperV drivers and this is the only application having the issue.
system is 2012 R2 in a 2012 R2 HyperV environment.
Wondering if anyone has any ideas, here is the crashdump:
*******************************************************************************
* *
* 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: 0000000048020004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800d730ac34, address which referenced memory
Debugging Details:
------------------
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
WRITE_ADDRESS: 0000000048020004
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiSwapThread+114
fffff800`d730ac34 86840100000248 xchg al,byte ptr [rcx+rax+48020000h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER
BUGCHECK_STR: AV
PROCESS_NAME: MEIMAPS.EXE
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
TRAP_FRAME: ffffd001e4a46750 -- (.trap 0xffffd001e4a46750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000004
rdx=fffffa800c1afac0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800d730ac34 rsp=ffffd001e4a468e0 rbp=ffffe0016520ff18
r8=0000000000000001 r9=0000000000000004 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiSwapThread+0x114:
fffff800`d730ac34 86840100000248 xchg al,byte ptr [rcx+rax+48020000h] ds:00000000`48020004=??
Resetting default scope
MISALIGNED_IP:
nt!KiSwapThread+114
fffff800`d730ac34 86840100000248 xchg al,byte ptr [rcx+rax+48020000h]
LAST_CONTROL_TRANSFER: from fffff800d73dd4e9 to fffff800d73d19a0
STACK_TEXT:
ffffd001`e4a46608 fffff800`d73dd4e9 : 00000000`0000000a 00000000`48020004 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd001`e4a46610 fffff800`d73dbd3a : 00000000`00000001 ffffe001`6523e080 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd001`e4a46750 fffff800`d730ac34 : ffffd001`e5995180 ffffe001`6523e080 00000000`fffffffe 00000000`fffffffe : nt!KiPageFault+0x23a
ffffd001`e4a468e0 fffff800`d730a6e9 : ffffe001`652451c0 fffff800`d733e185 00000000`00000001 ffffd001`e4a46a09 : nt!KiSwapThread+0x114
ffffd001`e4a46980 fffff800`d72d6bb3 : ffffe001`6523e080 00000000`00000001 ffffe001`6522e080 fffff800`6600dd82 : nt!KiCommitThreadWait+0x129
ffffd001`e4a46a00 fffff800`d7627872 : ffffe001`6617dd00 00000000`00000006 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x373
ffffd001`e4a46a90 fffff800`d73dd1b3 : ffffe001`6523e080 00000000`ffffffff 00000000`00000000 ffffe001`6617dd00 : nt!NtWaitForSingleObject+0xb2
ffffd001`e4a46b00 00007ffd`fc66121a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`20087138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`fc66121a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSwapThread+114
fffff800`d730ac34 86840100000248 xchg al,byte ptr [rcx+rax+48020000h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiSwapThread+114
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 6.3.9600.18007
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:ip_misaligned
FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}
Followup: MachineOwner
---------