Error Medic

Computer Blue Screen (BSOD): Complete Fix Guide for Windows & Mac Startup, Memory, USB, and Game Crashes

Fix computer blue screen errors fast. Step-by-step guide for BSOD on startup, memory management, USB triggers, game crashes, and computers that won't boot.

Last updated:
Last verified:
2,207 words
Key Takeaways
  • Root Cause 1: Faulty or incompatible drivers (graphics, USB, storage) are the #1 trigger for BSODs, especially during gaming or when plugging in USB devices.
  • Root Cause 2: Corrupted system files or bad RAM modules cause memory management BSODs (stop code 0x0000001A) and random blue screens on startup.
  • Root Cause 3: Overheating hardware, failing hard drives, or incompatible software updates cause persistent blue screens that prevent normal boot.
  • Quick Fix Summary: Boot into Safe Mode, run 'sfc /scannow' and Windows Memory Diagnostic, update or roll back drivers, and check disk health with CHKDSK to resolve most BSOD scenarios without reinstalling Windows.
Fix Approaches Compared
MethodWhen to UseTimeRisk
SFC + DISM ScanCorrupted system files, random BSODs, post-update crashes10-30 minLow
Windows Memory Diagnostic / MemTest86MEMORY_MANAGEMENT (0x1A) BSOD, random crashes under load30 min - 8 hrsLow
Driver Rollback / UpdateBSOD after driver install, USB device triggers crash, game crashes10-20 minLow-Medium
CHKDSK Disk RepairBSOD on startup, computer won't boot, disk read errors20-120 minMedium
Startup Repair (WinRE)Computer blue screened and won't boot, stuck at BSOD loop15-30 minLow
Clean Boot / Safe ModeIsolate third-party software causing constant blue screens15-30 minLow
Windows Reset / ReinstallAll other methods failed, persistent unrecoverable BSOD1-4 hrsHigh (data loss risk)
Hardware Replacement (RAM/HDD)MemTest86 confirms bad RAM, SMART data shows failing drive30-60 minMedium

Understanding the Computer Blue Screen (BSOD)

A Blue Screen of Death (BSOD) is Windows' emergency stop mechanism — it halts the OS to prevent data corruption when a fatal kernel-level error occurs. Every BSOD includes a stop code (e.g., MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) that points to the root cause. Mac computers rarely display a true blue screen; instead they show a kernel panic or a gray/black screen — covered in a dedicated section below.

Common BSOD Stop Codes and Their Meanings

  • 0x0000001A — MEMORY_MANAGEMENT: Bad RAM, corrupted page file, or driver writing to invalid memory.
  • 0x0000007E — SYSTEM_THREAD_EXCEPTION_NOT_HANDLED: Usually a driver crash.
  • 0x000000D1 — DRIVER_IRQL_NOT_LESS_OR_EQUAL: A driver attempted to access memory at an improper IRQL — very common with network/USB drivers.
  • 0x00000050 — PAGE_FAULT_IN_NONPAGED_AREA: Faulty RAM or corrupted driver.
  • 0x0000007B — INACCESSIBLE_BOOT_DEVICE: Windows can't read the boot drive — seen when the computer blue screened and won't boot.
  • 0xC000021A — STATUS_SYSTEM_PROCESS_TERMINATED: Critical system process (winlogon, csrss) crashed.

Step 1: Read the Blue Screen and Capture the Stop Code

When the BSOD appears, note the stop code displayed in large text (e.g., MEMORY_MANAGEMENT) and the failing module listed at the bottom (e.g., ntoskrnl.exe, nvlddmkm.sys). If the screen disappears too fast, disable automatic restart:

  1. Right-click This PCPropertiesAdvanced system settings.
  2. Under Startup and Recovery, click Settings.
  3. Uncheck Automatically restart.
  4. Click OK.

Alternatively, read crash dumps stored at C:\Windows\Minidump\ using WinDbg or the free tool WhoCrashed.


Step 2: Boot into Safe Mode (When the Computer Won't Start Normally)

If your computer blue screens on startup or keeps blue screening in a loop:

  1. Force-shut down the PC three times in a row during the Windows logo — Windows will automatically enter Windows Recovery Environment (WinRE).
  2. Navigate to TroubleshootAdvanced OptionsStartup SettingsRestart.
  3. Press 4 for Safe Mode or 5 for Safe Mode with Networking.

In Safe Mode, Windows loads only essential drivers, which isolates software/driver-related crashes.


Step 3: Run System File Checker and DISM

Corrupted system files cause random and startup BSODs. Run these commands in an elevated Command Prompt (right-click → Run as administrator):

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart after completion. SFC will report Windows Resource Protection found corrupt files and repaired them on success, or could not perform the requested operation if system corruption is too deep (proceed to DISM first in that case).


Step 4: Check RAM with Windows Memory Diagnostic

For MEMORY_MANAGEMENT BSODs and random crashes:

  1. Press Win + R, type mdsched.exe, press Enter.
  2. Choose Restart now and check for problems.
  3. Let the scan run through at least two passes.

For a more thorough test, boot from a MemTest86 USB drive and run overnight. Any errors confirm bad RAM that must be replaced.


Step 5: Update or Roll Back Drivers

BSOD when plugging in USB device → Update or reinstall USB/chipset drivers. BSOD when playing games → Roll back or clean-reinstall the GPU driver.

To roll back a driver:

  1. Open Device Manager (Win + X → Device Manager).
  2. Expand the relevant category (Display adapters, Universal Serial Bus controllers).
  3. Right-click the device → PropertiesDriver tab → Roll Back Driver.

For NVIDIA GPUs, use DDU (Display Driver Uninstaller) in Safe Mode for a clean removal before reinstalling the latest driver from nvidia.com.


Step 6: Check Disk Health with CHKDSK

A failing drive causes INACCESSIBLE_BOOT_DEVICE and startup BSODs. Run:

chkdsk C: /f /r /x

Schedule the scan on reboot when prompted. After completion, also check SMART data using CrystalDiskInfo (Windows) or smartctl -a /dev/sda (Linux dual-boot). Reallocated sectors or pending sectors indicate a failing drive requiring replacement.


Step 7: Use Startup Repair (Computer Won't Boot)

If the computer blue screened and won't boot:

  1. Boot from a Windows 10/11 USB installer.
  2. Select Repair your computerTroubleshootStartup Repair.
  3. Let it run automatically.

Startup Repair fixes corrupted Boot Configuration Data (BCD), which is the most common cause of unbootable systems after a BSOD crash.


Step 8: Perform a Clean Boot to Identify Software Conflicts

For computers blue screening constantly or randomly:

  1. Press Win + R, type msconfig, Enter.
  2. On the Services tab, check Hide all Microsoft services, then click Disable all.
  3. On the Startup tab, click Open Task Manager and disable all startup items.
  4. Restart and test. If stable, re-enable services in batches to find the culprit.

Mac Computer Blue Screen / Kernel Panic

Mac computers (Apple silicon and Intel) don't truly display a blue screen but show a kernel panic (dark gray screen with a progress bar, then restart) or get stuck on a blue or gray loading screen during startup.

Fixes for Mac startup blue screen:

  • NVRAM/PRAM Reset: Shut down, then hold Option + Command + P + R for 20 seconds on boot (Intel Macs).
  • Safe Mode: Hold Shift while booting (Intel) or hold Power until startup options appear, then Shift-click Continue in Safe Mode (Apple Silicon).
  • First Aid in Disk Utility: Boot to macOS Recovery (Command + R), open Disk Utility, select the startup disk, click First Aid.
  • Reinstall macOS: From Recovery, use Reinstall macOS without erasing data.

Gateway Computer Blue Screen

Gateway PCs (now owned by Acer) follow standard Windows BSOD procedures above. Additionally, check for Gateway-specific driver updates via Acer's support portal at acer.com/support. Gateway laptops are known to have outdated BIOS versions that cause stability issues — update the BIOS from the manufacturer support page.


When to Replace Hardware

Proceed to hardware replacement when:

  • MemTest86 shows RAM errors → Replace RAM sticks one at a time to identify the faulty module.
  • SMART data shows 5+ reallocated sectors or pending uncorrectable sectors → Replace the drive immediately.
  • CPU or GPU temperatures exceed 95°C under load (check with HWMonitor) → Reapply thermal paste or replace the cooler.

Frequently Asked Questions

bash
# ============================================================
# BSOD DIAGNOSTIC & REPAIR COMMANDS (Run as Administrator)
# ============================================================

# --- Step 1: Repair System Files ---
# Run DISM first to repair the Windows image, then SFC
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

# --- Step 2: Check and Repair Disk ---
# Schedule CHKDSK on next reboot (replace C: with your drive letter)
chkdsk C: /f /r /x
# From WinRE Command Prompt, also try:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

# --- Step 3: Read Recent Crash Dump Info (PowerShell) ---
# List recent minidumps with timestamps
Get-ChildItem -Path "C:\Windows\Minidump" | Sort-Object LastWriteTime -Descending | Select-Object -First 10

# --- Step 4: Check Event Logs for BSOD Stop Codes (PowerShell) ---
Get-WinEvent -LogName System | Where-Object { $_.Id -eq 41 -or $_.Id -eq 1001 -or $_.Id -eq 6008 } | Select-Object TimeCreated, Id, Message | Format-List

# --- Step 5: View installed drivers (find third-party drivers) ---
driverquery /FO CSV /SI | findstr /V "Microsoft"

# --- Step 6: Check RAM slots and speed via WMIC ---
wmic memorychip get BankLabel, Capacity, Speed, Manufacturer

# --- Step 7: Check Disk SMART Status via PowerShell ---
Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus, Size

# --- Step 8: Disable Automatic Restart on BSOD (CMD) ---
wmic recoveros set AutoReboot = False

# --- Step 9: Export crash dump info (requires WinDbg or kd) ---
# Run from WinDbg command line after opening the minidump file:
# !analyze -v
# .bugcheck
# !lmi <module_name>

# --- Step 10: Clean Boot via BCDEdit (Safe Mode alternative) ---
# To boot into Safe Mode from CMD (Next reboot only):
bcdedit /set {current} safeboot minimal
# To revert back to normal boot after troubleshooting:
bcdedit /deletevalue {current} safeboot

# --- Step 11: Roll Back a Specific Driver via PNPUTIL ---
# List all third-party drivers
pnputil /enum-drivers
# Remove a specific driver by INF name (e.g., oem15.inf)
pnputil /delete-driver oem15.inf /uninstall

# --- Step 12: Check temperature logs (requires OpenHardwareMonitor CLI) ---
# Alternative: Use WMIC for quick CPU check
wmic /namespace:\\root\wmi PATH MSAcpi_ThermalZoneTemperature get CurrentTemperature
# Convert result: (CurrentTemperature - 2732) / 10 = Celsius
E

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and system administrators with 10+ years of experience diagnosing Windows kernel panics, BSOD crashes, hardware failures, and enterprise infrastructure incidents. Our guides are tested on real hardware and virtual environments before publication.

Sources

Related Articles in Other Computer Blue Screen

Explore More windows Guides