Memtest86+ found errors in one setup, but not in others

[KriB]

Hi!

I just installed a new cpu and two new RAM modules on my mobo. Before upgrading, my system had been running perfectly for months, but when playing Borderlands the day after I got a BSOD after abt two hours.

So, without much ado I decided there might be something iffy with my new components.
The next day I downloaded Memtest86+ v4.2, put it on a USB stick and rebooted. The test started and I left the computer for abt 5 mins. (There is a limit to how interesting watching a memtest run is, right?)
I came back and whoa! 10 errors in test 4, and this was only after 8 mins of running! Here is a pic of the error if you are interested...

So, I shut down my computer right away and took out one of the memory modules and booted again. Started the test, ran it for 10 mins. No errors.
OK, probably not this module, then.
Shut down system again and swapped the memory module. Used the same slot, mind you!
Ran it again, no problems after 10 mins. OK, what is this....?
Shut down again and put the other module into the system and booted again with both modules in. The modules have now swapped places, remember!
Started the full test again, waited for 10 mins, no errors! OK, I leave it overnight.
This morning the test had done 17 passes without any errors at all!

What to do? Are my modules faulty? Is Memtest86+ not able to see the error in some cases? Or is the sequence of the modules important to have a faultfree system and I should not worry now that I have swapped the modules and have no errors reported?

I have seen recommendations to swap modules when having problems, but I want to make sure I have a system that is ok.

It has been less than a week, so I can make a 1 for 1 swap with my dealer if I want to and can prove errors. Should I?

PS: I have not swapped the modules back yet to see if I get the error again. Will do so later tonight.

My first post, weee....

 

[Turbonium]

Do an overnight test or longer of each module on its own. That will tell you if one of the modules is faulty (or both). That would be a good start.

 

[KriB]

Do an overnight test or longer of each module on its own. That will tell you if one of the modules is faulty (or both). That would be a good start.

I can do that.

 

[Soulkeeper]

Is this an overclocked system ?
what are the specs for the hardware ?
many factors can result in memtest errors besides faulty memory (ie: heat, cpu/cache, bios settings, voltages, etc.)

 

[Meghan54]

Is this an overclocked system ?
what are the specs for the hardware ?
many factors can result in memtest errors besides faulty memory (ie: heat, cpu/cache, bios settings, voltages, etc.)

Also, there are other factors that can induce errors, such as not cleaning the memory slots and introducing a fleck of dust into the slot when seating the new memory stick (which almost sounds like what happened here---the repeated seating dislodged/removed the offending dirt/dust from the slot) or the stick of memory isn't quite seated down into the slot all the way---again, repeated seating of the stick "fixes" the problem, just like what happened to the OP.

Bet there's no problem with the memory. From what I've experienced over the years, if a stick of memory faults in Memtest, it always faults if the IC's on the stick are truly bad.

 

[KriB]

Hi, guys!
This not an overclocked system.

I left Memtest running when I left home this morning, and the latest update is that it had found errors when I arrived home this afternoon. This time at another place, indicating that one of the modules is faulty since I swapped places. I bought them as a pair, so I will go to the shop and get a one for one exchange as I am entitled to.

Thanks for your help!