BSOD evidence reference

Stack and loaded modules

Use the call stack and module list as diagnostic leads while avoiding automatic blame from a single filename.

Evidence to preserve

  • 1
    Preserve the unedited dump
  • 2
    Review stack context and module versions
  • 3
    Correlate a module with repeatable evidence

How to use this reference safely

Start with the exact affected operation and collect the evidence above before selecting a repair branch. Change one relevant variable at a time, repeat the same operation, and preserve any changed result.

Official source: Microsoft bug check code reference
A stop code, parameter, or named module is evidence to correlate; it does not by itself prove a single cause.

Related BSOD intelligence