BSOD Troubleshooting: A Beginner’s Fix Guide

BSOD Troubleshooting Guide for Beginners

A Blue Screen of Death looks scary. It doesn’t have to stay a mystery. Every BSOD carries a stop code. That code tells you exactly which subsystem failed. This guide shows you how to read it and fix the actual cause, not just make the screen go away.

Step 1: Read the Stop Code, Don’t Just Restart

When the blue screen appears, look for a line that says “Stop code:” followed by text like MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL. Write it down before rebooting.

If the PC restarts before you can read it, Windows may be set to auto-restart on failure. Turn that off first:

1. Open System Properties → Advanced → Startup and Recovery.
2. Uncheck “Automatically restart.”
3. Reproduce the crash. This time the code stays on screen.

ℹ️ Technical Note: The stop code is the single most useful piece of information you have. Skipping it and jumping straight to reinstalling Windows often means fixing nothing and seeing the same crash again later.

PC Turns On Then Off: Causes and Fix

Step 2: Find the Crash Dump File

Windows saves a memory dump every time a BSOD occurs. This file records what the system was doing at the moment of failure.

1. Download a free minidump analysis tool (WhoCrashed is a common, beginner-friendly option).
2. Run it. It reads the dump automatically.
3. Look for the line naming the faulting driver or module.

This single line often points straight at the cause: a specific driver file, a hardware subsystem, or a Windows component.

Step 3: Match the Stop Code to a Category

Different stop codes point toward different causes. Here are the most common ones:

Use this table as a starting point, not a final answer. Confirm with the tests below before replacing anything.

BIOS Reset Not Working: Fix Guide

Step 4: Test RAM First

RAM issues cause a large share of BSODs, especially MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA codes.

1. Create a bootable Memtest86 USB drive.
2. Run at least one full pass. Overnight gives a more thorough result.
3. Any reported error confirms RAM instability.

If you enabled an XMP or EXPO profile for faster RAM speeds, reset to the default JEDEC speed and retest. Many RAM-related BSODs disappear the moment the overclock profile is removed, even on otherwise healthy sticks.

Step 5: Check Drivers

If the minidump names a specific driver, that’s your starting point.

• Update it to the latest version from the manufacturer, not just through Windows Update.
• Roll it back if the crash started right after a recent update.
• Uninstall it entirely if it’s for hardware you no longer use.

For GPU-related codes like VIDEO_TDR_FAILURE, use a clean driver installer utility to remove the old driver completely before installing a fresh one. A partial update often leaves conflicting files behind.

⚠️ WARNING: Never delete system driver files manually through File Explorer. This can break far more than the one driver you’re trying to fix. Always use the manufacturer’s uninstaller or a dedicated driver-removal tool.

PC Freezes Randomly: Causes and Fix

Step 6: Check for Storage Problems

Codes like CRITICAL_PROCESS_DIED and DPC_WATCHDOG_VIOLATION often point to a failing drive.

1. Run chkdsk /f from an elevated command prompt and restart to let it scan.
2. Check the drive’s health using its manufacturer’s diagnostic tool, or a general SMART-reading utility.
3. For SSDs, check the firmware version against the manufacturer’s latest release. Outdated firmware causes real, documented BSOD issues on several drive models.

A drive nearing failure often shows other symptoms too: slow file access, occasional freezes, or files that won’t open. If you see those alongside the BSOD, back up your data immediately before doing anything else.

Step 7: Rule Out Hardware Instability

Codes like WHEA_UNCORRECTABLE_ERROR point toward the CPU, motherboard, or an overclock pushed too far.

• Reset any CPU or GPU overclock to stock settings and retest.
• Reset any undervolt applied through software, since an overly aggressive undervolt can cause instability that looks identical to a hardware fault.
• Check for bulging capacitors on the motherboard (see our separate guide on this) if the crashes coincide with random restarts as well.
• Check CPU and GPU temperatures under load. Overheating can trigger the same kind of stop codes as a genuine hardware fault.

Step 8: Use Driver Verifier for Persistent Cases

If the minidump doesn’t clearly point to one driver, Windows has a built-in stress-testing tool for exactly this situation.

1. Open Command Prompt as Administrator.
2. Type verifier and press Enter.
3. Select “Create custom settings” and choose all standard checks.
4. Select all drivers, or just non-Microsoft drivers if you want to narrow the scope faster.
5. Restart. Driver Verifier stresses every selected driver until one fails, forcing a BSOD that names the culprit clearly in the dump.

⚠️ WARNING: Driver Verifier can cause frequent crashes while it’s active. This is expected behavior, not a new problem. Disable it afterward with verifier /reset and a restart.

RAM Not Detected: Causes and Fix

When to Suspect Hardware Over Software

Lean toward a hardware cause, not a software one, if:

• The BSOD happens randomly, with no pattern tied to a specific program
• Memtest86 shows actual errors
• The crash coincides with random restarts or shutdowns under load
• Temperatures run high right before the crash
• The system is also showing bulging capacitors or other visible damage

Lean toward software if:

• The crash always happens during the same specific action, like launching one program
• It started right after a driver or Windows update
• Memtest86 comes back completely clean after a full pass
• Driver Verifier reliably names the same non-Microsoft driver

Quick Reference Checklist

• Disabled automatic restart to capture the actual stop code
• Analyzed the minidump with a tool like WhoCrashed
• Matched the stop code to a likely category
• Ran Memtest86 for at least one full pass
• Reset RAM to default speed if XMP/EXPO was active
• Updated or rolled back the driver named in the dump
• Checked drive health and SSD firmware version
• Reset any CPU/GPU overclock or undervolt
• Checked temperatures under load
• Ran Driver Verifier if the cause still isn’t clear

Reading the stop code first saves hours of guessing. It points you toward RAM, a driver, storage, or hardware instability before you touch a single setting.

PC Restarts Randomly: Causes and Fix

Recommendation: Looking for a professional bi-directional diagnostic tool with full system coverage? Use code DIAGNOZABAM for 10% off.

Transparency note: Affiliate link. Purchasing through it costs you nothing extra. View Thinkcar Deal →