Right Click = Explorer Not Responding

[H2SO4]

here is mine, thanks in advance.

Your crash is uncannily similar to Nikolay's. Check out the post I just wrote regarding a way to try to obtain a more informative dump.

 

[Nikolay]

There you go:

Heap metadata is corrupted. The bad data causes a crash when an attempt is made to validate a particular heap region. However, an indeterminate amount of time has already passed between the original corruption of the data and the eventual crash.

There's a way to make the OS apply greater scrutiny to the heap operations within a given process. That can lead to catching the heap corruptor at the time it does its business, as opposed to later on when its too late and the evidence is obliterated. The procedure:

1) On an elevated (run as admin) CMD prompt, from the directory where you installed the debugging tools: gflags /p /enable Explorer.exe /full

2) Reboot or restart Explorer (same effect).

3) Once again, run the "cscript adplus.vbs...." command from before.

4) Reproduce the Explorer crash again.

5) Find the new DMP file, hopefully the small one with "2nd_chance" in its name, and upload just that for analysis.

I can't reproduce the problem after that, but when I close cdb.exe, I can.

Also, explorer seems to be using a lot of memory now then it used to after these commands.

 

[Panic]

I had to do lots and lots of right clicking on stuff opening folders right clicking on files etc etc in order to crash this time from some reason. but finally it did, i dunno if its worth a mention but after it crashes i cant right click at all unless i keep leting explorer restart and keep right clicking eventually it wont crash for a while but it take a long long time of restarting explorer and right clicking.

 

[Panic]

right clicking eventually lead to a bsod the other day(maybe not related to the right click problem) although maybe that would be useful, here is that file aswell

 

[H2SO4]

right clicking eventually lead to a bsod the other day(maybe not related to the right click problem) although maybe that would be useful, here is that file aswell

dadder.sys - your "death adder" Razer mouse driver.

I have absolutely no reason to link your BSOD to the Explorer heap crashes. It was the clicking, rather than the fact that you were clicking in Explorer that triggered the bug in dadder.sys which caused the BSOD.

 

[Panic]

yea, ive since uninstalled the driver and have been using the native mouse driver. so any idea what going on with explorer?

 

[H2SO4]

yea, ive since uninstalled the driver and have been using the native mouse driver. so any idea what going on with explorer?

This applies to your situation as well - your crashes are identical:

http://www.sevenforums.com/crashes-...orer-has-stopped-responding-2.html#post342287

(I can't yet be certain whether it applies to Nikolay until I see one of his dumps after running the "gflags" command.)

 

[Nikolay]

I ended up doing a clean install. Explorer was taking up a lot of memory and the sluggish performance was unbearable. Thank you so much for the help H2S04, you deserve a lotta rep.

 

[sleepylynx]

I've been experiencing the Right-click Windows Explorer errors also. I figured I would post mine and see if you find anything different in my crash. I appreciate all the advice you are giving H2SO4. Great stuff. Thanks.

RapidShare: 1-CLICK Web hosting - Easy Filehosting

 

[Xplaced]

I am having the same problem. It does it more on my work PC than my home PC. I use Razer mice on both computers and Windows auto-updated the mouse driver to the Razer one for both (though their software isn't installed). Maybe I should try installing the Razer software from their site to see if that makes any difference.

I've seen Razer software BSOD PCs before. It's crazy to think that can do it, but it sure can and will sometimes. I think it just has to do with a crazy bug that gets in there in some versions of their stuff. Usually getting the latest software fixes it (if they have an update).

I had a Lachesis mouse (gosh, that was the worst mouse I've ever used besides a Mac mouse) and it's software BSOD'd my computer on random occasions.

I don't know if my problem is the same or not, but since I'm running two Razer mice and both machines are seeing this problem, I'm likely to think that could be it.

The two mice I have are a Pro Click 1.6 and a Diamondback 3G, both of which are very similar mice.

 

[Xplaced]

It could be dumb luck, but since installing the updated Windows 7 drivers from Razerzone for my mice, I have not had that right-click error on either PC since. That's been since I last posted here, nearly two weeks ago.

If for some reason it does do it again, I will try to post here and let you guys know. As of now though, the problem is resolved for me until it rears its ugly head.

 

[digadigado]

I've been reading about Win7-x64 hanging or crashing when right-clicking in Explorer. I think it is a coding error in Explorer. Why? For me it started after a clean install (and and again after a reinstall) before anything other than Win7 was on the system. Don't know about x32 - haven't seen any posts for that OS version.

After installing various apps which add to the context menu(WinZip, WinAmp, Notepad++ etc) it still happens. One post on sevenforums recommended Mark Russinovitch's Autoruns program (excellent!). Using it I disabled every context handler(even Win7's) and it still sporadically hangs Explorer when I right-click on a drive/folder/file. If all context handlers are disabled, it seems they're innocent.

I've looked for an online method of submitting a problem report to Microsoft but all I found were pay solutions. I'm not about to pay them $259 (really!) to help them find one of their problems. They can come to sevenforums and their own newsgroups and get lots of feedback.

I can't think of anything else to do except hope that Microsoft eventually acknowledges that this is a widespread problem and deigns to look into it. You might try Autoruns (Google Russinovitch Autoruns) and see if it helps you. You can disable and re-enable individual context handlers via a GUI, not the registry.

Good luck and...
Grrrrr!

 

[Panic]

Just though id pop back in and let you guy's know i fixed the problem, it turns out to be caused by the weirdest thing ever. i had private browsing enabled in firefox, i didn't think it would have any effect on explorer.exe and that it could only effect firefox.exe itself but low and behold i disabled it and explorer hasent crashed since. it dosen't make much sense since i think it was crashing even when i had firefox closed but it fixed the problem.

 

[Tomel]

I'm also having frequent "Windows Explorer Not Responding" problems on my two Windows 7 systems, a netbook and a desktop both with Home Premium installed. After careful observation over several weeks now, it seems that it happens if I "jiggle" the mouse slightly at the same time that I right click. If I right click very carefully, no problem. Never had the problem with my former XP system. Don't like to do it, but might have to lower the mouse sensitivity a little to see if that helps.

 

[funtalk]

I'm also having frequent "Windows Explorer Not Responding" problems on my two Windows 7 systems, a netbook and a desktop both with Home Premium installed. After careful observation over several weeks now, it seems that it happens if I "jiggle" the mouse slightly at the same time that I right click. If I right click very carefully, no problem. Never had the problem with my former XP system. Don't like to do it, but might have to lower the mouse sensitivity a little to see if that helps.

I confirmed the "jiggle" indeed (often) triggers the "not responding" error in explorer.
The question is how do we fix it? update mouse driver? any hints?

 

[Tomel]

funtalk . . .

It may simply be coincidence, but when I switched from Avast Antivirus to MS Security Essentials, the problem went away and has not re-occurred. The switch from Avast was the only software change that I made (other than routine Windows Updates) from the time I was having the problems and when the problems disappeared.

 

[coldmotion]

This works

First go to any site and install "ShellExView". It's a small program. It will tell you in the right hand column which dates were the last to be modified. You can choose either of two dates of the latest changes and you can decide which programs caused your problem by the date.

Then do this:
1. Click the start button
2. Type in the search box "Event Viewer" and hit enter
3. On the left side navigation go to "Windows Logs" and expand it
4. Click on "Application"
5. In the box to the right scroll down until you find an error entry with "Application Error" in the source column, and highlight it.
6. In the box beneath on the "General" tab you will see lines of information. Look towards the bottom of the list and you will see "Faulting application path". This is basically what you were trying to do when the error happened. Beneath that entry will be "Faulting module path". This should tell you what program caused the error.
7. Uninstall the program, reinstall it, update it... whatever. But do SOMETHING with it. In my case I uninstalled the program referenced in the "Faulting module path", restarted the pc and it was an instant fix.

THen:
Star  Run   OK  Regedit HKLM Local Machine \ Software \ Microsoft \ SQMClienti \ Windows \ Disabled Session
At this point you will be presented under four keys, you can not find MachineThrottling, open the subkey marked with the triangle and there you will find "throttling" of course without the quotes. For added security export the subkey and save it in a safe folder having a lot of care, being able to restore immediately place if the operation is successful, but I assure you the result at 100%. Now delete the subkey Throttling with the right of our mouse, tidy up the registry and now pay attention: back on the desktop, we need to turn off the computer does not restart, repeat off. Wait 10 seconds and switch, problem solved. We will not have the Windows explorer has stopped working, start the machine and operating system Windows 7 will work beautifully, making it even more, even if it is already faster than about 14/18%.

These steps were gathered from other sites I have researched. But I had done one more thing: After I was then able to right click again the icons were still greyed out. So I went to desktop first and selected all. THen right click, properties and all of the properties will show up at one time. UNCHECK the hidden file icon at the bottom and apply. They will all turn good again. THen go to downloads, pictures, documents and all and use edit to select all. UNCHECK the hidden button again and apply and all will turn good again. DO this with every page you have lightened hidden icons on. This will work for hundreds of icons on a page at one time.

My problem was Ad aware. I deleted that plus spybot and malwarebytes. Seems they caused a bad problem with the shell somewhere but I believe it was the ad aware that was the main. But not for sure. I had a hard time deleting ad aware so I stopped it in task manager and anywhere else I could like msconfig from the run search box.

My system is restored well and is faster too. Try it in any combination and it works. I did not have to put the Throttle key back in either. It had no value anyway. I still saved it by exporting just in case. You'll figure it out once you start playing with it. Not that difficult.

The event viewer and the SHellExView program will show you exactly what is cursing your right click blunder. It even shows you their file locations. YOU CAN ALSO right click on the item in question in event viewer and it will let you go to properties and find a previous version you can use. If it is needed. But this works.

 

[bduerr]

thye response in the window was:
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\system32\SHELL32.dll
Report Id: 2b7b234e-4dc8-11e5-a73d-f04da2dd94cc