Memtest86, how do you like to use it?

N

NEODARK

Gawd
Joined
Aug 10, 2004
Messages
1,002
Just wondering how ppl use memtest86 to test the stability of their memory when O/C'd

I heard some ppl like to run test#5 for about an hour and if it passes with no errors it means stable memory..

others just run the full gamut of tests and let it cycle for a couple of hours. if it passes with no errors it means stable memory..

so how do you like to use mem test?
 
I don't. My understand is that errors from the memory and the cpu can't be resolved so I see no big advantage to it over Prime95. Maybe others will correct me if I'm wrong. :D
 
deeppow said:
I don't. My understand is that errors from the memory and the cpu can't be resolved so I see no big advantage to it over Prime95. Maybe others will correct me if I'm wrong. :D
Click to expand...

They can usually be resolved (if you're OCing a lot) by reducing their clock speeds.
However, sometimes you get bad chips and they just generate errors.
 
What's wrong with the editer, it should allow me to delete this!!!!!!!!!!!!!!!!!!!!!!! Sorry folks.
 
rtierney said:
They can usually be resolved (if you're OCing a lot) by reducing their clock speeds.
However, sometimes you get bad chips and they just generate errors.
Click to expand...

I can do the same using Prime95, no difference.
 
What makes you say that? Give my some proof, I'm willing to accept the answer.
 
just use the damn blend test on prime. if ur mem can pass that, it's not likely that ur ram will crash.
 
Memtest86 is much better and faster at detecting errors in memory access then any windows based program. That's a fact.

I run the default loop of tests overnight, any problems then the oc doesn't make the cut.
 
Memtest86+
Troubleshooting Memory Errors

Please be aware that not all errors reported by Memtest86 are due to bad memory. The test implicitly tests the CPU, L1 and L2 caches as well as the motherboard. It is impossible for the test to determine what causes the failure to occur. However, most failures will be due to a problem with memory module. When it is not, the only option is to replace parts until the failure is corrected.

Once a memory error has been detected, determining the failing SIMM/DIMM module is not a clear cut procedure. With the large number of motherboard vendors and possible combinations of memory slots it would be difficult if not impossible to assemble complete information about how a particular error would map to a failing memory module. However, there are steps that may be taken to determine the failing module. Here are four techniques that you may wish to use:

1) Removing modules
This is simplest method for isolating a failing modules, but may only be employed when one or more modules can be removed from the system. By selectively removing modules from the system and then running the test you will be able to find the bad modules. Be sure to note exactly which modules are in the system when the test passes and when the test fails.

2) Rotating modules
When none of the modules can be removed then you may wish to rotate modules to find the failing one. This technique can only be used if there are three or more modules in the system. Change the location of two modules at a time. For example put the module from slot 1 into slot 2 and put the module from slot 2 in slot 1. Run the test and if either the failing bit or address changes then you know that the failing module is one of the ones just moved. By using several combinations of module movement you should be able to determine which module is failing.

3) Replacing modules
If you are unable to use either of the previous techniques then you are left to selective replacement of modules to find the failure.

4) Avoiding allocation
Click to expand...
ect
 
Talonz said:
I run the default loop of tests overnight, any problems then the oc doesn't make the cut.
Click to expand...
I run all tests overnight. I'll manage to get a few passes through ten to twelve hours.
 
For those buying new memory, it's a handy tool to check for any problems. If new memory doesn't pass say a 24 hour plus test, you can then return/exchange the modules, instead of encountering trouble in the future.
The test is worth it for that alone.

gl
 
The most useful thing I find about memtest is you can boot of a floppy or cd, and NOT go into your primary OS to test overclocks. you dont have to worry about borking your RAID array or anything else...having lost Arrrays before to aggresive overclocks, memtest allows me to check everything before i put my data at risk.

its also more flexible than prime, IMO
 
so i guess its safer to run "all" default tests instead of a specific "one test" to find errors?
 
Talonz said:
Memtest86 is much better and faster at detecting errors in memory access then any windows based program. That's a fact.

I run the default loop of tests overnight, any problems then the oc doesn't make the cut.
Click to expand...

If you are running tests overnight, why do you care if it's faster?
 
You must log in or register to reply here.
Back
Top