Memtest86 Errors

Reaction score
2
Location
Queensland Australia
I've been running memtest on a laptop that has 16GB of RAM. The owner was complaining that it was real slow and sluggish. Though this seems to be my experience with windows 10 which is what the laptop is running. Has anyone else noticed this?
Anyway I thought it's probably just due for a clean and tune up. Though as always I like to check the hardware to make sure it's not at fault.
I often run memtest but almost never come up with errors.
This time I did, and I'm hoping that someone with more experience and understanding of memtest can help me out. Are these errors serious? Would these errors contribute to slower speeds? Does the RAM need replacing?

Please see attached photo for current memtest screen.

Thanks in advance for any light you can shed on this for me.
 

Attachments

  • 20170121_185757_resized_2.jpg
    20170121_185757_resized_2.jpg
    870.6 KB · Views: 44
You might find this of interest.

Why am I only getting errors during Test 13 Hammer Test?

The Hammer Test is designed to detect RAM modules that are susceptible to disturbance errors caused by charge leakage. This phenomenon is characterized in the research paper Flipping Bits in Memory Without Accessing Them: An Experimental Study of DRAM Disturbance Errors by Yoongu Kim et al. According to the research, a significant number of RAM modules manufactured 2010 or newer are affected by this defect. In simple terms, susceptible RAM modules can be subjected to disturbance errors when repeatedly accessing addresses in the same memory bank but different rows in a short period of time. Errors occur when the repeated access causes charge loss in a memory cell, before the cell contents can be refreshed at the next DRAM refresh interval.

Starting from MemTest86 v6.2, the user may see a warning indicating that the RAM may be vulnerable to high frequency row hammer bit flips. This warning appears when errors are detected during the first pass (maximum hammer rate) but no errors are detected during the second pass (lower hammer rate). See MemTest86 Test Algorithms for a description of the two passes that are performed during the Hammer Test (Test 13). When performing the second pass, address pairs are hammered only at the rate deemed as the maximum allowable by memory vendors (200K accesses per 64ms). Once this rate is exceeded, the integrity of memory contents may no longer be guaranteed. If errors are detected in both passes, errors are reported as normal.

The errors detected during Test 13, albeit exposed only in extreme memory access cases, are most certainly real errors. During typical home PC usage (eg. web browsing, word processing, etc.), it is less likely that the memory usage pattern will fall into the extreme case that make it vulnerable to disturbance errors. It may be of greater concern if you were running highly sensitive equipment such as medical equipment, aircraft control systems, or bank database servers. It is impossible to predict with any accuracy if these errors will occur in real life applications. One would need to do a major scientific study of 1000 of computers and their usage patterns, then do a forensic analysis of each application to study how it makes use of the RAM while it executes. To date, we have only seen 1-bit errors as a result of running the Hammer Test.

There are several actions that can be taken when you discover that your RAM modules are vulnerable to disturbance errors:

  • Do nothing
  • Replace the RAM modules
  • Use RAM modules with error-checking capabilities (eg. ECC)
Depending on your willingness to live with the possibility of these errors manifesting itself as real problems, you may choose to do nothing and accept the risk. For home use you may be willing to live with the errors. In our experience, we have several machines that have been stable for home/office use despite experiencing errors in the Hammer Test.

You may also choose to replace the RAM with modules that have been known to pass the Hammer Test. Choose RAM modules of different brand/model as it is likely that the RAM modules with the same model would still fail the Hammer test.

For sensitive equipment requiring high availability/reliability, you would replace the RAM without question and would probably switch to RAM with error correction such as ECC RAM. Even a 1-bit error can result in catastrophic consequences for say, a bank account balance. Note that not all motherboards support ECC memory, so consult the motherboard specifications before purchasing ECC RAM.
Source: http://www.memtest86.com/troubleshooting.htm
 
from article linked above...

"The errors detected during Test 13, albeit exposed only in extreme memory access cases, are most certainly real errors"

I would swap RAM for known good and test again.
 
The owner was complaining that it was real slow and sluggish. Though this seems to be my experience with windows 10 which is what the laptop is running. Has anyone else noticed this?

As a general rule, my experience has been just the opposite. Assuming the PC's hardware specs are sufficient, most PCs will run faster on Win 10 than Win 7 or Win 8. Where Win 10 PCs have had problems have been from an upgrade from Win 7 or Win 8 and the original Win had issues.
 
Why bother even wasting time on testing/swapping ram etc
Ram is so cheap I'd just swap it out for new modules and be done with it.
My .02

Well, either way he's likely going to be swapping the RAM out. I don't consider it a waste of time to leave a machine unattended for several hours while running tests, allowing for other tasks to be accomplished. Plus I'd want to validate for my own sanity that the errors no longer showed after the RAM swap.
 
I usually follow up a memtest with Prime95 overnight when in doubt. (A memory error would show up as a BSOD, not slowness.)

I agree with @glricht slowness in Win10 is not standard. My first checks are Updates always running and anti-virus issues.
 
Last edited:
You might find this of interest.


Source: http://www.memtest86.com/troubleshooting.htm
Thanks for that. It was of some help.

from article linked above...

"The errors detected during Test 13, albeit exposed only in extreme memory access cases, are most certainly real errors"

I would swap RAM for known good and test again.
Thanks, yea I'll probably inform the owner that he may need some more RAM.

As a general rule, my experience has been just the opposite. Assuming the PC's hardware specs are sufficient, most PCs will run faster on Win 10 than Win 7 or Win 8. Where Win 10 PCs have had problems have been from an upgrade from Win 7 or Win 8 and the original Win had issues.
Ok I'm not sure if this one was an upgrade. Possibly, others that I've experienced Win10 on have been upgrades. Are there any tricks fix that slow sluggishness that comes from upgrades with out doing a fresh install?

Well, either way he's likely going to be swapping the RAM out. I don't consider it a waste of time to leave a machine unattended for several hours while running tests, allowing for other tasks to be accomplished. Plus I'd want to validate for my own sanity that the errors no longer showed after the RAM swap.
I agree, I dont feel right charging for Hardware without something to suggest that it's needed. Plus as cheap as RAM may be, some people may not be willing to spend that extra.
 
Last edited:
The rowhammer vulnerability is just that – vulnerable to a rowhammer attack. If the system is not under such an attack, the errors are moot and unlikely to be the cause of slow running.

More likely to be f'ed up by Windows update.:mad: Or a HDD problem.
 
I usually follow up a memtest with Prime95 overnight when in doubt.

I agree with @glricht slowness in Win10 is not standard. My first checks are Updates always running and anti-virus issues.
Yea Ill run Prime95 next.

Usually when a customer tells me that their computer is running slow, I think what are their running services and whats in their start up. Then I go on to check for Virus & Malware. Then a general clean up etc. But as I said I like to also check the hardware cause I know that can sometimes be apart of the problem.

I once had a laptop where the customer said it was running slow and doing strange things. Aside from that it was working when he gave it to me. I had just started looking it over when it completely crash (from nothing that I had done). When I turned back on, it wouldn't boot. It was as though there was no HDD. Further test showed that the HDD had failed. Was probably going too anyway, was just unfortunate that it happened while I had it. I don't think the guy was too happy about it. Not sure he believed me. By the time he came to pick it up and I explained what happened. I had already prepared a couple qoutes for a new HDD. But I never herd back from him.
 
Back
Top