VMWARE Host Purple Screen of Death

My VMWare Host running ESXi5.5.0 has started to crash every other day.  Not sure why, no physical changes have been made to this server.  I have attached the Purple Screen of Death.  Any Ideas???
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Jeremy BromleyIT ConsultantCommented:
Looks like a memory issue to me...
Seth SimmonsSr. Systems AdministratorCommented:
what server is this running on?  is it supported?
any custom images being used?
is the firmware for the system current?
Jeremy BromleyIT ConsultantCommented:
There is also a patch which relates to the specific error message you are getting - might be worth getting this and updating...

It looks like the error relates to the PageFile for VMware, so it is possibly either memory or HDD related.

#PF Exception 14 patch
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Often, when PSOD occur, it's due to a hardware or driver issues.

1. Check Hardware, Run Diagnostics, Run Memtest86+ for memory.

2. Check CPUs, Heatsinks and Fans

3. Check no new hardware has been added.

4. Check the Hardware is certified for use with ESXi 5.5.

see the HCL

Check the VMware Hardware Compatability Lists HCL here

The VMware Hardware Compatibility List is the detailed lists showing actual vendor devices that are either physically tested or are similar to the devices tested by VMware or VMware partners. Items on the list are tested with VMware products and are known to operate correctly.Devices which are not on the list may function, but will not be supported by VMware.


5. Update ALL BIOS and firmware for the hardware from the latest Smartstart Firmware DVD.

6. Make sure the OEM HP version of ESXi 5.5 is in use, download from HP/VMware site.
sfletcher1959VPAuthor Commented:
This server has been up and running perfectly for over a year.  The only new changes recently have been upgrades to Windows Server 2012 R2.  It may be a driver issue with the new OS.  I saw a KB article on VMWare that speaks to the NIC Driver (specifically E1000e).  Is there a way to look at the Nic to see what driver it is using from the Edit Settings console?  I see three options for nics.  E1000, E1000e and VMNic3.  Any suggestions on which to use?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You SHOULD always always always use the VMXNET3.

It's been that way since, forever....

Use the E1000 for installation, and then switch it...to VMXNET3.
Jeremy BromleyIT ConsultantCommented:
I wouldn't have thought that upgrading one of the internal VMs would cause a PSOD though, sounds much more like hardware to me...
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
VMs, and unsupported Guest OS, can cause PSOD!

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
2 mayor updates are released to ESXi 5.5 since you installed it.

Look at the top of backtrace? What do you see?
I see the crash message listed world ID 33111, if your log file location is persistant, you could check your vmkernel and VM specific logs to see which VM was using this world ID at the time of the crash.

As other have suggest you could try and change the NIC type of VMXNET3 and see if the crashes stop
sfletcher1959VPAuthor Commented:
Thanks Andrew
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

From novice to tech pro — start learning today.