Learning Center / PC & Laptop Troubleshooting / Lesson 7

Windows Blue Screen Errors

Course: PC & Laptop Troubleshooting · Lesson 7 of 20 · Reading time: about 2 minutes, plus the activity

Windows sometimes stops because it cannot safely continue. People often call this a blue-screen error or BSOD, although the screen's appearance can vary. The useful details are the stop code, timing and circumstances.

Before you start

Beginner · Build on the basics

Lesson format: Explanation and activity

Helpful preparation

Review these topics first if they are unfamiliar. You can still open every lesson.

By the end, you should be able to

  • Record a stop code and incident context
  • Choose evidence relevant to a blue-screen investigation

Capture the clue

Record the displayed code and any named driver. Did the stop happen during startup, after sleep, while gaming or after connecting a new device? Was there a recent update? A photo can help, but avoid sharing personal information visible on the screen.

Possible causes include drivers, hardware, firmware or other system problems. A named file can be involved in the failure without being the original cause.

Start with a small, relevant investigation

Save and back up work when Windows is usable. Disconnect a newly added nonessential external device if the timing points to it, then compare. Obtain supported drivers from the equipment maker or Windows Update rather than downloading arbitrary “BSOD fixer” tools.

Safe Mode loads a limited driver and service set. Success there may narrow the issue but doesn't by itself prove which component is faulty. More advanced diagnosis may use crash dump files, which can contain sensitive memory data.

Try it: write a useful incident note

Use a fictional case: “Stop occurs only after connecting a new USB dock; no stop when the dock is absent.” Name one comparison test and one detail to record.

Possible answer: compare normal use with the dock disconnected; record the exact code and dock model.

Quick check

  1. Does every stop error mean faulty RAM?
  2. Is the exact code more useful than “it turned blue”?
Show answers and explanation
  1. No.
  2. Yes; precise details help narrow the investigation.

Read further

Microsoft: stop-error troubleshooting