New
#181
I have the same problem
Ran the shellexview
it was for sure the AVG Shell Extension Class disabled it and windows explorer functions like it should again !!! I am able to recreate the exception error if I enable it again every time.
I also thought this might solve some of the C++ issues as there was a C++ error when I was installing the AVG that I had to fix first.
Now it shows the file is C:\Program Files\AVG\AVG9\avgse.dll
Is it safe to delete it or will it mess up the AVG program?
I signed up just to share this in hope that it will help someone else.
Thanks
I have had this problem with the retail versions of both Vista x64 and Windows 7 x64. Home Prem. editions both.
I have been working and researching this problem for a couple of weeks now.
I believe I may have stumbled upon the answer or at least narrowed it down a bit.
As this error seems to effect just about every app written for windows in recent years ...
and..
As this error is unpredictable and hard to duplicate...
and...
as the error is usually predicated by using the right-mouse button...
and...
as this error seems to give a "heap corruption" error...
and...
as a lot of people are getting faulty messages about bad memory...
AND...
as some people can go for days even weeks without this problem.
It is my belief that this is a memory "leak" problem or at best a poorly protected memory space that is being accessed or overwritten/erased and/or re-written too.
The clipboard seems to be the area where we are getting into trouble. As memory space is used by most applications and the memory space set aside for this use(clipboard use), is in most cases being corrupted by applications NOT trying to use "clipboard" space, and some that actually are trying to manipulate the "clipboard" memory space, such as Firefox's privacy settings trying to clear the "clipboard"...and some apps in general are quite possibly corrupting the clipboard data as well as other data it(the app), was trying to store or other applications/services/system process data nearby.
It almost appears as a size problem. Like 3rd party apps are not using either the correct memory space size and/or location. Or MS has not given the correct specifications to 3rd party vendors.
What got me thinking along these lines is the right-mouse button issue. It calls up among other things, the "copy and paste" menu...which of course is tied to the "clipboard".
Also, the inability to re-produce the error at will can be explained by the fact that sometimes the date ISN'T corrupted in memory...and/or maybe the space has been erroneously protected and whenever some other process or app tries to use that space it THEN shows up as an error..or causes a crash. When nothing is using the now corrupted space...no crash. I can now more-or-less, re-produce this "crash" at will.
This would also explain the HUGE array of applications being caught up in this...Its not your programs(IMHO), its a memory management issue...causing EVERYBODY'S applications to fail or causing Explorer to fail.
This would also explain the "Heap corruption issue" and how people are getting what apear to be memory problems or bad memory errors and how after re-booting itself 4-5 times..the problem vanishes. (memory cleared).
If somebody has a better idea of what else could be addressing all these issues simultaneously -please feel free to correct me.
If you'd like to take a crack at reproducing this "crash"
Reboot your machine...then just use your clipboard and copy and paste a few things...I go online because there is a definite conflict with Firefox's privacy protection and the OS's clipboard...I copy some random text...then exit FF and within a few right-clicks of the mouse...BINGO! Crash...of explorer. This also explains why people who don't do much cutting/pasting...can go for a long time without an error. I'm assuming this of course.
That's make sense. And I think that Microsoft needs to fix it soon, or I will go back to Windows Vista- in my experience, a really stable OS-. If the copy/paste options are involved in this problem, every PC with Win 7 is a potencial victim of explorer crashes.
A few minutes ago I have had a lot of crashes, after modifying some Windows Shell options with the program Autoruns. Reboot and, then, all fine again...
EDIT: I did it (go online and copy some text, then shut down Firefox and do a right click). Result: Crash of explorer. With Opera or IE8 explorer doesn't crash.
Last edited by Rouphen; 29 Nov 2009 at 09:44.
I don't seem to have this problem with Windows 7; however, I do have other issuse with Windows 7. I bought a new computer with Windows 7 64 bit already installed. Could it be that this issue appears only when upgrading from a previous version of Windows on an older computer with older graphics drives, etc.? Getting all of these flaws fixed in future service packs will keep the Microsoft programmers very busy in the coming months.
Well, I did a clean install of Win 7, not an update- which isn't recommended anyway-. In fact, I did two clean installs. The first of them was in my second HDD- to test the OS-, and that Win 7 Ultimate 64 didn't crash one single time, but I've used it only a few days.
After trying Otterbear suggestions, I sent Firefox to a short period- I hope- of holidays. Now I'm using Opera 10.10, and everything it's ok. Temporarily again? Who knows...
I suspect Winrar or Firefox. I removed both and I have copied and pasted right clicked blah blah blah for 2 days straight and no problems. I could always get a right click explorer crash after a reboot, not anymore.
Incedently FF has upgraded and fixed the issue (or rather dealt with MS's problem), in their latest version...whether that is a beta version or not right now I don't know. I have been working closely with them and they seem to have developed a working solution.
Like I said earlier, This is not winzip,FF, or any other application causing the problem, its just that ALL programs have to use memory and sometimes that memory is corrupted (due to insufficient reserved space management), and causes them to crash or explorer to crash.
IMHO, your not solving the problem by getting rid of all the software that is designed to run on Vista and Windows 7...your just avoiding it and replacing is with what will look like a different problem with the new app..(if it uses that particular memory allocated space).
I feel a little better, knowing that this will be worked out with MS and the 3rd party software developers..eventually. New OS's will have these kinds of issues and there is a learning curve for both parties.
Firefox has already developed ways to fix or deal with it..and I'm sure others will be close behind.
Hope this helps.
Update:
Just to clarify all I did was DISABLE Private Browsing in Firefox 3.5.5
I have NOT had a SINGLE right click crash since doing so. I did not do anything else to solve the problem. I've been right clicking like a mad man and I have not had a single crash!!!!!
I am 99.93% confident I will no longer have this crash. Thanks to all that provided this possible solution!