VMware Cloud Community
thorwitt
Contributor
Contributor

Exception type 14 in world...

Our ESX1 (from 3) crashed yesterday with a PSOD. This is the second time in one week. HA did not work. Any ideas what the problem could be?

Tags (1)
0 Kudos
2 Replies
Texiwill
Leadership
Leadership

Hello,

Generally a PSOD implies some form of hardware issue.... In your case it could be memory or memory on a storage controller, etc.

  • Open up the box and reseat memory, cards and look for obvious things (I had one where a heat sync was loose)

  • verify your BIOS settings are correct for your version of ESX

  • verify that your BIOS and firmware are up to date per vendor for your version of ESX.

  • run memtest86+ for at least 24-48 hours

  • run full (ignoring disk timeout tests) hardware diagnostics on it for at least 24-48 hours.

These should pinpoint the problems.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
thorwitt
Contributor
Contributor

HP Insight Diagnostics with 100 Loops works without an errors. So server hardware should be ok. Any other ideas to analyze this PSOD?

0 Kudos