Why does my Lenovo laptop keep getting BSOD with the error DRIVER_IRQL_NOT_LESS_OR_EQUAL?

This stop code on Lenovo laptops almost always points to a driver — usually the GPU driver (nvlddmkm.sys for NVIDIA or amdkmdag.sys for AMD), network adapter driver, or chipset driver — attempting to access memory at an invalid interrupt request level. Use BlueScreenView or WinDbg on the minidump file in C:\Windows\Minidump\ to identify the exact driver. Then uninstall it using DDU (for GPU) or Device Manager in Safe Mode, and install the latest version from the manufacturer's website or Lenovo Support.

My Lenovo Legion gets a BSOD only during gaming. What causes this?

Gaming-only BSODs on Lenovo Legion laptops are most commonly caused by: (1) GPU driver instability under sustained load — update or roll back NVIDIA/AMD drivers; (2) CPU or GPU overheating due to dust buildup or dried thermal paste — monitor temps with HWiNFO64 and clean the cooling system; (3) RAM instability under memory-intensive workloads — test with MemTest86; or (4) power delivery issues when the GPU demands peak wattage — ensure you are using the correct charger (usually 230W or 300W for Legion) and check the power adapter is not faulty.

How do I fix Lenovo BSOD CRITICAL_PROCESS_DIED on Windows 11?

CRITICAL_PROCESS_DIED means a Windows core process (like csrss.exe, winlogon.exe, or a kernel component) terminated unexpectedly. On Lenovo laptops with Windows 11 this often follows a botched Windows Update or Lenovo Vantage conflict. Steps to fix: (1) Boot into Safe Mode; (2) Run 'sfc /scannow' and DISM RestoreHealth commands in an elevated Command Prompt; (3) Uninstall the most recent Windows Update via Settings > Windows Update > Update History > Uninstall Updates; (4) Reinstall Lenovo Vantage and system drivers from Lenovo Support. If the BSOD persists, a clean Windows reinstall is the most reliable resolution.

My Lenovo ThinkPad shows BSOD after Windows Update. How do I rollback?

If a Windows Update caused the BSOD, you have two options. First, try rolling back the update: go to Settings > Windows Update > Update History > Uninstall Updates, and remove the most recently installed Cumulative Update. Second, if Windows fails to boot, use Advanced Startup (hold Shift at restart) > Troubleshoot > Advanced Options > Uninstall Updates. For driver-related update BSODs, go to Device Manager, right-click the suspect device (often display adapter or network adapter), and select 'Roll Back Driver'. You can also block a specific problematic update using Microsoft's 'Show or Hide Updates' troubleshooter.

Can Lenovo BSOD be caused by faulty RAM, and how do I test it?

Yes — RAM faults are a significant cause of BSODs on Lenovo devices, producing stop codes like MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA, and IRQL_NOT_LESS_OR_EQUAL. To test: (1) Run Windows Memory Diagnostic (mdsched.exe) for a quick check; (2) For thorough testing, use MemTest86 — create a bootable USB from memtest86.com, boot from it, and run at least two full passes. Any reported errors confirm faulty RAM. If errors are found, try running with one stick at a time to isolate the bad module, then replace it. On most Lenovo Legion and IdeaPad models, SO-DIMM RAM is user-replaceable.

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 tests, thermal fixes, and registry repairs for Lenovo Legion and all Lenovo laptops

Last updated: March 1, 2026

Last verified: March 1, 2026

2,222 words

Key Takeaways

Root cause 1: Outdated, corrupt, or incompatible drivers — especially GPU (NVIDIA/AMD), chipset, or Lenovo Vantage-related drivers — are the #1 trigger for Lenovo BSODs with stop codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, and PAGE_FAULT_IN_NONPAGED_AREA.
Root cause 2: Faulty or overclocked RAM, thermal throttling due to dust accumulation, and corrupted Windows system files (triggering CRITICAL_PROCESS_DIED or MEMORY_MANAGEMENT BSODs) are common hardware-side causes, especially on Lenovo Legion gaming laptops.
Root cause 3: Lenovo-specific software conflicts — including Lenovo Vantage, Legion Toolkit, and firmware bugs — can destabilize the kernel and cause repeated blue screens, often fixed by updating BIOS/UEFI firmware and reinstalling Lenovo system software.
Quick fix summary: Boot into Safe Mode, run Driver Verifier and WinDbg to identify the faulty driver, update or roll back the offending driver, run SFC /scannow and DISM to repair system files, test RAM with MemTest86, check thermals with HWiNFO64, and update BIOS to the latest version from Lenovo Support.

Fix Approaches Compared
Method	When to Use	Time	Risk
Update/Roll Back Drivers	BSOD after Windows Update or driver install; stop codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL	10-20 min	Low
SFC & DISM System File Repair	CRITICAL_PROCESS_DIED or SYSTEM_SERVICE_EXCEPTION after software corruption	15-30 min	Low
MemTest86 RAM Test	MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA, random BSODs under load	2-8 hours	None
Update BIOS/UEFI Firmware	Repeated BSODs after hardware upgrade or on new Lenovo Legion units	20-30 min	Medium
Reinstall Lenovo Vantage / Legion Toolkit	BSODs tied to Lenovo software or after major Windows update	15-25 min	Low
Clean Windows Reinstall	Persistent BSODs with no identifiable single cause; corrupted OS	1-3 hours	High (data loss)
WinDbg / BlueScreenView Analysis	Identifying root cause before attempting fixes	10-15 min	None
Thermal Paste Replacement	Overheating BSODs; CPU/GPU temps above 95°C under load on Legion	30-60 min	Medium (hardware)

Understanding the Lenovo BSOD Problem

A Blue Screen of Death (BSOD) on a Lenovo or Lenovo Legion laptop is Windows' way of halting to prevent hardware or data damage. The screen displays a stop code — a technical clue pointing to the failure source. Common stop codes seen on Lenovo devices include:

DRIVER_IRQL_NOT_LESS_OR_EQUAL — a driver tried to access memory at an invalid IRQL
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — a system thread encountered an unhandled exception (often GPU driver related)
PAGE_FAULT_IN_NONPAGED_AREA — a process tried to access non-existent memory
MEMORY_MANAGEMENT — memory corruption or RAM hardware fault
CRITICAL_PROCESS_DIED — a critical Windows process terminated unexpectedly
KMODE_EXCEPTION_NOT_HANDLED — kernel mode code exception, often linked to hardware incompatibility
WHEA_UNCORRECTABLE_ERROR — hardware-level error detected by Windows Hardware Error Architecture

Lenovo Legion users frequently report BSODs during gaming sessions, often tied to NVIDIA/AMD GPU driver conflicts, aggressive CPU/GPU overclocking, or thermal throttling.

Step 1: Capture the Crash Dump and Identify the Faulty Driver

Before touching drivers or settings, identify what is actually causing the BSOD.

Enable complete memory dumps:

Press Win + R, type sysdm.cpl, press Enter.
Go to Advanced > Startup and Recovery > Settings.
Under Write debugging information, select Kernel memory dump.
Click OK and restart.

After the next crash, the dump file will be at C:\Windows\Minidump\.

Use BlueScreenView (free, no install required): Download NirSoft BlueScreenView, point it at C:\Windows\Minidump\, and it will list the driver that caused each crash in the Caused By Driver column. Common culprits on Lenovo:

nvlddmkm.sys — NVIDIA display driver
amdkmdag.sys — AMD GPU driver
LenovoVantageService.exe — Lenovo Vantage
intelppm.sys — Intel processor power management
tcpip.sys — network stack (often Killer/Realtek driver related)

Use WinDbg for deep analysis: Install WinDbg from the Microsoft Store, open the .dmp file, and run:

!analyze -v

Look for the FAULTING_MODULE and STACK_TEXT sections.

Step 2: Boot into Safe Mode

If the BSOD occurs at startup, hold Shift and click Restart from the login screen, then navigate: Troubleshoot > Advanced Options > Startup Settings > Restart > Press 4 (Safe Mode)

In Safe Mode, Windows loads only essential drivers, allowing you to uninstall problematic drivers or run repairs.

Step 3: Update or Roll Back Drivers

For GPU drivers (most common Lenovo Legion fix):

Press Win + X > Device Manager.
Expand Display adapters, right-click your GPU, select Update driver or Roll back driver.
For NVIDIA: Use DDU (Display Driver Uninstaller) in Safe Mode to completely remove old drivers, then install the latest from nvidia.com.
For AMD: Use AMD Cleanup Utility, then install from amd.com.

For Lenovo chipset and system drivers: Visit support.lenovo.com, enter your model (e.g., Legion 5 Pro, ThinkPad X1 Carbon), and download the latest:

Chipset driver
Intel ME (Management Engine) firmware
Thunderbolt/USB driver
Wi-Fi driver (Intel/Killer/Realtek)

Step 4: Repair Windows System Files

Run these commands in an Administrator Command Prompt:

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

Restart after completion. SFC repairs protected system files; DISM repairs the Windows image itself.

Step 5: Test RAM with MemTest86

For MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA BSODs:

Download MemTest86 and create a bootable USB.
Boot from the USB and run at least 2 full passes (4+ hours recommended).
Any errors indicate failing RAM — replace the faulty DIMM.

On many Lenovo Legion models, RAM is user-replaceable (2x SO-DIMM slots). Reseat RAM sticks as a first step.

Step 6: Check Thermals and Clean Cooling System

Lenovo Legion BSODs during gaming are frequently thermal. Use HWiNFO64 to monitor:

CPU Package Temp: sustained >95°C = thermal throttling risk
GPU Hot Spot Temp: >100°C = danger zone

Fixes:

Clean laptop vents with compressed air (every 6-12 months).
In Lenovo Vantage or Legion Toolkit, switch to Performance Mode to increase fan speed.
Advanced: Replace dried thermal paste on CPU/GPU die (improves temps by 10-20°C on 2+ year old units).
Enable Fn + Q Performance Mode directly on Lenovo Legion keyboards.

Step 7: Update BIOS/UEFI Firmware

Lenovo frequently releases BIOS updates that fix stability and BSOD issues.

Press Win + R, type msinfo32, check BIOS Version/Date.
Go to support.lenovo.com, search your model.
Download the latest BIOS update (.exe installer for Windows flash).
Run the installer — do not interrupt — laptop must be plugged in.

Warning: Never flash BIOS on battery power. A failed flash can brick the device.

Step 8: Reinstall or Remove Lenovo Vantage / Legion Toolkit

Lenovo Vantage and third-party tools like Legion Toolkit can conflict with Windows updates.

To reinstall Lenovo Vantage:

Uninstall from Settings > Apps.
Also uninstall Lenovo Vantage Service and LenovoUtility.
Restart, then reinstall from the Microsoft Store.

For Legion Toolkit conflicts: Check the project's GitHub issues page for known BSOD-related bugs and update to the latest release.

Step 9: Check Event Viewer for Pre-BSOD Events

Open Event Viewer (eventvwr.msc) > Windows Logs > System and look for Critical or Error events timestamped just before each BSOD. Filter for Event ID 41 (unexpected shutdown) and Event ID 1001 (BugCheck — records the stop code and dump file location).

Step 10: Last Resort — Clean Windows Reinstall

If BSODs persist after all above steps:

Back up all data to external drive.
Create Windows 11/10 installation media via Microsoft Media Creation Tool.
Boot from USB, select Custom Install, format the system partition, and reinstall.
After reinstall, install only Lenovo drivers from the official support page — avoid third-party driver updaters.

Frequently Asked Questions

powershell

# ============================================================
# Lenovo BSOD Diagnostic & Repair Script
# Run in PowerShell as Administrator
# ============================================================

# --- 1. Check recent BSOD events in Event Log ---
Write-Host "=== Recent BSOD Events (Event ID 41 & 1001) ==="
Get-WinEvent -FilterHashtable @{LogName='System'; Id=41,1001} -MaxEvents 10 |
    Select-Object TimeCreated, Id, Message |
    Format-List

# --- 2. List minidump files ---
Write-Host "=== Minidump Files ==="
$dumpPath = "C:\Windows\Minidump"
if (Test-Path $dumpPath) {
    Get-ChildItem $dumpPath -Filter "*.dmp" | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length
} else {
    Write-Host "No minidump folder found. Enable kernel memory dumps in System Properties."
}

# --- 3. Run System File Checker ---
Write-Host "=== Running SFC (System File Checker) ==="
sfc /scannow

# --- 4. Run DISM Health Restore ---
Write-Host "=== Running DISM RestoreHealth ==="
DISM /Online /Cleanup-Image /RestoreHealth

# --- 5. Check Driver Verifier status ---
Write-Host "=== Driver Verifier Status ==="
verifier /query

# --- 6. Enable Driver Verifier for unsigned/3rd party drivers (use carefully) ---
# Uncomment to enable -- causes BSOD intentionally if faulty driver found
# verifier /standard /driver *.sys

# --- 7. List recently installed drivers ---
Write-Host "=== Drivers Installed in Last 30 Days ==="
$cutoff = (Get-Date).AddDays(-30)
Get-WmiObject Win32_PnPSignedDriver |
    Where-Object { $_.DriverDate -and [datetime]::ParseExact($_.DriverDate.Substring(0,8), 'yyyyMMdd', $null) -ge $cutoff } |
    Select-Object DeviceName, DriverVersion, DriverDate |
    Sort-Object DriverDate -Descending |
    Format-Table -AutoSize

# --- 8. Check RAM usage and errors ---
Write-Host "=== Memory Diagnostics Scheduled ==="
# This schedules Windows Memory Diagnostic on next reboot:
# MdSched.exe   (uncomment to launch GUI)
# For CLI scheduling:
schtasks /run /tn "\Microsoft\Windows\MemoryDiagnostic\ProcessMemoryDiagnosticEvents"

# --- 9. Check temperatures via WMI (basic, use HWiNFO64 for full detail) ---
Write-Host "=== CPU Temperature Sensors (if available via WMI) ==="
Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace "root/wmi" 2>$null |
    ForEach-Object {
        $tempC = ($_.CurrentTemperature - 2732) / 10
        Write-Host "Thermal Zone: $($_.InstanceName) | Temp: ${tempC}°C"
    }

# --- 10. Check BIOS version ---
Write-Host "=== Current BIOS Version ==="
Get-WmiObject Win32_BIOS | Select-Object Manufacturer, Name, Version, ReleaseDate | Format-List

# --- 11. Export system info to file ---
Write-Host "=== Exporting System Info to Desktop ==="
Get-ComputerInfo | Out-File "$env:USERPROFILE\Desktop\lenovo_sysinfo.txt"
Write-Host "System info saved to Desktop\lenovo_sysinfo.txt"

# --- 12. Check for pending Windows Updates ---
Write-Host "=== Checking Windows Update Status ==="
(New-Object -ComObject Microsoft.Update.AutoUpdate).Results

Write-Host ""
Write-Host "=== Diagnostic Complete. Review output above and minidump files. ==="
Write-Host "Next steps: Open BlueScreenView, point to C:\Windows\Minidump, identify faulty driver."

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows system administrators with 10+ years of experience diagnosing kernel crashes, BSOD events, and hardware faults across enterprise and consumer environments. We specialize in translating cryptic stop codes into actionable fixes for everyday users and IT professionals alike.

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.