none
IE 9 (X64) Crashes upon launch RRS feed

  • Question

  • We have an issue with a number of machines where upon launching IE 9 in X64 bit mode, it instantly crashes. 

    See log below:

    Description:
    Faulting application name: iexplore.exe, version: 9.0.8112.16421, time stamp: 0x4d762323
    Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c92c
    Exception code: 0x80000003
    Fault offset: 0x000000000002749b
    Faulting process id: 0xf2c
    Faulting application start time: 0x01d04dd14e6bc318
    Faulting application path: C:\Program Files\Internet Explorer\iexplore.exe
    Faulting module path: C:\Windows\system32\ole32.dll
    Report Id: 8c28ffe5-b9c4-11e4-9f4e-00218693fb00

    Have tried all the obvious -Disable Add-Ons, Reset Internet Explorer Settings, Change advanced setting to 'use software rendering instead of GPU rendering.'

    I have run SFC /scannow, that came back with no issues....

    Does any one have any ideas as to what could be causing this?

    Thanks



    Saturday, February 21, 2015 1:56 PM

Answers

  • Hi Joe,

    The module that is most likely causing the crash is the sxwmon64.dll:

    *** WARNING: Unable to verify timestamp for sxwmon64.dll
    *** ERROR: Module load completed but symbols could not be loaded for sxwmon64.dll
    *** WARNING: Unable to verify timestamp for ieframe.dll
    *** WARNING: Unable to verify timestamp for iertutil.dll
    *** WARNING: Unable to verify timestamp for iexplore.exe
    Unable to load image C:\Windows\System32\mshtml.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mshtml.dll
    Probably caused by : memory_corruption ( memory_corruption!ole32 )

    Some information on and the location of the sxwmon64.dll which appears to be a component of Lumension Endpoint Security:

    00000001`80000000 00000001`80045000   sxwmon64 T (no symbols)          
        Loaded symbol image file: sxwmon64.dll
        Image path: C:\Windows\System32\sxwmon64.dll
        Image name: sxwmon64.dll
        Timestamp:        Thu Aug 11 11:58:05 2011 (4E43FC0D)
        CheckSum:         0004413E
        ImageSize:        00045000
        File version:     4.4.1564.0
        Product version:  4.4.0.0
        File flags:       0 (Mask 3F)
        File OS:          4 Unknown Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    If you want to confirm the sxwmon64.dll is the issue go to the C:\Windows\System32 folder and rename the sxwmon64.dll to sxwmon64.old.

    You may have to log out and log back in again for the change to take effect.

    Afterwards rename the sxwmon64.old back to sxwmon64.dll and check for updates for the Lumension Endpoint Security software.

    According to the following link VERSION 4.4 SR7 supports IE9 x86 but "IE9 x64 not recommended":

    https://www.lumension.com/kb/582.aspx

    • Marked as answer by Joe.Bawn Sunday, February 22, 2015 5:04 PM
    Sunday, February 22, 2015 4:48 PM

All replies

  • 1 - Please run Norton LiveUpdate

    2 - Reboot

    3 - Test

    Regards,


    Vincenzo Di Russo
    Microsoft® MVP Windows Internet Explorer, Windows & Security Expert - since 2003.
    Moderator in the Microsoft Community and TechNet Forums
    My MVP Profile

    Saturday, February 21, 2015 2:25 PM
  • Hi Vincenzo,

    Thanks for the prompt reply! We do not use Norton, we are running McAfee VirusScan Enterprise + AntiSpyware Enterprise - Version number 8.8.0.1247

    This is only effecting a handful of machines, all over machines are okay with the same setup. 

    Thanks

    Saturday, February 21, 2015 2:45 PM
  • Consider capturing a user-mode dump of the iexplore.exe crash to get more information on the crash and which has the potential to pinpoint the cause.

    You can configure Windows to create user-mode dumps. Create a System Restore Point first.

    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 a 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

    Saturday, February 21, 2015 6:18 PM
  • Hi Auggy,

    I have captured some user-mode dump files - they can be accessed here: https://onedrive.live.com/redir?resid=4B52E61249332635!142&authkey=!AE73wVlWmnedBXE&ithint=folder%2cdmp

    Thanks
    Joe

    Sunday, February 22, 2015 9:08 AM
  • Hi Joe,

    The module that is most likely causing the crash is the sxwmon64.dll:

    *** WARNING: Unable to verify timestamp for sxwmon64.dll
    *** ERROR: Module load completed but symbols could not be loaded for sxwmon64.dll
    *** WARNING: Unable to verify timestamp for ieframe.dll
    *** WARNING: Unable to verify timestamp for iertutil.dll
    *** WARNING: Unable to verify timestamp for iexplore.exe
    Unable to load image C:\Windows\System32\mshtml.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mshtml.dll
    Probably caused by : memory_corruption ( memory_corruption!ole32 )

    Some information on and the location of the sxwmon64.dll which appears to be a component of Lumension Endpoint Security:

    00000001`80000000 00000001`80045000   sxwmon64 T (no symbols)          
        Loaded symbol image file: sxwmon64.dll
        Image path: C:\Windows\System32\sxwmon64.dll
        Image name: sxwmon64.dll
        Timestamp:        Thu Aug 11 11:58:05 2011 (4E43FC0D)
        CheckSum:         0004413E
        ImageSize:        00045000
        File version:     4.4.1564.0
        Product version:  4.4.0.0
        File flags:       0 (Mask 3F)
        File OS:          4 Unknown Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    If you want to confirm the sxwmon64.dll is the issue go to the C:\Windows\System32 folder and rename the sxwmon64.dll to sxwmon64.old.

    You may have to log out and log back in again for the change to take effect.

    Afterwards rename the sxwmon64.old back to sxwmon64.dll and check for updates for the Lumension Endpoint Security software.

    According to the following link VERSION 4.4 SR7 supports IE9 x86 but "IE9 x64 not recommended":

    https://www.lumension.com/kb/582.aspx

    • Marked as answer by Joe.Bawn Sunday, February 22, 2015 5:04 PM
    Sunday, February 22, 2015 4:48 PM
  • Hi Auggy,

    That seemed to do the trick! I will check for updates on Lumension and let you know how I get on. 

    Thanks again!

    Joe

    Sunday, February 22, 2015 5:03 PM
  • You're welcome, and good luck!

    To follow up on the added registry key, you can delete the C:\CrashDumps folder anytime.

    You can leave the added registry key intact or you can delete it anytime if you wish.

    You can run the following .reg file to delete:

    Windows Registry Editor Version 5.00[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\iexplore.exe]

    Sunday, February 22, 2015 5:31 PM