Solved Windows Explorer crashes randomly and has to restart

Hi everyone,

Windows Explorer seems to crash randomly with me (it does not happen with every computer session but seems to happen when I want to open a window) and has to restart; then, after a few seconds, it crashes again and has to restart yet again (seems to happen when I try opening the window again after Explorer restarts) Have got the latest Windows updates and Service Pack 1. The issue started after installing the recommended Microsoft updates described over here:
http://www.sevenforums.com/windows-updates-activation/159549-6-new-updates-4-26-11-a.html
After the updates had been successfully installed, I was asked to reboot my computer. After the reboot,when I wanted to open a window, Explorer crashed (30th April logs; see below).

Since my computer is in German, the crash logs are also in German. I have translated them into English, so if a few things sound a bit odd, it's because it's my own translation, though I was able to recall a few of the English terms thanks to my other laptop, which is in English (but has no problems at all with Explorer...)

I've inserted all the crash logs below - two from 30th April (two crashes which happened after each other) and three from today (13th May, also happened right after reach other). I've separated the logs with broken lines for viewing convenience. Any idea what's causing explorer to crash and how to fix the problem?

Crash logs 30th April 2011

Source
Windows-Explorer

Summary
Can no longer function

Date
‎30.‎04.‎2011 16:27

Status
Report sent.

Description
Path of faulting application: C:\Windows\explorer.exe

Problem signature
Problem event name: APPCRASH
Application name: Explorer.EXE
Application version: 6.1.7601.17567
Application time stamp: 4d672ee4
Faulting module name: StackHash_1b9c
Faulting module version: 6.1.7601.17514
Faulting module time stamp: 4ce7c8f9
Exception code: c0000374
Exception offset: 00000000000c40f2
Operating system version: 6.1.7601.2.1.0.768.3
System locale ID: 2055
Additional information 1: 1b9c
Additional information 2: 1b9cf58aa3eb0253ef97003bb64067ff
Additional information 3: 03ac
Additional information 4: 03ac16ea463d149f9db0f3854ef50a80

Additional information on the problem
Bucket ID: 34781360

---

Source
Windows-Explorer

Summary
Can no longer function

Date
‎30.‎04.‎2011 16:35

Status
Report sent.

Description
Path of faulting application: C:\Windows\explorer.exe

Problem signature
Problem event name: APPCRASH
Application name: Explorer.EXE
Application version: 6.1.7601.17567
Application time stamp: 4d672ee4
Faulting module name: StackHash_1b9c
Faulting module version: 6.1.7601.17514
Faulting module time stamp: 4ce7c8f9
Exception code: c0000374
Exception offset: 00000000000c40f2
Operating system version: 6.1.7601.2.1.0.768.3
System locale ID: 2055
Additional information 1: 1b9c
Additional information 2: 1b9cf58aa3eb0253ef97003bb64067ff
Additional information 3: 03ac
Additional information 4: 03ac16ea463d149f9db0f3854ef50a80

Additional information on the problem
Bucket ID: 34781360


Crash logs 13th May 2011

Source
Windows-Explorer

Summary
Can no longer function

Date
‎13.‎05.‎2011 23:00

Status
Report sent.

Description
Path of faulting application: C:\Windows\explorer.exe

Problem signature
Problem event name: APPCRASH
Application name: Explorer.EXE
Application version: 6.1.7601.17567
Application time stamp: 4d672ee4
Faulting module name: msvcrt.dll
Faulting module version: 7.0.7600.16385
Faulting module time stamp: 4a5bdfbe
Exception code: c0000005
Exception offset: 0000000000001221
Operating system version: 6.1.7601.2.1.0.768.3
System locale ID: 2055
Additional information 1: 4404
Additional information 2: 4404685a13a37192da1ef5a3a8b8e62e
Additional information 3: 0913
Additional information 4: 0913d5d2ddb8e2e68083d6b11cd405f9

Additional information on the problem
Bucket ID: 34772631

---

Source
Windows-Explorer

Summary
Can no longer function

Date
‎13.‎05.‎2011 23:01

Status
Report sent.

Description
Path of faulting application: C:\Windows\explorer.exe

Problem signature
Problem event name: APPCRASH
Application name: Explorer.EXE
Application version: 6.1.7601.17567
Application time stamp: 4d672ee4
Faulting module name: ntdll.dll
Faulting module version: 6.1.7601.17514
Faulting module time stamp: 4ce7c8f9
Exception code: c0000005
Exception offset: 00000000000532d0
Operating system version: 6.1.7601.2.1.0.768.3
System locale ID: 2055
Additional information 1: 4e75
Additional information 2: 4e75b8d4b21d94e23a2323ae9cc375fb
Additional information 3: 69b2
Additional information 4: 69b295f9dd9fdcdcd50998e63b8859f6

Additional information on the problem
Bucket ID: 32430540

---

Source
Windows-Explorer

Summary
Can no longer function

Date
‎13.‎05.‎2011 23:02

Status
Not sent

Description
Path of faulting application: C:\Windows\explorer.exe

Problem signature
Problem event name: APPCRASH
Application name: Explorer.EXE
Application version: 6.1.7601.17567
Application time stamp: 4d672ee4
Faulting module name: StackHash_6f36
Faulting module version: 6.1.7601.17514
Faulting module time stamp: 4ce7c8f9
Exception code: c0000374
Exception offset: 00000000000c40f2
Operating system version: 6.1.7601.2.1.0.768.3
System locale ID: 2055
Additional information 1: 6f36
Additional information 2: 6f364e767aab3b9b866e0ff63311dded
Additional information 3: 3eea
Additional information 4: 3eeaf5550e2498cd4cce5ee704c1758e

I also recall that when I booted the computer yesterday, HP Update popped up in the system tray asking me to search for HP updates (well, obviously...) and an Adobe window was also waiting for me, announcing that there was an update for Flash Player. Don't know if these update notifications might have had anything to do with Explorer crashing when I tried to open the Control Panel (I think that that was the first window I wanted to open). What I am absolutely sure about is that I had not opened Firefox.
Which makes me wonder if the Explorer crashes from April and May are related to each other...or not.

I'd first suggest trying this free tool: ShellExView - Shell Extension Manager For Windows
Use it to disable ALL non-Microsoft extensions and see if that stops the crashing.

If not, then we'll need a bit more info: http://www.sevenforums.com/crash-lockup-debug-how/34940-generating-memory-dump-crashing-process.html

Also have a look here: http://www.sevenforums.com/crash-lo...bleshooting-explorer-exe-crashing-issues.html

Hi usasma,

Thanks for your answer. I did a lot of reading on explorer crashes and I thought it might come to downloading ShellExView. Is it better to create a system restore point or an image (with the inbuilt Win 7 imaging program) before installing this program and disabling all non-Microsoft extensions? My Windows 7 came preinstalled on the computer, and I don't have the Win7 installation CD/DVD.

PS: How come only your pants are cranky?

I'd say that a System Restore point would be adequate - but you can never tell, so backup everything "just in case"

Well, it's only my pants that are cranky because of the darned leiderhosen I got while stationed in Bavaria (Bamberg) (just kidding!).

Uhm, sorry if this is a silly question...I guess I have to download the 64-bit version of ShellExViewer for my Windows 7 64-bit system? Some 32-bit applications run without problems on a 64-bit system...and some don't, of course

Yep, get the 64 bit version.

Thanks :-D It's very late over here, so I'll hop off to bed and tackle the issue when I have a "fresh" brain :-D Thanks for your help and patience

Sorry about the long delay - I was so annoyed by the Windows Explorer that I stuffed the laptop into my cupboard 45 days ago and returned to my Vista. Today I took it out again - I had run chkdsk (I don't think it found anything) and removed KB2515325 beforehand locking away the laptop; it addresses Explorer crashing when working with the taskbar, and I thought that it was to blame.
Well...today I had the same error, after installing updates from Windows Updates; the computer had to reboot to install the updates, and after the reboot, when I opened the control panel or some other window, Explorer crashed and restarted. Then I closed the window, and again Explorer crashed and restarted. According to Event Viewer, the error nearly always occurs in module ntdll.dll.
The only option I can see now is to install the registry key suggested under step 5 over here and have the dump checked out by you guys the next time Explorer crashes - I cannot reproduce the issue, the only vague pattern is that it seems to occur following a reboot after installing Windows updates (but it has also cropped when no Windows updates were installed) and it requires that I click on something (no right-click, however), for example when I open or close a window.
I don't want to do anything else because it would just be guessing, and it looks like a dump might be able to pin-point the issue - is this correct reasoning on my part? Also, I do not have a Windows 7 CD; the OS came preinstalled. Sigh.

Have you made the restore/recovery DVD's that the system should be setup to make? It's usually listed under HP Recovery Manager in the Start Menu. If not, please make them.

Here's some steps for troubleshooting crashing explorer.exe issues: http://www.sevenforums.com/crash-lo...bleshooting-explorer-exe-crashing-issues.html

And here's a link on how to capture a memory dump of a crashing process: http://www.sevenforums.com/crash-lockup-debug-how/34940-generating-memory-dump-crashing-process.html

We'll take a look at the dump to see if there's anything that we can figure from it.

Hi usasma,

Your pants are still cranky? :-D Thank you for your response Making Recovery Discs was one of the first things I did before setting up the computer. I shudder at the thought of using them, though, considering the hours I put into setting up my laptop lovingly and patiently
I read your links, and I find the second one rather complicated (I don't know anything about running a CMD prompt), while step 5 in the first link seems more straightforward (the one with installing the registry key). I have an administrator account, by the way (I'm the only person who uses the computer). Which method do you recommend for creating a dump - CMD prompt or the reg key?

I'd suggest the first link first - as it contains more troubleshooting info than the second one does.
If the steps in the first link don't work, then move on to the second link.

The Command Prompt isn't that difficult (but is, I acknowledge, very intimidating) and we can walk you through it if necessary.

Okay, I'll try out step 5 (with the registry key) first, in order to pin-point what exactly is going on. I've seen André Ziegler (who made the key available) solve many Windows Explorer problems with that method (but he doesn't seem to have posted in 2011), I just hope the dump isn't too big, otherwise I won't know how to upload it over here to sevenforums It's a nuisance that I cannot reproduce the issue, so I'll just have to wait for the next crash :-/ Thanks for being so patient with me :-D

The dumps are usually pretty large.
If they're too large to upload, pick a free file-hosting service and upload it there. Then just provide us with a link to download it from.

I saw Andre posting over on the Microsoft Answers forums earlier this year - but haven't been over there myself in a while (the restructuring makes it very confusing to me because of my eye problems).

Okay, I've merged the registry key as listed under step 5 over here. Now I guess I've got to wait for the next crash. *swallows*

I'm back again...dumpless so far...It's very odd, and I may be wrong, but since I removed Adobe Acrobat Reader 9.4.5 and installed Adobe Reader X in its place about two weeks ago, there have not been any Windows Explorer issues so far. However, on the same day I installed Reader X, I also installed the August Microsoft updates (Patch Tuesday), so if the issue is indeed fixed, then I'm not sure what fixed it - updating the Adobe Reader software or the Windows updates. I'm still going to keep an eye on the problem, and if an Explorer crash/restart does occur again, then I will post back with the dump.

Just FYI - nearly all Windows Updates are problem free. Rarely does a problem escape their pre-release testing.
Most times the errors are due to outdated/older drivers or program files on the system - or malware.

The first thing that I do at work (if I encounter update problems) is to update the drivers and any older programs on the customer's system. That fixes most of the problems that I encounter with Windows Updates that aren't malware related.

Thanks for your help and patience, usasma
Marking this thread solved.