Office 365 apps crashing

Start each affected Office application in Office Safe Mode and test it during normal use; if the crashes stop, disable its add-ins individually to identify the faulty component.

1. Isolate Office add-ins

Safe Mode prevents Office add-ins and some customizations from loading, making it the most relevant untried test after updates, repair, and reinstallation.

1. Press Windows+R.
2. Run the command for an affected application:
   • Excel: excel /safe
   • Word: winword /safe
   • PowerPoint: powerpnt /safe
3. Confirm the title bar shows (Safe Mode).
4. Use the application long enough to determine whether it remains stable.

If it does not crash:

1. Select File > Options > Add-Ins.
2. At the bottom, select COM Add-ins under Manage, then select Go.
3. Record the enabled items, then clear one add-in.
4. Restart the application normally and retest.
5. Repeat until the crash stops. Leave the identified add-in disabled, or obtain an updated version from its publisher.
6. Repeat under any application-specific add-in category shown in the Manage list.

Microsoft specifically documents this Safe Mode and one-at-a-time add-in isolation process for Office crashes.^1^

If the application still crashes in Safe Mode, add-ins are unlikely to be responsible. Do not repeat repair or reinstallation; move to system-level isolation.

2. Test for a background software conflict

A clean boot starts Windows with essential services and startup programs only.

1. Sign in with an administrator account.
2. Search for and open System Configuration (msconfig).
3. On Services, select Hide all Microsoft services, then Disable all and Apply.
4. On Startup, select Open Task Manager.
5. Record the currently enabled startup items, then disable them.
6. Restart Windows and test the affected Office applications.

The PC can temporarily lose functionality while in this state. Do not change options under Advanced boot options.

• Stable during clean boot: Re-enable half the disabled services and startup items at a time, restarting and retesting after each change. Continue dividing the affected group until the conflicting item is isolated.
• Still crashing: The failure is not caused by a disabled third-party service or startup application.
• When finished, open msconfig, select General > Normal startup, restore the recorded startup items, and restart.^2^

3. Check device drivers separately

Checking Windows Update does not necessarily establish that every manufacturer driver is current. If Safe Mode and clean boot do not isolate the issue, check the PC manufacturer for current graphics, printer, mouse, and keyboard drivers. Microsoft identifies older or incompatible device drivers as another Office crash path.^1^

Prioritize graphics or dock/display drivers if the crashes began after firmware, GPU, docking-station, or display changes.

4. Capture a crash dump if no cause is identified

Event Viewer can lack enough detail for a silent exit. Windows Error Reporting (WER) can save a local user-mode dump when the process crashes. This requires administrator rights and changes the registry; use a mini dump first because full dumps can contain document or memory contents.

Open Command Prompt as administrator and configure only the affected executables:

reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\WINWORD.EXE" /v DumpType /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\EXCEL.EXE" /v DumpType /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\POWERPNT.EXE" /v DumpType /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\OUTLOOK.EXE" /v DumpType /t REG_DWORD /d 1 /f

Reproduce the crash, then check:

%LOCALAPPDATA%\CrashDumps

WER uses that location by default, and DumpType=1 requests a mini dump.^3^

Remove the configuration afterward:

reg delete "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\WINWORD.EXE" /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\EXCEL.EXE" /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\POWERPNT.EXE" /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\OUTLOOK.EXE" /f

5. Escalate with the isolated results

For a Microsoft 365 business subscription, an administrator can open Microsoft 365 admin center > Help & support, describe the affected applications, and attach or securely provide:

• Whether each application crashed in Office Safe Mode
• Whether it crashed during a clean boot
• Exact Office build and Windows version
• Crash time and Event Viewer faulting-module details
• The generated .dmp file

The support option requires an administrator and a subscription purchased through Microsoft; partner-purchased subscriptions should be escalated through the partner.^4^

References

1. I get a "stopped working" error when I start Office applications on my PC | Microsoft Support
2. [Windows 10](https://support.microsoft.com/windows/experience/startup-boot/how-to-perform-a-clean-boot-in-windows)
3. Collecting User-Mode Dumps
4. Get support for Microsoft 365 for business