Memtest's accuracy

Associate
Joined
21 Jul 2005
Posts
706
Location
London
Recently I occasionally had the infamous windows "cannot read from memory, debug or cancel" errors and constantly lock ups during Tomb Raider Anniversary. Ran memtest and a lot of errors were found. How accurate is Memtest? Quite a few people have reported having failed it even the memory is brandnew. Should I RMA my memory, Corsair XMS2 6400 C4 2GB Dual Channel?
 
toucam said:
Recently I occasionally had the infamous windows "cannot read from memory, debug or cancel" errors and constantly lock ups during Tomb Raider Anniversary. Ran memtest and a lot of errors were found. How accurate is Memtest? Quite a few people have reported having failed it even the memory is brandnew. Should I RMA my memory, Corsair XMS2 6400 C4 2GB Dual Channel?
What MOBO do you have?

Are you OCing and if so, what are your bios settings for voltages, CPU, and memory?

Do your errors only occur with 1 game?
 
I think I have found out what caused the problem. For some reason the DRAM setting in BIOS was DDR835 where it was supposed to be 668 because my FSB is 334 @ 3Ghz , 2.0v. I played TRA for about 2h yesterday and ran memtest again for over 1h no problem. Mobo is P5W DH, E6600.
Cheers for the replies guys.
 
markyp23 said:
If you are talking about HCI Design Memtest then I disagree

It picked up errors that the memtest86+ couldn't even after running it all night. Only downside is you have to run 2 copies manually for 2Gb and 4 copies if you have 4Gb RAM. I use both just to be safe.
 
OK fair point. It's not been as good in my experience and it's also slightly dependent on your Windows installation.

I mean whenever you've got dodgy memory (as in faulty) Memtest86+ lets you know in seconds and that windows program took the best part of an hour to do that for me.

Although Memtest86+ can take some time to spot stability errors, which I see was what the topic was asking for. :)

Just reread the post and it's safe to say if memtest86+ finds an error then there is an error.
 
Last edited:
Back
Top Bottom