<?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 A500 Memory / controller errors. in HPE 9000 and HPE e3000 Servers</title>
    <link>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899010#M34964</link>
    <description>Would the wrong part number memory cause these errors? I used this box last week to test a processor terminator with a pair of a3863-66501 (1gb kit) and did not have any problems. I know I should be using either A5572A,a5840a,a5841a,or a6114a but I don't have any on hand at this moment. Using an a500 (a5570) with a 440 processor, master and slave vrm and no drives. &lt;BR /&gt;&lt;BR /&gt;Attached is the giant log of errors. &lt;BR /&gt;&lt;BR /&gt;Why does it indicate Main Memory MISSING also?&lt;BR /&gt;</description>
    <pubDate>Fri, 29 Apr 2005 11:54:09 GMT</pubDate>
    <dc:creator>Steven  Bucek</dc:creator>
    <dc:date>2005-04-29T11:54:09Z</dc:date>
    <item>
      <title>A500 Memory / controller errors.</title>
      <link>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899010#M34964</link>
      <description>Would the wrong part number memory cause these errors? I used this box last week to test a processor terminator with a pair of a3863-66501 (1gb kit) and did not have any problems. I know I should be using either A5572A,a5840a,a5841a,or a6114a but I don't have any on hand at this moment. Using an a500 (a5570) with a 440 processor, master and slave vrm and no drives. &lt;BR /&gt;&lt;BR /&gt;Attached is the giant log of errors. &lt;BR /&gt;&lt;BR /&gt;Why does it indicate Main Memory MISSING also?&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Apr 2005 11:54:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899010#M34964</guid>
      <dc:creator>Steven  Bucek</dc:creator>
      <dc:date>2005-04-29T11:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: A500 Memory / controller errors.</title>
      <link>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899011#M34965</link>
      <description>Error code starting with 7 is memory related only.&lt;BR /&gt;&lt;BR /&gt;Though both are SDRAM but be it's specific to some model of the systems. I generally search the compatibility of the part in partsurfer (&lt;A href="http://partsurfer.hp.com)" target="_blank"&gt;http://partsurfer.hp.com)&lt;/A&gt; before I try using them.&lt;BR /&gt;&lt;BR /&gt;Now in your case either the memory is defective or not compatible. You may test the memory in one of the compatible system.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;TT&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 30 Apr 2005 01:47:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899011#M34965</guid>
      <dc:creator>Thayanidhi</dc:creator>
      <dc:date>2005-04-30T01:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: A500 Memory / controller errors.</title>
      <link>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899012#M34966</link>
      <description>I haven't seen that particular failure.  Can you move your suspect board to another part of memory and see if the error follows the board ?&lt;BR /&gt;</description>
      <pubDate>Tue, 03 May 2005 14:47:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899012#M34966</guid>
      <dc:creator>Kent Ostby</dc:creator>
      <dc:date>2005-05-03T14:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: A500 Memory / controller errors.</title>
      <link>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899013#M34967</link>
      <description>Steven,&lt;BR /&gt;That A3863-66501 is workstation memory, not designed for the A Class server.  You are probably experiencing a timing issue, bus speed is probably way off.  That's also why it's showing up as "missing", the system doesn't understand what is installed and is doing it's best to tell you that.  If you get to BCH, try running an "IN ME" (INfo MEmory) to see if any memory is being seen in the system.&lt;BR /&gt;&lt;BR /&gt;I hope this helps.&lt;BR /&gt;&lt;BR /&gt;Good Luck - Tim</description>
      <pubDate>Tue, 03 May 2005 21:07:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899013#M34967</guid>
      <dc:creator>timmy b.</dc:creator>
      <dc:date>2005-05-03T21:07:55Z</dc:date>
    </item>
    <item>
      <title>Re: A500 Memory / controller errors.</title>
      <link>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899014#M34968</link>
      <description>Thanks for all your input, I have found the solution. &lt;BR /&gt;&lt;BR /&gt;The problem turned out to be the processor terminator. Of the 3 proc-terms I had in the lab, 2 had 1 little fuzzy button missing,  the other one looked fine but still didn't work.  I pulled a proc-term from a working machine and I was able to boot to the PDC without any gsp errors. I tried these bad proc-terms in the working A thats WAS in production (heh) and the errors followed. &lt;BR /&gt;&lt;BR /&gt;What I dont understand is why the gsp reported the 'memory' and 'controller' errors, had me looking in the wrong place.&lt;BR /&gt;&lt;BR /&gt;10000 points for everyone!! &lt;BR /&gt;</description>
      <pubDate>Wed, 04 May 2005 11:21:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-9000-and-hpe-e3000-servers/a500-memory-controller-errors/m-p/4899014#M34968</guid>
      <dc:creator>Steven  Bucek</dc:creator>
      <dc:date>2005-05-04T11:21:37Z</dc:date>
    </item>
  </channel>
</rss>

