Quote: Originally Posted by Dazeon
If it weren't for this issue then Windows 7 would be perfect!
BTW. I forgot to say, yeah, the issue will occur once and then continue to occur around four to six times, then revert back to normal behavior.
@Most of the posters on this thread:
I empathise with your pain, though I can't necessarily offer any solutions. A few thoughts...
An Explorer crash is one of those generic symptoms which can occur for umpteen different reasons. References to "this issue" abound (not just in the quoted text), and from an end-user point of view it's certainly understandable that all Explorer crashes are mentally "bucketised" as the same problem.
However, it's many different problems which all look the same from the outside
Explorer is a pseudo-container process, almost like IExplore.exe. They're targets for all sorts of add-on code which would seek to extend the functionality of the OS in various ways. Some of those add-ons, like shell extensions, are relatively easy to deactivate because of the availability of specialised tools. Others are "injected code" which is far more difficult to spot and isolate at the sysadmin level.
My (relatively confident) guess is that Microsoft gets thousands of reports every day regarding "Explorer crashing" - most as automated WER report submissions, some by users seeking phone support, and many in the form of web submissions/complaints. Windows 7 is not special in this regard - similar symptoms always occurred under older versions too, the vast majority due to add-ons.
Hence, Microsoft presumably wouldn't be particularly perturbed until their reporting telemetry and some form of debug analysis identifies crash patterns which point at their code as the culprit. When your installed user base is measured in the millions, even thousands of generic problem reports do not necessarily mean there's anything wrong in your own code.
a) If your aim is simply to give yourself the greatest possible chance of getting rid of the symptom, without necessarily understanding it, reinstall the OS and be very judicious about add-ons afterwards. Try to add shell extensions and context menu handlers slowly, one-at-a-time, so that you get a feel for the likely culprit if things start acting up again. Easier said than done, I realise.
b) If you'd like to understand, go through this procedure to generate a memory dump of the crash, and then examine it with a debugger, or start your own thread if you'd like assistance: http://www.sevenforums.com/crash-loc...g-process.html
The results may be in the "obvious 3rd-party involvement", "unknown", or "points at MS" categories, but at least you'll have a better idea of what it might be.
c) Be careful about reading too much into others' misdiagnoses. In the absence of information, people come up with all sorts of bizarre explanations, and then manage to comprehensively convince themselves (and others) that the observed patterns fit their theory.