On Fri, 25 Jan 2008 09:25:59 EST, Lennart Sorensen said:

quoted text
> Personally I just don't bother with memtest anymore.  The only thing it
> tells you is that you have errors or that you might have errors but it
> didn't find them.  It never tells you that you do not have errors and it
> often does miss that you have errors since marginal memory is more
> likely to fail under cpu load it seems which memtest doesn't do.

It's been quite some time since I've gone the "run memtest for 24 hours" route.

However, I still recommend that for odd cases, you let memtest make *one* cycle
through its tests - that's only an hour-ish, and if it hits something, then
you *know* you have some hardware issues to deal with.