Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon
From: Drew Cooper [MSFT] (dcoop_at_online.microsoft.com)
Date: 12/16/03
- Next message: José Arturo: "Prevent Desktop Icon Change"
- Previous message: Torgeir Bakken (MVP): "Re: EFS problem"
- In reply to: John Corson: ""Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Next in thread: Lester Stiefel: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Reply: Lester Stiefel: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Reply: AKM: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 15 Dec 2003 17:36:14 -0800
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).
-- Drew Cooper [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. "John Corson" <john@corson.org> wrote in message news:ALoDb.10473$F22.1901@lakeread02... > 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--- > >
- Next message: José Arturo: "Prevent Desktop Icon Change"
- Previous message: Torgeir Bakken (MVP): "Re: EFS problem"
- In reply to: John Corson: ""Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Next in thread: Lester Stiefel: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Reply: Lester Stiefel: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Reply: AKM: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|