Memtest86+ v2.00: what Test# to use?

[LOUISSSSS]

need to run memtest86+ v2.00 to test out some ram, is test 5 still the one to use? or should i leave it on default and run all the tests???

 

[n7]

I always run all of them...

But maybe i'm crazy :Q

 

[LOUISSSSS]

for how long do u run them when checking for errors on a 1 x 1gb of ddr2 800?

does anyone know the significance of test#5? it keeps ringing a bell in my head

 

[n7]

Seems google agrees; apparently test 5 is the best one for really stressing RAM, & based on how many times i've made it to test 5 before seeing errors, it seems to be accurate.

Individual Test Descriptions

Memtest86 executes a series of numbered test sections to check for errors. These test sections consist of a combination of test algorithm, data pattern and cache setting. The execution order for these tests were arranged so that errors will be detected as rapidly as possible. A description of each of the test sections follows:

Test 0 [Address test, walking ones, no cache]

Tests all address bits in all memory banks by using a walking ones address pattern.

Test 1 [Address test, own address]

Each address is written with its own address and then is checked for consistency. In theory previous tests should have caught any memory addressing problems. This test should catch any addressing errors that somehow were not previously detected.

Test 2 [Moving inversions, ones&zeros]

This test uses the moving inversions algorithm with patterns of all ones and zeros. Cache is enabled even though it interferes to some degree with the test algorithm. With cache enabled this test does not take long and should quickly find all "hard" errors and some more subtle errors. This test is only a quick check.

Test 3 [Moving inversions, 8 bit pat]

This is the same as test one but uses a 8 bit wide pattern of "walking" ones and zeros. This test will better detect subtle errors in "wide" memory chips. A total of 20 data patterns are used.

Test 4 [Moving inversions, random pattern]

Test 4 uses the same algorithm as test 1 but the data pattern is a random number and it's complement. This test is particularly effective in finding difficult to detect data sensitive errors. A total of 60 patterns are used. The random number sequence is different with each pass so multiple passes increase effectiveness.

Test 5 [Block move, 64 moves]

This test stresses memory by using block move (movsl) instructions and is based on Robert Redelmeier's burnBX test. Memory is initialized with shifting patterns that are inverted every 8 bytes. Then 4mb blocks of memory are moved around using the movsl instruction. After the moves are completed the data patterns are checked. Because the data is checked only after the memory moves are completed it is not possible to know where the error occurred. The addresses reported are only for where the bad pattern was found. Since the moves are constrained to a 8mb segment of memory the failing address will always be less than 8mb away from the reported address. Errors from this test are not used to calculate BadRAM patterns.

Test 6 [Moving inversions, 32 bit pat]

This is a variation of the moving inversions algorithm that shifts the data pattern left one bit for each successive address. The starting bit position is shifted left for each pass. To use all possible data patterns 32 passes are required. This test is quite effective at detecting data sensitive errors but the execution time is long.

Test 7 [Random number sequence]

This test writes a series of random numbers into memory. By resetting the seed for the random number the same sequence of number can be created for a reference. The initial pattern is checked and then complemented and checked again on the next pass. However, unlike the moving inversions test writing and checking can only be done in the forward direction.

Test 8 [Modulo 20, ones&zeros]

Using the Modulo-X algorithm should uncover errors that are not detected by moving inversions due to cache and buffering interference with the the algorithm. As with test one only ones and zeros are used for data patterns.

Test 9 [Bit fade test, 90 min, 2 patterns]

The bit fade test initializes all of memory with a pattern and then sleeps for 90 minutes. Then memory is examined to see if any memory bits have changed. All ones and all zero patterns are used. This test takes 3 hours to complete. The Bit Fade test is not included in the normal test sequence and must be run manually via the runtime configuration menu.

 

[LOUISSSSS]

^^won't quote it cuz its too long ^^
good info! i was looking for that at the memtest85.org site.

i ran 2 x full tests of memtest86+ v2.00 and it stopped it automatically after reaching 100% and said test finished press esc to exit.

what do people normally mean by run memtest86+ v2.00 for 24 hours, when the default testing stops itself after 20 minutes or so (100%)

 

[nefariouscaine]

thats interesting - never had it just stop on me for reaching 100% - do have to say i kinda like 2.0 a lot more than previous versions especially for testing out 4 gigs

you are running it from a boot CD right?

 

[LOUISSSSS]

Originally posted by: nefariouscaine
thats interesting - never had it just stop on me for reaching 100% - do have to say i kinda like 2.0 a lot more than previous versions especially for testing out 4 gigs

you are running it from a boot CD right?

yea, if u leave v2.00 on its default tests when it finishes all the tests it says something along the lines of "finished testhing. press esc to exit or reboot"

it isn't the most conclusive test tho, for example:
i was testing 1 x 1gb of DDR2 800 Ballistix ram and it passed the V2.00 test twice in a row, then that same ram passed the HCI memtest for 20 minutes, but failed P95 v25.6 BLEND after 2-3 hours...

 

[nefariouscaine]

Originally posted by: LOUISSSSS

Originally posted by: nefariouscaine
thats interesting - never had it just stop on me for reaching 100% - do have to say i kinda like 2.0 a lot more than previous versions especially for testing out 4 gigs

you are running it from a boot CD right?

yea, if u leave v2.00 on its default tests when it finishes all the tests it says something along the lines of "finished testhing. press esc to exit or reboot"

it isn't the most conclusive test tho, for example:
i was testing 1 x 1gb of DDR2 800 Ballistix ram and it passed the V2.00 test twice in a row, then that same ram passed the HCI memtest for 20 minutes, but failed P95 v25.6 BLEND after 2-3 hours...

If the memory passes memtest but the system isn't stable under a prime test that IMO means that something else isn't 100% stable

are you doing these tests with the rest of your system fully stock too

 

[Big Lar]

Originally posted by: nefariouscaine

Originally posted by: LOUISSSSS

Originally posted by: nefariouscaine
thats interesting - never had it just stop on me for reaching 100% - do have to say i kinda like 2.0 a lot more than previous versions especially for testing out 4 gigs

you are running it from a boot CD right?

yea, if u leave v2.00 on its default tests when it finishes all the tests it says something along the lines of "finished testhing. press esc to exit or reboot"

it isn't the most conclusive test tho, for example:
i was testing 1 x 1gb of DDR2 800 Ballistix ram and it passed the V2.00 test twice in a row, then that same ram passed the HCI memtest for 20 minutes, but failed P95 v25.6 BLEND after 2-3 hours...

If the memory passes memtest but the system isn't stable under a prime test that IMO means that something else isn't 100% stable

are you doing these tests with the rest of your system fully stock too

What he said, but to add a bit,"usually" if the memory passes in memtest but not in Orthos/prime, it is either the Northbridge Voltage is a tad low, the Vdimm voltage is a bit low, or the Vid,(cpu volts) is a tad low, or a combination of all 3. Now, what I just stated is a "Blanket Statement" if you get my drift, as it could very well be something else.

What I suggest is;

Run memtest off boot and run at Least 10 Passes of Test3,Test5 and Test8.
Then if that passes, run about 5 passes of the entire memtest. If it passes there, try Memtest for windows and let it run at Least 300%. If that passes, you should be good to go as far as ram goes.

Larry

 

[LOUISSSSS]

Originally posted by: Big Lar

What I suggest is;

Run memtest off boot and run at Least 10 Passes of Test3,Test5 and Test8.
Then if that passes, run about 5 passes of the entire memtest. If it passes there, try Memtest for windows and let it run at Least 300%. If that passes, you should be good to go as far as ram goes.

Larry

what if i do that an my ram passes it all but fails when i run P95 Blend after a few hours?
i've arleady set a proper vCore + vRam. i have FSB + MCH @ +0.10v

 

[Big Lar]

If it passes all that ram testing,AND your temps are good now, maybe try bumping the vcore just a tad.