Does this mean my ram is going bad?

Aatrex · Post by **Aatrex** » Wed Jun 29, 2005 7:37 am

I get these semi often...every few days or so. Isn't it displaying a hex address or something? Not quite sure what's causing it but my first instinct is that my ram is dying.

Aatrex · Post by **Aatrex** » Wed Jun 29, 2005 7:38 am

I also get some that say the memory could not be "read". Instead of the memory could not be "written".

Tikker · Post by **Tikker** » Wed Jun 29, 2005 9:42 am

I used to get that error when I had my CPU overclocked too high

clocked it down a bit, error went away

Post by **Gidan** » Wed Jun 29, 2005 9:58 am

Its rare that the message you have would actually indicate bad physical memory. My guess is the While the program you were running believed that memory location still belonged to it, windows had realocated it to something else. Ther are many accounts of this happening all over the internet, best to just google it and find the one that best matches your situation.