The VM restarted due to a guest OS crash (Bug Check 0x162 / BSOD)
search cancel

The VM restarted due to a guest OS crash (Bug Check 0x162 / BSOD)

book

Article ID: 417841

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

The following event is displayed in the vSphere Client:
Guest operating system has crashed.


You may see the Blue Screen Of Death (BSOD) log like below under vmware.log.

vmware.log
---
YYYY-MM-DDTHH:MM:SS.Z Wa(03) vcpu-1 - WinBSOD: Synthetic MSR[0x40000100] 0x162
YYYY-MM-DDTHH:MM:SS.Z Wa(03)+ vcpu-1 -
YYYY-MM-DDTHH:MM:SS.Z Wa(03) vcpu-1 - WinBSOD: Synthetic MSR[0x40000101] 0xffffac8d9244b080
YYYY-MM-DDTHH:MM:SS.Z Wa(03)+ vcpu-1 -
YYYY-MM-DDTHH:MM:SS.Z Wa(03) vcpu-1 - WinBSOD: Synthetic MSR[0x40000102] 0xffffac8e71e55e00
YYYY-MM-DDTHH:MM:SS.Z Wa(03)+ vcpu-1 -
YYYY-MM-DDTHH:MM:SS.Z Wa(03) vcpu-1 - WinBSOD: Synthetic MSR[0x40000103] 0xffffffff
YYYY-MM-DDTHH:MM:SS.Z Wa(03)+ vcpu-1 -
YYYY-MM-DDTHH:MM:SS.Z Wa(03) vcpu-1 - WinBSOD: Synthetic MSR[0x40000104] 0x0
YYYY-MM-DDTHH:MM:SS.Z Wa(03)+ vcpu-1 -
---

Environment

ESXi 7.0
ESXi 8.0

Resolution

Please engage with the guest OS vendor to investigate further.

Additional Information

Identifying critical Guest OS failures within virtual machines
https://knowledge.broadcom.com/external/article/315245/identifying-critical-guest-os-failures-w.html