Blue Screen on Lenovo Laptop: Fix BSOD, DPC_WATCHDOG_VIOLATION, SYSTEM_SERVICE_EXCEPTION & More
Fix Lenovo laptop blue screen errors including DPC_WATCHDOG_VIOLATION, INACCESSIBLE_BOOT_DEVICE & WDF_VIOLATION with step-by-step commands and driver fixes.
- Most Lenovo blue screens are caused by outdated or corrupt drivers, especially Intel RST, Realtek USB (rtusba64.sys), or graphics drivers.
- Stop codes like DPC_WATCHDOG_VIOLATION, SYSTEM_SERVICE_EXCEPTION, WDF_VIOLATION, and INACCESSIBLE_BOOT_DEVICE each point to specific subsystems — driver, storage, or Windows system files.
- Quick fix: Boot into Safe Mode, uninstall the offending driver via Device Manager or DISM, run 'sfc /scannow' and 'chkdsk /f /r', then update all Lenovo drivers through Lenovo Vantage or manual INF install.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Update/Rollback Drivers via Device Manager | Driver-related BSOD (DPC_WATCHDOG, WDF_VIOLATION, rtusba64.sys) | 10–20 min | Low |
| SFC & DISM System File Repair | Corrupted Windows system files causing SYSTEM_SERVICE_EXCEPTION | 15–40 min | Low |
| CHKDSK Bad Sector Scan | INACCESSIBLE_BOOT_DEVICE or storage-related BSOD on startup | 30–90 min | Low |
| Disable Intel RST / Switch SATA Mode | INACCESSIBLE_BOOT_DEVICE on Lenovo IdeaPad/ThinkPad after BIOS update | 5–10 min | Medium |
| Windows Startup Repair (WinRE) | Cannot boot into Windows at all; repeated blue screen on startup | 20–40 min | Low |
| Clean Reinstall of Windows | All other methods failed; persistent or undiagnosable BSOD | 60–120 min | High (data loss) |
| Lenovo Vantage Driver Update | Generic or unidentified BSOD; no specific stop code | 15–30 min | Low |
| Memory (RAM) Diagnostic | Random BSOD with no consistent stop code or after RAM change | 30–60 min | None |
Understanding Lenovo Blue Screen Errors
A Blue Screen of Death (BSOD) on a Lenovo laptop — whether it's a ThinkPad, IdeaPad 3, IdeaPad 330, Legion 5, Legion Pro, or X1 Carbon — halts Windows with a stop code and a sad-face emoji. The screen typically reads:
Your PC ran into a problem and needs to restart.
Stop code: DPC_WATCHDOG_VIOLATION
Common stop codes on Lenovo hardware include:
- DPC_WATCHDOG_VIOLATION — A driver or hardware component did not respond within the timeout window.
- SYSTEM_SERVICE_EXCEPTION — A system service or driver threw an unhandled exception (often
atikmdag.sys,nvlddmkm.sys, orrtusba64.sys). - WDF_VIOLATION — Windows Driver Framework detected a contract violation in a kernel-mode driver.
- INACCESSIBLE_BOOT_DEVICE — Windows cannot access the boot volume, usually after a firmware or SATA controller mode change.
- MEMORY_MANAGEMENT — Faulty RAM or a driver is writing to protected memory.
Step 1: Identify the Stop Code and Faulty Driver
Before fixing anything, extract the exact stop code and the offending .sys file from the minidump.
Method A — Windows Event Viewer:
- Press
Win + R, typeeventvwr.msc, press Enter. - Navigate to Windows Logs → System.
- Filter by Event ID 41 (Kernel-Power) or Event ID 1001 (BugCheck).
- The BugCheck entry shows the stop code and parameters.
Method B — WinDbg / WhoCrashed:
Download WhoCrashed (free) from Resplendence Software. Point it at C:\Windows\Minidump to get a plain-English summary of each crash dump including the culprit driver.
Method C — PowerShell one-liner:
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 1001} | Select-Object -First 5 | Format-List TimeCreated, Message
Step 2: Boot Into Safe Mode (If Windows Won't Start)
If your Lenovo laptop shows a blue screen on startup and loops:
- Force-shutdown the laptop three times in a row by holding the power button during boot. Windows will enter Automatic Repair mode.
- Select Advanced options → Troubleshoot → Advanced options → Startup Settings → Restart.
- Press F4 for Safe Mode or F5 for Safe Mode with Networking.
Alternatively, boot from a Windows USB installer and choose Repair your computer.
Step 3: Fix DPC_WATCHDOG_VIOLATION on Lenovo
This is the most common Lenovo BSOD, often triggered by Intel Rapid Storage Technology (RST) drivers or SSD firmware.
Fix A — Update Intel RST Driver:
- Go to Device Manager (
devmgmt.msc). - Expand IDE ATA/ATAPI Controllers or Storage Controllers.
- Right-click Intel RST entry → Update driver.
- Alternatively, download the latest RST driver from Intel's website: https://www.intel.com/content/www/us/en/download-center/home.html
Fix B — Switch SATA Controller Mode (for INACCESSIBLE_BOOT_DEVICE too):
- Restart and enter BIOS: press F1 (ThinkPad) or F2 (IdeaPad/Legion) repeatedly at boot.
- Navigate to Config → Storage → SATA Controller Mode.
- Switch from RAID to AHCI or vice versa depending on your current setting.
- Save and reboot. If Windows fails to start, revert the change.
Fix C — Disable Intel RST via Registry (before switching to AHCI):
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStorV" /v Start /t REG_DWORD /d 0 /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci" /v Start /t REG_DWORD /d 0 /f
Run these in an elevated Command Prompt before changing the BIOS SATA mode to avoid a boot failure.
Step 4: Fix rtusba64.sys Blue Screen on Lenovo
The file rtusba64.sys belongs to the Realtek USB audio/card reader driver. It is a known offender on Lenovo IdeaPad and Legion models.
- Open Device Manager.
- Expand Universal Serial Bus controllers or Sound, video and game controllers.
- Find any Realtek USB device, right-click → Uninstall device (check "Delete the driver software for this device").
- Restart. Windows will attempt to reinstall a generic driver.
- To prevent auto-reinstall, block the driver via Group Policy or install the updated Realtek driver from Lenovo's support page: https://pcsupport.lenovo.com
Step 5: Fix SYSTEM_SERVICE_EXCEPTION and WDF_VIOLATION
Both stop codes commonly implicate third-party antivirus software, GPU drivers, or USB drivers.
GPU Driver Reinstall (NVIDIA/AMD on Legion 5, IdeaPad Gaming 3):
- Boot into Safe Mode.
- Download DDU (Display Driver Uninstaller) from Guru3D.
- Run DDU in Safe Mode to fully remove GPU drivers.
- Reboot normally and install the latest GPU driver from NVIDIA or AMD directly.
Antivirus / Security Software: Temporarily uninstall third-party antivirus (Avast, McAfee, Kaspersky) in Safe Mode. If the BSOD stops, the security driver was the cause. Reinstall after updating to the latest version.
Step 6: Run System File Checker and DISM
Corrupt Windows system files are a frequent cause of SYSTEM_SERVICE_EXCEPTION on Lenovo laptops.
:: Run as Administrator
sfc /scannow
:: If SFC reports unfixable errors, use DISM:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
:: Then re-run SFC
sfc /scannow
Step 7: Check Disk Health (INACCESSIBLE_BOOT_DEVICE)
For Lenovo laptops crashing with a blue screen and stop code INACCESSIBLE_BOOT_DEVICE, run disk checks:
:: Schedule CHKDSK on next reboot (C: drive)
chkdsk C: /f /r /x
:: Check NVMe SSD health with PowerShell
Get-PhysicalDisk | Select FriendlyName, HealthStatus, OperationalStatus, Size
:: Or use CrystalDiskInfo for a GUI health report
Step 8: Check RAM with Windows Memory Diagnostic
Random BSODs with varying stop codes on Lenovo IdeaPad or ThinkPad often indicate failing RAM.
- Press
Win + R, typemdsched.exe, press Enter. - Choose Restart now and check for problems.
- The tool runs on next boot and logs results in Event Viewer under Windows Logs → System (Event ID 1101 or 1102).
For more thorough testing, create a bootable MemTest86 USB and run it overnight.
Step 9: Update BIOS Firmware on Lenovo
Outdated BIOS can cause hardware compatibility issues leading to BSODs, especially on ThinkPad X1 Carbon and Legion 5 models.
- Open Lenovo Vantage → Device → System Update.
- Install any available BIOS/UEFI firmware updates.
- Alternatively, visit https://pcsupport.lenovo.com, enter your model number, and download the BIOS update package.
- Run the
.exeinstaller while plugged into AC power.
Warning: Never update BIOS on battery power. A failed BIOS flash can brick the laptop.
Step 10: Last Resort — Windows Startup Repair or Reset
If the laptop shows a blue screen on startup and all driver/file fixes fail:
- Boot to WinRE (Windows Recovery Environment) using a Windows 10/11 USB installer.
- Select Troubleshoot → Advanced options → Startup Repair. Let it run.
- If Startup Repair fails, try System Restore to a known-good restore point.
- If no restore points exist, select Reset this PC and choose Keep my files for a non-destructive reinstall.
For persistent Lenovo blue screen issues on startup with INACCESSIBLE_BOOT_DEVICE, the bootrec commands can rebuild the BCD store:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Frequently Asked Questions
# ============================================================
# Lenovo Blue Screen Diagnostic & Fix Script
# Run as Administrator in PowerShell
# ============================================================
# 1. Check last 5 BugCheck events (BSOD records)
Write-Host "=== Recent BSOD Events ==" -ForegroundColor Cyan
Get-WinEvent -LogName System -ErrorAction SilentlyContinue |
Where-Object { $_.Id -eq 1001 -and $_.ProviderName -eq 'Microsoft-Windows-WER-SystemErrorReporting' } |
Select-Object -First 5 |
Format-List TimeCreated, Message
# 2. List minidump files
Write-Host "
=== Minidump Files (open with WinDbg or WhoCrashed) ===" -ForegroundColor Cyan
Get-ChildItem -Path "$env:SystemRoot\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue |
Sort-Object LastWriteTime -Descending |
Select-Object -First 10 |
Format-Table Name, LastWriteTime, Length -AutoSize
# 3. Run System File Checker
Write-Host "
=== Running SFC (System File Checker) ===" -ForegroundColor Cyan
sfc /scannow
# 4. Run DISM health restore
Write-Host "
=== Running DISM RestoreHealth ===" -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth
# 5. Schedule CHKDSK on C: drive at next reboot
Write-Host "
=== Scheduling CHKDSK for next reboot ===" -ForegroundColor Cyan
echo Y | chkdsk C: /f /r
# 6. Check physical disk health
Write-Host "
=== Disk Health Status ===" -ForegroundColor Cyan
Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus |
Format-Table -AutoSize
# 7. List recently installed drivers (last 30 days)
Write-Host "
=== Recently Installed/Updated Drivers (last 30 days) ===" -ForegroundColor Cyan
$cutoff = (Get-Date).AddDays(-30)
Get-WmiObject Win32_PnPSignedDriver |
Where-Object { $_.DriverDate -ne $null -and [datetime]::ParseExact($_.DriverDate.Split('.')[0], 'yyyyMMdd', $null) -gt $cutoff } |
Select-Object DeviceName, DriverVersion, DriverDate |
Sort-Object DriverDate -Descending |
Format-Table -AutoSize
# 8. Check for rtusba64.sys specifically
Write-Host "
=== Checking for rtusba64.sys (known Lenovo BSOD driver) ===" -ForegroundColor Cyan
$rtusba = Get-WmiObject Win32_PnPSignedDriver | Where-Object { $_.InfName -like '*rtusba*' -or $_.DeviceName -like '*Realtek USB*' }
if ($rtusba) {
Write-Host "Found Realtek USB driver(s) — consider updating or uninstalling:" -ForegroundColor Yellow
$rtusba | Select-Object DeviceName, DriverVersion, InfName | Format-Table -AutoSize
} else {
Write-Host "rtusba64.sys not found in signed driver list." -ForegroundColor Green
}
# 9. Run Windows Memory Diagnostic (scheduled for next reboot)
Write-Host "
=== Scheduling Memory Diagnostic ===" -ForegroundColor Cyan
Start-Process -FilePath "mdsched.exe"
# 10. Reset BSOD minidump path (ensure dumps are saved)
Write-Host "
=== Verifying Crash Dump Configuration ===" -ForegroundColor Cyan
$crashKey = 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl'
$dumpType = (Get-ItemProperty -Path $crashKey -Name CrashDumpEnabled -ErrorAction SilentlyContinue).CrashDumpEnabled
if ($dumpType -lt 3) {
Set-ItemProperty -Path $crashKey -Name CrashDumpEnabled -Value 3
Write-Host "Crash dump type set to Small Memory Dump for future BSODs." -ForegroundColor Green
} else {
Write-Host "Crash dump already configured (type: $dumpType)." -ForegroundColor Green
}
Write-Host "
=== Diagnostics Complete. Review output above and reboot. ===" -ForegroundColor GreenError Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, Windows SREs, and hardware diagnostics specialists with combined experience across enterprise IT, cloud infrastructure, and consumer device support. We produce hands-on, command-level troubleshooting guides grounded in real incident post-mortems and verified against official Microsoft, Lenovo, Intel, and NVIDIA documentation.
Sources
- https://support.microsoft.com/en-us/windows/troubleshoot-blue-screen-errors-5c62726c-6489-52da-a372-3831d059de49
- https://pcsupport.lenovo.com/us/en/solutions/ht505725-blue-screen-error-messages-on-windows
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x3b--system-service-exception
- https://www.intel.com/content/www/us/en/download/15079/intel-rapid-storage-technology-intel-rst-user-interface-and-driver.html
- https://answers.microsoft.com/en-us/windows/forum/all/bsod-wdf-violation/4cb9e9fd-2a61-4a85-8960-1b6d03c87e2d
- https://stackoverflow.com/questions/tagged/bsod