<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Host crash in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714192#M266764</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, just what I wanted to see.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Oct 2015 17:10:51 GMT</pubDate>
    <dc:creator>jdickerson</dc:creator>
    <dc:date>2015-10-06T17:10:51Z</dc:date>
    <item>
      <title>Host crash</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714189#M266761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a esxi 5.1 host that crashed. Can anyone determine the cause from my screenshot of the stop screen? Also, what tools are available with esxi and vsphere to troubleshoot host crashes? Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="host-crash.jpg"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/61832i9D358C6F1233CEB0/image-size/large?v=v2&amp;amp;px=999" role="button" title="host-crash.jpg" alt="host-crash.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Oct 2015 23:32:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714189#M266761</guid>
      <dc:creator>jdickerson</dc:creator>
      <dc:date>2015-10-04T23:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: Host crash</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714190#M266762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;H4 class="docheading Cause"&gt;Cause&lt;/H4&gt;&lt;P class="doccontent cc_Cause"&gt;&lt;/P&gt;&lt;DIV&gt;This issue occurs when there are hardware or software issues on the host such as:&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Hardware faults occur when there are issues with CPU, memory, or main board components. &lt;/LI&gt;&lt;LI&gt;Software issues are more complex and require more detailed examination to troubleshoot the reason for the fault.&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;H4 class="docheading Resolution"&gt;Resolution&lt;/H4&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt; To investigate this issue: &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;You must extract the log file that led to the Purple Diagnostic Screen (PSOD) crash and examine for potential cause.&amp;nbsp; For more information on extracting the log file, see &lt;A href="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;docTypeID=DT_KB_1_1&amp;amp;externalId=1006796" target="_blank"&gt;Extracting the log file after an ESX or ESXi host fails with a purple screen error (1006796)&lt;/A&gt;. &lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;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 &lt;A href="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;docTypeID=DT_KB_1_1&amp;amp;externalId=1004250" name="&amp;amp;amp;lpos=apps_scodevmw : 3" target="_blank"&gt;Interpreting an ESX/ESXi host purple diagnostic screen (1004250)&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt; &lt;/LI&gt;&lt;LI&gt;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. &lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;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 &lt;A href="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;docTypeID=DT_KB_1_1&amp;amp;externalId=1008524" name="&amp;amp;amp;lpos=apps_scodevmw : 4" target="_blank"&gt;Collecting Diagnostic Information for VMware Products (1008524)&lt;/A&gt; and &lt;A href="https://www.vmware.com/support/file-sr/" name="&amp;amp;amp;lpos=apps_scodevmw : 5" target="_blank"&gt;How to Submit a Support Request&lt;/A&gt;.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Oct 2015 04:42:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714190#M266762</guid>
      <dc:creator>VijaySendhur</dc:creator>
      <dc:date>2015-10-05T04:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: Host crash</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714191#M266763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First of all, your 5.1 host is terribly outdated! You are running it at "update1" level. Why? Since then there were many patches, so grab the latest one (they are cumulative) and update ESXi to the latest level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Second, in your PSOD I see "E1000". There was some problem with this NIC, this has been fixed later "update2" patch. So one more reason to update your ESXi-host to the latest level!&lt;/P&gt;&lt;P&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2059053" title="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2059053"&gt;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2059053&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Oct 2015 06:52:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714191#M266763</guid>
      <dc:creator>JarryG</dc:creator>
      <dc:date>2015-10-05T06:52:30Z</dc:date>
    </item>
    <item>
      <title>Re: Host crash</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714192#M266764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, just what I wanted to see.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Oct 2015 17:10:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714192#M266764</guid>
      <dc:creator>jdickerson</dc:creator>
      <dc:date>2015-10-06T17:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: Host crash</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714193#M266765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thats the correct answer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Oct 2015 18:28:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Host-crash/m-p/2714193#M266765</guid>
      <dc:creator>RaviMV</dc:creator>
      <dc:date>2015-10-06T18:28:26Z</dc:date>
    </item>
  </channel>
</rss>

