Memory Region Not Read
25 Apr 2005 14:57:41 UTC
Topic 189041
(moderation:
When running E@H, I frequently get the following windows application error: "The instruction at '0x6910f2e8'referenced memory at '0x0000004c'. The memory could not be 'read'.
Any idea what would be causing this?
Memory Region Not Read
)
First guess is bad/broken memory or overclocked cpu/memory.
Also it could be broken Windows.
Check it with memtest86+.
Hence some claim that they have good machine, and the application is broken.
The address 0x6910f2e8 is way
)
The address 0x6910f2e8 is way out of the memory segment of the app, this is probably a broken system lib (graphics driver? does this occur when the graphics should be shown?). If it always occurs on the same memory address (in the _process_ address space) I would consider it rather unlikely to be a hardware defect.
BM
BM