explorer.exe

  • Thread starter Thread starter Stephen Doyle
  • Start date Start date
S

Stephen Doyle

Whenever I try to open any mp3 file via my documents I get the error message
"explorer.exe has generated errors and will be closed by Windows. You will
need to restart the program."
The only changes to my system in the last few days were when I upgraded
winmx. I have since uninstalled winmx altogether (I hope), but the problem
persists.
Any ideas welcome.
Cheers
Stephen
 
Hi,

this could be a malfunctioning shell extension or any application,
that handles mp3 extensions and where its parent is the explorer.exe.
You should try a shell extension manager to check out whether this
can be solved with it or not. You shoud also check for malfunctioning
mp3 codecs from third party developers installed with some players
or codecpacks. For example, the Mediaplayer does not work well
with some plugins e.g codecs and filters

Try this: http://demosten.com/shellexman/ to remove any "corrupted"
extension managers...

Please Inform me, or better send me a screenshot of your solution or
the persisting problem...

Best Regards

Kerem Gümrükcü
 
this could be a malfunctioning shell extension or any application,
that handles mp3 extensions and where its parent is the explorer.exe.
You should try a shell extension manager to check out whether this
can be solved with it or not. You shoud also check for malfunctioning
mp3 codecs from third party developers installed with some players
or codecpacks. For example, the Mediaplayer does not work well
with some plugins e.g codecs and filters

Try this: http://demosten.com/shellexman/ to remove any "corrupted"
extension managers...

Please Inform me, or better send me a screenshot of your solution or
the persisting problem...

Best Regards

Kerem Gümrükcü
Click to expand...

Kerem,
I ran shellexman and got the error message "shellexman.exe has generated
errors and will be closed by Windows. You will need to restart the program."
Stephen
 
Hi Stephen,

try to run Windows in safe mode and then check
wich application makes your explorer.exe crash...

Ok, then try this: Close all instances of explorer.exe and let only the
taskmanager run.
The start the extension manager (you need the full path to the executable!)
drectly
from taskmanager. This should work (i hope)...

If not, use a Debugger (Dr. Watson or Windows Debugger to find the problem),
to see what PE files have been loaded with the explorer or your application.
Then it is more possible to find your problem...

Can you send a screenshot? (push "print-button" to make one and paste it
inside MS Paint or
whatever Graphics Application you want)


Best Regards

Kerem Gümrükcü
 
Kerem Gümrükcü said:
Hi Stephen,

try to run Windows in safe mode and then check
wich application makes your explorer.exe crash...

Ok, then try this: Close all instances of explorer.exe and let only the
taskmanager run.
The start the extension manager (you need the full path to the executable!)
drectly
from taskmanager. This should work (i hope)...

If not, use a Debugger (Dr. Watson or Windows Debugger to find the problem),
to see what PE files have been loaded with the explorer or your application.
Then it is more possible to find your problem...

Can you send a screenshot? (push "print-button" to make one and paste it
inside MS Paint or
whatever Graphics Application you want)


Best Regards

Kerem Gümrükcü
Click to expand...

When you say start the extension manager, do you mean explorer.exe from its
root directory D:\WINNT
Windows Debugger seemed to require 2 computers, is that right?
Stephen
 
Hi Stephen,
When you say start the extension manager, do you mean explorer.exe from
its
root directory D:\WINNT
Click to expand...

yes, this is the explorer.exe i mean.
Windows Debugger seemed to require 2 computers, is that right?
Click to expand...

This depends on the situation: If you want to debug user-mode data (this is
your concern)
then you can do this localy on ONE and your computer. If you want to debug
kernel-code
like drivers, then you must connect (there are some debuggers that can debug
kernel code
on a single machine, but you should not care, only if you are developing
hardware or drivers)
via serial line, usb, firewire or paralell-port to gain access to the target
(debugee) machine.

But you should set up a running Dr. Watson and catch FatalApp's with Dr.
Watson an then
examine the error dump (should be full dump of the crushed application).

Try my first solution (running Shell Manager without explorer) and then we
will see...

Best Regards

Kerem Gümrükcü
 
Back
Top