<?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: DL360 Memory Parity Errors in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl360-memory-parity-errors/m-p/2985157#M18746</link>
    <description>Which Generation of DL360 was it?  (one?)  Also, what size(s)/brand(s) of memory are you using?  Was the blue screen 0x0000002E?  Maybe this will help someone with the diagnosis :).</description>
    <pubDate>Fri, 30 May 2003 14:38:59 GMT</pubDate>
    <dc:creator>Kelcey E. Decker</dc:creator>
    <dc:date>2003-05-30T14:38:59Z</dc:date>
    <item>
      <title>DL360 Memory Parity Errors</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl360-memory-parity-errors/m-p/2985156#M18745</link>
      <description>We are trying to install the Oracle forms runtime componants on a DL360.  During the install we get a Blue Screen that indicates a "Memory Parity Error".&lt;BR /&gt;&lt;BR /&gt;We have tried it on 2 different servers and both have Citix installed on them...and both got the same error.&lt;BR /&gt;&lt;BR /&gt;Any known work-arounds?  Is this a known issue?  &lt;BR /&gt;&lt;BR /&gt;Thanks for any help</description>
      <pubDate>Fri, 30 May 2003 11:46:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl360-memory-parity-errors/m-p/2985156#M18745</guid>
      <dc:creator>Eric Wilkes</dc:creator>
      <dc:date>2003-05-30T11:46:44Z</dc:date>
    </item>
    <item>
      <title>Re: DL360 Memory Parity Errors</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl360-memory-parity-errors/m-p/2985157#M18746</link>
      <description>Which Generation of DL360 was it?  (one?)  Also, what size(s)/brand(s) of memory are you using?  Was the blue screen 0x0000002E?  Maybe this will help someone with the diagnosis :).</description>
      <pubDate>Fri, 30 May 2003 14:38:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl360-memory-parity-errors/m-p/2985157#M18746</guid>
      <dc:creator>Kelcey E. Decker</dc:creator>
      <dc:date>2003-05-30T14:38:59Z</dc:date>
    </item>
  </channel>
</rss>

