memory diagnostic failure

The problem is usually Norton. The program might not "like" the CAS memory settings in the BIOS, or the speed of the FSB.

If you have done a regular memory diagnostic, and the computer exhibits no symptoms of a memory problem, such as lockups and crashes ... I'd ignore the program. On nearly every computer I've owned, at some point, Norton has specified a bad memory address during the diagnostic run. I've yet to find a single module that really had a problem. I've had perfectly good memory that the diagnostic program could not even "find"!

Especially significant is that the "bad" memory address changes after you boot the machine. If there was a true problem, the bad address would be static and it would show up during the POST as an error.

You might consider running other memory diagnostics programs in order to give you some peace of mind, but Norton is not to be trusted in this instance.

Toejam31

<font color=purple>My Rig:</font color=purple> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">http://www.anandtech.com/mysystemrig.html?rigid=6847</A>

What address was it? I ran Norton Diags (I dont normally bother with stuff like that but was trying to sort out another problem), it also said I had a bad address, and was always the same number, I'm at work now so I cant look, but I'd be interested to see if its the same address, What type of memory is it? Mines corsair pc 150 cas2, Please post back with the address, I wouldnt be suprised if its the same.


Next time you wave - use all your fingers

The POS Norton Memory checker can't deal with amounts of memory over 256MB (BTW I gather you installed 256 <font color=blue> MB </font color=blue> not KB ), generating the kind of error you saw - but the memory is perfectly good, you don't have a problem and just ignore the SW.

That info is buried somewhere in Norton support pages...


How terrible is wisdom when it brings no profit to the wise