TR Forums

I had a set of [url="http://www.newegg.com/Product/Product.aspx?Item=N82E16820226095&Tpk=996770"]996770[/url] that produced 1 error per pass of memtest 86+, so I bought a set of [url="http://www.newegg.com/Product/Product.aspx?Item=N82E16820226099"]996776[/url] to replace it. For a while, I couldn't get it to boot, and only by using the XMS profile could I get it working (manually inputting the timings and voltage didn't help), and it was stable in Windows. However, during Memtest 86+, it would get through one pass, partially through another, and stop altogether. The timer stopped with it. Is the RAM bad? Is there something else I should look at? The other set, 996770, would run as long as I left it and would reliably produce 1 error per pass. This time, no errors came back, but Memtest stopped.

Memtest is being run from a 4GB PNY Flash drive that has no obvious issues.

I'm running:

Phenom II X4 925 (C3)
M5A97
996776, 996770
500W Silverstone Strider
GTX460

Everything is bone stock for memtest, and the RAM is using XMP or manual settings for the run.

What could be causing this? Is the RAM fine? I just built this comp a week or two ago and I want to get all this sorted so I don't have to keep messing with it.

Thanks

PS, by "Memtest stops," I mean that memtest freezes.

By the way, it's Memtest 4.2, I think

Have you tried running 1 stick at a time to see if it's any different?

No, but I don't know why I didn't think of that!

What could possibly make Memtest freeze up?

Let see.

What can stop memtest from working?


Common issues:
Defective memory, or memory not capable of running the advertised spec (same as defective to me)
Defective memory controller (on motherboard) or memory controller no capable of running the advertised spec (same as defective to me)
Incorrect memory timings
Incorrect memory voltage

Rare issues:
Power supply out of regulation (causes random issues)
Bad CPU (specifically will fail tests that include the L2 Cache but not others)

Extremely Rare:
Other hardware causing issues with the motherboard at a low level
bug in memtest+ 4.2