If you happen to search Google for one of the following phrases you might expect Google to return a list of official VMware Knowledgebase articles on the topic.

• crash debug screen
• machine crash screen
• ESX Server PSOD
• Purple screen crash report
• Decode purple screen error

Guess what? VMware’s own document standards prevent us from using any of these phrases in the articles, and Google isn’t smart enough to know a PSOD really means a Decoding Machine Check Exception. So instead of finding the best information you really need at that moment, you get a ton of 3rd party information.

Our community forums don’t have as strict rules about terminology so I have just created this post:

ESX Server PSOD

in hopes it ranks well and directs customers to the information they need on ESX purple screens.

This post brought to you by VMwarewolf

ESX PSODs

Continuing my Resolution Path series, here is another download for you all, this time in the Fault area of VI3. Download the zipfile here and keep it handy for the next time you run into any fault related issues.

What is a “fault” problem?  Good question.  It’s more of an internal term used at VMware for how they align their support teams.  Fault cases include such things as Purple Screens of Death (PSOD), Linux faults on the console OS, Hung ESX Servers, and internal errors and panics.

Again, down the left column in yellow are common problems we get calls on. To the right of each problem are steps one would take to resolve the problem. I have included hyperlinks to help get you to the answers fast.

Feel free to share!

This post brought to you by VMwarewolf

Common Fault issues in VMware Infrastructure