If the module name doesn’t ring any bells to you, look at the module path: if the path goes to the System32 folder, then you are dealing with a crash caused by Outlook itself. In the crash report, look for the “Faulting module name” and “Faulting module path” (this is the actual component that triggered the Outlook crash). If your Outlook 2013 crashed recently, OffCAT should report these crashes: click on one of them to open the actual crash event report. Notice the red icons in the above screenshot: they indicate Outlook crashes. It should look similar to the below screenshot: Do not ignore the suggestions prompted by OffCAT, otherwise these issues are likely to cause Outlook problems.Īfter the scan report was compiled, open it and look for the “ Event Logs section: Application Event Log Entries for the Last Outlook crashes“. The main advantage of this Outlook diagnostics method is that it reports not just information about your Outlook 2013 crashes, but it also scans Outlook for invalid registry entries, performance issues, outdated add-ins, available Outlook updates and other known issues.

Once you’ve installed the Office Configuration Analyzer Tool (OffCAT), run it and choose to generate an Outlook report by clicking on “Start a scan” -> select Outlook -> type any name you want in the label section and click on “Start scanning”.

Unfortunately it isn’t mentioned anywhere in Outlook… This free diagnostics tool is a pretty new addition to the Office suite but it works for all Outlook versions starting with Outlook 2003. The best thing to do is to download and install the Office Configuration Analyzer Tool. How to identify your Outlook crash reason – a conflict between 3rd party add-ins or between Outlook and a 3rd party Outlook add-in. – a Windows system infected with a virus / malware code There are four major reasons that can cause Outlook to crash: If Outlook keeps crashing, read this article to find out the most frequent causes for Outlook crashes and their solutions.

Outlook crashes when opening run scan