none
Excel 2016 randomly crashes - restarts RRS feed

  • Question

  • Faulting application name: EXCEL.EXE, version: 16.0.6366.2062, time stamp: 0x569c4dbe
    Faulting module name: ntdll.dll, version: 10.0.10586.20, time stamp: 0x5654262a
    Exception code: 0xc0000374
    Fault offset: 0x000dc089
    Faulting process id: 0x13f8
    Faulting application start time: 0x01d158d62f580907
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE
    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
    Report Id: e985866e-5702-4742-ba6f-1013249d309c
    Faulting package full name: 
    Faulting package-relative application ID: 

    Can't tell on which part of Code it crashes, but sometimes it works normal, and sometimes crash + restart., try {} Catch does not help.

    Wednesday, January 27, 2016 8:50 AM

All replies

  • Hi,

    Would you inform the further detail of your issue?
    Especially, when crashed and what did you do at that time.
    And also your system environment.
    Regards.
    Wednesday, January 27, 2016 9:21 AM
  • Hi,

    Would you inform the further detail of your issue?
    Especially, when crashed and what did you do at that time.
    And also your system environment.
    Regards.

    Windows 10 Enterprise - 64 bit,

    I was using VSTO Excel Add-in, that function i used opens workbook, collects information, converts strings/numbers closes workbook, again opens other workbook and so on... But it's not always crashes.

    And after this crash i can't open ANY Excel file got error: http://prntscr.com/9veyoj, tried restart PC not helped. Tried Repair - not helped. Tried online repair - NOT HELPED. But i can open blank Excel workbook. Tried to open VSTO Add-in - its working, and i can open all files using Add-in functions, but if i tried to open file manually got same error. After i closed Add-in again only blank document opens..

    Wednesday, January 27, 2016 9:56 AM
  • Hi,

    Thanks for your quick explanation.

    I'd ask you some.
      1. Did you consult with who had made the VSTO Add-in?
      2. What does it mean by "Repair"?  Repair Excel 2016? or workbooks?
      3. Do other PCs have the same issue?  Only your machine?

    Regards.

    Wednesday, January 27, 2016 10:14 AM
  • 1. It's is my VSTO Add-In. On Excel 2007/2010 no Excel crashes a lot of users using and got no complains. 

    2. Sry, 'Quick Repair', and Later 'Online Repair' via 'Programs and Features' -> 'Change'

    3. Actually crashing on Excel 2013 it is very rare scenario, on Excel release version i was terrible and very common thing to see 'Microsoft Excel has stop working...' and only after lot of updates it's working almost fine. But on new Excel 2016 crashing - restarting it's not very rare, happens few times per day. And as i said in my c# code i'm always using Try{}Catch..

    And it's first time then i can't open my Excel documents - "There was a problem sending the command to the program", all add-ins disabled i just double click on any file.. even if i create new that not helps..

    sry for my english.


    Wednesday, January 27, 2016 10:31 AM
  • Hello Julius,

    What line of code exactly causes Excel crash? Do you run another threads?

    Are you able to reproduce the issue with a newly created empty add-in project?

    Make sure you release all underlying COM objects in the code instantly. Use System.Runtime.InteropServices.Marshal.ReleaseComObject to release an Excel object when you have finished using it. Then set a variable to Nothing in Visual Basic (null in C#) to release the reference to the object. Read more about that in the Systematically Releasing Objects article.

    Wednesday, January 27, 2016 11:21 AM
  • Hello Julius,

    What line of code exactly causes Excel crash?

    Can't tell because i don't know. Developer PC is on 'Excel 2007' which works fine without any errors. At procedure i made try{} catch.. but it does not catch anything because i made messageBox.show, excel just stops responding and restarts by it self.

    Trying to reinstall Office on that machine which is not opening Excel documents.

    And.. check it--> http://prntscr.com/9vfydf

    Wednesday, January 27, 2016 11:31 AM
  • Hi Julius,

    Normally, the VSTO add-in run under its application domain, the domain crash shouldn't affect the Excel application.

    Did you communicate with other application in the add-in? And which operation cause the crashes? I suggest that you debug the code to narrow down which line of code cause this issue so that we can understand the issue and provide some helpful suggestions.

    Regards & Fei


    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, January 28, 2016 1:52 AM
    Moderator
  • We are seeing the same issue. For us, Excel 2016 64 bit crashes on exit when using our addin. You can normally work and everything, but when you close down Excel you get and "Excel has crashed" message box.

    Other versions of Excel, as well as Excel 2016 32 bit, do not have this issue.

    Were are getting a different Exception code though:

    Faulting application name: EXCEL.EXE, version: 16.0.6001.1034, time stamp: 0x561f40a3
    Faulting module name: ucrtbase.DLL, version: 10.0.10240.16384, time stamp: 0x559f3851
    Exception code: 0x40000015
    Fault offset: 0x0000000000065a5f
    Faulting process id: 0x450
    Faulting application start time: 0x01d11b8cf0fd7651
    Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE
    Faulting module path: C:\Program Files\Microsoft Office\Root\Office16\ucrtbase.DLL
    Report Id: 431089f1-8780-11e5-90cb-001c42be5d20



    Thursday, January 28, 2016 2:54 PM
  • I remember this was an issue with OFFICE 2013 and updates were provided for the fix.

    https://support.microsoft.com/en-us/kb/2968204

    Please check for the updates if it helps.


    A user friendly computer first requires a friendly user

    Thursday, January 28, 2016 3:28 PM
  • Hi Julius,

    Normally, the VSTO add-in run under its application domain, the domain crash shouldn't affect the Excel application.

    Did you communicate with other application in the add-in? And which operation cause the crashes? I suggest that you debug the code to narrow down which line of code cause this issue so that we can understand the issue and provide some helpful suggestions.

    Regards & Fei


    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.


    Well it crashes, the only thing what can i give or do it's Event Logs after crash, I can't debug or say on which code line the issue is, because vsto add-in running on different pc. My vsto add-in created on VS2010, .NetFrameWork 3.5, Excel 2007 and only for 32-bit office, and i can't upgrade it cause a lot of users still using 2007, 2010 Excel..

    Hi bahushekh,
    it's up to date! :) If someone says my excel crashed its the first thing I'm check it's Excel version.
    Friday, January 29, 2016 6:45 AM
  • Hi Julius,

    Thanks for the detail explanation.

    Would you minding provide a sample code and steps to help us to reproduce this issue and for the further investigation.

    Regards & Fei


    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, February 1, 2016 7:58 AM
    Moderator
  • Hi Julius (and Fei Xui),

    A friend of mine is running into an Excel 2016 crash which seems very similar to that reported here.

    One of the Application Error events in the event log look like this:

    Faulting application name: EXCEL.EXE, version: 16.0.6568.2025, time stamp: 0x56b3ae2c
    Faulting module name: ntdll.dll, version: 10.0.10586.103, time stamp: 0x56a853dc
    Exception code: 0xc0000374
    Fault offset: 0x000dc759
    Faulting process id: 0x280c
    Faulting application start time: 0x01d170106f855865
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE
    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
    Report Id: f4b2f93d-ec42-46c2-845f-311ef659a563
    Faulting package full name:
    Faulting package-relative application ID:

    I notice that my friend is getting the same error - 0xc0000374 means STATUS_HEAP_CORRUPTION (in ntstatus.h). I don't know whether the ntdll.dll is significant, or whether that is just where the heap corruption is detected. 

    He is also using Excel 2016 (32-bit) on Windows 10 (64-bit).

    I see that he has a slightly higher patch version of Excel 2016 and Windows 10 than Julius had, but the versions are very close.

    The crash occurs after some minutes (not after exactly the same time, but it consistently crashes) when executing a long-running VBA macro that manipulates a workbook and recalculates. There is no VSTO add-in involved. The same workbook and VBA routines continues to work perfectly on Excel 2010 on another machine.

    Different to Julius, after a crash, restarting Excel works fine. We don't see any problem opening files after the crash.

    We will try to work towards a reproducible case too - a smaller book and VBA macro that we can submit to Microsoft for analysis.

    @Fei Xue - It would be a great help to find out from the Microsoft crash telemetry data whether there have been more heap corruption crashes in Excel 2016.

    Regards,

    Govert

    Excel-DNA - Free and easy .NET for Excel

    Friday, February 26, 2016 12:06 PM
  • Hi all

    Just wanted to share my experience until now with:
    Windows 10 64bit + Excel 16 32bit

    Unfortunately I was not able to solve issue or replicate on other laptops

    Some time back I started similar thread. Excel on my laptop crashes or restarts unexpectedly. If interested, please refer to thread "Out of memory and VBA project password after saving"
    Frankly issues described in this thread are still annoying even though I tried to "repair" and re-installed MS Office.

    Here is the list of issues:
    Complete crash: when "fill effects..." are used in "Conditional formatting" and I click "Manage rules"

    Excel crashes and restarts:
    When VBA project is open and in a workbook I have blank "User form", NO VBA code at all - if you exit and click save "Out of memory" is displayed.

    Unexpected crash:
    Sometimes having 2 or 3 workbooks open Excel closes unexpectedly. (Complex file can be damaged in such event.)

    I also thought Add-ins could be a reason, but that is not true. I uninstalled all add-ins - no result
    I personally believe this issue has nothing to do with Add-ins and it could be big bug :) in Excel 16 -32 bit

    Regards and good luck finding solution. Hope it will be useful with case on my laptop too

    Gio

    Friday, February 26, 2016 5:37 PM
  • Hi Gio, After an Excel crash, you can go to the Application Log in the Windows Event Viewer, and get more details on the crash. The Exception Code there will indicate what type of error it was. I thonk posting more information on the specific errors you get will help. -Govert
    Sunday, February 28, 2016 2:20 PM
  • Deleted
    Wednesday, March 2, 2016 11:02 PM
  • I have been having ongoing issues for months now.  I have tried reinstalling office many times.  The last time it worked without error for a couple of weeks but has now come back.  This is the latest error.

    I am at a loss to solve this one and have to keep saving my document every minute or so in case it crashes.  Not fun.

    Faulting application name: EXCEL.EXE, version: 16.0.6568.2025, time stamp: 0x56b3ae2c
    Faulting module name: ntdll.dll, version: 10.0.10586.122, time stamp: 0x56cc16f5
    Exception code: 0xc0000374
    Fault offset: 0x000dc7a9
    Faulting process id: 0xbe8
    Faulting application start time: 0x01d175d246003190
    Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE
    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
    Report Id: e234faf2-6a0f-4f4e-a332-c45358207527
    Faulting package full name: 
    Faulting package-relative application ID: 

    Friday, March 4, 2016 6:05 AM
  • Same for me also. Only noticed it happening in the last couple of weeks, but its exactly the same as the previous posts:

    Faulting application name: EXCEL.EXE, version: 16.0.6568.2025, time stamp: 0x56b3ae2c
    Faulting module name: EXCEL.EXE, version: 16.0.6568.2025, time stamp: 0x56b3ae2c
    Exception code: 0xc0000005
    Fault offset: 0x004b62c7
    Faulting process ID: 0x173c
    Faulting application start time: 0x01d18fe3f399de70
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE
    Faulting module path: C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE
    Report ID: 5577e1a1-fc07-11e5-8299-d8cb8a7c08ab
    Faulting package full name: 
    Faulting package-relative application ID: 

    Wednesday, April 6, 2016 3:12 PM
  • Just to jump on the bandwagon, we are having similar Excel crashes, on multiple machines and for multiple users.  Win10x64Ent

    Sample Event Log entries:

    Faulting application name: EXCEL.EXE, version: 16.0.4393.1000, time stamp: 0x573b3066
    Faulting module name: ntdll.dll, version: 10.0.10586.306, time stamp: 0x571af2eb
    Exception code: 0xc0000005
    Fault offset: 0x000000000002fe34
    Faulting process id: 0x2248
    Faulting application start time: 0x01d1e0f2871b285b
    Faulting application path: C:\Program Files\Microsoft Office\Office16\EXCEL.EXE
    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
    Report Id: d6ddb663-4d25-11e6-b5bb-801934265e43
    Faulting package full name: 
    Faulting package-relative application ID: 

    Faulting application name: EXCEL.EXE, version: 16.0.4393.1000, time stamp: 0x573b3066
    Faulting module name: KERNELBASE.dll, version: 10.0.10586.306, time stamp: 0x571af331
    Exception code: 0xe0000003
    Fault offset: 0x0000000000071f28
    Faulting process id: 0x2b04
    Faulting application start time: 0x01d1e1ae44e923a0
    Faulting application path: C:\Program Files\Microsoft Office\Office16\EXCEL.EXE
    Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
    Report Id: 0d6a7500-ca85-4579-a8b9-9193afae556b
    Faulting package full name: 
    Faulting package-relative application ID: 

    Any assistance on this would be awesome!

    Wednesday, July 20, 2016 8:53 PM
  • We also see the error to many times. Is there a fix allready?

    Naam van toepassing met fout: EXCEL.EXE, versie: 16.0.4456.1003, tijdstempel: 0x58139d4f
    Naam van module met fout: ntdll.dll, versie: 10.0.14393.447, tijdstempel: 0x5819be95

    Uitzonderingscode: 0xc0000374

    Foutmarge: 0x000d98c1

    Id van proces met fout: 0x1954

    Starttijd van toepassing met fout: 0x01d2455f0d0903df

    Pad naar toepassing met fout: C:\Program Files (x86)\Microsoft Office\Office16\EXCEL.EXE

    Pad naar module met fout: C:\WINDOWS\SYSTEM32\ntdll.dll

    Rapport-id: 4706434e-a1ab-40a5-bdc3-f0ef49e0708f

    Thursday, November 24, 2016 6:54 AM
  • Apparently no as we are still seeing this error. nobody seems to be willing or able to tackle this at Microsoft. Maybe put more manpower on writing decent code instead of creating new (buggy) features?
    Monday, March 6, 2017 1:01 PM
  • I know this is an old thread but did anyone get anywhere with this? I have a heavy VBA workbook (plenty of userforms, conditional formation, etc.) that works fine on Excel 2010 and seems to sputter on 2013 and now 2016. Randomly shuts down & restarts (usually after a macro completes). 

    Windows Event viewer: 

    Faulting application name: EXCEL.EXE, version: 16.0.11601.20144, time stamp: 0x5cc36cc8

    Faulting module name: ntdll.dll, version: 10.0.16299.665, time stamp: 0xa06372a8

    Exception code: 0xc0000374

    Fault offset: 0x000da2a9

    Faulting process id: 0x6588

    Faulting application start time: 0x01d50a846fef6cf1

    Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE

    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

    Report Id: 3bcf94ba-855d-443a-b393-a04c95d192e6

    Faulting package full name:

    Faulting package-relative application ID:

    Faulting application name: EXCEL.EXE, version: 16.0.11601.20144, time stamp: 0x5cc36cc8

    Faulting module name: EXCEL.EXE, version: 16.0.11601.20144, time stamp: 0x5cc36cc8

    Exception code: 0xc0000005

    Fault offset: 0x000b9116

    Faulting process id: 0x48ac

    Faulting application start time: 0x01d50a858ede756d

    Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE

    Faulting module path: C:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE

    Report Id: ffdb897c-45e2-4d67-900a-ce0b1084d68b

    Faulting package full name:

    Faulting package-relative application ID:

    Any suggestions would be great.

     
    Tuesday, May 14, 2019 7:33 PM
  • Try out the below mentioned steps to fix the crashing issue of excel:     

    1. Remove COM add-ins.

    2.Remove MS excel animation.

    3.Explore excel file details and contents.

    4. Run Excel in safe mode.

    For further details follow the link given below:

    http ://www.repairexcel.com/blog/how-to-stop-excel-from-crushing

    F

    Wednesday, August 14, 2019 6:40 AM
  • Hello Julius Bank,

    you could use procdump from sysinternals to get a Dump.

      Hendrik

    Thursday, August 15, 2019 1:16 PM