explorer.exe crashes

[dexterp]

Indeed, I looked on the net for explorer.exe crashing .. and did not find anything until I've read this forum ..and True_Falcon talking about context menus ... so I went to regedit and found the DRIVE contect menu in there....

Well I've found that taking out the context menu for Alcool 120% corrected my problem ...

So What I'm saying is that, it maybe a problem like this but no necessarily Alcool 120% ... so check this out guys.. try to remember if you installed a software that maybe puts some context menus in explore.exe... and maybe you'll find your answer !

See ya .. thanks for reading me ...

Originally Posted by True_Falcon

Hey !! Skip all the others - this is the one that fixes the problem.

It's not SP2, cuz I have not installed it yet.

Certain badly behaved programs can do it and the one that did it to me is not likely the one that did it for others. For reference, for me it was a freeware zipper, TugZip. When I disabled its context menu, the problem was fixed. Tugzip still works just fine but I can't access it from right-clicks. No problem though - I just use the start menu.

[DaveH]

I had the same problem of Internet Explorer exiting spontaneously several times a day with a Exception number: c0000005 (access violation).
I tried all the above suggestions but none helped. Dr. Watson nearly always indicated nttdll.dll was at the top of the stack when the memory access error occurred.

I loaded Mozilla Firefox as my browser and have been using that for two weeks and have not had a single instance of it exiting spontaneously.

I still get the problem once every couple days, with another program exiting spontaneously, usually Eudora.exe, again with nttdll.dll at the top of the stack. But the frequency is low enough that it is easier to restart the program than to attempt further to fix it. I think there is some bug in nttdll.dll, or at least a way that when several programs are using the same .dll, one can do something that leaves it in a state where the next access can fail.

Looking at the Dr. Watson log I can see that the problem happened once every few days every since I bought this computer in March 2004, but it started happening much more often immediately after I installed XP SP2.

Dave