<?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: esxi6 machine stop in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi6-machine-stop/m-p/2683574#M261054</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;By seeing this screen its difficult to fidn the issu. you just login in the console and check for the logs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First check your hardware is supported&amp;nbsp; for vSphere 6.0.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 May 2015 07:42:20 GMT</pubDate>
    <dc:creator>CoolRam</dc:creator>
    <dc:date>2015-05-20T07:42:20Z</dc:date>
    <item>
      <title>esxi6 machine stop</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi6-machine-stop/m-p/2683573#M261053</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ALL,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was caused attached error, do you guys know what's the problem?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="捕获.PNG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/59431i83C35ED80372E103/image-size/large?v=v2&amp;amp;px=999" role="button" title="捕获.PNG" alt="捕获.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2015 05:28:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/esxi6-machine-stop/m-p/2683573#M261053</guid>
      <dc:creator>yhq_34</dc:creator>
      <dc:date>2015-05-20T05:28:11Z</dc:date>
    </item>
    <item>
      <title>Re: esxi6 machine stop</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi6-machine-stop/m-p/2683574#M261054</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;By seeing this screen its difficult to fidn the issu. you just login in the console and check for the logs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First check your hardware is supported&amp;nbsp; for vSphere 6.0.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2015 07:42:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/esxi6-machine-stop/m-p/2683574#M261054</guid>
      <dc:creator>CoolRam</dc:creator>
      <dc:date>2015-05-20T07:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: esxi6 machine stop</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi6-machine-stop/m-p/2683575#M261055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As the screenshot says: there was unrecoverable hardware error in your system, probably pcpu1. And it also says what to do: contact your hardware-vendor. You can not do much more. You could try to update bios for your motherboard, and you could try to update cpu-microcode, but I think ESXi 6.0 contains already the latest version.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2015 09:43:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/esxi6-machine-stop/m-p/2683575#M261055</guid>
      <dc:creator>JarryG</dc:creator>
      <dc:date>2015-05-20T09:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: esxi6 machine stop</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi6-machine-stop/m-p/2683576#M261056</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you've run into an Uncorrectable Machine Check Error. The Error register's value is be00000000010093. After debugging this means that you have a memory read error (that also points out to the memMap throwing the PSOD) on Channel 17 - there is not that many channels in modern systems. The first thing I recommend doing is checking the CPU1's memory - ideally by running memtest for an extended period of time. If you have a warranty contact with vendor, have them replace the CPU along with all the memory sticks because in my live I haven't seen Channel 17.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2015 12:10:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/esxi6-machine-stop/m-p/2683576#M261056</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-05-20T12:10:29Z</dc:date>
    </item>
  </channel>
</rss>

