A crash dump can reveal the bug check parameters and loaded modules. A module named in a dump is a lead, not automatic proof that the named driver or hardware caused the crash.
Protect your files first
Back up important files when possible. If the drive is encrypted, locate the BitLocker recovery key before recovery changes. Stop if storage appears to be failing or this is a work or school managed PC.
When this guide applies
A crash dump can reveal the bug check parameters and loaded modules. A module named in a dump is a lead, not automatic proof that the named driver or hardware caused the crash.
Check the exact Windows version and whether the PC is managed by a workplace or school before following instructions.
Steps
Use Microsoft’s WinDbg from an official source on your own PC. Open the dump, run !analyze -v, and record the bug check code, parameters, and analysis text. Cross-check with the exact Microsoft bug-check page.
Record the result of the step before deciding whether to continue. A failed step is diagnostic evidence; it does not automatically justify a reset or reinstall.
Limits and stop points
Dumps may contain sensitive data. Do not upload them to a public error search. Driver Verifier belongs to advanced test environments, not a first step.
If the result does not match the guide, use the official reference below or contact the device maker with the exact error and steps already attempted.
Keep track of your checks
This checklist stays in this browser session. It is not sent to WinErrors.