Windows won’t start

Blue screen with a stop code appears during startup

Instead of loading normally, Windows briefly or persistently shows a blue screen with a specific stop code (like an all-caps phrase and a code such as 0x0000...) right as it's trying to start.

Difficulty
Intermediate
Time
30–90 minutes
DIY cost
$0
Pro cost
$100–$220

Symptoms

  • Blue screen flashes or stays visible during startup, before login
  • A specific stop code and short description is shown
  • PC may restart automatically after the blue screen
  • Happens consistently at roughly the same point in startup

Likely causes

  • CommonFaulty or incompatible driver loading at bootMany startup blue screens trace back to a specific driver, often storage or graphics related.
  • CommonCorrupted system filesDamage to core Windows files can trigger a crash before the desktop loads.
  • PossibleFailing RAMMemory errors frequently cause blue screens, especially ones that appear inconsistently.
  • PossibleFailing or corrupted driveRead errors on the boot drive can trigger a startup crash with a storage-related stop code.
  • PossibleRecently installed hardware or overclockingNew components or aggressive performance settings can cause instability during boot.

What to do

  1. Note down the exact stop code text shown (for example MEMORY_MANAGEMENT or SYSTEM_SERVICE_EXCEPTION); it points to a specific likely cause.
  2. Interrupt startup 2–3 times to force Windows into the Recovery Environment, then try Startup Repair first.
  3. If you recently added hardware or overclocked anything, remove it or reset to default settings and try booting again.
  4. From Recovery Environment Command Prompt, run 'chkdsk C: /f /r' and then 'sfc /scannow' to check disk and system file integrity.
  5. Try Safe Mode; if it boots successfully there, a driver is likely responsible and can be rolled back or removed from Device Manager.
  6. If you have access to Windows Memory Diagnostic (search for it once booted, or run 'mdsched' from Recovery Command Prompt), run a memory test to rule out RAM.
  7. Look up the specific stop code along with your PC's model or the specific driver named in the error for more targeted guidance, since stop codes cover many different underlying causes.

Tools and parts

  • Bootable Windows recovery USB drive

When to call a pro

If the specific stop code and basic checks (disk, drivers, memory) don't lead to a fix, a technician can run deeper hardware diagnostics and interpret the crash dump file.

Safety

Generally low risk

Generally low risk for a careful person. Stop if anything looks different from what this guide describes.

Related guides

Operator provides AI-generated troubleshooting information. It can be wrong. For safety-critical, electrical, gas, structural, medical, automotive safety, or other high-risk problems, consult a qualified professional.