none
Internet Explorer Crashing RRS feed

  • Question

  • Hi,

    Windows 7 SP1 Enterprise edition is installed with Internet Explorer 11. 

    It works for some time and crashes. User works on the Five 9 Softphone in the Internet Explorer. Share the procedure to capture the IE Crash dumps and how the dump can be analyzed. 


    Regards, Boopathi

    Friday, April 13, 2018 4:06 PM

Answers

  • hi,

    Thanks for posting.

    For your issue, you could try the following suggestion to capture the IE crash dumps and analyse the dumps.

    Windows Error Reporting

    Crash dumps are a valuable resource for us and Windows 7 provides us with some great features for generating crash dumps through Windows Error Reporting (WER).

    The registry key (LocalDumps) is not created by default for us in the registry so you will have to roll up your sleeves and do the dirty work yourself. 

    If a Mini dump is too small or a full dump is too big then we have the option of creating a Custom dump. When the DumpType is set to 0, we are indicating to WER that we would like to generate the dump using the value in CustomDumpFlags. 

    Program Database Files (PDB)

    Whenever you compile an application using either Debug or Release configuration, a PDB file will be generated along with the Portable Executable. 

    Creating an Application to Crash

    To do this we will create a Console application that generates a NullReferenceException. 

       1.  Open Visual Studio 2010
       2.  File->New Project and select Console Application from the Visual Studio Templates
       3.  Name the Application CrashDumpTest and click OK
       4.  Switch the configuration from Debug to Release using the Configuration Manager

    Here is where we will create an object of type generic List(Of String). We will not use the New keyword and as a result our List will contain a Null Reference. We then will try to add an item to the list. Navigate to the Main method of the console application and add the following code.

    After the application has been built do the following:

        1.  Navigate to the Release Folder which was the destination for your build
        2.  Open Windows Explorer and create a Folder on the C Drive called Temp
        3.  Copy CrashDumpTest.exe and CrashDumpTest.pdb to the Temp folder  

    Now to execute CrashDumpTest.exe and generate a Crash Dump.

    Rather than debugging the program from here, we will choose Close Program and try to simulate the scenario where a user of your application has sent you the dump file and we will open the dump file directly from the file system in Visual Studio 2010.

    Opening and Analyse a Dump File in Visual Studio 2010

     1.  Open Visual Studio 2010

     2.  File->Open File, navigate to your Dump folder and select the CrashDumpTest dump file, and then click the Debug with Mixed

    3.  Select Break, and in the next Call Stack window, Select on the menu Debug->Windows->Call Stack

    4.  To specify the location of your PDB File, on the Menu choose Debug->Options and Settings

    5.  Select the Symbols tree item that is located under the Debugging tree item. You can add a folder to the Symbol file (.pdb) locations by clicking the yellow folder button, Click OK to close the dialog



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

    Harap diingat untuk menandai balasan sebagai jawaban jika mereka membantu.
    Jika Anda memiliki umpan balik untuk TechNet Subscriber Support, hubungi tnmff@microsoft.com

    Monday, April 16, 2018 7:41 AM

All replies

  • hi,

    Thanks for posting.

    For your issue, you could try the following suggestion to capture the IE crash dumps and analyse the dumps.

    Windows Error Reporting

    Crash dumps are a valuable resource for us and Windows 7 provides us with some great features for generating crash dumps through Windows Error Reporting (WER).

    The registry key (LocalDumps) is not created by default for us in the registry so you will have to roll up your sleeves and do the dirty work yourself. 

    If a Mini dump is too small or a full dump is too big then we have the option of creating a Custom dump. When the DumpType is set to 0, we are indicating to WER that we would like to generate the dump using the value in CustomDumpFlags. 

    Program Database Files (PDB)

    Whenever you compile an application using either Debug or Release configuration, a PDB file will be generated along with the Portable Executable. 

    Creating an Application to Crash

    To do this we will create a Console application that generates a NullReferenceException. 

       1.  Open Visual Studio 2010
       2.  File->New Project and select Console Application from the Visual Studio Templates
       3.  Name the Application CrashDumpTest and click OK
       4.  Switch the configuration from Debug to Release using the Configuration Manager

    Here is where we will create an object of type generic List(Of String). We will not use the New keyword and as a result our List will contain a Null Reference. We then will try to add an item to the list. Navigate to the Main method of the console application and add the following code.

    After the application has been built do the following:

        1.  Navigate to the Release Folder which was the destination for your build
        2.  Open Windows Explorer and create a Folder on the C Drive called Temp
        3.  Copy CrashDumpTest.exe and CrashDumpTest.pdb to the Temp folder  

    Now to execute CrashDumpTest.exe and generate a Crash Dump.

    Rather than debugging the program from here, we will choose Close Program and try to simulate the scenario where a user of your application has sent you the dump file and we will open the dump file directly from the file system in Visual Studio 2010.

    Opening and Analyse a Dump File in Visual Studio 2010

     1.  Open Visual Studio 2010

     2.  File->Open File, navigate to your Dump folder and select the CrashDumpTest dump file, and then click the Debug with Mixed

    3.  Select Break, and in the next Call Stack window, Select on the menu Debug->Windows->Call Stack

    4.  To specify the location of your PDB File, on the Menu choose Debug->Options and Settings

    5.  Select the Symbols tree item that is located under the Debugging tree item. You can add a folder to the Symbol file (.pdb) locations by clicking the yellow folder button, Click OK to close the dialog



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

    Harap diingat untuk menandai balasan sebagai jawaban jika mereka membantu.
    Jika Anda memiliki umpan balik untuk TechNet Subscriber Support, hubungi tnmff@microsoft.com

    Monday, April 16, 2018 7:41 AM
  • Thank you for the Steps. It will be helpful for capturing and analyzing dumps

    Regards, Boopathi

    Monday, April 16, 2018 2:28 PM