none
Excel 2016 crashes after a debug session RRS feed

  • Question

  • Hello,

    Start Visual Studio - I tried VS 2015 and 2010 - and create any project type, say a Windows Forms Application or Class Library, specify the path to Excel 2016 in the Start External Program property and press {F5}. This starts Excel; [open a workbook and] close Excel. After a delay, Excel crashes with the following record in the Application log:

    Faulting application name: EXCEL.EXE, version: 16.0.6001.1038, time stamp: 0x563492ff
    Faulting module name: ntdll.dll, version: 6.1.7601.19045, time stamp: 0x56258e62
    Exception code: 0xc0000005
    Fault offset: 0x0002e056
    Faulting process id: 0x29d0
    Faulting application start time: 0x01d1268ed3f1d710
    Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE
    Faulting module path: C:\Windows\SysWOW64\ntdll.dll
    Report Id: 177cd265-9282-11e5-84e6-d8fee3a7a654

    I'm ready to provide extra details if required.


    Regards from Belarus (GMT + 3),

    Andrei Smolin
    Add-in Express Team Leader

    Please mark answers and useful posts to help other developers use the forums efficiently.

    Wednesday, November 25, 2015 11:20 AM

All replies

  • Hi Andrei,

    I made a test with your description, but I failed to reproduce your issue. Have you used Excel automation in your Windows Forms Application?

    >> After a delay, Excel crashes with the following record in the Application log

    How did you find Excel crash? Did original opened excel file crashed or after you close this excel file which opened by winform, then open a new excel file, this excel file crashed?

    It would be helpful if you could share us simple code in your winform application and details steps.

    Best Regards,

    Edward


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Thursday, November 26, 2015 1:58 AM
  • Thank you, Edward.

    The point is, there's no custom code in the application. Not a single line.

    > How did you find Excel crash?

    I tried closing Excel without opening a workbook. That is, I press {F5}, Excel starts, shows the Start screen, I close Excel, it closes visually, EXCEL.EXE is shown in the Processes list, after 3-8 seconds I see the "Microsoft Excel is trying to recover your information" window, then it closes, the debug session ends and I see the record in the Application log.


    Regards from Belarus (GMT + 3),

    Andrei Smolin
    Add-in Express Team Leader

    Please mark answers and useful posts to help other developers use the forums efficiently.

    Thursday, November 26, 2015 2:35 PM
  • Hi Andrei,

    I suggest you do as below to make a trouble shooting.

    1. In VS, press ctrl+ F5 to check whether this issue still exist
    2. Click Excel.exe manually to check whether this issue still exist
    3. In your winform project, use Process.start to launch excel application instead of using start external program

    For a general suggestion, I suggest you repair your Office.

    Best Regards,

    Edward


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Friday, November 27, 2015 5:12 AM
  • Hello Edward,

    The situation is worse than that. To start with, it is reproducible on several machines here. Our customers confirm this. I suppose the issue is caused by having Office [2010,] 2013 and 2016 installed on the same machine. To check this I'm going to set up a machine with Office 2016 and some Visual Studio. I'll let you know about my result.


    Regards from Belarus (GMT + 3),

    Andrei Smolin
    Add-in Express Team Leader

    Please mark answers and useful posts to help other developers use the forums efficiently.

    Wednesday, December 2, 2015 2:10 PM
  • Hi Andrei,

    In my option, we could install more than one version of Office on a single computer, but installing multiple Office version is not recommended.

    Please feel free to let us know your result.

    Best Regards,

    Edward


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Friday, December 4, 2015 2:24 AM
  • Hello Edward,

    I confirm getting the same crash when Office 2016 64bit is installed (with no previous Office versions) on Windows 10. I've created a Windows Forms application with no custom code in VS 2015 14.0.2472.00 Update 1. I set the path to EXCEL.EXE in the "Start External program" field and pressed {F5}. Excel starts showing the Start screen. I close Excel and see the details of the crash in the Application log (Event Viewer). Here are the details:

    [QUOTE]
    Faulting application name: EXCEL.EXE, version: 16.0.6001.1038, time stamp: 0x56348f37
    Faulting module name: ntdll.dll, version: 10.0.10240.16430, time stamp: 0x55c59f92
    Exception code: 0xc0000005
    Fault offset: 0x000000000002ebf4
    Faulting process ID: 0x78
    Faulting application start time: 0x01d1327489b2e103
    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report ID: c855b44f-496b-4c0a-8577-1c5b9902e127
    Faulting package full name:
    Faulting package-relative application ID:
    [/QUOTE]

    I've installed an update for Office 2016 and now the crash details are as follows:

    [QUOTE]
    Faulting application name: EXCEL.EXE, version: 16.0.6001.1043, time stamp: 0x564c8d54
    Faulting module name: ntdll.dll, version: 10.0.10240.16430, time stamp: 0x55c59f92
    Exception code: 0xc0000005
    Fault offset: 0x000000000002ebf4
    Faulting process ID: 0x1234
    Faulting application start time: 0x01d1327646b83899
    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report ID: ccc18a5b-f3eb-4583-bf5d-edc889e594d0
    Faulting package full name:
    Faulting package-relative application ID:
    [/QUOTE]


    Regards from Belarus (GMT + 3),

    Andrei Smolin
    Add-in Express Team Leader

    Please mark answers and useful posts to help other developers use the forums efficiently.

    Wednesday, December 9, 2015 11:43 AM
  • I need to add that the issue occurs on all of our machines and also on machines our customers; several of them monitor this topic. Your suggestions don't work for me. The issue only occurs when closing Excel during a debug session. If you need any other details, please let me know.

    Regards from Belarus (GMT + 3),

    Andrei Smolin
    Add-in Express Team Leader

    Please mark answers and useful posts to help other developers use the forums efficiently.

    Wednesday, December 9, 2015 12:18 PM
  • Hi Andrei,

    To narrow down this issue, I suggest you try to run excel from command line to check whether excel will crash.

    Best Regards,

    Edward


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Thursday, December 10, 2015 8:40 AM
  • Sorry for the delay. For me, the issue occurs only when I start Excel 2016 from the Visual Studio IDE; I've made sure there's no Excel extension enabled. The issue doesn't occur if I use the Run command or the Command Prompt; running the latter with or without elevated privileges doesn't make any difference: Excel doesn't fail.

    If you think I can provide any extra info, don't hesitate: I'm ready to help.


    Regards from Belarus (GMT + 3),

    Andrei Smolin
    Add-in Express Team Leader

    Please mark answers and useful posts to help other developers use the forums efficiently.

    Wednesday, December 16, 2015 7:30 AM
  • Hi Andrei,

    >> After a delay, Excel crashes with the following record in the Application log:
    How did you launch your excel when excel crashes with manual, code or with start external program property from VS?

    >> The issue only occurs when closing Excel during a debug session
    If you press ctrl+F5 to run your project without debugging, will this issue still exist?
    What is your VS version, community or ultimate?

    Best Regards,

    Edward


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Thursday, December 17, 2015 7:45 AM
  • I set Start External Program to c:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE. This is reproducible with VS 2010 Premium, VS 2012 Premium, VS 2013 Premium, VS 2015 Professional on a Class Library and Windows Forms Application projects (with no custom code) built on x86 and Any CPU platforms. Windows 7 x64 + Excel 2016 32 bit 16.0.6366.2036. Ctrl+F5 doesn't produce the issue.


    Regards from Belarus (GMT + 3),

    Andrei Smolin
    Add-in Express Team Leader

    Please mark answers and useful posts to help other developers use the forums efficiently.

    Friday, December 18, 2015 12:36 PM
  • Hi Andrei,

    Thank you for posting in the MSDN Forum.  

    I'm trying to involve some senior engineers into this issue and it will take some time. Your patience will be greatly appreciated.  

    Sorry for any inconvenience and have a nice day!

    Best Regards,

    Edward


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Monday, December 28, 2015 5:13 AM
  • Hi @all,

    I am experiencing almost same beheaviour in Word 2016:

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Application Error" /> 
      <EventID Qualifiers="0">1000</EventID> 
      <Level>2</Level> 
      <Task>100</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2016-01-29T08:46:34.341551500Z" /> 
      <EventRecordID>17612</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>Vetinari.scheibenwelt.local</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>WINWORD.EXE</Data> 
      <Data>16.0.6366.2056</Data> 
      <Data>568f31f0</Data> 
      <Data>ntdll.dll</Data> 
      <Data>10.0.10586.20</Data> 
      <Data>5654262a</Data> 
      <Data>c0000005</Data> 
      <Data>00032bee</Data> 
      <Data>1684</Data> 
      <Data>01d15a712e7053cd</Data> 
      <Data>C:\Program Files (x86)\Microsoft Office\root\Office16\WINWORD.EXE</Data> 
      <Data>C:\Windows\SYSTEM32\ntdll.dll</Data> 
      <Data>703dfdc5-ab08-4765-a86d-ce1789c80153</Data> 
      <Data /> 
      <Data /> 
      </EventData>
      </Event>


    Specialized in data encryption, digital signature, smart card management, electronic invoicing, VSTO & Sharepoint development, Windows 8 Apps, Windows Phone Apps, http://www.bogad.at

    Friday, January 29, 2016 8:56 AM
  • is there any new information or workaround about this issue?

    Tuesday, April 5, 2016 7:51 AM
  • I am able to reproduce a very similar case.  This only happens with Office 2016.  I have both Office 2013 and Office 2016 on my machine.  I develop an add-in for Microsoft Office, so my debugging is all done by starting an external program and launching Excel.

    When I am debugging (F5) and I close Excel, after a few seconds I get "Microsoft Excel has stopped working".  If I do ctrl+F5 the problem does not occur.  If I run Excel outside of the debugger it does not occur.  I am using Visual Studio 2015, but I went back to an older project using Visual Studio 2013 and was able to reproduce it there as well.  I don't recall having this issue in the past, it has only started recently, perhaps that indicates that it was introduced by an update to Excel 2016?

    The details are as follows:

    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: EXCEL.EXE
      Application Version: 16.0.6001.1073
      Application Timestamp: 56ff9482
      Fault Module Name: mso20win32client.dll
      Fault Module Version: 0.0.0.0
      Fault Module Timestamp: 56ff90bd
      Exception Code: c0000005
      Exception Offset: 000b3653
      OS Version: 6.1.7601.2.1.0.256.4
      Locale ID: 1033
      Additional Information 1: 5219
      Additional Information 2: 52196d166e6c9fc5ff5dfddef865a032
      Additional Information 3: 4e16
      Additional Information 4: 4e16aa66b00474d6b6c9f9062bd1b72a

    Tuesday, April 26, 2016 8:41 PM
  • Experiencing the same problem.

    Event Details are:-

    

    Faulting application name: EXCEL.EXE, version: 16.0.6001.1073, time stamp: 0x56ff9482
    Faulting module name: EMET.DLL, version: 5.2.0.1, time stamp: 0x5503c3e4
    Exception code: 0xc0000005
    Fault offset: 0x00063f82
    Faulting process id: 0x1d64
    Faulting application start time: 0x01d1aa8ae217806a
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE
    Faulting module path: C:\Windows\AppPatch\EMET.DLL
    Report Id: dcebd20b-1681-11e6-a4cf-463500000031

    - System
    - Provider
    [ Name] Application Error
    - EventID 1000
    [ Qualifiers] 0
    Level 2
    Task 100
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2016-05-10T07:36:10.000000000Z
    EventRecordID 38876
    Channel Application
    Computer CSCGBRAE691469.fcg.com
    Security
    - EventData
    EXCEL.EXE
    16.0.6001.1073
    56ff9482
    EMET.DLL
    5.2.0.1
    5503c3e4
    c0000005
    00063f82
    1d64
    01d1aa8ae217806a
    C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE
    C:\Windows\AppPatch\EMET.DLL

    dcebd20b-1681-11e6-a4cf-463500000031

    Tuesday, May 10, 2016 7:41 AM
  • I have also just walked into this issue myself. I too have tested whether it was to do with our own add-in but have come to the same conclusion as everyone else, that it will throw the exception even on clean built machine with just Visual Studio and Office 2016.

    Upon attaching a third party debugger to Excel, i received the following exceptions upon close:

    First chance exception on 8F328C7A (C0000008, EXCEPTION_INVALID_HANDLE)!

    First chance exception on 77D0DC0E (C0000005, EXCEPTION_ACCESS_VIOLATION)! - Originating from ntdll.dll

    Is there any update regarding this issue?

    Thursday, June 30, 2016 11:59 AM