An easier way to view crashes in the Windows Event Log
In a previous article I wrote about how to identify crashes in the Windows Event Log.
You need to use the Windows Event Viewer, inspect each entry looking for some keywords then decode the XML data to get the information you want. All a bit slow, tedious and error prone.
So we wrote a tool to do that for you: Event Log Crash Browser.
Event Log Crash Browser scans your event log looking for crash events, then picks out only the information that is useful:
- The executable.
- The DLL that crashed (if it did crash in a DLL, rather than non-DLL memory).
- The exception code.
- The offset into the DLL of the crash location (or the location in memory for non-DLL crashes).
- We also read the version information from the DLL so that we can identify the company responsible for the DLL that crashed.
You can sort on any column, and filter by exception type, executable and DLL.
It’s a really easy way to see what failures are happening on your machine. A lot more convenient than Windows Event Viewer. Looking at this machine I can see that the Visual Studio compiler, linker and IDE crash from time to time. I can also see that the WMI provider service dies quite often from a heap corruption – this is a core bit of Microsoft technology that has problems. Most of the other failures are related to the software under development and test on this machine.