explorer.exe randomly crashing!

[cavekas]

Hi everyone!

The problem is, that randomly there is a popup that says explorer.exe encountered a problem and needs to close and blablabla... So explore shuts down, my desktop is wiped out, but with any luck it lasts for 10-20 secs. If not, I have to manually start explorer. It also terminated any programs running naturally.

Could any of you say what the problem could be, I sent an error report but Microsoft has got no idea!!!

This is the error text:

Faulting application explorer.exe, version 6.0.2800.1221, faulting module ntdll.dll, version 5.1.2600.1217, fault address 0x00007ec4.
Event ID: 1002

And there is another one, with event id 1000, other parameters seem to be tha same...

So, can u say whats going on???

[snowmonkey]

cavekas, If I had problem with explorer.exe and ntdll.dll, I wouldn't wait for some other issue to make the matter worst,,, Of course you don't expect Microsoft to tell you that your operating system is hosed and you have to reinstall it,, but I do,, your sure bet would be saving the important files and reinstall XP from scratch (just a friendly advise)

cheers

[Play_The_0dds]

windows media player 9, you have it, or had it and removed it. it is responsible, it is garbage, it is evil. follow snowmonkey's advice and do a fresh install of xp and do not reload wmp9

[cavekas]

So u say there is no other way than just to make a fresh install? Could this problem be associated with anything else to, I mean this problem hasnt occured for a while now...well I'll wait and see I guess

[TAB]

cavekas

known_criminal and snowmonkey are giving you good advice, but you might try looking for a virus first, since your sympton is similar to those caused by some of the recent virus outbreaks like lovesan and blaster. The following website has a good program for free which will scan your computer and also remove the virus if you have it. Just look for "download Stinger." Otherwise, the other guys have already given you your only recourse.

http://us.mcafee.com/virusInfo/defau...al/Stinger.asp

Regards,

TAB

[mrgeeky]

Reinstalling is for when you have a serious issue that cannot be resolved. Your issue can. There are quite a few issues that could be causing you problem. use the error from event viewer and google the issue you will see many people have had this issue and many people have reformatted or reinstalled only to have the same problem when they reinstall. What a waste of time.
One such cause for this issue maybe, go through all your installed programs and check the help menu on anything your not sure of to see if it was originally created for win 98, 2000 etc, and not for XP. If this is the case you may have compatiblity issues.
If so, go to start, all programs, etc. Right click on each program and check properties. Check click on compatibility, compatibilty mode (from memory) and choose either win2000, win 98 or Win 95 if thats what the program was originally created for. Any one will do.
Then click on disable visual themes ( I think it is).
I have used this to resolve a similar issue.

You could also use MSconfig to selectivly disable etc etc, till you find out the cause.
Lots of reasons, lots of diff fixes, reinstalling isnt the answer.
good luck.

[mrgeeky]

all those having troubles with Faulting Application Explorer.exe, version 6.0.2800.1106, faulting module ntdll.dll [fault addresses WILL VARY]--after much trouble and examination, we offer the following fix which Microsoft should provide--and have not.

The trouble lies within -->> ntdll.dll 6.0.2800.1106 <<--which is an absolute Turkey. Previous versions of this Mod worked fine, it is changed and advanced during the routine MS Critical Update Process, in my case installing the Update Rollup 1 for XP [K826939]. Other updates change this dll as well, forming the above [.1106] which locks and crashes.

If you remove the offending Update--the previous version will then be restored.

Then all will be fine, you think. Sounds simple. The problem is that Microsoft also created an incredible design fault--producing several Updates that MAY or MAY NOT be seen in the Add/Remove Programs. Swell. This is a problem for many of their Updates, feel free to complain. For this particular case you are getting rid of -->> ntdll.dll 6.0.2800.1106 <<--, so first MAKE A SYSTEM RESTORE POINT, and then try this:

1. Begin with a Registry Search [Regedit] for the OFFENDING UPDATE. You will find it. Expand until you have located the STRING [window on right] that holds the DELETE instruction. Mousey Highlight and copy this string. Close your Regedit;

2. Go to RUN--paste/insert your STRING--and hit OKAY [go]. This will bring up the UNINSTALL FUNCTION that you could not find in your Add/Remove Programs;

3. During UNINSTALL, you will need two items, (A) your XP Disc, and (B) the location of the ntdll.dll installation mod to instruct the process toward completion. Ntdll is located in your Sys32, and is not that difficult to find, simply browse, tap, continue. [If you are a newbie remember, you can always find the Ntdll by using the General Search function. Make a note of what file that is located in, then go back to BROWSE.] Follow the UNINSTALL INSTRUCTIONS, and you are nearly home free;

4. During the UNINSTALL, you might get warning messages like "...WINDOWS May Not Work Properly If Removal..." Etc. I did NOT get this, but an IT Professional buddy of mine did. Ignore these. Keep moving forward...

5. When the process completes, REBOOT. For extra measure, we shutdown completely, and then bring the system back.

Now test your OS. Smile. This has worked. Again, the problem is -->> ntdll.dll 6.0.2800.1106 <<--, which is some serious damn GiGo [Garbage In, Garbage Out.] If you use previous versions of the above dll, you shouldn't have any troubles.

For those who had this problem created by installing Critical Update 826939, Microsoft promises that when you remove this update rollup--the previous critical updates that this replaced will suddenly be restored in the Add/Remove Programs. Not true, at least on two systems, which typically run 100 percent. We're working on that, as well as letting Microsoft know how we feel about these issues...

In case you had our trouble, it's amusing to read the uninstall portion of this hotfix. http://support.microsoft.com/default...b;en-us;815021