none
IE11 broswer frequently turn up Stop Working to Updated win 8.1 RRS feed

  • Question

  • IE11  browser these days has frequently turned up " Stop Working... "  to Updated the win 8.1 see the attach please.

    Friday, March 6, 2015 11:58 AM

All replies

  • Can you open the Action Center on the taskbar > Maintenance > View reliability history > View all problem reports

    Can you right-click on a few of the "Internet Explorer"  "Stopped working" errors > View technical details

    What are the details of the errors?

    There is a "Copy to Clipboard" link at the bottom.

    Paste the information first into Notepad and then recopy the information from Notepad to post here.

    Friday, March 6, 2015 9:16 PM
  • Thank you auggy here for this.

    Reliability corrupted since Feb. 22 2015 discovered.

    From the suggestion of Microsoft, tried as below photo , please review it , 86bit adobe flash player could not been installed on the win8.1 ?

    Could not find you mentioned "Clipboard" ?

    • Edited by BleuOisou Saturday, March 7, 2015 2:17 AM
    Saturday, March 7, 2015 2:15 AM
  • Can you do the following:

    Windows Key + S > type view all problem reports and then click on "View all problem reports"

    Under "Internet Explorer" double-click on a recent Internet Explorer error.

    At the bottom there is a "Copy to clipboard" link.

    Can you click on the "Copy to clipboard' link then paste the information first into Notepad and then recopy the information from Notepad to post here.

    Do this for a few of the errors.



    • Edited by auggyMVP Saturday, March 7, 2015 1:18 PM
    Saturday, March 7, 2015 1:16 PM
  • Yes, get it down here now. Above screenshot Install 64bit is 86x at the Manage Add-In  ?

    Source
    Internet Explorer

    Summary
    Stopped working

    Date
    ‎7/‎3/‎2015 10:11

    Status
    Report sent

    Description
    Faulting Application Path:    C:\Program Files (x86)\Internet Explorer\iexplore.exe

    Problem signature
    Problem Event Name:    BEX
    Application Name:    IEXPLORE.EXE
    Application Version:    11.0.9600.17416
    Application Timestamp:    5452eed9
    Fault Module Name:    StackHash_3004
    Fault Module Version:    0.0.0.0
    Fault Module Timestamp:    00000000
    Exception Offset:    PCH_76_FROM_ntdll+0x0003CC2C
    Exception Code:    c0000409
    Exception Data:    0000001a
    OS Version:    6.3.9600.2.0.0.256.48
    Locale ID:    3076
    Additional Information 1:    3004
    Additional Information 2:    3004d68a9cd75c03a806b6f6121ce77d
    Additional Information 3:    52da
    Additional Information 4:    52dafc48bc1e5f244270b9032ab197dd

    Extra information about the problem
    Bucket ID:    02ad994b27ae3282c692729dc3ae987b (81807765847)

    Sunday, March 8, 2015 12:13 AM
  • The faulting module is not positively identified:

    Fault Module Name:    StackHash_3004
    Fault Module Version:    0.0.0.0
    Fault Module Timestamp:    00000000

    It may help to see what modules are loaded during a crash.

    Can you download and run the following application (AppCrashView):

    http://www.nirsoft.net/utils/app_crash_view.html

    Click on one of the recent iexplore.exe errors.

    Can you copy and paste the information that appears in the lower window that has loaded modules.

    Sunday, March 8, 2015 12:32 PM
  • How to read them please?

    Version=1
    EventType=BEX
    EventTime=130701678859331028
    ReportType=2
    Consent=1
    UploadTime=130701678859651173
    ReportIdentifier=419934ba-c46f-11e4-be91-fc4dd4f2edfd
    IntegratorReportIdentifier=419934b9-c46f-11e4-be91-fc4dd4f2edfd
    WOW64=1
    NsAppName=IEXPLORE.EXE
    Response.BucketId=02ad994b27ae3282c692729dc3ae987b
    Response.BucketTable=5
    Response.LegacyBucketId=81807765847
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=IEXPLORE.EXE
    Sig[1].Name=Application Version
    Sig[1].Value=11.0.9600.17416
    Sig[2].Name=Application Timestamp
    Sig[2].Value=5452eed9
    Sig[3].Name=Fault Module Name
    Sig[3].Value=StackHash_3004
    Sig[4].Name=Fault Module Version
    Sig[4].Value=0.0.0.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=00000000
    Sig[6].Name=Exception Offset
    Sig[6].Value=PCH_76_FROM_ntdll+0x0003CC2C
    Sig[7].Name=Exception Code
    Sig[7].Value=c0000409
    Sig[8].Name=Exception Data
    Sig[8].Value=0000001a
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.3.9600.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=3076
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=3004
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=3004d68a9cd75c03a806b6f6121ce77d
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=52da
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=52dafc48bc1e5f244270b9032ab197dd
    UI[2]=C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
    LoadedModule[0]=C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
    LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL
    LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll
    LoadedModule[4]=C:\WINDOWS\system32\apphelp.dll
    LoadedModule[5]=C:\WINDOWS\SYSTEM32\msvcrt.dll
    LoadedModule[6]=C:\WINDOWS\SYSTEM32\iertutil.dll
    LoadedModule[7]=C:\Program Files (x86)\McAfee\Gkp\HcApi.dll
    LoadedModule[8]=C:\WINDOWS\SYSTEM32\RPCRT4.dll
    LoadedModule[9]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll
    LoadedModule[10]=C:\WINDOWS\SYSTEM32\SspiCli.dll
    LoadedModule[11]=C:\WINDOWS\SYSTEM32\sechost.dll
    LoadedModule[12]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
    LoadedModule[13]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
    LoadedModule[14]=C:\Program Files (x86)\McAfee\Gkp\HcThe.dll
    LoadedModule[15]=C:\WINDOWS\SYSTEM32\user32.dll
    LoadedModule[16]=C:\WINDOWS\SYSTEM32\GDI32.dll
    LoadedModule[17]=C:\WINDOWS\system32\IMM32.DLL
    LoadedModule[18]=C:\WINDOWS\SYSTEM32\MSCTF.dll
    LoadedModule[19]=C:\WINDOWS\SYSTEM32\shcore.dll
    LoadedModule[20]=C:\WINDOWS\SYSTEM32\combase.dll
    LoadedModule[21]=C:\WINDOWS\SYSTEM32\IEFRAME.dll
    LoadedModule[22]=C:\WINDOWS\SYSTEM32\SHLWAPI.dll
    LoadedModule[23]=C:\WINDOWS\SYSTEM32\ole32.dll
    LoadedModule[24]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll
    LoadedModule[25]=C:\WINDOWS\SYSTEM32\SHELL32.dll
    LoadedModule[26]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17415_none_a9ed7f470139b3c1\comctl32.dll
    LoadedModule[27]=C:\Program Files (x86)\Internet Explorer\IEShims.dll
    LoadedModule[28]=C:\WINDOWS\SYSTEM32\comdlg32.dll
    LoadedModule[29]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
    LoadedModule[30]=C:\WINDOWS\system32\uxtheme.dll
    LoadedModule[31]=c:\PROGRA~2\mcafee\SITEAD~1\saHook.dll
    LoadedModule[32]=C:\WINDOWS\SYSTEM32\urlmon.dll
    LoadedModule[33]=C:\WINDOWS\SYSTEM32\WININET.dll
    LoadedModule[34]=C:\WINDOWS\SYSTEM32\USERENV.dll
    LoadedModule[35]=C:\WINDOWS\SYSTEM32\profapi.dll
    LoadedModule[36]=C:\WINDOWS\SYSTEM32\Secur32.dll
    LoadedModule[37]=C:\WINDOWS\SYSTEM32\WS2_32.dll
    LoadedModule[38]=C:\WINDOWS\SYSTEM32\NSI.dll
    LoadedModule[39]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
    LoadedModule[40]=C:\WINDOWS\SYSTEM32\winhttp.dll
    LoadedModule[41]=C:\WINDOWS\system32\mswsock.dll
    LoadedModule[42]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
    LoadedModule[43]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
    LoadedModule[44]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
    LoadedModule[45]=C:\WINDOWS\system32\rsaenh.dll
    LoadedModule[46]=C:\WINDOWS\SYSTEM32\bcrypt.dll
    LoadedModule[47]=C:\WINDOWS\SYSTEM32\clbcatq.dll
    LoadedModule[48]=C:\Program Files (x86)\Internet Explorer\ieproxy.dll
    LoadedModule[49]=C:\WINDOWS\system32\dwmapi.dll
    LoadedModule[50]=C:\WINDOWS\SYSTEM32\IEUI.dll
    LoadedModule[51]=C:\WINDOWS\SYSTEM32\MSHTML.dll
    LoadedModule[52]=C:\WINDOWS\SYSTEM32\d2d1.dll
    LoadedModule[53]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
    LoadedModule[54]=C:\WINDOWS\SYSTEM32\DWrite.dll
    LoadedModule[55]=C:\WINDOWS\SYSTEM32\dxgi.dll
    LoadedModule[56]=C:\WINDOWS\SYSTEM32\d3d11.dll
    LoadedModule[57]=C:\WINDOWS\SYSTEM32\nvwgf2um.dll
    LoadedModule[58]=C:\WINDOWS\SYSTEM32\PSAPI.DLL
    LoadedModule[59]=C:\WINDOWS\SYSTEM32\MLANG.dll
    LoadedModule[60]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
    LoadedModule[61]=C:\Windows\SYSTEM32\actxprxy.dll
    LoadedModule[62]=C:\Windows\System32\rasadhlp.dll
    LoadedModule[63]=C:\WINDOWS\System32\fwpuclnt.dll
    LoadedModule[64]=C:\WINDOWS\SYSTEM32\ninput.dll
    LoadedModule[65]=C:\Windows\SYSTEM32\ieapfltr.dll
    LoadedModule[66]=C:\WINDOWS\system32\msimtf.dll
    LoadedModule[67]=c:\PROGRA~2\mcafee\SITEAD~1\saPlugin.dll
    LoadedModule[68]=C:\WINDOWS\SYSTEM32\VERSION.dll
    LoadedModule[69]=C:\WINDOWS\SYSTEM32\OLEACC.dll
    LoadedModule[70]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
    LoadedModule[71]=C:\WINDOWS\SYSTEM32\WINSTA.dll
    LoadedModule[72]=C:\WINDOWS\SYSTEM32\sxs.dll
    LoadedModule[73]=c:\PROGRA~2\mcafee\SITEAD~1\mcieplg.dll
    LoadedModule[74]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
    LoadedModule[75]=C:\WINDOWS\SYSTEM32\normaliz.dll
    LoadedModule[76]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17415_none_7c5769eaaa0aa358\comctl32.dll
    LoadedModule[77]=c:\PROGRA~2\mcafee\SITEAD~1\mcbrwctl.dll
    LoadedModule[78]=C:\WINDOWS\SYSTEM32\powrprof.dll
    LoadedModule[79]=C:\WINDOWS\SYSTEM32\dcomp.dll
    LoadedModule[80]=C:\WINDOWS\SYSTEM32\jscript9.dll
    LoadedModule[81]=C:\WINDOWS\SYSTEM32\CRYPT32.dll
    LoadedModule[82]=C:\WINDOWS\SYSTEM32\MSASN1.dll
    LoadedModule[83]=C:\Windows\SYSTEM32\uiautomationcore.dll
    LoadedModule[84]=C:\WINDOWS\SYSTEM32\schannel.dll
    LoadedModule[85]=C:\WINDOWS\SYSTEM32\WINTRUST.dll
    LoadedModule[86]=C:\WINDOWS\SYSTEM32\gpapi.dll
    LoadedModule[87]=C:\WINDOWS\SYSTEM32\ncrypt.dll
    LoadedModule[88]=C:\WINDOWS\SYSTEM32\NTASN1.dll
    LoadedModule[89]=C:\Windows\SYSTEM32\cryptnet.dll
    LoadedModule[90]=C:\WINDOWS\SYSTEM32\WLDAP32.dll
    LoadedModule[91]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
    LoadedModule[92]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
    LoadedModule[93]=C:\WINDOWS\SYSTEM32\webio.dll
    LoadedModule[94]=C:\WINDOWS\system32\windowscodecs.dll
    LoadedModule[95]=C:\WINDOWS\system32\ncryptsslp.dll
    LoadedModule[96]=C:\WINDOWS\SYSTEM32\XmlLite.dll
    LoadedModule[97]=C:\WINDOWS\SYSTEM32\WINMM.dll
    LoadedModule[98]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
    LoadedModule[99]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll
    LoadedModule[100]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
    LoadedModule[101]=C:\WINDOWS\SYSTEM32\T2EMBED.DLL
    LoadedModule[102]=C:\WINDOWS\System32\UIAnimation.dll
    LoadedModule[103]=C:\WINDOWS\SYSTEM32\D3D10Warp.dll
    LoadedModule[104]=C:\WINDOWS\system32\windowscodecsext.dll
    LoadedModule[105]=C:\Windows\SYSTEM32\msxml6.dll
    LoadedModule[106]=C:\Windows\System32\Windows.Globalization.dll
    LoadedModule[107]=C:\Windows\System32\Bcp47Langs.dll
    LoadedModule[108]=C:\WINDOWS\SYSTEM32\globinputhost.dll
    LoadedModule[109]=C:\WINDOWS\SYSTEM32\MFPlat.DLL
    LoadedModule[110]=C:\WINDOWS\SYSTEM32\RTWorkQ.DLL
    LoadedModule[111]=C:\WINDOWS\SYSTEM32\AVRT.dll
    LoadedModule[112]=C:\Windows\SYSTEM32\MFMediaEngine.dll
    LoadedModule[113]=C:\WINDOWS\SYSTEM32\twinapi.appcore.dll
    LoadedModule[114]=C:\Windows\System32\Windows.Media.MediaControl.dll
    LoadedModule[115]=C:\Windows\System32\WinTypes.dll
    LoadedModule[116]=C:\Windows\System32\MMDevAPI.DLL
    LoadedModule[117]=C:\Windows\SYSTEM32\Macromed\Flash\Flash.ocx
    LoadedModule[118]=C:\WINDOWS\SYSTEM32\DSOUND.dll
    LoadedModule[119]=C:\WINDOWS\SYSTEM32\DINPUT8.dll
    LoadedModule[120]=C:\WINDOWS\SYSTEM32\mscms.dll
    LoadedModule[121]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
    LoadedModule[122]=C:\WINDOWS\SYSTEM32\ImgUtil.dll
    LoadedModule[123]=C:\WINDOWS\System32\Wpc.dll
    LoadedModule[124]=C:\WINDOWS\System32\NETAPI32.dll
    LoadedModule[125]=C:\WINDOWS\System32\wevtapi.dll
    LoadedModule[126]=C:\WINDOWS\System32\netutils.dll
    LoadedModule[127]=C:\WINDOWS\System32\srvcli.dll
    LoadedModule[128]=C:\WINDOWS\System32\wkscli.dll
    LoadedModule[129]=C:\WINDOWS\System32\SAMCLI.DLL
    LoadedModule[130]=C:\WINDOWS\SYSTEM32\DPAPI.DLL
    LoadedModule[131]=C:\WINDOWS\SYSTEM32\FAULTREP.DLL
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=BEX
    AppName=Internet Explorer
    AppPath=C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=2071C2C694212DBF0B1138ABFEB26A46

    Monday, March 9, 2015 1:25 AM
  • Hi,

    Would you please usig Procdump to capture a IE crash dump file? This could help us find the reason of this problem more effective.

    Download Procdump:

    https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

    You can refer to the content of the link below to learn how to generate the dump file using procdump:

    http://support.c2c.com/2014/08/13/howto-use-procdump-for-troubleshooting-service-crashes/

    Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. After captured the dump file, please upload the dump file to your OneDrive and post the sharing link here.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, March 9, 2015 3:13 PM
    Moderator
  • Also there are some suspect modules such as modules related to McAfee.

    The problem could also be related to the NVIDIA graphic driver.

    Obtaining a crash dump may help pinpoint the cause of the crash.

    Here's another way to obtain a crash dump:

    If you copy and paste the following in Notepad and save as a .reg file (save with the .reg extension and give it any name such as iedump.reg), then right-click the .reg file and select "Merge" to add to the registry, a .dmp file at the time iexplore.exe crashes should be created in the C:\CrashDumps folder:

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\iexplore.exe]
    "DumpFolder"=hex(2):43,00,3a,00,5c,00,43,00,72,00,61,00,73,00,68,00,44,00,75,\
    00,6d,00,70,00,73,00,00,00


    After Internet Explorer (iexplore.exe) crashes, can you then make the .dmp file available (provide link) via public folder on OneDrive or similar site?

    Here's a couple of links on using OneDrive (SkyDrive):

    http://windows.microsoft.com/en-ca/skydrive/add-photos-files-faq

    http://windows.microsoft.com/en-ca/onedrive/share-file-folder

    More info on collecting user-mode dumps:
    »msdn.microsoft.com/en-us/library···85).aspx

    If you would rather pursue the issue without generating a crash dump post back.

    Tuesday, March 10, 2015 12:41 PM
  • Extract the downloaded Prodump.zip and copyto the Archive server? Where is the server indicating  please, am client ? According to the instance dos not recognized ? And

    For a spontaneous crash: procdump -ma MyProcess.exe C:\C2CDumps
    For a terminating process: procdump -e -ma MyProcess.exe C:\C2CDumps  not found ?




    • Edited by BleuOisou Tuesday, March 10, 2015 2:49 PM
    Tuesday, March 10, 2015 2:42 PM
  • Hi,

    For your problem, you can use procdump with the command line below to generate dump file:

    md c:\dumps|procdump -h -ma iexplore c:\dumps\iexplore


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, March 11, 2015 8:03 AM
    Moderator
  • Look at the screenshots, command not recognized Roger , please?

    Thursday, March 12, 2015 1:24 AM
  • Hi,

    There is bit of problem of former command, I made a test in our testing enviroment. To capture IE hung dump file, firstly you need to start IE, then open TaskMager to check its PID, then run procdump command below:

    Procdump -h PID

    When this command running, it would keep monitoring IE process untill it is hung up, then a minidump file would be generated at the root of Procdump directory folder.

    Here is the running screenshot:


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, March 13, 2015 5:55 AM
    Moderator
  • From the procdump where to express the IE opening then stopped error ? Unable to read it.  Does this have to be monitored right at when error showing ? Since the TechNet.Microsoft.com info has accorded to get over this problem few days ?  Please advise it .

    • Edited by BleuOisou Friday, March 13, 2015 4:20 PM
    Friday, March 13, 2015 4:17 PM
  • Hi,

    The reason why Procdump couldn't generate the dump file because of IE doesn't encounter any unresponding during Procdump monitoring IE process.

    On the other hand, according to your screenshot, IE seems like working with no problem. Therefore, how about your problem now? Is IE still keeping apprears unresponding? If this is uncertainly issue, it would be better to follow auggy's suggestion to collect Windows application crash dump.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, March 16, 2015 8:58 AM
    Moderator
  • Thank you Roger replying me.

    IE11 blocking time where , which features, in lines of capture suggested to find the problems on it please?

    Monday, March 16, 2015 10:54 PM
  • If you are still having issues do you want to try the registry edit I posted which should force a dump of the IE crash when one occurs.
    Wednesday, March 18, 2015 10:16 PM
  • Thank you very much Auggy for the completive performance of a diagnose.

    One more thing, to enable the procdump \   log debug string , exception monitor , how to shall please?

    Sent to  tnmff@microsoft.com an Ieplore.sln that maybe remind something ?

     
    • Edited by BleuOisou Thursday, March 19, 2015 7:46 AM
    Thursday, March 19, 2015 1:26 AM