Fault application excel exe

Thanks to @jkpieterse and @Comintern for advice.

The reasons for the problem were identified as migrating to Excel 2016 64 bit while using 32 bit controls and VBA code.

In the end there were a number of changes we had to make to prevent Excel crashing.

1) Removing all code and object references to the ListView object.

2) Following guidelines in this Microsoft article for ensuring VBA compatibility with Office 2016 64 bit: https://learn.microsoft.com/en-us/office/client-developer/shared/compatibility-between-the-32-bit-and-64-bit-versions-of-office

3) We ultimately contacted Microsoft support who recommended that to avoid the issue where Excel crashes, that we install a new registry key in:

HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0ExcelOptions

Name: ForceVBALoadFromSource
Type: DWORD
Value = 1

(See Knowledge base article: https://support.microsoft.com/en-gb/help/4011597/december-5-2017-update-for-excel-2013-kb4011597)
They explained that this is a fix Microsoft have rolled out to force Excel to compile VBA fully on 64 bit systems which prevents problems when 32 bit code partially compiles.

Obviously you should backup your registry and create a restore point before applying this fix (and check with your Tech department if you have one!)

Prior to the support call I’d narrowed down the point of the crash to when a particular form was called. Prior to this point the VBA code was running fine, an ADODB connection had been successfully made to a SQL Server database with data being returned. When the form was called the application crashed. If I loaded a different form, the application did not crash implying there were other controls or code causing a compile error or conflict.

Also, I identified that the application did not crash if the Visual Studio Editor window was already open. I was able to add a line of code to programmatically open the VBE window (plus some to resize it so it did not hide the form):

Application.VBE.MainWindow.Visible = True
With Application.VBE.MainWindow
    .Width = 500
    .Height = 500
End With

After adding this code, the application did not crash either.

The problem form was too complex to recreate without a significant cost in development. fortunately the Microsoft fix has resolved the problem.

Microsoft Excel has stopped working.
Microsoft Word has stopped working.
Microsoft Outlook has stopped working.
Microsoft PowerPoint has stopped working.

Hi Friends,

Like you, I faced this problem after I upgraded my MS Office 2010 to MS Office 2013 and spent plenty amount of hours trying to fix it.
YES IT’S FRUSTRATED! Just look at the screenshot of me trying to find a solution on this:

Event Viewer Errors:

(might be varies from you, but you get the picture)

Faulting application name: EXCEL.EXE, version: 15.0.4420.1017, time stamp: 0x50673286
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x70c
Faulting application start time: 0x01ce148bae1be7ed
Faulting application path: C:Program Files (x86)Microsoft OfficeOffice15EXCEL.EXE
Faulting module path: unknown
Report Id: ec6f1ad1-807e-11e2-ba40-4437e69e70e1

Faulting application name: WINWORD.EXE, version: 15.0.4420.1017, time stamp: 0x5067349a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x588
Faulting application start time: 0x01ce13fb6fe1ad27
Faulting application path: C:Program Files (x86)Microsoft OfficeOffice15WINWORD.EXE
Faulting module path: unknown
Report Id: ae8f3bec-7fee-11e2-90f9-4437e69e70e1

Faulting application name: OUTLOOK.EXE, version: 15.0.4420.1017, time stamp: 0x506734e2
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x8cc
Faulting application start time: 0x01ce13f3e5651137
Faulting application path: C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE
Faulting module path: unknown
Report Id: 27012797-7fe7-11e2-bcd6-4437e69e70e1

The description for Event ID 0 from source MSOIDSVC.EXE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

InitializeSvcAPI failed with hr = 0x80048883

By the way, just for your information; I’m running Windows 7 Professional 64-bit and Microsoft Office 2013 Standard 32-bit.

The Solutions

I have 2 known fixes here; before trying anything, please make sure you can run excel/winword/powerpoint/outlook in safe mode, otherwise these 2 fixes is not for you. I’ll use Excel for example.

Press Win + R for run, then enter excel /safe

If Excel 2013 successful run in safe mode, proceed with the fixes, else go back to Google. Good luck.

Fix 1: If you have an Epson Scanner / ABBYY-FineReader

(ABBYY-FineReader is a software bundled together with Epson Scanner)

Fix 1a
1. Run Excel in safe mode. (Win + R ; «excel /safe«)
2. Go to File — Options
3. Go to Add-ins
4. Choose COM Add-ins and press Go…
5. Uncheck every box and press OK.
Try to run Excel normally now.

Fix 1b
1. Go to Control Panel
2. Click on Uninstall a program
3. Right click on ABBYY-FineReader and click uninstall.
4. Restart if necessary.
Try to run Excel normally now.

Update: another fix for ABBYY-FineReader
Open ABBYY-FineReader, go to the help menu and search for new updates. Download the newest update. Uninstall ABBYY-FineReader and then reinstall it with the newly downloaded update. Now ABBYY-FineReader works flawlessly scanning into Word and Excel. Also, the newest update does not use add-ins to do it.
(thanks to Anonymous commenter on August 1, 2015)

Fix 2: Disable hardware acceleration

(This fixed MY problem!)

1. Run regedit (Win + R ; «regedit«)
2. Browse to HKEY_CURRENT_USERSoftwareMicrosoftOffice15.0Common
3. Create a New Key and name it «Graphics«
4. Select Graphics, right-click on the right panel and create a New DWORD (32-bit) Value and name it DisableHardwareAcceleration.
5. Enter Value data as 1
Try to run Excel normally now.

For some reason, if you’re using any USB docking station with DisplayLink driver, please uninstall or update the driver to atleast version 7.1 M1.
Link to download: http://www.displaylink.com/support/downloads.php

Good luck!

Give me a Like, a +1 or just drop a comment if this fix yours!

Regards,
Jo.