<?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: DL 380 G3 NMI parity error with W2k3 in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl-380-g3-nmi-parity-error-with-w2k3/m-p/3344421#M32956</link>
    <description>HP Replaced the mainboard of DL380 and all is ok now.&lt;BR /&gt;This thread is over&lt;BR /&gt;thanks all</description>
    <pubDate>Mon, 06 Sep 2004 01:41:44 GMT</pubDate>
    <dc:creator>Stefano Giusto_1</dc:creator>
    <dc:date>2004-09-06T01:41:44Z</dc:date>
    <item>
      <title>DL 380 G3 NMI parity error with W2k3</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl-380-g3-nmi-parity-error-with-w2k3/m-p/3344418#M32953</link>
      <description>Just installed a DL 380 G3&lt;BR /&gt;W2k3 is on and works fine&lt;BR /&gt;done forest preparation to installa exchange server 2003&lt;BR /&gt;leaved the server running last night&lt;BR /&gt;this morning server was on blue screen with nmi error&lt;BR /&gt;now every boot shows the nmi error&lt;BR /&gt;RAM is OK&lt;BR /&gt;W2k3 starts correctly in safe mode&lt;BR /&gt;All bios and drivers up to date</description>
      <pubDate>Thu, 29 Jul 2004 06:51:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl-380-g3-nmi-parity-error-with-w2k3/m-p/3344418#M32953</guid>
      <dc:creator>Stefano Giusto_1</dc:creator>
      <dc:date>2004-07-29T06:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: DL 380 G3 NMI parity error with W2k3</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl-380-g3-nmi-parity-error-with-w2k3/m-p/3344419#M32954</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;What's the exact error message of the blue screen ?&lt;BR /&gt;&lt;BR /&gt;I've been getting what sounds like a similar fault on a BL20p G2. The machine ran fine with just the OS installed, but then started crashing when it had some load, in my case with Citrix Metaframe. I can't remember the exact error, but I know it had NMI in it somewhere...&lt;BR /&gt;&lt;BR /&gt;I'll post again, when I get to the office.&lt;BR /&gt;&lt;BR /&gt;Rob</description>
      <pubDate>Fri, 30 Jul 2004 00:38:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl-380-g3-nmi-parity-error-with-w2k3/m-p/3344419#M32954</guid>
      <dc:creator>Rob Leadbeater</dc:creator>
      <dc:date>2004-07-30T00:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: DL 380 G3 NMI parity error with W2k3</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl-380-g3-nmi-parity-error-with-w2k3/m-p/3344420#M32955</link>
      <description>If its a memory parity error and the memory checks out. It could be your controler card, are you using the 5I + . I had some memory issues with it, the 5I+ does have some memory on it.&lt;BR /&gt;&lt;BR /&gt;Good Luck</description>
      <pubDate>Mon, 30 Aug 2004 08:40:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl-380-g3-nmi-parity-error-with-w2k3/m-p/3344420#M32955</guid>
      <dc:creator>FRED JEWELL JR</dc:creator>
      <dc:date>2004-08-30T08:40:44Z</dc:date>
    </item>
    <item>
      <title>Re: DL 380 G3 NMI parity error with W2k3</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl-380-g3-nmi-parity-error-with-w2k3/m-p/3344421#M32956</link>
      <description>HP Replaced the mainboard of DL380 and all is ok now.&lt;BR /&gt;This thread is over&lt;BR /&gt;thanks all</description>
      <pubDate>Mon, 06 Sep 2004 01:41:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl-380-g3-nmi-parity-error-with-w2k3/m-p/3344421#M32956</guid>
      <dc:creator>Stefano Giusto_1</dc:creator>
      <dc:date>2004-09-06T01:41:44Z</dc:date>
    </item>
  </channel>
</rss>

