Lenovo BSOD: How to Fix Blue Screen of Death on Lenovo & Lenovo Legion Laptops
Fix Lenovo BSOD errors fast. Step-by-step guide covering driver updates, RAM checks, and Windows fixes for Lenovo Legion and all Lenovo laptops.
- Root Cause 1: Outdated, corrupt, or incompatible drivers — especially GPU, chipset, and Lenovo-specific firmware drivers — are the #1 cause of BSOD on Lenovo and Lenovo Legion laptops.
- Root Cause 2: Faulty or incompatible RAM, overheating hardware, or a corrupted Windows system file (ntoskrnl.exe, hal.dll) triggering stop codes like MEMORY_MANAGEMENT (0x0000001A), DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1), or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.
- Root Cause 3: Conflicting third-party software, aggressive overclocking (common on Legion gaming models), or a failing SSD/HDD causing CRITICAL_PROCESS_DIED or KERNEL_SECURITY_CHECK_FAILURE.
- Quick Fix Summary: Boot into Safe Mode, update or roll back drivers via Device Manager, run 'sfc /scannow' and DISM to repair Windows, check RAM with Windows Memory Diagnostic, and if needed perform a clean driver install using DDU (Display Driver Uninstaller) for GPU drivers.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Update/Roll Back Drivers | BSOD after Windows Update or driver install; stop code mentions a .sys file | 15-30 min | Low |
| SFC & DISM Repair | Corrupted system files suspected; CRITICAL_PROCESS_DIED or KERNEL_SECURITY_CHECK_FAILURE | 20-45 min | Low |
| Windows Memory Diagnostic / MemTest86 | MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA stop codes; random BSODs | 30 min – 8 hrs | None |
| DDU Clean GPU Driver Install | GPU driver corruption; SYSTEM_THREAD_EXCEPTION_NOT_HANDLED with nvlddmkm.sys or atikmpag.sys | 30-60 min | Low |
| CHKDSK Disk Repair | BSOD with BAD_POOL_HEADER or after sudden shutdowns; SSD/HDD suspected | 15 min – 2 hrs | Low-Medium |
| BIOS/UEFI Firmware Update | BSODs persist after all software fixes; hardware compatibility issues on Legion | 20-30 min | Medium |
| Windows Reset / Clean Install | All other methods failed; frequent unrecoverable BSODs | 1-3 hrs | High (data loss) |
Understanding Lenovo BSOD Errors
A Blue Screen of Death (BSOD) on a Lenovo or Lenovo Legion laptop is Windows' emergency stop mechanism — it halts the operating system the moment it detects a fatal error that it cannot safely recover from. The screen displays a stop code (e.g., MEMORY_MANAGEMENT, DRIVER_IRQL_NOT_LESS_OR_EQUAL) and, in most cases, saves a minidump file to C:\Windows\Minidump\ for post-mortem analysis.
Lenovo Legion gaming laptops are particularly prone to BSOD events due to their dual-GPU configurations (integrated Intel/AMD + discrete NVIDIA), aggressive power management, and the fact that many users push hardware with overclocking and third-party utilities like MSI Afterburner or Lenovo Vantage.
Common Lenovo BSOD Stop Codes
- MEMORY_MANAGEMENT (0x0000001A) — RAM error or memory allocation failure.
- DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) — A driver tried to access memory at an illegal IRQL level. Often tied to network or GPU drivers.
- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — A system thread generated an exception that the error handler didn't catch. Common culprits:
nvlddmkm.sys(NVIDIA),atikmpag.sys(AMD),igdkmd64.sys(Intel). - KERNEL_SECURITY_CHECK_FAILURE — Data corruption or memory corruption detected. Can be RAM, SSD, or driver-related.
- CRITICAL_PROCESS_DIED — A critical Windows process (like smss.exe or csrss.exe) was terminated unexpectedly.
- PAGE_FAULT_IN_NONPAGED_AREA — The system attempted to access a memory page that wasn't available. Hardware or driver issue.
- BAD_POOL_HEADER — Kernel memory pool corrupted. Often caused by faulty drivers or failing storage.
Step 1: Read the BSOD and Collect the Minidump
The first step is to capture the exact stop code and the associated .sys file (if listed). Modern Windows 10/11 BSODs show a QR code and a stop code on the blue screen.
If the system reboots too fast:
- Go to Settings > System > About > Advanced System Settings.
- Under Startup and Recovery, click Settings.
- Uncheck Automatically restart under System failure.
- Set Write debugging information to Small memory dump (256 KB).
Analyze minidumps with WinDbg:
Install WinDbg from the Microsoft Store. Open a .dmp file from C:\Windows\Minidump\ and run:
!analyze -v
This outputs the exact faulting driver, memory address, and stack trace.
Alternatively, use WhoCrashed (free tool) which parses minidumps and gives plain-English explanations.
Step 2: Boot into Safe Mode
If the BSOD occurs on startup, you must boot into Safe Mode to perform repairs:
- Power on the Lenovo laptop and immediately press F8 (older systems) or hold Shift and click Restart from the login screen.
- Navigate to Troubleshoot > Advanced Options > Startup Settings > Restart.
- Press 4 for Safe Mode or 5 for Safe Mode with Networking.
In Safe Mode, only essential drivers load, which often prevents the BSOD from occurring and lets you make repairs.
Step 3: Update or Roll Back Drivers
GPU Drivers (Most Common Fix for Legion BSODs):
For NVIDIA GPU crashes (nvlddmkm.sys):
- Download Display Driver Uninstaller (DDU) from Wagnardsoft.
- Boot into Safe Mode.
- Run DDU and select "Clean and restart" for NVIDIA.
- After reboot, download the latest driver directly from nvidia.com — do NOT use GeForce Experience auto-install initially.
- Install using Custom Install > Clean Installation.
For AMD GPU crashes (atikmpag.sys or amdkmdag.sys):
- Use DDU in Safe Mode to remove AMD drivers.
- Download the latest Adrenalin driver from amd.com.
- Install with factory reset option checked.
Chipset and System Drivers:
- Open Lenovo Vantage or Lenovo System Update and run all recommended updates.
- Visit support.lenovo.com, enter your model number, and manually download chipset, BIOS, and firmware updates.
- In Device Manager, right-click any devices with yellow exclamation marks and update drivers.
To roll back a driver that caused a BSOD after an update:
- Open Device Manager (devmgmt.msc).
- Right-click the device > Properties > Driver tab > Roll Back Driver.
Step 4: Run System File Checker and DISM
Corrupted Windows system files are a frequent BSOD trigger. Run these commands in an elevated (Administrator) Command Prompt:
sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After DISM completes, run sfc /scannow again and then reboot.
Step 5: Test RAM
For MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA BSODs:
Built-in Windows Memory Diagnostic:
- Press Win + R, type
mdsched.exe, press Enter. - Select Restart now and check for problems.
- Let it complete two passes. Check Event Viewer afterward: Windows Logs > System, filter for source "MemoryDiagnostics-Results".
MemTest86 (More thorough):
- Download from memtest86.com and create a bootable USB.
- Boot from USB and run at least 2 full passes (8+ passes recommended).
- Any errors indicate faulty RAM that must be replaced or reseated.
For Lenovo Legion models with two RAM slots, try running with one stick at a time to isolate a faulty module.
Step 6: Check Storage Health
For BAD_POOL_HEADER, CRITICAL_PROCESS_DIED, or BSODs that occur during file operations:
chkdsk C: /f /r /x
This requires a reboot to run. Also check SSD health with CrystalDiskInfo (free). A "Caution" or "Bad" status means the drive is failing and needs immediate replacement.
For NVMe SSDs on Legion laptops:
wmic diskdrive get status
Step 7: Update BIOS/UEFI Firmware
For persistent BSODs that survive all software fixes, a BIOS update may resolve hardware compatibility or power management bugs:
- Check your current BIOS version: Press Win + R, type
msinfo32, look for BIOS Version/Date. - Go to support.lenovo.com, enter your model (e.g., Legion 5 Pro, ThinkPad X1), and download the latest BIOS update.
- Run the BIOS updater from within Windows (most Lenovo BIOS updates support this) or boot from USB.
- Never interrupt a BIOS update — keep the laptop plugged in.
Step 8: Thermal and Power Management Checks
Lenovo Legion laptops generate significant heat. Thermal throttling or sudden shutdowns due to overheating can mimic or trigger BSOD events.
- Use HWiNFO64 or MSI Afterburner to monitor CPU/GPU temperatures under load.
- CPU temps above 95°C or GPU above 90°C indicate a cooling problem.
- Repaste the CPU/GPU thermal compound if the laptop is 2+ years old.
- Ensure the laptop vents are clean — use compressed air.
- In Lenovo Vantage, set the Thermal Mode to Balanced or Performance (avoid overriding with aggressive overclocks if BSODs are occurring).
Step 9: Check for Conflicting Software
Third-party applications that interact with hardware at a low level can cause BSODs:
- Antivirus software — Some AV drivers are buggy. Try disabling or uninstalling (especially older versions of Avast, McAfee).
- Overclocking utilities — Uninstall MSI Afterburner, XTU, or ThrottleStop temporarily.
- VPN drivers — Some VPN kernel drivers (e.g., older Cisco AnyConnect) cause IRQL errors.
- Lenovo Vantage — Rarely, a corrupt Vantage installation itself can cause issues. Uninstall and reinstall from the Microsoft Store.
Use Autoruns (Sysinternals) to identify and disable third-party drivers starting with Windows.
Step 10: Windows Reset as Last Resort
If all steps above fail:
- Go to Settings > System > Recovery > Reset this PC.
- Choose Keep my files for a less destructive reset, or Remove everything for a full clean install.
- A clean Windows install will rule out any software-level cause and confirm if the issue is hardware.
Frequently Asked Questions
# ============================================================
# Lenovo BSOD Diagnostic & Fix Script
# Run as Administrator in PowerShell
# ============================================================
# --- 1. Display last 10 BSOD events from Event Viewer ---
Write-Host "=== Recent Critical System Errors ==="
Get-WinEvent -LogName System -MaxEvents 100 | Where-Object { $_.LevelDisplayName -eq 'Critical' } | Select-Object TimeCreated, Id, Message | Format-Table -Wrap | Select-Object -First 10
# --- 2. List minidump files ---
Write-Host "`n=== Minidump Files (most recent first) ==="
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length
# --- 3. Run System File Checker ---
Write-Host "`n=== Running SFC (System File Checker) ==="
sfc /scannow
# --- 4. Run DISM to repair Windows image ---
Write-Host "`n=== Running DISM RestoreHealth ==="
DISM /Online /Cleanup-Image /RestoreHealth
# --- 5. Schedule CHKDSK on next reboot ---
Write-Host "`n=== Scheduling CHKDSK for next reboot ==="
cmd /c "echo Y | chkdsk C: /f /r /x"
# --- 6. Check disk SMART status via WMIC ---
Write-Host "`n=== Disk Drive Status ==="
Get-WmiObject -Class Win32_DiskDrive | Select-Object Model, Status, MediaType
# --- 7. List recently installed drivers (last 30 days) ---
Write-Host "`n=== Drivers installed in last 30 days ==="
$cutoff = (Get-Date).AddDays(-30)
Get-WinEvent -LogName System -MaxEvents 5000 | Where-Object { $_.Id -eq 7045 -and $_.TimeCreated -gt $cutoff } | Select-Object TimeCreated, Message | Format-Table -Wrap
# --- 8. Check Windows Memory Diagnostic results ---
Write-Host "`n=== Memory Diagnostic Results ==="
Get-WinEvent -LogName System -MaxEvents 500 | Where-Object { $_.ProviderName -eq 'Microsoft-Windows-MemoryDiagnostics-Results' } | Select-Object TimeCreated, Message
# --- 9. Export System Info for Lenovo support ---
Write-Host "`n=== Exporting System Info to Desktop ==="
msinfo32 /report "$env:USERPROFILE\Desktop\LenovoSystemInfo.txt"
Write-Host "System info saved to Desktop as LenovoSystemInfo.txt"
# --- 10. GPU Driver Info ---
Write-Host "`n=== GPU Driver Information ==="
Get-WmiObject Win32_VideoController | Select-Object Name, DriverVersion, DriverDate, Status | Format-List
# --- 11. Thermal / Temperature Check (requires HWiNFO or WMI sensor) ---
Write-Host "`n=== CPU Info ==="
Get-WmiObject -Class Win32_Processor | Select-Object Name, CurrentClockSpeed, MaxClockSpeed, NumberOfCores
Write-Host "`n=== BSOD Diagnostic Complete. Review output above and check Desktop for SystemInfo report. ==="
# --- Optional: Open WhoCrashed download page ---
# Start-Process "https://www.resplendence.com/whocrashed"
# --- Optional: Open Lenovo Driver Downloads page ---
# Start-Process "https://support.lenovo.com/solutions/ht003029"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 hardware failures, driver conflicts, and OS-level crashes across enterprise and consumer environments. We specialize in turning cryptic stop codes and kernel panics into actionable, step-by-step fixes backed by real diagnostic data and official documentation.
Sources
- https://support.microsoft.com/en-us/windows/resolving-blue-screen-errors-in-windows-60b73bdb-7518-d4b3-e37c-8c7f9b1c3d1d
- https://support.lenovo.com/us/en/solutions/ht035729-how-to-troubleshoot-blue-screen-bsod-problems
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/getting-started-with-windbg
- https://answers.microsoft.com/en-us/windows/forum/all/bsod-driver-irql-not-less-or-equal/3c3b2857-d2a0-4f5a-a48d-fd8c5a8e09d7
- https://www.memtest86.com/
- https://www.wagnardsoft.com/
- https://github.com/nicehash/NiceHashQuickMiner/issues/305