Why did Outlook crash?

How can I find more information about why Outlook crashed?

In the Event Viewer you can often find out more information about why Outlook crashed. The Event Viewer is a general location in Windows itself where applications and Windows can write status events when for instance a service is started/stopped, an application is launched or closed, if a backup was successful, who logged on to the system, etc… It also contains events for when an application unexpectedly stopped or crashed.

Open Event Viewer
There are quite a few number of ways to open it. Some of them are;

  • Start-> Run; eventvwr
  • Start-> Control Panel (classic mode)-> Administrative Tools-> Event Viewer
  • Start-> Control Panel (Windows XP)-> Performance and Maintenance-> Event Viewer
  • Start-> Control Panel (Windows Vista)-> System and Security-> Event Viewer
  • Start-> Control Panel (Windows 7)-> System and Maintenance-> Event Viewer
  • Right click on (My) Computer is the Start Menu or in Explorer and choose Manage.
    Expand System Tools to see Event Viewer.
  • C:\Windows\System32\eventvwr.msc
  • In Windows Vista and Windows 7;
    Start-> type; Event Viewer

Locating the Outlook entries
Outlook logs its entries to the Application log. Upon expanding the Event Viewer in Windows XP, you’ll see this log directly. In Windows Vista and Windows 7, you’ll have to expand the “Windows Logs” folder first as well.

In the “Source” column the application that created the Event is listed. You’ll have to look for “Outlook” here. Scroll until you have found the most recent entry or entries which were written during your last Outlook session.

If you are having finding the correct event entry (for instance when you want to see if the same happened a few days ago), then you can also apply a filter to the log to only show the entries with the Event Level “Error” and Event Source being Outlook.
In Windows XP you’ll find the filter command in the View menu. For Windows Vista and Windows 7 you can find the filter command in the Actions pane on the right or by right clicking on the Application log.

Looking up the meaning of the entries
When you have found the entry, you can find more information about the event in the Preview Pane (when you use Windows XP, you’ll have to double click the entry to launch it in its own windows). The most important information for troubleshooting purposes can be found by looking at the “Event ID” number and the full text description.

The full text description can sometimes already tell you what is going on when it reveals the name of an add-in that you have installed. Disable the add-in and see if Outlook starts normally now. If it does, uninstall, reinstall or update the add-in or contact the vendor of the add-in to help you further troubleshooting their product.

If the description field is not clear, then you can also try to find more information about it via Microsoft Support website. For instance, when you want to find out more about Event ID 27 you can type the following search phrase;
Outlook error Event ID 27

Event IDs are not always clear enough. Especially when you get and error 1000 or 1001 you’ll get a lot of results as these are used for more generic crashes. In those cases it helps to also post some keywords from the description field, especially when it contains references to dll-files.

Another great resource for looking up Event IDs is EventID.Net.

First troubleshooting steps
It is not always directly needed to start to analyze your (Outlook) issues by opening the Event Viewer and dive into technical descriptions. Many issues allow themselves to be solved by easy deduction.

For instance, if Outlook works in Outlook Safe Mode, it usually means that the issue is caused by an add-in or corrupt dat-file.

Other general troubleshooting steps can be found here.

If you have issues finding the cause, you can always post in the Outlook newsgroups with the exact error message. Open the event by double clicking on it and press the copy button to easily paste it in the newsgroup message.

Note: When you have crashes with references to dll-files, never delete or manually replace these dll-files unless you are specifically instructed to do so by a renowned support specialist or instructions from a trustworthy source. Never (ever!), replace dll-files with dll-files that you obtained from one of the many dll-download sites that are around. These are usually modified, virus infected or the wrong version and will do your computer more harm than good.

MAPILab
Use "4PM76A8" to get a discount when ordering!