VMware Cloud Community
gib2017
Contributor
Contributor

purple screen esxi 5.5

what can i do?

where is problem?:(

Tags (1)
Reply
0 Kudos
4 Replies
Alex_Romeo
Leadership
Leadership

Hi,

VMware Knowledge Base

        Cause

This issue occurs when there are hardware or software issues on the host such as:

  • Hardware faults occur when there are issues with CPU, memory, or main board components.
  • Software issues are more complex and require more detailed examination to troubleshoot the reason for the fault.

       Resolution

style="background-position:repeat;color:rgb(0, 0, 0);margin-bottom:20px" data-aura-rendered-by="35:168;a"
  • Examine the extracted log file for any anomalous events immediately before the purple diagnostic screen such as logged hardware failures, memory or CPU errors, and also look for warnings or errors from other software modules. For more information, see Interpreting an ESX/ESXi host purple diagnostic screen (1004250)
     
  • If you suspect a hardware fault, subject the host to rigorous memory and CPU testing. On hosts with multiple CPUs, arrange to run several tests at the same time. The usual troubleshooting techniques for hardware can be used, such as switching memory modules and CPUs between sockets.
     
  • If you cannot perform the above steps because the host fails to power up or boot, submit a support request to your hardware vendor. If its not a hardware issue, then to resolve the issue, collect diagnostic information from the ESXi host and submit a support request. For more information, see Collecting Diagnostic Information for VMware Products (1008524) and How to Submit a Support Request.


ARomeo

Blog: https://www.aleadmin.it/
Reply
0 Kudos
MikeStoica
Expert
Expert

You'd better upgrade it to the latest version. 5.5 is out of support for a long time and 6.0 support will end next month

Reply
0 Kudos
msripada
Virtuoso
Virtuoso

It is a known issue with 5.5 and is fixed as per the kb

VMware Knowledge Base

Thanks,

MS

Reply
0 Kudos
IRIX201110141
Champion
Champion

Thats an easy one!  It was fixed for 6 years!!!

See VMware Knowledge Base

Regards,
Joerg

Reply
0 Kudos