Win7 "Windows Explorer has stopped working" Problem

Found it!

http://www.nirsoft.net/utils/shexview.html

Remove everything from there, except maybe you AV. Then see how it is on the reboot.

On x64 systems, ShellExView now always shows the shell extensions for x64 applications, even on the 32-bit version of ShellExView. If you want to get the shell extensions list for 32-bit applications, use ShellExView with /wow64 command-line option.
 
Last edited:
Already used this Shell software but still think Windows 7 alone own OS may have some bugs in some dll files that need to fix the problems that same in Vista SP2 when it was released June 2009 but fixed it few months later, Microsoft still working to release new hotfix patch or maybe SP1 to fix the problems. I still think it more likely to be Windows 7 OS that has some bugs in some files like dll or exe so have to wait until the hotfix patch is release
 
Getting the error with windows live messenger at startup and 64bit internet explorer (moved onto chrome now) 32bit internet explorer never had any problems though i dont think
 
Well I still haven't managed to fix this, every time it comes up it has the same Additional Info:

Problem Event Name: APPCRASH
Application Name: Explorer.EXE
Application Version: 6.1.7600.16404
Application Timestamp: 4a765771
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5be02b
Exception Code: c000041d
Exception Offset: 000000000003202d
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: ad4f
Additional Information 2: ad4ff2910f4e212dac59bdc5b4a9838c
Additional Information 3: 2abd
Additional Information 4: 2abd8ab19cf237282e603bae0ac4594a


Its getting really annoying now... I hope Microsoft do something soon.
 
Yes people included myself has the problems and yes Microsoft can see the numbers of problems they recieved and then fix the update hotfix patch so dont know when it come out - I looked up the NTdll.dll date way back to July 2009 that may the older version and update the new version to fix the problem so maybe in few weeks or even months.. I still think it more likely to be Windows 7 OS itself with lots of bugs with some crashing. I have the same problems so have to wait for the update fix patch to be relelase.
 
Well I still haven't managed to fix this, every time it comes up it has the same Additional Info:

Problem Event Name: APPCRASH
Application Name: Explorer.EXE
Application Version: 6.1.7600.16404
Application Timestamp: 4a765771
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5be02b
Exception Code: c000041d
Exception Offset: 000000000003202d
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: ad4f
Additional Information 2: ad4ff2910f4e212dac59bdc5b4a9838c
Additional Information 3: 2abd
Additional Information 4: 2abd8ab19cf237282e603bae0ac4594a


Its getting really annoying now... I hope Microsoft do something soon.

Yes Im the same as you as annoying when the crashing message came up and the i log off and then back on.. it still bugs in W7 itself
 
when I removed Logitech version 4.80 for my MX Rev mouse and then reboot and then see to be ok but i will keep press right button and see if error message come up or not - let u know

it may have Windows 7 itself or even any driver with older date before Win 7 release cos the mouse driver I used was May 2009 that much older so Ive removed it and wait for next one. I checked numbers of drivers for hardwares which are wee bit older that may have caused problems with ntdl.dll so keep check until MS fix the problems when update is avial.
 
it seem to be working fine after i removed the driver of Logitech SetPoint 4.80 for my MX mouse -- it didnt any error message as I kept right-click quite a lots. Maybe some drivers has out of date and crashed with Windows 7 dll but Im still watch for any error message to come up - if it still work fine then it may cause my older driver for mouse, keyboard or anything else you already installed with older version and out of date. If you do the same as I did then keep watch for any message to pop up -- it still unanswer what is cause of Explorer.exe crashing as Microsoft still working on it.
 
I spend wee bit time to see what it cause so think it would be software in Windows 7 bugs during update at the begin same as Vista SP2 when it was released in June 2009 and fixed few weeks later that what I think it may have caused by some of update for W7 that mess with ntdll.dll which Explorer.exe stop working and restart - have to wait for next update hotfix patch to fix it. Look like one of update that may have put wrong one for Windows 7.. it happen to be mistake by MS team to put update after it was released on 22nd Oct.
 
Been getting this crash myself but according to my logs it's ffdshow that's causing it. Will remove and re-install my codecs and see what happens. Never had any of this trouble before I installed Pro!
 
Haven't heard of any fix for it, but it turned out that my explorer crashes were caused by my printer - I couldn't find a driver for it so found a 'similar' one and used that; this put another option in my right-click menu. As soon as I removed the printer driver the extra option in right-click disappeared and the crashes stopped.

Might be worth having a look at any programs you have installed which add to the right-click menu, I've seen a few cases of this causing the explorer crashes in other forums.
 
First off make sure youve updated your OS, secondly make sure youve recently went through anti-Malware scans (if you dont currently have one then you can downlaod Malware Bytessimply by typing it into google) If that doesnt work then try Trend Housecall again by typing it into google)
If that again doesnt work then damn :D
 
I just found out that it was Firefox 3.5 with private browsing mode that left enable that cause crashing so Ive switched off and then it seem working fine also Ive deleted one line in registry editor (SQM Client) -- I spend over an hour with lots of right-click mouse button = no crashing. either you switch off private browsing mode or go back to 3.0.15 that would stop crashing.
 
Back
Top Bottom