不涉及
部分Windows系统虚拟机出现蓝屏故障,确认这些故障虚拟机都是相同模板部署;
虚拟机蓝屏产生dump日志,登录虚拟机操作系统内部,收集dump日志后分析:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa8305246010, The address that the exception occurred at
Arg3: fffff880057b6758, Exception Record Address
Arg4: fffff880057b5fb0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
+ff
fffffa83`05246010 1102 adc dword ptr [rdx],eax
EXCEPTION_RECORD: fffff880057b6758 -- (.exr 0xfffff880057b6758)
ExceptionAddress: fffffa8305246010
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000007ca770e5
Attempt to write to address 000000007ca770e5
CONTEXT: fffff880057b5fb0 -- (.cxr 0xfffff880057b5fb0)
rax=fffffa8305244600 rbx=000000000002c600 rcx=0000000000000000
rdx=000000007ca770e5 rsi=fffffa8305245600 rdi=fffffa8305245600
rip=fffffa8305246010 rsp=fffff880057b6990 rbp=fffffa83044bf000
r8=0000000000012408 r9=00000000000007ff r10=000000000000074d
r11=0000000000000000 r12=fffff880057b6aa8 r13=fffff8a00a0c50a8
r14=000000000000000c r15=fffffa8304170770
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
fffffa83`05246010 1102 adc dword ptr [rdx],eax ds:002b:00000000`7ca770e5=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 000000007ca770e5
WRITE_ADDRESS: 000000007ca770e5
FOLLOWUP_IP:
srvnet!SrvNetSendData+ff
fffff880`0490de3f b803010000 mov eax,103h
FAILED_INSTRUCTION_ADDRESS:
+5cd72faf043fddb8
fffffa83`05246010 1102 adc dword ptr [rdx],eax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa83044bf000 to fffffa8305246010
SYMBOL_ON_RAW_STACK: 1
STACK_ADDR_RAW_STACK_SYMBOL: fffff880057b6a00
STACK_COMMAND: dds 057B6A00-0x20 ; kb
STACK_TEXT:
00000000`057b69e0 ????????
00000000`057b69e4 ????????
00000000`057b69e8 ????????
SYMBOL_NAME: srvnet!SrvNetSendData+ff
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: srvnet
IMAGE_NAME: srvnet.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79478
FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_srvnet!SrvNetSendData+ff
BUCKET_ID: X64_0x7E_BAD_IP_srvnet!SrvNetSendData+ff
Followup: MachineOwner
从日志中可以看出蓝屏代码0xc0000005,导致蓝屏的是srvnet.sys。
使用命令crm resource cleanup tomcat6,清理CVM双机报错信息后,HA问题解决。
微软官网对应解决方案:***.***/zh-cn/help/2719594/0x00000050-stop-error-in-windows-7-or-in-windows-server-2008-r2
该案例对您是否有帮助:
您的评价:1
若您有关于案例的建议,请反馈:
该案例暂时没有网友评论
✖
案例意见反馈
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作