Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon
From: Lester Stiefel (les7342_at_verizon.net)
Date: 12/16/03
- Next message: Jupiter Jones [MVP]: "Re: Ending pop-ups"
- Previous message: jane: "asp.net"
- In reply to: Drew Cooper [MSFT]: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Next in thread: John Corson: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Reply: John Corson: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 16 Dec 2003 01:28:48 -0500 To: "Drew Cooper [MSFT]" <dcoop@online.microsoft.com>
Drew Cooper [MSFT] wrote:
> 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!! ----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==---- http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups ---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---
- Next message: Jupiter Jones [MVP]: "Re: Ending pop-ups"
- Previous message: jane: "asp.net"
- In reply to: Drew Cooper [MSFT]: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Next in thread: John Corson: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Reply: John Corson: "Re: "Memory Could Not Be Written" - Explorer.exe & Winlogon"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
