In message <
[email protected]> "JAD"
windows is the least of things that will effect a memory test ,
mb subsystems have more impact than software. Your case (your prior post) is
a little different, as you use this for no apparent reason other than
finding out if your memory timings were correct. Unfortunately many users
toss mods out based on the out come of these tests. To me memtesters tell
you what you already suspect, a bad system. Is it memory - MB - heat - a
lamp on the top - a power problem? who's to say, the memtester won't help
you with those things. You can't test components in a suspect machine, the
outcome will always be suspect.
True, but once I can consistently identify the problem, I can start
moving hardware between PCs to identify whether a problem follows a
piece of hardware.
Since I have multiple sticks of DDR, if it was a single failing stick
then I'd have been able to identify it by testing each stick in
sequence. If one consistently failed, and in more then one slot, then
there would be a problem with that stick (and/or compatibility with the
motherboard) and I would have isolated the problem. I could then try
that stick in another PC and if the problem continues, then I'd know it
was definitely that stick.
It's not the be all and end all of diagnostics tools, but when used
appropriately it's a very powerful tool. It might not be able to
identify all failure modes, but if it does identify a failure then
*something* is definitely wrong (but identifying what is wrong takes a
little more legwork)
