Windows Explorer crashing on right-click under x64 RTM

[H2SO4]

the explorer right click issue has happend since always and yes off a fresh format. as for the MMC issue only started occurring along with the explorer issue after this format and after the reliability patch update. before that it was only the right click issue. as for the dumps que folder only has one dumb from a long time ago and its produced multiple error reports so i don't believe its working as it should. weird thing is not even the event viewer is picking up the MMC errors or the explorer ones now... like the shell will restart itself randomly on right clicks and during that time if i proceed to go to event viewer then the MMC errors will be displayed. not sure what i could have possibly changed.

Sorry dude, I keep on being distracted by other issues, but I'm quite intrigued by this issue and I really do want to try to help - if I can.

Could you please try going through this alternative procedure to try to obtain some dumps:

http://www.sevenforums.com/general-...-crashing-when-deleting-files.html#post284148

It may also be useful if you start a separate thread. This one's technically dealing with another person's crashes, and they may not stem from the same root cause.

 

[Vincent]

I would have to agree with the previous posters that this issue seems to be related in some way to Firefox. I have done clean installs of Windows 7 RTM (x64) and Vista x64 on two separate computers and I have had the issue the OP described happen exactly. After removing Firefox from both systems, the issue has disappeared.

Out of curiosity, has anyone submitted a bug report to Firefox's bugzilla?

 

[Lucky098]

will this help>?? DLL-files.com - Download all your missing dll-files.

 

[Eddie48]

I would have to agree with the previous posters that this issue seems to be related in some way to Firefox. I have done clean installs of Windows 7 RTM (x64) and Vista x64 on two separate computers and I have had the issue the OP described happen exactly. After removing Firefox from both systems, the issue has disappeared.

Out of curiosity, has anyone submitted a bug report to Firefox's bugzilla?

I've had the same problem with windows explorer crashing, I'm using Windows 7 Home Premium. However, I have not installed Firefox at all with 7 HP 64bit. So for myself it doesn't seem to be related to Firefox. Maybe it's a ghost...

 

[Lucky098]

I would have to agree with the previous posters that this issue seems to be related in some way to Firefox. I have done clean installs of Windows 7 RTM (x64) and Vista x64 on two separate computers and I have had the issue the OP described happen exactly. After removing Firefox from both systems, the issue has disappeared.

Out of curiosity, has anyone submitted a bug report to Firefox's bugzilla?

I've had the same problem with windows explorer crashing, I'm using Windows 7 Home Premium. However, I have not installed Firefox at all with 7 HP 64bit. So for myself it doesn't seem to be related to Firefox. Maybe it's a ghost...

me too when I completed installed W7 HP x64 without install anything and it still crashing - seem to be the OS problems like ntdll.dll that what i looked up in my own system -- it could be the Win 7 itself that may have cause problems in dll files

 

[Vincent]

Lucky, when you reinstalled Windows 7, did you run all of the Windows updates before this happened, or did this occur from a clean install with no updates?

 

[Solace]

i believe all of these errors are probably linked together and that ur assumptions are correct and that my problem is strongly similar enough to this guys to not need the new thread. when one symptom occurs they ALL happen at the same time until it clears up.

 

[H2SO4]

i believe all of these errors are probably linked together and that ur assumptions are correct and that my problem is strongly similar enough to this guys to not need the new thread. when one symptom occurs they ALL happen at the same time until it clears up.

Up to you of course, but story-based crash troubleshooting is almost always pointless. Everything that starts off with "my grandma had that problem too, and then she uninstalled XYZ" is a well-meaning but misguided attempt to skip the "diagnosis" and go straight to the "solution" phase. Since nobody (yet) knows precisely what's causing your crashes, all proposed solutions are just wild stabs in the dark.

 

[Vincent]

Up to you of course, but story-based crash troubleshooting is almost always pointless. Everything that starts off with "my grandma had that problem too, and then she uninstalled XYZ" is a well-meaning but misguided attempt to skip the "diagnosis" and go straight to the "solution" phase. Since nobody (yet) knows precisely what's causing your crashes, all proposed solutions are just wild stabs in the dark.

I would challenge that. A big part of troubleshooting is pattern recognition. When the "story" is reasonably complete with the appropriate details (ex: when did it begin, what have you tried, when does it seem to occur, etc.), it can be possible to easily link it to an existing issue. While it may not determine the exact cause of the issue from a programming point of view, it does have a high likelihood of rectifying the issue - which is quite frankly the only thing we as end users care about.

 

[H2SO4]

Up to you of course, but story-based crash troubleshooting is almost always pointless. Everything that starts off with "my grandma had that problem too, and then she uninstalled XYZ" is a well-meaning but misguided attempt to skip the "diagnosis" and go straight to the "solution" phase. Since nobody (yet) knows precisely what's causing your crashes, all proposed solutions are just wild stabs in the dark.

I would challenge that. A big part of troubleshooting is pattern recognition. When the "story" is reasonably complete with the appropriate details (ex: when did it begin, what have you tried, when does it seem to occur, etc.), it can be possible to easily link it to an existing issue.

Sure, except the story is entirely incomplete in this instance. There are X posters, Y separate problem permutations, Z suggested "resolutions" - all superimposed on top of each other into a waveform which is quite inscrutable without some serious "social fourier analysis"

While it may not determine the exact cause of the issue from a programming point of view, it does have a high likelihood of rectifying the issue - which is quite frankly the only thing we as end users care about.

I think what you're advocating is the trial-and-error approach. Nothing wrong with that, under many circumstances. However, the more complex the problem, and the greater the number of moving parts, the more difficult it becomes to guess the correct answer based on the "story so far", and the more impractical it is to "shotgun" (obliterate) all possible problem causes.

I sincerely wish you luck with your chosen approach.

 

[Lucky098]

Ive reformatted and reinstalled and it working prefect - no crashing after I changed the cable from DVI to HDMI by plugged DVI-I to VGA that work prefect -- boot up is 1024x720 with Win 7 own logo (nice look) and then 1920x1080 when Log-on screen or Welcome come up (I set LCD tv as PC instead of Just Scan) that work fine.

 

[chrisk1]

On my machine, it wasn't Firefox 3.5.3, but CCleaner. CCleaner was cleaning explorer files. If you use CCleaner, make sure it isn't cleaning explorer files. Since this change, neither of my Windows 7 Pro (64bit) machines have had an explorer crash.

 

[Lucky098]

I dont use CCleaner as Im still waiting for new version of Tuneup as I used the older version of 2009 that dont support Win 7 and wait for the 2010 version is coming - it good one and safe to clean, it give you to choose which one to aviod cleaning my mistake also plenty of features - the Tuneup 2009 only work in Xp and Vista and newer version 2010 will add for Windows 7 soon. Anyway have to careful with Explorer.exe and aviod cleaning this folder that may cause crashing as well.

 

[Eddie48]

Windows explorer stops responding...

I just installed Windows 7 HP 32 bit on an older computer, it seems after I installed Adobe Flash player and Adobe Reader 9 I got the same problems with right click and then explorer not responding. I did a system restore from the Windows 7 HP DVD to a few hours before I installed the Adobe flash player. Now I don't get the right click explorer not responding error. On my other computer that has the 64 bit version of Windows 7 Home Premium I still get the same error but not very often.

 

[TechN9Ne1730]

The problem is now fixed for me. It was one of two things. It either had to be the latest windows updates, or something to do with nvidia. I just got my 4890 yesterday and removed all the nvidia apps and drivers and now I accidentally clicked in my recycle bin and it didnt crash!

EDIT: Spoke to soon sort of. I can now right click in the recycle bin window, but if i click on just the desktop icon, explorer crashes.

 

[Dazeon]

I've been there before TechN9Ne1730...

Gotta love that false sense of security! Yay, it's fixed, OH.

Maybe it is a Windows Update, would explain a lot.

 

[Lucky098]

that what I wonder about Windows update or even with nivdia driver for motherboard or graphic card that may have cause problems - I wait until next graphic card or motherboard driver version when it release cos both were older date before W7 was release so that may have cause Explorer.exe crashing... before I install these - it was ok but after install it was crashing so I use old version of Nvidia motherboard driver that seem ok - the new version seem to be buggy, I used the Nvidia 15.25 version instead of new 15.51

 

[Garett]

For me, the immediate explorer crashes I was receiving went away after getting rid of the newest version of Acronis True Image Home's backup context menu button. There was no setting in the program to remove it, I had to look up what registry keys to delete. I had also previously removed the Nvidia Control Panel's context button through the settings, but with no relief. So, the only extra context button that is left is Microsoft's Security Essentials. We'll see if I get any more crashes in the next day or so.

 

[BenjaWiz]

Explorer keeps crashing asking to restart it I am running Win7 Ultimate x64 retail fresh install.

Faulting application name: explorer.exe, version: 6.1.7600.16404, time stamp: 0x4a765771
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b
Exception code: 0xc000041d
Fault offset: 0x0000000000051da0
Faulting process id: 0x7a8
Faulting application start time: 0x01ca5ed20c1542cc
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 58185790-cac5-11de-a4b6-0080c5121221

 

[TomasWin7]

Benja,

Sounds like you got this too:

http://www.sevenforums.com/crashes-...click-desktop-causing-explorer-exe-crash.html

The dreaded ntdll.dll

lolol