Home Product SupportIdentify a code

support · reviewed answer

Windows blue screen: what to record before trying fixes

Photograph the exact stop code and any named driver, note the trigger and preserve dump files. Prove whether the crash follows one driver, update, peripheral or workload before reinstalling Windows.

Direct answer

Photograph the exact stop code and any named driver, note the trigger and preserve dump files. Prove whether the crash follows one driver, update, peripheral or workload before reinstalling Windows.

What this covers

  • Windows 11 reaches a blue or black stop-code screen and restarts
  • The exact condition described in the direct answer
  • Customer-accessible observations and controls

What it does not cover

  • ×A different model, region or software interface that contradicts the cited source
  • ×A displayed code with a separate manufacturer meaning
  • ×Live electrical, gas, sealed-system or battery-cell repair
Try in this order0 of 4 completed

  1. Establish the exact starting state

    Reversible

    Record the stop code, time, recent update/hardware and whether it repeats in the same task.

  2. Separate the fault or decision boundary

    Reversible

    Disconnect new nonessential peripherals and use reliability/update history or Safe Mode only when needed.

  3. Apply the narrowest correction

    Reversible

    Update, roll back or remove the one proven driver/update; run hardware diagnostics for repeatable memory/storage symptoms.

  4. Verify before escalating

    Reversible

    Repeat the original workload and monitor for the same code across multiple restarts.

Evidence ledger

Sources behind this answer

Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.

01
Microsoft SupportTroubleshooting Windows unexpected restarts and stop code errors

Microsoft's own stop-code troubleshooting article.

Exact questions

Common follow-ups

What is the short answer to “Windows blue screen: what to record before trying fixes”?+

Photograph the exact stop code and any named driver, note the trigger and preserve dump files. Prove whether the crash follows one driver, update, peripheral or workload before reinstalling Windows.

What should I check before changing anything?+

Record the stop code, time, recent update/hardware and whether it repeats in the same task.

How do I know the action worked?+

Repeat the original workload and monitor for the same code across multiple restarts.

When should I stop?+

Back up important data before storage tests, firmware changes, reset or reinstall.

Change recordAug. 17, 2026 — Added as a distinct support intent with its own scope, diagnostic boundary, verification and first-party source.
Report a correction
Wrong device or version?

Match the path before repeating the steps.

Match another device