ECC errors on a MacPro 5,1 with 8 slots filled

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ken
    Junior Member
    • Sep 2019
    • 4

    #1

    ECC errors on a MacPro 5,1 with 8 slots filled

    I upgraded the memory on a MacPro 5,1 to 64GB (8x8GB) using "Hynix HMT31GR7AFR4C-H9 8GB 1333MHz ECC DDR3".

    Running memtest86 the first time showed numerous ECC errors (correctable) at a single memory address with test 13 (Hammer) labeled "Ch/Sl: 2-0". Then I moved the modules that were in slots #1 and #2 into #3 and #4 (and vice versa), and the memory in slots #5 and #6 into #7 and #8 (and vice versa). After that, memtest86 shows numerous ECC errors on just about every test, not just Hammer, and at a different single address.

    I don't know how to interpret this. I thought that slots #3 and #7 would correspond to channel 2, so it's confusing seeing that Ch/Sl 2-0 is still being reported. Any thoughts would be most welcome. Thanks Click image for larger version  Name:	memtest86-1.jpg Views:	0 Size:	326.8 KB ID:	59059
    image widget
    Last edited by ken; May-01-2025, 02:28 AM. Reason: Trying to add a second image file showing the second test results
  • ken
    Junior Member
    • Sep 2019
    • 4

    #2
    This is the second test (different address, ECC errors on multiple tests, not just 13 (Hammer).
    Attached Files

    Comment

    • David (PassMark)
      Administrator
      • Jan 2003
      • 11092

      #3
      The channel and slot numbers reported are what we get from the memory controller in the CPU.
      The software doesn't really have any knowledge of the physical locations of the slots.
      And there is no real reason to expect the slot numbers reported by an Intel CPU to match the number of slots by Apple (assuming apple even gives them a number).

      If one RAM stick was bad, moving it to a different slot should change the error address, assuming other slots are also in use (how much it changes depends on a bunch of complex factors, like channel interleaving).

      Seems likely these are real errors (but then get corrected by the ECC function)

      Comment

      Working...