You test ONLY one modue at a time. You replace any memory module that fails any part of the test. You don't need to know what fails. If you use any module that fails the test for any reason, there is something wrong with you.
You must run it for 4 hours or 7 passes, which ever takes longer. Usually 7 passes is required. This assures that all components have been thoroughly testedl. If there are any failures, you assume the worst. The guys who designed this test in about 2004 do have a website, and there are detailed explanations at that website, which I believe is www.memtest86.com. They are finally charging a small fee for most recent versions of the test, but the free one is still good enough. The earn whatever they get, because they spent five years getting it perfect. There are other memory tests, and we have an expensive device in our shop that tests nearly all memory modules out there. I don't think any of the expensive tests and equipment have anything over on the MemTest86 tests. Why do you need more information? If memory is defective, it is defective. There is no issue, but I guess you can try to create one if you want. The test is recommend on every tech support site. You can find more details on any of them, or on the website of the designers. Any test that works better is on a machine that costs $600. RB - - - - - Last, but not least, avoid clichés like the plague. ... .... ..... ...... ....... William Safire On Sat, Oct 17, 2009 at 2:27 PM, Rob Bell <[email protected]> wrote: > > > Jeffrey Race wrote: > >> On Sat, 17 Oct 2009 10:47:09 -0500, Alex Austin wrote: >> >> I'm not sure you can. Basically, any failure it finds indicates that you >>> need to replace ram. While it's more verbose, it's essentially a >>> pass/fail >>> test. >>> >> >> >> Agreed. But WHAT fails? I have two RAM DIMMs and also onboard memory. >> I don't know how to interpret the screen report because there are no >> instructions, and I can't refer the screen report to anyone because I >> can't access it as a file. Seems like there's some issue here >> > > > As someone else mentioned previously, pull out the removable memory then > run the test. If it fails the on-board memory is bad. Otherwise put each > one of the removable sticks in at a time and test again. You'll find the > bad one that way. > > Rob > > _______________________________________________ > Thinkpad mailing list > [email protected] > http://stderr.org/cgi-bin/mailman/listinfo/thinkpad > _______________________________________________ Thinkpad mailing list [email protected] http://stderr.org/cgi-bin/mailman/listinfo/thinkpad
