<?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: Cisco UCS B200 M3 Purple Screen Of Death in Unified Computing System Discussions</title>
    <link>https://community.cisco.com/t5/unified-computing-system-discussions/cisco-ucs-b200-m3-purple-screen-of-death/m-p/3337839#M24848</link>
    <description>&lt;P&gt;Looks like you have a hardware problem. I would open a TAC case for diagnosis and RMA if required.&lt;/P&gt;</description>
    <pubDate>Mon, 26 Feb 2018 13:51:05 GMT</pubDate>
    <dc:creator>Wes Austin</dc:creator>
    <dc:date>2018-02-26T13:51:05Z</dc:date>
    <item>
      <title>Cisco UCS B200 M3 Purple Screen Of Death</title>
      <link>https://community.cisco.com/t5/unified-computing-system-discussions/cisco-ucs-b200-m3-purple-screen-of-death/m-p/3337838#M24847</link>
      <description>&lt;P&gt;We have a Hardware fault with of the UCS blade’s Processors. UCS blade is unable to recover Purple screen of Death even after reboots. Once rebooted blades has crashed on below blank screen can’t go further than Selftest&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 21:26:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-computing-system-discussions/cisco-ucs-b200-m3-purple-screen-of-death/m-p/3337838#M24847</guid>
      <dc:creator>IamDaMayor</dc:creator>
      <dc:date>2019-03-01T21:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco UCS B200 M3 Purple Screen Of Death</title>
      <link>https://community.cisco.com/t5/unified-computing-system-discussions/cisco-ucs-b200-m3-purple-screen-of-death/m-p/3337839#M24848</link>
      <description>&lt;P&gt;Looks like you have a hardware problem. I would open a TAC case for diagnosis and RMA if required.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Feb 2018 13:51:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-computing-system-discussions/cisco-ucs-b200-m3-purple-screen-of-death/m-p/3337839#M24848</guid>
      <dc:creator>Wes Austin</dc:creator>
      <dc:date>2018-02-26T13:51:05Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco UCS B200 M3 Purple Screen Of Death</title>
      <link>https://community.cisco.com/t5/unified-computing-system-discussions/cisco-ucs-b200-m3-purple-screen-of-death/m-p/3338544#M24856</link>
      <description>&lt;P&gt;Blade is NoT recognizing it's CPU's and not recovering crash state.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After PSOD, blade rebooted and it's going past the Self test, UCS manager is generating loads of error messages&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2018 09:53:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-computing-system-discussions/cisco-ucs-b200-m3-purple-screen-of-death/m-p/3338544#M24856</guid>
      <dc:creator>IamDaMayor</dc:creator>
      <dc:date>2018-02-27T09:53:01Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco UCS B200 M3 Purple Screen Of Death</title>
      <link>https://community.cisco.com/t5/unified-computing-system-discussions/cisco-ucs-b200-m3-purple-screen-of-death/m-p/3352331#M24986</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I had same problem&amp;nbsp;3 times.&lt;/P&gt;
&lt;P&gt;It is mostly about Memory. If TAC engineer check all memory errors periodically, memory errors will be seen. That means, theese memories can cause PSOD problem. After replacing all of unhealthy memories, I haven't seen any PSOD for 3 months.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Mar 2018 12:27:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-computing-system-discussions/cisco-ucs-b200-m3-purple-screen-of-death/m-p/3352331#M24986</guid>
      <dc:creator>turgutates.can</dc:creator>
      <dc:date>2018-03-21T12:27:20Z</dc:date>
    </item>
  </channel>
</rss>

