Use care30 minute route

Windows shows an error or crash code

Turn a vague error into evidence by recording the exact message, time and trigger before looking up codes or changing drivers and system files.

Start with quick checks Open learning route

Quick answer

The safest way to start

Capture the complete error text, code, timestamp and triggering action, then reproduce it once safely before choosing a repair path.

Quick answer

Capture the complete error text, code, timestamp and triggering action, then reproduce it once safely before choosing a repair path.

Best first action

Save screenshots and a short timeline before dismissing dialogs, clearing logs, reinstalling software or running cleanup utilities.

What not to do

Do not search only a shortened error phrase or run unrelated repair commands without preserving the exact code and context.

When to stop

Stop repeated testing if the error involves drive failure, overheating, electrical problems, encryption keys, repeated blue screens during startup or irreplaceable data.

Expected result

The exact original action no longer produces the error.

1 · Triage

Quick checks before changing anything

Use these checks to narrow the problem and avoid applying an unrelated fix.

Capture the exact wording

Photograph or copy the complete message, hexadecimal code, stop code, file name and button labels. Similar-looking errors can have different causes.

Record the time and trigger

Note the exact time, application, action and whether the error repeats after restart. This makes Event Viewer and reliability records useful.

Check the scope

Determine whether one app fails, one user account fails, or Windows itself crashes. Scope controls which logs and repair steps are relevant.

2 · Stabilize

Safe first actions

Mark actions as you complete them. Progress is stored only in this browser.

Preserve the evidenceSave screenshots and a short timeline before dismissing dialogs, clearing logs, reinstalling software or running cleanup utilities.Look up the code in contextUse a code lookup as a starting point, then compare the description with the observed trigger, recent change and affected component.Avoid broad driver changesDo not update every driver or run multiple repair tools at once. Change the component connected to the evidence and keep a rollback path.

3 · Diagnose and resolve

Step-by-step route

Continue only when the result of the current step supports the next one.

1
Classify the error
Separate application errors, update errors, boot errors and stop-code crashes.
Expected resultYou choose the correct evidence source and avoid irrelevant fixes.
2
Correlate time and logs
Use Event Viewer, Reliability Monitor or update history around the recorded time.
Expected resultThe error is connected to a process, driver, update or hardware event.
3
Reverse the most likely recent change
Roll back or repair one relevant update, driver or application and reproduce the same action.
Expected resultThe error stops after a reversible, evidence-based change.
4
Check system and hardware health
Use DISM/SFC, memory tests or drive checks only when the error pattern points there.
Expected resultPersistent errors are escalated with logs instead of repeated guessing.

Stop and escalate when

Stop repeated testing if the error involves drive failure, overheating, electrical problems, encryption keys, repeated blue screens during startup or irreplaceable data.

4 · Verify

How to know the problem is resolved

The exact original action no longer produces the error.
Two normal restarts complete without the same crash.
The final change and supporting evidence are recorded.

5 · Build the skill

Recommended learning route

Open these lessons in order when you need more detail or want to prevent the issue from returning.

Lesson 1

Capture useful error information

Record exact messages, codes, timing and recent changes before attempting fixes.

Windows Essentials · Troubleshooting Essentials

Lesson 2

Use Event Viewer without getting overwhelmed

Filter recent critical and error events and connect them to the time a problem occurred.

Windows Essentials · Troubleshooting Essentials

Lesson 3

Capture a BSOD stop code

Record the stop code, failed module and time instead of relying on memory.

PC Troubleshooting Guided Learning Lab · Crashes and Blue Screens

Lesson 4

Review drivers and updates

Connect a crash to recent driver, firmware or Windows changes.

PC Troubleshooting Guided Learning Lab · Crashes and Blue Screens

Lesson 5

Run system-file repair safely

Use DISM and SFC with clear expectations and verify the result.

PC Troubleshooting Guided Learning Lab · Repair and Recovery Decisions

6 · Practice and reference

TipsMake tools and guides

Practice with tools

BSOD Code LookupLook up Windows stop codes and review likely causes and safe first checks.Windows Event Log AnalyzerGroup exported Event Viewer records around crashes, shutdowns, disk and application errors.Windows Update Error LookupResearch an exact Windows Update error code before attempting broad repairs.

Continue with guides

Common BSOD error codesReview common Windows stop codes and initial troubleshooting context.Troubleshoot Windows with Event Viewer logsConnect Windows events to the time and context of a failure.

Related routes

Continue with a connected problem

Common questions

FAQ

Does the error code always identify the failed part?

No. A code identifies a condition, not necessarily the root cause. The same code can result from a driver, storage, memory, update or software interaction, so context matters.

Should I clear Event Viewer before troubleshooting?

No. Clearing logs removes timeline evidence. Filter by the recorded time and source, then export relevant events if you need to share them.

Browse all problem hubs Explore Knowledge Map