Help with VMWare error screen

Hello experts,
we have a HP server (ML380 Generation 6) server, we have VMware running on the box and a snapshot of SBS 2011 server, for whatever reason the server ground to a holt today and we were presented with a pink error screen. I attach it here and ideas what could be the cause ? Thanks in advance
ESXI-ERROR.jpg
LVL 1
unrealone1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Purple or Pink screens of death are usually caused by hardware issues.

Has it done this more than once ?

Can you reproduce the issue?

Are you using the HP OEM version of ESXi 5.5 ?

I would ensure that you have updated ALL the firmware on the server to the latest by HP.

Are you using the VMXNET3, if you are not replace the E1000 interface with it in the VM...
0
unrealone1Author Commented:
Hi Andrew,

This is the first time it's happened since the server was installed a while ago. I did have a problem with another ML350 G5 not running VMware but just windows and it hung up, this was due to a power supply and was a common problem with that model.

Not able to reproduce it no.

Just I am using the HP version 5.5.

I am using the E1000 NIC yes.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I would swap the network interface to the VMXNET3, and make sure VMware Tools is installed to support it.

Check again, setup syslog for logging, and persistent logs.

Part 11: HOW TO: Suppress Configuration Issues System logs on host are stored on non-persistent storage

so in the event if a crash in the future, you can look at the logs before crash.

Check FANS, Heatsinks, CPUs, Memory is seated correctly.

Check and Run Memtest86+ to check memory.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
unrealone1Author Commented:
Thanks, no problem since that change of nic to VMXNet3
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.