Donate SIGN UP

"Memory could not be read"

Avatar Image
michaellam | 14:43 Sun 12th Dec 2004 | Technology
2 Answers
An error in windows explorer keeps coming up saying: Instruction at "0x5ad71531" referenced memory at "0x000340d0". The memory could not be read. Does anyone know why this happens?
Gravatar

Answers

1 to 2 of 2rss feed

Best Answer

No best answer has yet been selected by michaellam. Once a best answer has been selected, it will be shown here.

For more on marking an answer as the "Best Answer", please visit our FAQ.
A corrupt program at a guess.  If you have acces to a system that is the same, compare the file sizes and date stamps of explorer.exe or of the program that falls over.
This is a bit of a chestnut

In my case it was a faulty dimm
I've seen it with faulty mb and with (I assume) corrupt DLLs
If it's just one prog Start by uninstall/reinstall

My guess is that it's intermittent because it's something stopping the end of memory being used ... normal useage is ok ... it's just when you push the system by opening more than usual resources.

1 to 2 of 2rss feed

Do you know the answer?

"Memory could not be read"

Answer Question >>