<?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: memory parity error in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550023#M7536</link>
    <description>This same error just started with us today. We are running ours with 256MB of Compaq RAM. It's been running great for two years until today. Any help would be appreciated. Thanks.</description>
    <pubDate>Wed, 01 Aug 2001 23:00:00 GMT</pubDate>
    <dc:creator>Ayman Altounji</dc:creator>
    <dc:date>2001-08-01T23:00:00Z</dc:date>
    <item>
      <title>memory parity error</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550022#M7535</link>
      <description>We have been having problems with our 1600R for approx two weeks now.  At least once a day the server will crash.  The error message is "MI: Parity Check / Memory Parity Error".  It has been stable  up to this point for two years and we have made no recent changes to the server.  One year ago we added RAM (3rd party) to bring it up to 1GB, but it has been stable since that time.  I have tried removing all of the 3rd party ram and the problem does not go away.  I have also tried replacing all of the RAM with memory from another Compaq server.  I have unloaded all nonessential services running on the server. There are no other third party devices in the machine.  Does anyone have any other suggestions?</description>
      <pubDate>Sun, 08 Jul 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550022#M7535</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-07-08T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: memory parity error</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550023#M7536</link>
      <description>This same error just started with us today. We are running ours with 256MB of Compaq RAM. It's been running great for two years until today. Any help would be appreciated. Thanks.</description>
      <pubDate>Wed, 01 Aug 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550023#M7536</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-08-01T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: memory parity error</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550024#M7537</link>
      <description>The same thing has happen to me. One of our 1600's (an intranet server) displays this behavior (started last wednesday). I have got the RAM module replaced but it has not helped a bit. Have you found a solution ?</description>
      <pubDate>Sun, 12 Aug 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550024#M7537</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-08-12T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: memory parity error</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550025#M7538</link>
      <description>This recently happened on my site, a proliant 6400r. I tried replacing the ram (1x128mb, 1x256mb) but to no effect. the server was rebooting at random intervals sometimes hanging during reboot after asr. With our availability of spares i replaced the processor cage (cpq313622-001) and the server has been stable since. The server is running windows terminal server and the memory parity error was displayed during a blue screen. Hope this helps.</description>
      <pubDate>Mon, 10 Sep 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550025#M7538</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-09-10T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: memory parity error</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550026#M7539</link>
      <description>We had the systemboard replaced since replacing the RAM did not help. Since then there has been no more errors.</description>
      <pubDate>Mon, 10 Sep 2001 23:00:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550026#M7539</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-09-10T23:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: memory parity error</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550027#M7540</link>
      <description>After replacing the (in order): Memory, I/O board, Array controller, I/O cage, CD ROM, Processor Cage, and backplane board, it ended up being the processor itself which went bad. Since replacing it, the system has run great.</description>
      <pubDate>Tue, 11 Sep 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550027#M7540</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-09-11T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: memory parity error</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550028#M7541</link>
      <description>Replacing the system board appears to have fixed it for us.  I have also seen this in older workstations.</description>
      <pubDate>Sun, 23 Sep 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550028#M7541</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-09-23T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: memory parity error</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550029#M7542</link>
      <description>We experienced the same error.  We ended up swapping out the memory and also the CPU cage.  I suspect that the CPU cage was the culprit though.</description>
      <pubDate>Thu, 08 Nov 2001 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550029#M7542</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-11-08T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: memory parity error</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550030#M7543</link>
      <description>I was experiencing the same problems with my 1600. It was accompanied by random reboots (about every 7 hours) and would fail to post about 3/4 of the time after reboot. Replacing the CPU cage did the trick. Has been running error free for about 2 weeks now.</description>
      <pubDate>Wed, 22 May 2002 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/memory-parity-error/m-p/2550030#M7543</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2002-05-22T23:00:00Z</dc:date>
    </item>
  </channel>
</rss>

