Richard said:
I just ran memtest86. I wasn't able to run the whole thing but in the
middle row (near the right), there were over 600 errors found. On the
bottom half of the screen, there were red lines of text listing which
test (#5) and failing address.
I also read that just one error means you have a problem, is that
right?
I don't need the smallest details, but does this mean my RAM is bad,
and would it explain why my browsers have been crashing?
Is there anything I can do about the problem? You can't fix RAM the
way you can run a chkdsk.
(I have 512M by the way).
Yes, 1 error is 1 error too many. You don't want any errors with
memtest86+ from memtest.org . Memtest86+ is actually an easy test
to pass, so if you're seeing errors, you're not in good shape. There
are actually other tests, such as Prime95, which are more sensitive
tests of proper computer function. But save Prime95 for later,
as memtest86+ is the test you want to conquer right now.
http://www.mersenne.org/freesoft/ (Version 25.9 is multithreaded)
If the number of errors in the entire pass is small (like a couple
errors), then sometimes increasing the DIMM voltage setting in the
BIOS helps. But that is typically an option on an enthusiast retail
motherboard, rather than something you find universally available
as an option.
Test #5 is where errors are typically detected. If the errors scroll
by very fast, that can mean an entire chip is bad (I had one like that).
If you have more than one stick of RAM, you can test the RAM one
stick at a time.
To work with RAM, you need an antistatic bag. That is to store
the RAM, between tests. You need to remove all power from the
PC, before adding or removing sticks of RAM. (I unplug the
power cord, as a way to remind myself there is no power present.)
If you test the sticks one at a time, you may get a better idea of
which one is bad.
For more specific help, it would be nice to know the make and model
of computer, or if you built the computer yourself, the make and
model of motherboard. The processor choice, and number, size, and
speed of RAM sticks, will add to the picture of your system.
You've done some good testing, trying to identify a software
problem. But now all your software tests are invalidated, as
it turns out you have bad RAM. Once the RAM is fixed, you're going to
have to rerun all the "problem" test cases, such as visiting
wunderground.com with Firefox.
Paul
