Outlook Add-In Causing Crashes: How to Identify the Problem Add-In With Event Viewer

Outlook can crash or freeze when a faulty add-in loads. This often happens after installing new software or an Outlook update. The crash is triggered by an add-in that has compatibility or code issues. This guide shows you how to use the Windows Event Viewer to find the exact add-in causing the problem.

You will learn to locate the crash log, interpret the error details, and identify the responsible add-in’s file name. Following the steps will let you disable the problematic component and restore Outlook stability.

Why Add-Ins Cause Outlook to Crash

Add-ins are small programs that extend Outlook’s functionality, like adding a PDF toolbar or CRM integration. They load directly into the Outlook process when the application starts. If an add-in contains buggy code, conflicts with another add-in, or is not compatible with your current version of Outlook or Windows, it can cause the main Outlook.exe process to fail.

This failure generates a crash report that Windows logs automatically. The Event Viewer application is the central tool in Windows for reading these system and application logs. The log entry for an Outlook crash will specify the exact module, which is a .dll or .exe file, that was active when the fault occurred. This module name is almost always the add-in itself.

How Event Viewer Captures the Crash Data

When Outlook stops working, Windows Error Reporting creates an event. This event is stored in the Application log with a source of “Application Error” or “.NET Runtime”. The event details include critical technical data like the Faulting Application, which will be OUTLOOK.EXE, and the Faulting Module. The Faulting Module path points to the file on your disk, allowing you to trace it back to a specific vendor’s add-in.

Steps to Find the Crashing Add-In in Event Viewer

Follow these steps after Outlook crashes. Do not restart Outlook first, as you need to check the log for the most recent error.

1. Open Windows Event Viewer
   Press the Windows key, type “Event Viewer”, and select the app. You can also open the Run dialog with Windows key + R, type eventvwr.msc, and press Enter.
2. Navigate to the Application Log
   In the left pane, expand “Windows Logs” and click on “Application”. This log shows events from all desktop applications, including Outlook.
3. Find the Outlook Crash Event
   Look at the list of recent events in the center panel. Click the “Date and Time” column header to sort by newest first. Scan for events with a source of “Application Error” and where the “Faulting application” name is OUTLOOK.EXE. The Level will be “Error” and it will have a red circle with a white X icon.
4. Examine the Event Details
   Double-click the error event to open its Properties window. Click on the “Details” tab and select “Friendly View” if available. Look for these key fields:
   – Faulting application: OUTLOOK.EXE
   – Faulting module path: This is the crucial line. It will show a file path ending in a .dll or .exe name, like C:\Program Files\Vendor\AddInName.dll.
5. Identify the Add-In from the Path
   The file name in the Faulting Module path is the crashing add-in. Common locations are C:\Program Files\Microsoft Office\root\Office16\ADDINS\ or C:\Users\[YourName]\AppData\ folders. Note the full name of the .dll file.
6. Confirm by Starting Outlook in Safe Mode
   Close Event Viewer. Press Windows key + R, type outlook.exe /safe, and press Enter. If Outlook starts without crashing, an add-in is confirmed as the cause. You can now disable the specific one you identified.

If the Crash Log Is Unclear or Missing

Event Viewer Shows No Recent Outlook Errors

If you cannot find an error, the crash might be logged under a different source like “.NET Runtime” or “Windows Error Reporting”. Use the “Filter Current Log” option on the right pane. Check the box for “Error” level and try entering “Outlook” or “.exe” in the includes field. Also, ensure you are looking at the correct time of the crash.

The Faulting Module is a Core Microsoft File

Sometimes the Faulting Module is a system file like ntdll.dll or a core Office file. This usually indicates the add-in caused a deeper system conflict, but the add-in itself may not be named. In this case, use Outlook’s built-in disable method. Go to File > Options > Add-ins. At the bottom, set “Manage” to “COM Add-ins” and click Go. Disable all add-ins, restart Outlook normally, and then re-enable them one by one until the crash returns.

Outlook Crashes Immediately on Startup

If Outlook crashes too fast to use Event Viewer, boot Windows in Safe Mode with Networking. Then start Outlook normally. If it works, a startup application or driver is interfering. You can also use the System Configuration tool (msconfig) to perform a clean boot, which disables all non-Microsoft services and startup items, helping to isolate the conflict.

Add-In Diagnosis Methods Compared

Diagnosis Method	Using Event Viewer	Using Outlook’s Disable List
Primary Use	Identify the exact faulty file after a crash	Isolate the problem when no clear log exists
Speed	Fast if log is clear	Slower, requires multiple restarts
Technical Skill Required	Moderate	Low
Certainty of Result	High, points to specific file	High, but process of elimination
Outlook Safe Mode Required	Only for final confirmation	Required to access the add-ins list initially

After identifying the add-in, open Outlook in Safe Mode again. Go to File > Options > Add-ins. Select COM Add-ins and click Go. Uncheck the box for the add-in you found in the Event Viewer log. Click OK and restart Outlook normally. Your crashes should stop. Consider checking the add-in vendor’s website for an updated version. For a permanent solution, keep the add-in disabled or remove it via Control Panel > Programs and Features if it is no longer needed.