Target audience for this post
People who troubleshoot Windows.
People interested in investigating Windows app crashes and errors.
What is it useful for?
This post cannot completely pinpoint the cause from the crash report alone.
However, it should help narrow down the programs causing the issue that cannot be identified solely from the blue screen memory dump or event logs.
Crash report available here
C:\ProgramData\Microsoft\Windows\WER\ReportArchiveCrash reports for apps and other programs are created within the above folder.
Example crash reports in the folder
Game and device apps, system files
For example, let's look at the crash report, Report.wer, located in the folder starting with Kernel_1a~.
This is a Bluescreen report. The EventType is labeled as Bluescreen, and it contains error codes and parameters. Error code 1a corresponds to Bug Check 0x1A: MEMORY_MANAGEMENT.
As such, you can verify error codes and other details without using debugging tools.
When an app crashes, you can narrow down the relevant programs by checking which modules are being loaded. After grasping the time of occurrence and overview from these crash reports, digging deeper into the event logs can sometimes help you narrow down not only errors and warnings but also the execution of related programs at the information level. I find these reports quite interesting.
