Guest OS Crashed suddenly

[chocomart]

Hi There!

Our LIVE VM suddenly rebooted and we found out on the Vsphere events that the Guest OS Crashed

[MikeStoica]

More details please about ESXi and vCenter version, what guest os (Windows,Linux).

You can check VM logs as well.

[mjtejero]

Yeeeeah sorry about that.

Here's some details on our environment:

VSphere & ESXi 6.5

Guest OS: Windows Server 2008 R2

[MikeStoica]

Did you checked vm logs?Do you have vmware tools installed?

[chocomart]

HI Mike,

Yes, there's a VMWare tools installed. what we've just seen on the "Event" section under Monitor in Vsphere is that the Guest Os has crashed.

I've generated the support Bundle for the logs, although i'm not pretty sure where to look inside those files.

[Jonathan77]

We had that this week on 2 of our critical VM.

After support case with VMware and MS.. we updated the tools from 10.2.x to 10.3.x

So far, so good and we are monitoring.

[chocomart]

Hi Jonathan77​,

Thanks for the idea, can you please share to me the link for the updated vmware tools version? currently we're sitting at 10.2 but when i'm trying to check for an update, there seems to be none.

[MikeStoica]

If you browse the datastore where the vm is located you will see in the vm folder a vmware.log file

[chocomart]

I've found the logs, it seems there was a registry error that crashed the Guest OS

[NathanosBlightc]

Hello

Suddenly crashing means you have problem with your memory or disk probably,

Is there any hardware dependency from physical host devices for your VM?

[MikeStoica]

Did you checked windows logs? Check the bsod file

[nparas5]

Hello ,

It seems your Server is crashed with Bug check BSOD. You need to analyse the Memory Dump created under "C:\Windows\System32" with the use of WinDBG Tool. It will give you exact details of Bugcheck.

You can also analyse MiniDump "C:\Windows\System32\MiniDump" it will only give you the details of the driver casued Bugcheck.

Moreove BugChecks are caused by Third Party drivers/softwares/ Only thing can help you solve this is you need to analyse the Memory.dmp file with the help of WinDBG Tool.

Refer this link to analyse the Memory Dump:

Step by Step tutorial to debugging memory dump caused by Blue Screen of Death by WinDbg – MyTechTwea...