Memtest86 v8.2 does not find error, v8.3 does. Which test is correct now?

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Hauser_Ger
    Junior Member
    • Feb 2020
    • 4
    #1

    Memtest86 v8.2 does not find error, v8.3 does. Which test is correct now?

    Hi,

    when I build my PC v8.2 was the latest. So I tested my RAM and it was fine. Did the test a couple of times.
    Since I ran into issues a few days ago, I tested again with 8.2: No errors.
    Then I downloaded the new version 8.3, which does find errors. Both can be reproduced. 8.2 no errors at all, 8.3 errors. So how can that be and which test is correct?

    Greets & thanks,
    Hauser
    Tags: None
    • David (PassMark)
      Administrator
      • Jan 2003
      • 11092
      #2
      There was no significant change to the test algorithms in V8.3 compared to V8.2. See,
      https://www.memtest86.com/support/ver_history.htm

      What were the details of the errors?

        Comment

        • Hauser_Ger
          Junior Member
          • Feb 2020
          • 4
          #3
          Originally posted by David (PassMark)
          There was no significant change to the test algorithms in V8.3 compared to V8.2. See,
          https://www.memtest86.com/support/ver_history.htm

          What were the details of the errors?
          I know, that's what I did first thing... (Looking at the changenotes.)
          Since I had no explenation for this, I was hoping you guys would have an idea.

          Error:
          Test: 6 Addr: *** Expected: FF FF FF 7D Actual: FF FF FF FD CPU: ***

          Getting only 4 errors in 2 of the 4 passes. Adresses change, never the same adress. CPU does vary too.

          Greets & thanks,
          Hauser

            Comment

            • David (PassMark)
              Administrator
              • Jan 2003
              • 11092
              #4
              Error was a single bit flip. So it looks like a real RAM error.

              But we don't really have any explanation for the difference in the V8.3 and V8.2 results. Error could be intermittent and maybe it was just random luck that 8.3 picked it up.

                Comment

                • Hauser_Ger
                  Junior Member
                  • Feb 2020
                  • 4
                  #5
                  Hi,

                  thanks for your quick reply.
                  I resettet the BIOS and loaded the profile again. Did the test again over and over with 8.2 and 8.3. NO more errors. Which is good - but I still don't get it.

                  Hope it stays this way!

                  Thanks again for your help!
                  Hauser

                    Comment

                    • David (PassMark)
                      Administrator
                      • Jan 2003
                      • 11092
                      #6
                      Maybe BIOS reset went back to default RAM voltages and clock speeds. (and / or disabled XMP).

                        Comment

                        • Hauser_Ger
                          Junior Member
                          • Feb 2020
                          • 4
                          #7
                          Settings are the same. Loaded the user profile where the settings were saved and checked them myself afterwards.

                          Maybe something went wrong, BIOS wise and resett / reload settings cured it.

                          Again, thx for your help!

                            Comment

                            Previous template Next
                            Working...