Unsolved

This post is more than 5 years old

Closed

10678

October 12th, 2001 01:00

memory could not be read

When Windows 2000 starts up, i'm greeted with an iexplore.exe message box with the following error message:

the instruction at "0x77fce69a" referenced memory at "0x00000000". The memory could not be

"read"

Click OK to terminate
Click cancel to debug


I've applied Windows 2000 sp2 and flashed the BIOS but still no luck. Any ideas?


1 Rookie

 • 

90 Posts

October 13th, 2001 14:00

davidealex,

Have you recently installed or updated the version of your Internet Explorer program as the iexplore.exe error would be related to that application?
I have been able to find many similar errors in the Microsoft Knowledge Base, but none that seem to be identical to the error that you listed.











October 15th, 2001 02:00

I installed AOL 6.0 a month or two ago, but this started recently. I'll uninstall AOL 6 and see what happens.
-David

DELL-Suzanne wrote:
- davidealex,
-
- Have you recently installed or updated the version
- of your Internet Explorer program as the
- iexplore.exe error would be related to that
- application?
- I have been able to find many similar errors in the
- Microsoft Knowledge Base, but none that seem to be
- identical to the error that you listed.
-
-
-
-
-
-
























1 Message

October 15th, 2001 11:00

My wife's CPxH does this, although it is an explore.exe
(shell) related error..(I think)

the same "memory could not be read", "debug or cancel"
type thing...
annoying but not fatal.

I was afraid it *might* be bad RAM, although I haven't done any touble-shooting yet.

She is running W2K pro, with the service pack,
and AOL's "special" version 5 specifically for W2K.

It might have something to do also with Mcafee virus
scanner she runs...the problem seems to not happen
if you deactivate the "on-all-the-time" background stupid scanner thing...




14 Posts

November 17th, 2004 12:00

I have this same problem.

14 Posts

November 18th, 2004 08:00

I think that this will come because I have too many open Handles, Threads and Processes.

0 events found

No Events found!

Top