<?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: Parity Check 2 in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796318#M12076</link>
    <description>I am also getting this error on my ProLiant 1600 6/450 (P08).  It's current BIOS ROM is vSP15911.exe, dated 11/8/2000.  To the best of my knowledge that is the most current.  I had upgraded my memory to 4x256MB (1GB total) and it has run fine for 18 - 24mos.  In the last few weeks, I started getting error messages.  When I run diags, I now get the 'Parity Check 2 - System DIMM Memory' error message.  I have tried to use ONLY two of the 256MB DIMMs and I have also put two original 128MB DIMMs back in the server.  The resulting error is the same.  Do I need to look at my hardware cage, backplane, or possibly some sort of a motherboard replacement?  Anyone have any suggestions?&lt;BR /&gt;&lt;BR /&gt;Thanks - Matt</description>
    <pubDate>Tue, 01 Jul 2003 11:44:07 GMT</pubDate>
    <dc:creator>Matt Allen_1</dc:creator>
    <dc:date>2003-07-01T11:44:07Z</dc:date>
    <item>
      <title>Parity Check 2</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796314#M12072</link>
      <description>On boot up I'm getting an error: &lt;BR /&gt;Parity Check 2 - System DIMM Memory &lt;BR /&gt; &lt;BR /&gt;Any idea what this error means? &lt;BR /&gt; &lt;BR /&gt;Thanks &lt;BR /&gt;Hank</description>
      <pubDate>Wed, 28 Aug 2002 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796314#M12072</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2002-08-28T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Parity Check 2</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796315#M12073</link>
      <description>Hello,&lt;BR /&gt;This error refers to a bad DIMM. But please update your System BIOS first and run System Configuration by downloading SP19619. I have seen instances where by running the latest System configuration the error messages like the one you have goes away.&lt;BR /&gt;&lt;BR /&gt;Regards,</description>
      <pubDate>Thu, 29 Aug 2002 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796315#M12073</guid>
      <dc:creator>Sunil Jerath</dc:creator>
      <dc:date>2002-08-29T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Parity Check 2</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796316#M12074</link>
      <description>When the system is booted I get the scanning for SCSI devices ans than the parity error comes up.  It never allows me to get to a point to run any software from CD or floppy.  The server just freezes once this error comes up. &lt;BR /&gt;I've tried pulling one DIMM and tried other slots, but each DIMM has the same result. &lt;BR /&gt; &lt;BR /&gt;Hank</description>
      <pubDate>Mon, 02 Sep 2002 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796316#M12074</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2002-09-02T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Parity Check 2</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796317#M12075</link>
      <description>Hi Hank, I read your post and wanted to know how you got overcame this issue, I have a Proliant 800 and the same symptoms is coming up for me today&lt;BR /&gt;&lt;BR /&gt;I get Parity Check 2 - System DIMM Memory&lt;BR /&gt;&lt;BR /&gt;i put the Smart start in the CD but i cannot accesss the Cd to run it, and i move the ram individually to the different slots and no luck as well&lt;BR /&gt;&lt;BR /&gt;Any help you can give will be appreciated it&lt;BR /&gt;&lt;BR /&gt;thanks Cesar</description>
      <pubDate>Sun, 15 Jun 2003 21:06:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796317#M12075</guid>
      <dc:creator>Cesar Leon</dc:creator>
      <dc:date>2003-06-15T21:06:19Z</dc:date>
    </item>
    <item>
      <title>Re: Parity Check 2</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796318#M12076</link>
      <description>I am also getting this error on my ProLiant 1600 6/450 (P08).  It's current BIOS ROM is vSP15911.exe, dated 11/8/2000.  To the best of my knowledge that is the most current.  I had upgraded my memory to 4x256MB (1GB total) and it has run fine for 18 - 24mos.  In the last few weeks, I started getting error messages.  When I run diags, I now get the 'Parity Check 2 - System DIMM Memory' error message.  I have tried to use ONLY two of the 256MB DIMMs and I have also put two original 128MB DIMMs back in the server.  The resulting error is the same.  Do I need to look at my hardware cage, backplane, or possibly some sort of a motherboard replacement?  Anyone have any suggestions?&lt;BR /&gt;&lt;BR /&gt;Thanks - Matt</description>
      <pubDate>Tue, 01 Jul 2003 11:44:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796318#M12076</guid>
      <dc:creator>Matt Allen_1</dc:creator>
      <dc:date>2003-07-01T11:44:07Z</dc:date>
    </item>
    <item>
      <title>Re: Parity Check 2</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796319#M12077</link>
      <description>I was on another forum and Phil Reah wrote that he had seen this problem a number of times and said the array controller was the problem child for this error.  I found that he was correct.  My 1850R booted fine after removing the array controller.  Imagine that.</description>
      <pubDate>Thu, 17 Jul 2003 20:00:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/parity-check-2/m-p/2796319#M12077</guid>
      <dc:creator>Michael Lepley</dc:creator>
      <dc:date>2003-07-17T20:00:44Z</dc:date>
    </item>
  </channel>
</rss>

