we are getting some random crashes occasionally. debug always has the same results. can anyone make anything of this? the host is up to date with both drivers and updates. I've been all over the host and can't find any issues. thank you
Loading Dump File [C:\Minidump\092613-10374-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbolfiles*http://msdl.microsoft.com/download/symbols;C:\Symbols
Executable search path is:
Windows 7 Kernel Version 9200 MP (16 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff800`b526d000 PsLoadedModuleList = 0xfffff800`b5539a20
Debug session time: Thu Sep 26 02:07:18.299 2013 (UTC - 7:00)
System Uptime: 18 days 8:02:55.169
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {3, 2, 0, fffff880048f77a0}
Probably caused by : vmswitch.sys ( vmswitch!memmove+1e0 )
Followup: MachineOwner
---------
0: 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: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880048f77a0, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800b55c5168
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000003
CURRENT_IRQL: 2
FAULTING_IP:
vmswitch!memmove+1e0
fffff880`048f77a0 8a440aff mov al,byte ptr [rdx+rcx-1]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0xD1
PROCESS_NAME: vmms.exe
TRAP_FRAME: fffff880082ce2a0 -- (.trap 0xfffff880082ce2a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8049315dc8
rdx=0000057fb6cea23c rsi=0000000000000000 rdi=0000000000000000
rip=fffff880048f77a0 rsp=fffff880082ce438 rbp=fffff880082ce7a0
r8=0000000000000004 r9=0000000000000000 r10=0000000000000024
r11=fffffa8049315dc4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
vmswitch!memmove+0x1e0:
fffff880`048f77a0 8a440aff mov al,byte ptr [rdx+rcx-1] ds:e080:00000000`00000003=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800b52c6769 to fffff800b52c7440
STACK_TEXT:
fffff880`082ce158 fffff800`b52c6769 : 00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`082ce160 fffff800`b52c4fe0 : 00000000`00000000 00000000`0000001e fffff880`082ce300 fffff880`082ce2a0 : nt!KiBugCheckDispatch+0x69
fffff880`082ce2a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
vmswitch!memmove+1e0
fffff880`048f77a0 8a440aff mov al,byte ptr [rdx+rcx-1]
SYMBOL_NAME: vmswitch!memmove+1e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vmswitch
IMAGE_NAME: vmswitch.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 510cbec2
FAILURE_BUCKET_ID: X64_0xD1_vmswitch!memmove+1e0
BUCKET_ID: X64_0xD1_vmswitch!memmove+1e0
Followup: MachineOwner
BarrySDCA