"Memory Could Not Be Written" - Explorer.exe & Winlogon

[John Corson]

At random times when trying to open a folder (directory),
I receive the following popup: "Application Error: The
instruction at "0x77f57ec4" referenced memory
at "0x00000067". The memory could not be "written".
A similar popup appears reading: "Application Error : The
exception unknown software exception (0xc015000f) occurred
in the application at location 0x77f6fca7."

When going to the event properties in the Administrative
Tools, I see under application events that the following
notation appears: "The shell stopped unexpectedly and
explorer.exe was restarted." It is a winlogon event with
event number 1002.

When this error occurs I have to click as many as three
popup notices. Following that, all icons on the desktop
disappear for a few seconds, the screen is refreshed,
icons re-appear and most applications running in the
background (anti-virus, etc) do not appear in the toolbar
until logging off and back on.

I have gone back to several different points in system
restore, uninstalled various software that I thought could
be the cultrate, etc. I am suspecting one major area that
I haven't tried -- Changing out memory. I recently
upgraded to ABIT KD-7 RAID m/b with Athlon XP2700+ CPU;
2048 mb DDR PC2700 ECC non buffered RAM. Would adding an
extra wait from the cycle between memory and CPU help?
I.e using Registered ECC RAM? Before I go to the added
EXPENSE of getting registered RAM I would like to have
confirmation.

I have tried swapping out memory modules, going down to
1024, etc. Currently I have 4 "sticks" of 512 each. One
person suggested having only 1 stick, no matter whether it
is buffered, registered, non buffered, non parity, etc.
He says to never use more than 1 module, yet I have always
used more than one on different systems and have never had
this issue.

Please help!

---John Corson---

 

[Drew Cooper [MSFT]]

It's hard to say what is causing the problem. Lots of apps can take
Explorer down. Or it might actually be an Explorer bug. The problem is
probably not your RAM, though.

Your best bet at a fix is to file the Watson report (that "report this to
Microsoft" thing that should pop up after Explorer restarts).

 

[Lester Stiefel]

It's hard to say what is causing the problem. Lots of apps can take
Explorer down. Or it might actually be an Explorer bug. The problem is
probably not your RAM, though.

Your best bet at a fix is to file the Watson report (that "report this to
Microsoft" thing that should pop up after Explorer restarts).

What Applications are installed on the system that this
happens on. Custom CD Burn software can lead to the "non
writable RAM " issue. Also some graphics editors, such as
autocad can cause it.

--

Lester Stiefel

Try http://www.familyradio.com/index.html

You might just like it!!

 

[AKM]

What does microsoft do with those reports? I've filed over a hundred of
them on this problem. So many people complain of it, so where can we
look to find progress?

 

[9806]

All memory reference errors come from either Page file or Physica
memory (RAM). The page file could be corrupted due to the hard driv
having bad sectors or the RAM has a bad chip. Both very probable bu
more likely your be the RAM in this case. Get the part fixed unde
warranty if possible or replace the part

980

 

[Spinner]

I had the same problem.
It turned out to be Spybot search and destroy that was causing the problem.
I turned off the immmunize option and the problem stopped, turned it back on
and the problem reappeared, so left it off and have not had a problem since.

 

[av_3000]

I've been having the exact same problem as you John, down to a tee. Same
messages, same annoyances. It doesn't seem to affect anything but is
damn annoying.

So if it's a mutual problem, maybe it's not hardware?

I'm going to see if turning off immunisation in Spybot makes a
difference.


av_3000

 

[9806]

These memory problems are very annoying "the memory could not be read"
or "the memory could not be written". How to rid of them is a bit of
trial and error some say it's hardware but it turns out to be a
software problem. What happen is that the program collides with another
program using the same memory line. This is a dud fault found in many
apps. The best way about fixing this problem is to update your software
or if the problem is in windows then run the installation over it as an
upgrade this should solve most problems. If the problem was based on
hardware you would have seen a blue screen by now.


9806