Computer Blue Screen (BSOD) Fix: Memory Management, Startup Crashes, Game Freezes & More
Fix computer blue screen errors on Windows & Mac. Step-by-step BSOD troubleshooting for memory, USB, startup, and gaming crashes. Works for all PC brands.
- Root Cause 1: Faulty or incompatible RAM triggers MEMORY_MANAGEMENT (0x0000001A) and PAGE_FAULT_IN_NONPAGED_AREA BSODs — run Windows Memory Diagnostic or MemTest86 to confirm.
- Root Cause 2: Corrupt or outdated drivers (GPU, USB, chipset) cause blue screens on startup, during gaming, and when plugging in USB devices — update or roll back drivers via Device Manager.
- Root Cause 3: Damaged system files or a failing hard drive produce recurring BSODs at boot — use sfc /scannow, DISM, and CHKDSK to detect and repair corruption.
- Quick Fix Summary: Boot into Safe Mode, run SFC and DISM repair commands, update all drivers, check RAM with MemTest86, scan the disk with CHKDSK, and review Event Viewer for the exact stop code before replacing hardware.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| sfc /scannow + DISM | Corrupt system files, recurring BSODs after updates | 15-30 min | Low |
| Driver rollback / update | BSOD after new hardware, GPU crash during gaming, USB blue screen | 10-20 min | Low |
| Windows Memory Diagnostic / MemTest86 | MEMORY_MANAGEMENT 0x1A, random BSODs, BSOD on startup | 30 min – 8 hrs | Low |
| CHKDSK /r /f | BSOD after disk error, blue screen every time you turn on the PC | 30-120 min | Low |
| System Restore / Reset This PC | Cannot identify cause, constant blue screening, unbootable system | 30-90 min | Medium |
| RAM reseating / replacement | MemTest86 errors confirmed, all software fixes failed | 30 min | Low-Medium |
| Clean Windows reinstall | All other methods exhausted, drive healthy, BSOD persists | 60-120 min | High (data loss) |
Understanding the Blue Screen of Death (BSOD)
A Blue Screen of Death (BSOD) — officially a Stop Error — occurs when Windows detects a fatal condition from which it cannot safely recover. The screen displays a stop code, a QR code, and a brief description. Common stop codes include:
- MEMORY_MANAGEMENT (0x0000001A) — RAM corruption or bad memory pages
- PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) — invalid memory reference
- IRQL_NOT_LESS_OR_EQUAL (0x0000000A) — driver accessing forbidden memory
- SYSTEM_SERVICE_EXCEPTION (0x0000003B) — driver or system service fault
- CRITICAL_PROCESS_DIED (0x000000EF) — essential Windows process terminated
- KERNEL_SECURITY_CHECK_FAILURE (0x00000139) — data corruption detected by kernel
- DPC_WATCHDOG_VIOLATION (0x00000133) — system unresponsive, often GPU/SSD driver
- WHEA_UNCORRECTABLE_ERROR (0x00000124) — hardware-level CPU or memory error
Mac computers display a spinning wheel or a grey/blue screen, which has different causes covered at the end of this guide.
Step 1: Record the Stop Code
Before fixing anything, read and write down the exact stop code shown on the blue screen. If the PC restarts too quickly:
- Go to Settings → System → About → Advanced System Settings → Startup and Recovery → Settings.
- Uncheck "Automatically restart" under System Failure.
- Set Write debugging information to Small memory dump (256 KB).
- Click OK. The next BSOD will freeze the screen so you can read the code.
Dump files are saved to C:\Windows\Minidump\. You can open them with WinDbg (Windows Debugger) from the Microsoft Store.
Step 2: Boot into Safe Mode
If your computer blue screened and won't boot normally:
- Power on and immediately press F8 (older Windows) or hold Shift while clicking Restart from the sign-in screen.
- Go to Troubleshoot → Advanced Options → Startup Settings → Restart.
- Press 4 for Safe Mode or 5 for Safe Mode with Networking.
Safe Mode loads only essential drivers. If the BSOD stops in Safe Mode, a third-party driver is the cause.
Step 3: Repair System Files (SFC and DISM)
Open Command Prompt as Administrator and run:
sfc /scannow
Wait for the scan to complete. If it reports errors it could not fix, run DISM to repair the Windows image store:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After DISM completes, run sfc /scannow again and restart.
Step 4: Update or Roll Back Drivers
Computer blue screen when plugging in a USB device → update or reinstall USB and chipset drivers. Computer blue screens when playing games → update or roll back GPU drivers.
- Press Win + X → Device Manager.
- Expand the relevant category (Display adapters, Universal Serial Bus controllers, etc.).
- Right-click the device → Update driver or Properties → Driver → Roll Back Driver.
- For NVIDIA GPUs, use DDU (Display Driver Uninstaller) in Safe Mode for a clean uninstall, then install the latest driver from nvidia.com.
- For AMD GPUs, use AMD Cleanup Utility before reinstalling.
Step 5: Check RAM with Windows Memory Diagnostic
- Press Win + R, type
mdsched.exe, press Enter. - Choose Restart now and check for problems.
- Windows will run two passes and report errors on next login.
For more thorough testing, use MemTest86 (bootable USB, runs outside Windows) for at least 2 full passes. Any errors mean one or more RAM sticks are faulty.
If errors are found:
- Power off and remove all but one RAM stick.
- Test each stick individually to identify the bad one.
- Replace the defective stick with a compatible replacement.
Step 6: Check the Hard Drive or SSD
chkdsk C: /f /r /x
If Windows asks to schedule the scan on next reboot, type Y and restart. CHKDSK will scan for bad sectors and attempt repair. For SSDs, also check manufacturer health tools (Samsung Magician, Crucial Storage Executive, CrystalDiskInfo).
Step 7: Check Event Viewer for Crash Details
- Press Win + R, type
eventvwr.msc. - Navigate to Windows Logs → System.
- Filter by Critical and Error events around the time of the BSOD.
- Look for Kernel-Power (Event ID 41), disk errors (Event ID 7), or driver errors.
Step 8: Use System Restore
If BSODs started after a specific update or software installation:
- Boot into Safe Mode.
- Press Win + R, type
rstrui.exe. - Select a restore point from before the blue screens began.
- Follow the wizard to restore.
Step 9: Reset or Reinstall Windows
If all steps above fail:
- Settings → Update & Security → Recovery → Reset this PC.
- Choose Keep my files for a soft reset or Remove everything for a full reinstall.
- Alternatively, boot from a Windows 10/11 USB and perform a clean installation.
Mac Computer Blue / Grey Screen Fix
Mac users who see a persistent blue or grey screen at startup should:
- Force restart: Hold Power for 10 seconds.
- Reset NVRAM: Hold Option + Command + P + R at startup for 20 seconds.
- Boot into Safe Mode: Hold Shift at startup (Intel) or hold Power until startup options appear (Apple Silicon).
- Run First Aid in Disk Utility from macOS Recovery (Command + R at boot).
- Reinstall macOS from Recovery if First Aid finds unrepairable errors.
Apple-branded or Gateway, Dell, HP desktop computers all follow the same Windows BSOD troubleshooting steps above — the brand does not change the diagnosis procedure.
Gateway and Older Desktop-Specific Notes
Gateway and other older desktop computers may display BSODs related to legacy BIOS settings. Enter BIOS (usually Del or F2 at boot) and:
- Disable Fast Boot if enabled.
- Ensure SATA mode matches your OS installation (AHCI for modern drives).
- Check that RAM speed (XMP/EXPO profiles) is set correctly for your sticks.
Frequently Asked Questions
# ============================================================
# Windows BSOD Diagnostic & Repair Script
# Run PowerShell as Administrator
# ============================================================
# Step 1: Disable automatic restart on BSOD so you can read the stop code
Write-Host "[1] Disabling auto-restart on BSOD..."
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl' -Name 'AutoReboot' -Value 0
# Step 2: Check Windows System File integrity
Write-Host "[2] Running System File Checker..."
sfc /scannow
# Step 3: Repair Windows image with DISM
Write-Host "[3] Running DISM Health Restore..."
DISM /Online /Cleanup-Image /RestoreHealth
# Step 4: Schedule CHKDSK on C: drive at next reboot
Write-Host "[4] Scheduling CHKDSK for next reboot..."
echo y | chkdsk C: /f /r /x
# Step 5: Check disk SMART status via WMI
Write-Host "[5] Reading disk SMART status..."
Get-WmiObject -Namespace root\wmi -Class MSStorageDriver_FailurePredictStatus | Select-Object InstanceName, PredictFailure, Reason
# Step 6: Export last 20 critical/error system events to a log file
Write-Host "[6] Exporting recent critical system events..."
$events = Get-WinEvent -LogName System -MaxEvents 500 | Where-Object { $_.Level -le 2 } | Select-Object -First 20
$events | Format-List TimeCreated, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\BSOD_Events.txt"
Write-Host "Event log saved to Desktop as BSOD_Events.txt"
# Step 7: List recently installed drivers (potential BSOD causes)
Write-Host "[7] Recent driver installs (last 7 days)..."
Get-WinEvent -LogName System | Where-Object { $_.Id -eq 7036 -and $_.TimeCreated -gt (Get-Date).AddDays(-7) } | Select-Object TimeCreated, Message | Format-Table -AutoSize
# Step 8: List minidump files for analysis
Write-Host "[8] Available minidump crash files..."
$dumpPath = "C:\Windows\Minidump"
if (Test-Path $dumpPath) {
Get-ChildItem $dumpPath -Filter *.dmp | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, @{Name='SizeMB';Expression={[math]::Round($_.Length/1MB,2)}}
} else {
Write-Host "No minidump folder found. Enable small memory dumps in System Properties."
}
# Step 9: Check current RAM info
Write-Host "[9] RAM Information..."
Get-WmiObject Win32_PhysicalMemory | Select-Object Manufacturer, PartNumber, Capacity, Speed, MemoryType | Format-Table -AutoSize
# Step 10: Launch Windows Memory Diagnostic
Write-Host "[10] Launching Windows Memory Diagnostic (will reboot)..."
# Uncomment the line below to actually schedule the memory test:
# Start-Process mdsched.exe
Write-Host ""
Write-Host "=== Diagnostic complete. Review BSOD_Events.txt on your Desktop. ==="
Write-Host "=== Next: Open WinDbg or upload .dmp files to https://www.osronline.com for analysis. ==="Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with 10+ years of experience diagnosing operating system crashes, kernel errors, and hardware failures across enterprise and consumer environments. Our guides are tested against real hardware fault scenarios and verified against official Microsoft, Apple, and hardware vendor documentation.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/fix-blue-screen-errors-in-windows-3b3c7272-ebab-9c95-7a5a-c2fa7f2ac9c7
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk
- https://support.apple.com/en-us/102603
- https://stackoverflow.com/questions/tagged/bsod
- https://www.memtest86.com/technical.htm
- https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/using-the-windows-debugger-to-debug-driver-issues