My computer blue screens every time I turn it on and won't boot into Windows — what should I do?

Force three hard shutdowns in a row to trigger Windows Automatic Repair, then navigate to Troubleshoot → Advanced Options → Startup Repair. If that fails, open Command Prompt from WinRE and run 'bootrec /fixmbr', 'bootrec /fixboot', and 'bootrec /rebuildbcd'. If the stop code mentions MEMORY_MANAGEMENT or INACCESSIBLE_BOOT_DEVICE, also run 'chkdsk C: /f /r' from WinRE Command Prompt. Persistent boot-loop BSODs with these steps failing usually indicate a failed hard drive or RAM module requiring hardware replacement.

My computer blue screens randomly with no consistent stop code — how do I diagnose it?

Random BSODs with varying stop codes most often point to bad RAM, an unstable power supply, or overheating. Run MemTest86 for at least 4 passes, check temperatures under load with HWiNFO64, and inspect your PSU capacity. Also check Event Viewer (eventvwr.msc) under Windows Logs → System for Critical events at the exact time of each crash. Install WhoCrashed to automatically parse minidump files in C:\Windows\Minidump and identify the fault module across multiple crashes.

My computer blue screens when playing games — is my GPU dying?

Not necessarily. Gaming BSODs are commonly caused by: (1) outdated or corrupt GPU drivers — reinstall using DDU in Safe Mode and get fresh drivers from nvidia.com or amd.com; (2) GPU or RAM overclocking — reset to stock speeds; (3) thermal throttling — clean dust from GPU heatsink and check that fans spin; (4) underpowered PSU struggling under gaming load. Use HWiNFO64 to log temperatures and voltages during gameplay. If stop codes are VIDEO_TDR_FAILURE or SYSTEM_SERVICE_EXCEPTION (igdkmd64.sys or nvlddmkm.sys), it's a driver issue. If WHEA_UNCORRECTABLE_ERROR appears, suspect hardware failure.

My computer blue screens when I plug in a USB device — how do I fix it?

This is almost always a USB driver or device firmware conflict. Steps: (1) Unplug all USB devices and reboot. (2) In Device Manager, uninstall all USB Root Hub and Host Controller entries, then reboot to let Windows reinstall clean drivers. (3) Plug devices in one at a time to identify the specific culprit. (4) Update the device driver from the manufacturer's website. (5) Try plugging into a different USB port (different controller). (6) Check for BIOS/UEFI firmware updates that may fix USB compatibility. The stop codes to look for are DRIVER_IRQL_NOT_LESS_OR_EQUAL or BUGCODE_USB_DRIVER.

Does an Apple or Mac computer get a blue screen like Windows?

Macs don't have a Windows-style BSOD, but they can display a persistent blue, grey, or black screen at startup indicating a serious error. Common fixes: (1) Boot to Recovery Mode (Command + R on Intel Macs, hold Power button on Apple Silicon) and run Disk Utility First Aid on the startup disk. (2) Reset NVRAM on Intel Macs (Option + Command + P + R at startup). (3) Run Apple Diagnostics (hold D at startup on Intel, hold Power on Apple Silicon) to test hardware. (4) Boot into Safe Mode (hold Shift) to disable third-party kernel extensions causing the hang. If these fail, a macOS reinstall via Recovery Mode is the next step.

Computer Blue Screen (BSOD) Fix: Stop Codes, Memory Management, Startup & Game Crashes Explained

Fix computer blue screen errors on Windows & Mac. Step-by-step diagnosis for BSOD on startup, during games, USB plug-in, and memory management stop codes.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,241 words

Key Takeaways

Most Windows BSODs are caused by faulty or incompatible drivers, bad RAM, corrupted system files, or overheating hardware — each producing a distinct stop code like MEMORY_MANAGEMENT (0x0000001A), IRQL_NOT_LESS_OR_EQUAL (0x0000000A), or KERNEL_SECURITY_CHECK_FAILURE.
Blue screens triggered by USB devices usually point to a driver conflict or a failing USB controller, while game-related BSODs often trace back to GPU drivers or overclocked hardware running out of thermal headroom.
Run 'sfc /scannow' and 'chkdsk /f /r' first, then use Windows Memory Diagnostic or MemTest86 for RAM, roll back or update the most recently changed driver, and check Event Viewer (eventvwr.msc) for the exact fault module before replacing hardware.

Fix Approaches Compared
Method	When to Use	Time	Risk
sfc /scannow + DISM	Corrupted Windows system files, BSOD after Windows Update	10–30 min	Low
Driver Rollback / Update	BSOD after installing new hardware or updating drivers	5–15 min	Low
Windows Memory Diagnostic	MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA stop codes	15–60 min	Low
MemTest86 (bootable)	Persistent RAM errors, random BSODs, won't boot normally	1–8 hrs	Low
chkdsk /f /r	BSOD related to disk I/O, bad sectors, or file corruption	30–120 min	Low-Medium
Safe Mode Driver Removal	Can't boot normally; suspect a specific driver	10–20 min	Low
System Restore	BSOD started after a recent software/driver change	20–40 min	Medium
Startup Repair (WinRE)	Computer won't boot at all, BSOD on every startup	15–45 min	Low
Reinstall Windows	All other methods failed, persistent unresolvable BSOD	1–3 hrs	High (data loss)
Hardware Replacement (RAM/SSD/GPU)	Confirmed hardware failure via diagnostics	Varies	Medium

Understanding the Blue Screen of Death (BSOD)

A Blue Screen of Death (BSOD) — officially called a Stop Error — occurs when Windows detects a fatal condition from which it cannot recover safely. The OS halts all processes and displays a blue screen with a stop code and (on Windows 10/11) a QR code linking to Microsoft's support site. The exact stop code is your primary diagnostic clue.

Common stop codes and their likely causes:

MEMORY_MANAGEMENT (0x0000001A): RAM hardware failure or driver corrupting memory.
PAGE_FAULT_IN_NONPAGED_AREA (0x00000050): Bad RAM, corrupted driver, or paging file issue.
IRQL_NOT_LESS_OR_EQUAL (0x0000000A): Driver accessing memory at an improper IRQL level.
KERNEL_SECURITY_CHECK_FAILURE (0x00000139): Driver or system file integrity violation.
DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1): A network or peripheral driver bug.
SYSTEM_SERVICE_EXCEPTION (0x0000003B): Often caused by antivirus or GPU drivers.
CRITICAL_PROCESS_DIED (0x000000EF): A core Windows process crashed unexpectedly.
VIDEO_TDR_FAILURE (0x00000116): GPU driver timeout — frequent during gaming.
WHEA_UNCORRECTABLE_ERROR (0x00000124): Hardware-level error (CPU, RAM, PSU).

Step 1: Record the Stop Code and Fault Module

When a BSOD appears, photograph the screen or note the stop code and the .sys or .dll file listed at the bottom. This file is usually the faulty driver.

If the system rebooted too fast to read it:

Press Win + R, type sysdm.cpl, go to Advanced → Startup and Recovery → Settings.
Uncheck Automatically restart so the BSOD stays visible.
After the next crash, open Event Viewer: press Win + R, type eventvwr.msc, navigate to Windows Logs → System, and filter for Critical events at the crash timestamp.
Check the minidump folder: C:\Windows\Minidump\. Use **WinDbg** or the free **WhoCrashed** tool to analyze .dmp files.

Step 2: Run Immediate System Integrity Checks

Open Command Prompt as Administrator and run these in order:

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

Restart after completion. These commands repair corrupted Windows system files — a frequent BSOD trigger after failed updates.

Step 3: Check the Hard Drive / SSD

A failing drive causes BSODs on startup and random reboots:

chkdsk C: /f /r /x

Schedule it for the next reboot when prompted. For SSDs and NVMe drives, also use the manufacturer's diagnostic tool (Samsung Magician, CrystalDiskInfo, Western Digital Dashboard) to check health attributes like Reallocated Sector Count.

Step 4: Test RAM

For MEMORY_MANAGEMENT or PAGE_FAULT stop codes:

Option A – Windows built-in (quick):

Press Win + R, type mdsched.exe, and choose Restart now and check for problems.
The tool runs two passes automatically and reports results in Event Viewer after reboot.

Option B – MemTest86 (thorough, bootable):

Download from memtest86.com, flash to a USB drive.
Boot from USB and run a minimum of 2 full passes (4+ recommended).
Any errors = RAM module failure. Reseat or replace sticks one at a time.

If you have dual-channel RAM, test each stick individually in the same slot to isolate a failing module.

Step 5: Update or Roll Back Drivers

Rolling back a driver:

Press Win + X → Device Manager.
Expand the relevant category (Display adapters, Network adapters, USB controllers).
Right-click the device → Properties → Driver tab → Roll Back Driver.

Updating drivers:

GPU: Always download directly from nvidia.com or amd.com — avoid Windows Update GPU drivers.
Use DDU (Display Driver Uninstaller) in Safe Mode for clean GPU driver replacement:
1. Boot to Safe Mode (hold Shift + click Restart → Troubleshoot → Advanced → Startup Settings → F4).
2. Run DDU, select "Clean and restart".
3. Reboot normally and install the latest driver from the vendor.

Step 6: BSOD When Plugging in a USB Device

This typically means a USB driver or firmware conflict:

Unplug all USB devices.
In Device Manager, expand Universal Serial Bus controllers.
Right-click each USB Root Hub and USB Host Controller → Uninstall device.
Reboot — Windows reinstalls USB drivers automatically.
If caused by a specific device, update that device's driver from the manufacturer's website.
Check BIOS for USB firmware updates.

Step 7: Gaming BSODs (VIDEO_TDR_FAILURE / SYSTEM_SERVICE_EXCEPTION)

BSODs during games are almost always GPU driver, overclocking, or thermal issues:

Check temperatures: Install HWiNFO64 or MSI Afterburner. GPU should stay below 85°C, CPU below 90°C under load.
Remove overclock: Reset GPU and RAM to stock speeds in BIOS or MSI Afterburner.
Reinstall GPU drivers using DDU (Step 5 above).
Test with integrated graphics (if available) to confirm the GPU is the problem.
Check PSU: Underpowered PSUs cause crashes under gaming load. Verify your PSU wattage covers GPU + CPU TDP with 20% headroom.
Update DirectX and Visual C++ redistributables via Windows Update.

Step 8: Computer Won't Boot — WinRE Recovery

If the machine BSODs before Windows loads:

Force shut down 3 times in a row — Windows will enter Automatic Repair mode.
Navigate: Troubleshoot → Advanced Options → Startup Repair.
If Startup Repair fails: Advanced Options → Command Prompt and run:
```
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
```
If still failing, use System Restore from the same menu.

Mac & Apple Computer Blue Screen

Macs don't display BSOD, but a persistent blue or grey screen at startup indicates:

Startup Disk issues: Boot to Recovery Mode (Command + R on Intel, hold Power on M1/M2). Run Disk Utility → First Aid.
NVRAM/PRAM reset (Intel only): Shut down, power on holding Option + Command + P + R for 20 seconds.
SMC reset: Follow Apple support steps for your specific Mac model.
Safe Mode: Hold Shift during startup to disable third-party extensions.

Gateway and Older Desktop BSODs

Older Gateway and legacy desktops often have outdated BIOS/UEFI firmware that triggers stop errors with modern hardware:

Visit the Gateway/Acer support site and check for BIOS updates.
Reset BIOS to default settings (Load Optimized Defaults).
Test each RAM stick individually — older motherboards are sensitive to RAM compatibility.
Check for capacitor bulging on the motherboard near the CPU socket or RAM slots (physical inspection).

Frequently Asked Questions

bash

# ============================================================
# WINDOWS BSOD DIAGNOSTIC & REPAIR SCRIPT
# Run all commands in Administrator Command Prompt or PowerShell
# ============================================================

# --- 1. Check for corrupted system files ---
sfc /scannow

# --- 2. Repair Windows image with DISM ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# --- 3. Schedule disk check on next reboot (replace C: if needed) ---
chkdsk C: /f /r /x
# Answer Y to schedule for next reboot

# --- 4. Run Windows Memory Diagnostic ---
mdsched.exe
# Select "Restart now and check for problems"

# --- 5. View recent BSODs via Event Viewer (filter last 7 days) ---
powershell -Command "Get-WinEvent -LogName System | Where-Object {$_.LevelDisplayName -eq 'Critical' -and $_.TimeCreated -gt (Get-Date).AddDays(-7)} | Select-Object TimeCreated, Id, Message | Format-List"

# --- 6. View minidump files (requires WinDbg or use WhoCrashed GUI) ---
dir C:\Windows\Minidump\

# --- 7. Check driver verifier status (advanced - use carefully) ---
verifier /query
# To enable Driver Verifier for all third-party drivers (causes intentional BSODs to catch bad drivers):
# verifier /standard /all
# To disable Driver Verifier:
# verifier /reset

# --- 8. List all non-Microsoft drivers (potential BSOD culprits) ---
powershell -Command "Get-WmiObject Win32_SystemDriver | Where-Object {$_.PathName -notlike '*\\Windows\\*'} | Select-Object Name, PathName, State | Format-Table -AutoSize"

# --- 9. Check system temperatures (requires OpenHardwareMonitor CLI or HWiNFO) ---
# Manual: Download HWiNFO64 from hwinfo.com and check sensor readings

# --- 10. Export system info for analysis ---
msinfo32 /report %USERPROFILE%\Desktop\sysinfo.txt

# --- 11. Check for pending Windows Updates ---
powershell -Command "(New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher().Search('IsInstalled=0').Updates | Select-Object Title"

# --- 12. WinRE commands (run from Advanced Options > Command Prompt) ---
# Fix boot records:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
# Scan all disks for Windows installations:
bootrec /scanos

# --- 13. Roll back a specific driver via PowerShell ---
# Replace 'DisplayAdapter' with the device class and name as needed
# pnputil /enum-drivers
# pnputil /delete-driver oem##.inf /uninstall

# --- 14. Check RAM slots and speed in PowerShell ---
powershell -Command "Get-WmiObject Win32_PhysicalMemory | Select-Object BankLabel, Capacity, Speed, Manufacturer | Format-Table"

# --- 15. Check disk health via SMART data (PowerShell) ---
powershell -Command "Get-WmiObject -Namespace root\wmi -Class MSStorageDriver_FailurePredictStatus | Select-Object InstanceName, PredictFailure, Reason"

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows systems administrators with 10+ years of experience diagnosing and resolving OS-level failures across enterprise and consumer environments. Our guides are built from real incident postmortems, Microsoft documentation, and hands-on lab testing to ensure every step is actionable and verified.

Sources

Explore More windows Guides

Acer Aspire Blue Screen of Death Fix: How to Stop BSOD Crashes on Acer Laptops

Fix Acer Aspire Blue Screen of Death errors fast. Step-by-step guide covering driver updates, RAM checks, overheating, and Windows repair commands.

Acer Aspire Blue Screen of Death Fix: Step-by-Step Troubleshooting Guide (BSOD Errors Solved)

Fix Acer Aspire blue screen of death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK and more. Step-by-step commands included.

Acer Aspire Blue Screen of Death Fix: Stop Codes, Causes & Complete Solutions

Fix Acer Aspire Blue Screen of Death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK_FAILURE & more with exact commands.