Announcement

Collapse
No announcement yet.

How do I know which module is bad based on the report?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • How do I know which module is bad based on the report?

    I have run the test on my system two times, and the key thing that I noticed is follows:
    First Test failed with error on Test 3 and 7:
    Lowest Error Address 0x65C3ACD7C (26051MB)
    Highest Error Address 0x65E3AD538 (26083MB)

    Second test failed with error on Test 3 and 5:
    Lowest Error Address 0x65C3ACD7C (26051MB)
    Highest Error Address 0x65C3ACD7C (26051MB)

    The total amount of memory in the system is 96 GB (2 x 16 and 2 x32). The 32GB are on A2 and B2, and 16GB are on A1 and B1 slots. I've been running this system for over a year with no problem, but lately it's been crashing randomly. Sometimes in 5 hours, sometimes in 30 minutes.

    Based on what is noted above for the Lowest and Highest Error Address, can some one guide me in on which of the 4 modules is bad?

    Thank you so much!

  • #2
    Memory address decode (to a physical location) is very complex. Especially for dual channel and even more so when you have sticks of different capacity. There is interleaving and hashing that takes place.

    The paid version of Memtest86 can do this however, but only for a limited set of CPUs, motherboards & RAM types. Unfornately each CPU family has a different memory controller so there are a huge number of permutations in the way RAM can be setup / installed.

    Details can be found here
    https://www.memtest86.com/tech_DIMM_Decoding.html

    Otherwise you can test one stick at a time. See also,
    https://www.memtest86.com/troubleshooting.htm



    Comment


    • #3
      Originally posted by David (PassMark) View Post
      Memory address decode (to a physical location) is very complex. Especially for dual channel and even more so when you have sticks of different capacity. There is interleaving and hashing that takes place.

      The paid version of Memtest86 can do this however, but only for a limited set of CPUs, motherboards & RAM types. Unfornately each CPU family has a different memory controller so there are a huge number of permutations in the way RAM can be setup / installed.

      Details can be found here
      https://www.memtest86.com/tech_DIMM_Decoding.html

      Otherwise you can test one stick at a time. See also,
      https://www.memtest86.com/troubleshooting.htm


      Thank you. I will start in pairs and go from there Appreciate the input.

      Comment

      Working...
      X