brahmasoccer09 wrote:
> Thanks for your input. I'm a bit weary to stop the Memtest (now that
> it's in its 12th hour), but I will try that tomorrow morning after I let
> it run overnight. The memory's worked fine in that system since I built
> it 6 months ago (the problem is only three weeks). They also worked in
> the Dell E510 together. They're 'this, '
> (http://www.newegg.com/Product/Produc...4038)'this'
> (http://www.newegg.com/Product/Produc...82E16820146055), and
> 'this' (http://www.newegg.com/Product/Produc...82E16820145525)
> one as well as a 256MB stick from the old E510 (which is a Samsung dunno
> what specs). So technically it's not 3.25GB its 3,328 MB. If it's any of
> the sticks, I'm guessing its that 6-year-old Samsung one.
>
>

Don't forget that the memory test is the CPU reading and writing memory
and nothing much else is going on. During real use you have DMA,
interrupts and other stuff happening more or less at random (random is
not the right word but you know what I mean). Therefore timing issues
may come into the calculation that will not show up in a straight memory
test.

Timing changes could come from a new device, a hardware failure, updated
drivers etc.