Right Click = Explorer Not Responding

H2SO4 · 29 Oct 2009

Panic said:

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 · 29 Oct 2009

H2SO4 said:

Nikolay said:

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 · 29 Oct 2009

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 · 29 Oct 2009

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 · 29 Oct 2009

Panic said:

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 · 29 Oct 2009

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

H2SO4 · 29 Oct 2009

Panic said:

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:

https://www.sevenforums.com/crashes-d...tml#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 · 30 Oct 2009

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 · 30 Oct 2009

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 · 05 Nov 2009

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.