<?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: NMI:  Parity Check/ Memory Parity Error, not a RAM issue. in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219647#M121489</link>
    <description>The drivers and firmware were updated after the Blue Screen occurred on one machine and before the Blue Screen occurred on another machine.  So, there is no correlation there.  I did not see this error show up in the logs.  However, I have found that going into the BIOS and disabling the No-Execute Memory Protection setting under the processor options makes the Blue Screen stop appearing.</description>
    <pubDate>Fri, 15 Jan 2010 18:51:59 GMT</pubDate>
    <dc:creator>Connoley</dc:creator>
    <dc:date>2010-01-15T18:51:59Z</dc:date>
    <item>
      <title>NMI:  Parity Check/ Memory Parity Error, not a RAM issue.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219645#M121487</link>
      <description>On a couple of my DL360 G6's and DL380 G6's, I get this Blue Screen error.  All of the hardware test out fine, and the firmware is updated.  Any suggestions or insight would be much appreciated.</description>
      <pubDate>Fri, 15 Jan 2010 18:36:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219645#M121487</guid>
      <dc:creator>Connoley</dc:creator>
      <dc:date>2010-01-15T18:36:41Z</dc:date>
    </item>
    <item>
      <title>Re: NMI:  Parity Check/ Memory Parity Error, not a RAM issue.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219646#M121488</link>
      <description>what is precise error &lt;BR /&gt;are all firmwares upto date # and drivers&lt;BR /&gt;&lt;BR /&gt;what errors in iml log&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Jan 2010 18:46:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219646#M121488</guid>
      <dc:creator>marcus1234</dc:creator>
      <dc:date>2010-01-15T18:46:02Z</dc:date>
    </item>
    <item>
      <title>Re: NMI:  Parity Check/ Memory Parity Error, not a RAM issue.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219647#M121489</link>
      <description>The drivers and firmware were updated after the Blue Screen occurred on one machine and before the Blue Screen occurred on another machine.  So, there is no correlation there.  I did not see this error show up in the logs.  However, I have found that going into the BIOS and disabling the No-Execute Memory Protection setting under the processor options makes the Blue Screen stop appearing.</description>
      <pubDate>Fri, 15 Jan 2010 18:51:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219647#M121489</guid>
      <dc:creator>Connoley</dc:creator>
      <dc:date>2010-01-15T18:51:59Z</dc:date>
    </item>
    <item>
      <title>Re: NMI:  Parity Check/ Memory Parity Error, not a RAM issue.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219648#M121490</link>
      <description>hmm seen this yet&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01955503" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01955503&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;enjoy :)&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 17 Jan 2010 17:47:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219648#M121490</guid>
      <dc:creator>marcus1234</dc:creator>
      <dc:date>2010-01-17T17:47:10Z</dc:date>
    </item>
    <item>
      <title>Re: NMI:  Parity Check/ Memory Parity Error, not a RAM issue.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219649#M121491</link>
      <description>The link might prove to be useful.  I look into it further.</description>
      <pubDate>Mon, 18 Jan 2010 14:43:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219649#M121491</guid>
      <dc:creator>Connoley</dc:creator>
      <dc:date>2010-01-18T14:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: NMI:  Parity Check/ Memory Parity Error, not a RAM issue.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219650#M121492</link>
      <description>I found the solution to this problem.  According to HP, who was able to confirm this with Intel, there is the â  No-Execute Memory Protectionâ   option in the BIOS that was designed to work in conjunction with Windows Server 2008.  If the option is enabled while running Server 2003, it may return a blue screen, â  NMI:  Parity Check/ Memory Parity Errorâ   as soon as it reaches Windows after the boot.  The HP rep said that we should disable the option on all of the new servers until we decide to upgrade to Server 2008 or later.</description>
      <pubDate>Wed, 20 Jan 2010 13:47:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219650#M121492</guid>
      <dc:creator>Connoley</dc:creator>
      <dc:date>2010-01-20T13:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: NMI:  Parity Check/ Memory Parity Error, not a RAM issue.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219651#M121493</link>
      <description>Thanks for your help Mark.  I can officially close the case on this particular Blue Screen.</description>
      <pubDate>Wed, 20 Jan 2010 13:49:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/nmi-parity-check-memory-parity-error-not-a-ram-issue/m-p/5219651#M121493</guid>
      <dc:creator>Connoley</dc:creator>
      <dc:date>2010-01-20T13:49:11Z</dc:date>
    </item>
  </channel>
</rss>

