windows 2008 server r2 安装vmware，创建子机启动时机器就蓝屏，蓝屏后产生dmp文件，windbg分析后是以下结果，麻烦麻烦帮忙看下
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: e
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
DPC_STACK_BASE: FFFFF80001520FB0
EXCEPTION_RECORD: fffff8000151a5f8 -- (.exr 0xfffff8000151a5f8)
ExceptionAddress: fffff880045ced6c (vmx86+0x0000000000005d6c)
ExceptionCode: c0000096
ExceptionFlags: 00000000
NumberParameters: 0
TRAP_FRAME: fffff8000151a6a0 -- (.trap 0xfffff8000151a6a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=00000000000000ce
rdx=0000000049656e69 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880045ced6c rsp=fffff8000151a830 rbp=000000000000000f
r8=0000000000000001 r9=00000000000306e4 r10=000000000000000f
r11=00000000000000ce r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
vmx86+0x5d6c:
fffff880`045ced6c 0f32 rdmsr
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001677bbe to fffff80001680190
STACK_TEXT:
fffff800`015196d8 fffff800`01677bbe : fffff800`0188773c fffff800`0169f0f3 fffff800`017c4b04 fffff800`0151a5f8 : nt!KeBugCheck
fffff800`015196e0 fffff800`016aae2d : fffff800`018864dc fffff800`017c4a84 fffff800`01601000 fffff800`0151a5f8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`01519710 fffff800`016a9c05 : fffff800`017c6fac fffff800`01519788 fffff800`0151a5f8 fffff800`01601000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`01519740 fffff800`016bab81 : fffff800`0151a5f8 fffff800`01519e50 fffff800`00000000 fffffa80`035e5180 : nt!RtlDispatchException+0x415
fffff800`01519e20 fffff800`0167f842 : fffff800`0151a5f8 00000000`000306e4 fffff800`0151a6a0 fffffa80`035e51a8 : nt!KiDispatchException+0x135
fffff800`0151a4c0 fffff800`0167e14a : fffffa80`039f5430 fffff880`010492f7 fffffa80`0291d140 fffff880`010492f7 : nt!KiExceptionDispatch+0xc2
fffff800`0151a6a0 fffff880`045ced6c : 00000000`00000006 fffff880`045d1dff 00000000`00000001 fffff880`009b9180 : nt!KiGeneralProtectionFault+0x10a
fffff800`0151a830 fffff880`045d1dff : 00000000`00000001 fffff880`009b9180 00000000`00000003 fffff800`017f2e80 : vmx86+0x5d6c
fffff800`0151a870 fffff880`045cdc4a : fffff880`058b06b0 fffff800`017f2e80 00000000`00000000 00000000`00000000 : vmx86+0x8dff
fffff800`0151a8b0 fffff800`0169f1c4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vmx86+0x4c4a
fffff800`0151a8e0 fffff800`0168a07a : 00000000`00000000 fffff800`0151aa40 00000000`00000001 fffffa80`0230fef0 : nt!KiIpiProcessRequests+0x194
fffff800`0151a9c0 fffff880`0249c9c2 : fffff800`01688ce9 00000000`00369e99 fffffa80`0230f2f8 fffff800`01800cc0 : nt!KiIpiInterrupt+0x12a
fffff800`0151ab58 fffff800`01688ce9 : 00000000`00369e99 fffffa80`0230f2f8 fffff800`01800cc0 00000000`00000001 : intelppm!C1Halt+0x2
fffff800`0151ab60 fffff800`01677e9c : fffff800`017f2e80 fffff800`00000000 00000000`00000000 fffff880`01048a00 : nt!PoIdle+0x52a
fffff800`0151ac40 00000000`00000000 : fffff800`0151b000 fffff800`01515000 fffff800`0151ac00 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
vmx86+5d6c
fffff880`045ced6c 0f32 rdmsr
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: vmx86+5d6c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vmx86
IMAGE_NAME: vmx86.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 539a4f64
IMAGE_VERSION: 10.0.3.48389
FAILURE_BUCKET_ID: X64_0x1E_vmx86+5d6c
BUCKET_ID: X64_0x1E_vmx86+5d6c
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x1e_vmx86+5d6c
FAILURE_ID_HASH: {a4cbd270-e7fb-ca0a-3667-53c31cb79059}
Followup: MachineOwner
---------
0: kd> r
rax=fffff80001519cf0 rbx=fffff800017c6fac rcx=000000000000001e
rdx=fffff8000151ac40 rsi=fffff80001601000 rdi=0000000000000000
rip=fffff80001680190 rsp=fffff800015196d8 rbp=0000000000000000
r8=fffff80001519e50 r9=fffff800015197d0 r10=fffff8000151ac70
r11=fffff80001519788 r12=fffff80001677e9c r13=fffff80001884910
r14=fffff80001677bb0 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000282
nt!KeBugCheck:
fffff800`01680190 4883ec28 sub rsp,28h