Windows Explorer dies regularly

[Guest]

Every so often I get an error that Windows Explorer has died. I have all the
latest updates and SP2 installed on XP Pro but I can't get it to stop dying.
The error in my application event log is as follows:

Source: Application Error
Category: (100)
Event ID: 1000
Type: Error
User: N/A
"
Faulting application EXPLORER.EXE, version 6.0.2900.2180, faulting module
unknown, version 0.0.0.0, fault address 0x02835ed5.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"

Any ideas would be welcomed.

 

[Malke]

Every so often I get an error that Windows Explorer has died. I have
all the latest updates and SP2 installed on XP Pro but I can't get it
to stop dying. The error in my application event log is as follows:

Source: Application Error
Category: (100)
Event ID: 1000
Type: Error
User: N/A
"
Faulting application EXPLORER.EXE, version 6.0.2900.2180, faulting
module unknown, version 0.0.0.0, fault address 0x02835ed5.

Unfortunately, we don't have enough information to give you focused
help. For instance, what exactly does "Windows Explorer has died" mean?
Aside from getting the error message, what happens? Do you lose the
graphical user interface only or does your computer reboot? Googling
for "Event ID: 1000 Explorer.exe" brings up a lot of links, but all
with different causes. We need to narrow down what happened and what is
going on.

The First Question Of Troubleshooting: what changed between the time
things worked and the time they didn't?

The Second Question of Windows Troubleshooting: what is the
malware/virus status of the machine? If you think it is clean, what
programs (and versions) did you use to determine this?

Malke

 

[Guest]

The problem is that I get an error that Windows Explorer has closed. I then
get prompted to send an error report (which I normally do) and then windows
explorer restarts. All of my other programs continue to run as normal but
the explorer program restarts, my start bar and task bar are restarted and
any explorer windows that are open are closed.

I have had this problem for quite a long time. I don't remember when it
started.

I currently have F-Secure Anti-Virus installed.

 

[Malke]

The problem is that I get an error that Windows Explorer has closed.
I then get prompted to send an error report (which I normally do) and
then windows
explorer restarts. All of my other programs continue to run as normal
but the explorer program restarts, my start bar and task bar are
restarted and any explorer windows that are open are closed.

I have had this problem for quite a long time. I don't remember when
it started.

I currently have F-Secure Anti-Virus installed.

It's always hard to diagnose problems that have been around for a long
time and are random. In your subject line you say that Explorer "dies
regularly" but in the body of your first post, you say this happens
"every so often". Can you identify what is running/you are doing when
this happens?

Here are some general suggestions to help narrow down the focus. As
always, in troubleshooting you must only make one change at a time and
test after each change before going onto the next thing.

A. First, make sure the computer is malware-free.
http://www.elephantboycomputers.com/page2.html#Removing_Malware

B. When it next happens, see if you can figure out if something you were
doing was different. Check Task Manager to see what is running. See if
this happens only when you do [some action].

C. Try clean-boot troubleshooting to see if something you are running is
causing the issue:

Clean boot in Windows XP - http://support.microsoft.com/kb/310353

Clean-boot advanced troubleshooting in Windows XP -
http://support.microsoft.com/kb/316434

How to Troubleshoot By Using the Msconfig Utility in Windows XP -
http://support.microsoft.com/?id=310560

D. Update the drivers for your hardware. Never get drivers from Windows
Update. Get them from:

1. The device mftr.'s website; OR
2. The motherboard mftr.'s website if hardware is onboard; OR
3. The OEM's website for your specific machine if you have an OEM
computer (HP, Dell, Sony, etc.).

Read the installation instructions on the website where you get the
drivers.

To find out what hardware is in your computer:

1. Read any documentation you got when you bought the computer.
2. If the computer is OEM, go to the OEM's website for your specific
model machine and look at the specs (you'll be there to get the drivers
anyway)
3. Download, install and run a free system inventory program like Belarc
Advisor. The older Aida32 is good for this, too.

http://www.belarc.com/free_download.html - Belarc Advisor
http://www.aumha.org/free.htm - Aida32 (hosted on Jim Eshelman's site)

E. Possibly this is caused by a hardware problem such as overheating or
a failing video card or memory module. Here are some general hardware
troubleshooting steps:
http://www.elephantboycomputers.com/page2.html#Hardware_Troubleshooting

Malke

 

[gls858]

Every so often I get an error that Windows Explorer has died. I have all the
latest updates and SP2 installed on XP Pro but I can't get it to stop dying.
The error in my application event log is as follows:

Source: Application Error
Category: (100)
Event ID: 1000
Type: Error
User: N/A
"
Faulting application EXPLORER.EXE, version 6.0.2900.2180, faulting module
unknown, version 0.0.0.0, fault address 0x02835ed5.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"

Any ideas would be welcomed.

There was a problem with on of MS patches causing IE to crash.
Here's an article. Not sure if this is relevant in your case.

http://news.zdnet.com/2100-1009_22-6106039.html

gls858

 

[Guest]

I didn't specify the dates and times that it dies, but it happens 2 or 3
times each day.

The error I get can be when I'm running any program so it doesn't seem
related to browsing or any particular program.

I get the message:

The instruction “0x03eb5ed5†referenced memeroy at “0x03eb5ed5â€. The memory
could not be “writtenâ€.

Click on OK to terminate the program
Click on CANCEL to debug the program.

Then I get

Data Execution Prevention – Microsoft Windows
To help protect your computer, Windows has closed this program.
Name: Windows Explorer
Publisher: Microsoft Corporation.

Close Message

Then I get “Do you want to send a report of this to Microsoft?†and I select
Send.

Are there debug or trace files anywhere that would contains information
related to the problem that I could look at or pass on to MS?

The problem is that I get an error that Windows Explorer has closed.
I then get prompted to send an error report (which I normally do) and
then windows
explorer restarts. All of my other programs continue to run as normal
but the explorer program restarts, my start bar and task bar are
restarted and any explorer windows that are open are closed.

I have had this problem for quite a long time. I don't remember when
it started.

I currently have F-Secure Anti-Virus installed.

It's always hard to diagnose problems that have been around for a long
time and are random. In your subject line you say that Explorer "dies
regularly" but in the body of your first post, you say this happens
"every so often". Can you identify what is running/you are doing when
this happens?

Here are some general suggestions to help narrow down the focus. As
always, in troubleshooting you must only make one change at a time and
test after each change before going onto the next thing.

A. First, make sure the computer is malware-free.
http://www.elephantboycomputers.com/page2.html#Removing_Malware

B. When it next happens, see if you can figure out if something you were
doing was different. Check Task Manager to see what is running. See if
this happens only when you do [some action].

C. Try clean-boot troubleshooting to see if something you are running is
causing the issue:

Clean boot in Windows XP - http://support.microsoft.com/kb/310353

Clean-boot advanced troubleshooting in Windows XP -
http://support.microsoft.com/kb/316434

How to Troubleshoot By Using the Msconfig Utility in Windows XP -
http://support.microsoft.com/?id=310560

D. Update the drivers for your hardware. Never get drivers from Windows
Update. Get them from:

1. The device mftr.'s website; OR
2. The motherboard mftr.'s website if hardware is onboard; OR
3. The OEM's website for your specific machine if you have an OEM
computer (HP, Dell, Sony, etc.).

Read the installation instructions on the website where you get the
drivers.

To find out what hardware is in your computer:

1. Read any documentation you got when you bought the computer.
2. If the computer is OEM, go to the OEM's website for your specific
model machine and look at the specs (you'll be there to get the drivers
anyway)
3. Download, install and run a free system inventory program like Belarc
Advisor. The older Aida32 is good for this, too.

http://www.belarc.com/free_download.html - Belarc Advisor
http://www.aumha.org/free.htm - Aida32 (hosted on Jim Eshelman's site)

E. Possibly this is caused by a hardware problem such as overheating or
a failing video card or memory module. Here are some general hardware
troubleshooting steps:
http://www.elephantboycomputers.com/page2.html#Hardware_Troubleshooting

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

 

[Malke]

I didn't specify the dates and times that it dies, but it happens 2 or
3 times each day.

The error I get can be when I'm running any program so it doesn't seem
related to browsing or any particular program.

I get the message:

The instruction “0x03eb5ed5†referenced memeroy at “0x03eb5ed5â€. The
memory could not be “writtenâ€.

Click on OK to terminate the program
Click on CANCEL to debug the program.

Then I get

Data Execution Prevention – Microsoft Windows
To help protect your computer, Windows has closed this program.
Name: Windows Explorer
Publisher: Microsoft Corporation.

Here's information about DEP:
http://support.microsoft.com/kb/875351/

Based on the information in your latest post, I would go through the
troubleshooting steps I already gave you. I would start with the
hardware troubleshooting and run Memtest86+ first. There is no "push
one button" to find out what is going on. Troubleshooting is deduction
usually by process of elimination in a methodical way.

If the procedures look too complex - and there is no shame in admitting
this isn't your cup of tea - take the machine to a professional
computer repair shop (not your local version of BigStoreUSA).

Malke