ie8 app crash, 019a87a1-7672-11df-8b80-0023aee6baaf__ - Faulting module path: C:\Windows\SysWOW64\mshtml.dll

Getting lots of these pairs in the application log

Faulting application name: iexplore.exe, version: 8.0.7600.16385, time stamp: 0x4a5bc69e
Faulting module name: mshtml.dll, version: 8.0.7600.16588, time stamp: 0x4be2b810
Exception code: 0xc0000005
Fault offset: 0x001bc4d5
Faulting process id: 0xe48
Faulting application start time: 0x01cb0a7e3b779c9b
Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe
Faulting module path: C:\Windows\SysWOW64\mshtml.dll
Report Id: 019a87a1-7672-11df-8b80-0023aee6baaf

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: iexplore.exe
P2: 8.0.7600.16385
P3: 4a5bc69e
P4: mshtml.dll
P5: 8.0.7600.16588
P6: 4be2b810
P7: c0000005
P8: 001bc4d5

Attached files:

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: 019a87a1-7672-11df-8b80-0023aee6baaf
Report Status: 1

System info:

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7600 Build 7600
Other OS Description  Not Available
OS Manufacturer Microsoft Corporation
System Model Studio XPS 435T
System Type x64-based PC
Processor Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz, 2668 Mhz, 4 Core(s), 8 Logical Processor(s)

McAfee AV suite

[1] I am seeing the following error logged. It seems to exhibit as a dialog message saying that Windows explorer has encountered an error (unspecified) and is restarting...

[2] ...with regard to the recommendation to run the fixit in both default and aggressive mode, I think, in hindsight, I should have done only the default and seen if that resolved the issue.

A1. EXPLORER.EXE is Windows Explorer, not Internet Explorer (IEXPLORE.EXE). If you've not encountered any problems (i.e., crashes) as a result of these errors, don't worry about it. But if Windows is "crashing," you will find appropriate assistance in this forum:


A2. Trust me: Running the "reset Windows Update components" Fix It in Agressive mode did not cause the EXPLORER.EXE errors.


BTW, the "Let me fix it myself" section of explains exactly what the Fix It will do automatically.


~Robear Dyer (PA Bear)
Microsoft MVP (Windows Client) since October 2002

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.


Question Info

Last updated May 16, 2018 Views 12,612 Applies to:

Related Forums