Why does my Lenovo laptop keep getting a blue screen with a sad face and the stop code DPC_WATCHDOG_VIOLATION?

DPC_WATCHDOG_VIOLATION on Lenovo laptops is most commonly caused by the Intel Rapid Storage Technology (IRST) driver being out of date or incompatible with your current Windows version. It can also be triggered by SSD firmware issues or conflicting storage controller modes in BIOS. Fix it by updating the IRST driver from Lenovo's support site, or by switching the SATA controller mode from 'RST with Optane' to 'AHCI' in BIOS (following the safe procedure to avoid creating an INACCESSIBLE_BOOT_DEVICE error in the process).

My Lenovo IdeaPad 330 or IdeaPad 3 blue screens with rtusba64.sys — what does this mean?

rtusba64.sys is the Realtek USB 3.0 or card reader driver. When it crashes, it means the driver is corrupt or incompatible with your current Windows kernel version. Boot into Safe Mode, open Device Manager, find the Realtek USB or card reader device, uninstall it (selecting 'Delete driver software'), then reboot. Download and install the latest Realtek driver from Lenovo's support page for your exact model number.

My Lenovo ThinkPad or X1 Carbon shows 'INACCESSIBLE_BOOT_DEVICE' on startup after a Windows update — how do I fix it?

This error almost always occurs when a Windows update changes how the storage controller driver initializes, or when the BIOS SATA mode doesn't match what Windows expects. Boot from a Windows installation USB, open Command Prompt from Recovery Options, and run: bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd. Also check BIOS settings (F1 on ThinkPad) to ensure the storage controller mode hasn't changed. If all else fails, you may need to reinstall Windows while preserving files using the 'Reset this PC' option.

My Lenovo Legion 5 or Legion laptop has a blue screen only when gaming — what causes this and how do I fix it?

Blue screens during gaming on Lenovo Legion laptops are typically caused by NVIDIA or AMD GPU driver issues, overheating, or RAM instability during high load. First, uninstall your current GPU driver using DDU (Display Driver Uninstaller) in Safe Mode and install the latest stable driver from NVIDIA or AMD directly. Check temperatures using HWiNFO or MSI Afterburner — if GPU/CPU temps exceed 95°C, clean the laptop vents and consider repasting the thermal compound. Also run MemTest86 to rule out RAM errors under load.

How do I fix a Lenovo laptop blue screen on startup when I can't even get to Windows?

If your Lenovo blue screens before Windows loads, force-shutdown the laptop 3 times during the Windows logo to trigger Automatic Repair. From there, go to Advanced Options → Startup Settings → Safe Mode. In Safe Mode, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in an elevated Command Prompt. If Safe Mode also fails, boot from a Windows USB installer, use the Recovery Command Prompt to run 'bootrec /rebuildbcd', and check the disk with 'chkdsk C: /f /r'. If the stop code is SYSTEM_SERVICE_EXCEPTION or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, use WinDbg or WhoCrashed to identify the offending .sys file from the minidump.

Blue Screen Lenovo Laptop: Fix BSOD Errors (DPC_WATCHDOG_VIOLATION, SYSTEM_SERVICE_EXCEPTION, INACCESSIBLE_BOOT_DEVICE & More)

Fix Lenovo laptop blue screen errors including DPC_WATCHDOG_VIOLATION, SYSTEM_SERVICE_EXCEPTION & INACCESSIBLE_BOOT_DEVICE with step-by-step commands and driver

Last updated: March 1, 2026

Last verified: March 1, 2026

2,284 words

Key Takeaways

Most Lenovo BSOD errors (DPC_WATCHDOG_VIOLATION, SYSTEM_SERVICE_EXCEPTION, WDF_VIOLATION) are caused by outdated, corrupt, or incompatible drivers — especially after Windows updates or hardware additions.
INACCESSIBLE_BOOT_DEVICE and blank blue screen on startup usually point to corrupt boot configuration, failed storage drivers (e.g., IRST/RST), or a failing SSD/HDD.
The rtusba64.sys BSOD is specifically caused by Realtek USB adapter drivers conflicting with the Windows kernel — uninstalling or updating the driver resolves it.
Quick fix summary: Boot into Safe Mode → run 'sfc /scannow' and 'DISM /RestoreHealth' → update or roll back drivers → check RAM with MemTest86 → repair boot with 'bootrec /fixmbr' if needed.

Lenovo Blue Screen Fix Approaches Compared
Method	When to Use	Time	Risk
Update/Roll Back Drivers (Device Manager)	After Windows Update or new hardware install causes BSOD	5–15 min	Low
SFC /scannow + DISM /RestoreHealth	Corrupted system files suspected; SYSTEM_SERVICE_EXCEPTION or WDF_VIOLATION	15–30 min	Very Low
Boot into Safe Mode + uninstall problem driver	Can't reach desktop; crash on startup (rtusba64.sys, rtusba64)	10–20 min	Low
Lenovo Vantage / System Update tool	Multiple drivers out of date; Lenovo-specific firmware needs update	20–40 min	Low
bootrec /fixmbr + bootrec /rebuildbcd	INACCESSIBLE_BOOT_DEVICE; won't boot at all	10–20 min	Medium
CHKDSK /f /r	Disk errors suspected; random crashes with disk-related stop codes	30–120 min	Low–Medium
MemTest86 RAM Test	Random BSODs across different stop codes; memory corruption suspected	60–240 min	Very Low
Reset / Clean Install Windows	All other fixes failed; persistent BSOD with no identifiable driver	60–180 min	High (data loss)

Understanding Lenovo Blue Screen Errors

A Blue Screen of Death (BSOD) on a Lenovo laptop — whether it's a ThinkPad, IdeaPad, Legion, or X1 Carbon — means Windows has encountered a fatal kernel error it cannot recover from safely. The screen displays a stop code (e.g., DPC_WATCHDOG_VIOLATION, SYSTEM_SERVICE_EXCEPTION, WDF_VIOLATION, INACCESSIBLE_BOOT_DEVICE) and either reboots or freezes with a sad face emoji and a QR code.

Common stop codes seen on Lenovo devices include:

DPC_WATCHDOG_VIOLATION — A Deferred Procedure Call ran too long; often SSD firmware or Intel RST driver issues.
SYSTEM_SERVICE_EXCEPTION — A system service crashed; caused by faulty drivers or corrupt system files.
WDF_VIOLATION — Windows Driver Framework violation; commonly Lenovo-specific drivers or USB drivers.
INACCESSIBLE_BOOT_DEVICE — Windows can't read the boot partition; often after a Windows update changes storage driver mode.
rtusba64.sys BSOD — Realtek USB 3.0/3.1 card reader or adapter driver conflict.
Blank blue screen with cursor — Display driver or GPU driver crash (common on Legion 5 and IdeaPad Gaming 3).

Step 1: Identify the Exact Stop Code

Before applying any fix, confirm which stop code you're dealing with.

If you can reach the desktop:

Press Win + X → select Event Viewer.
Navigate to Windows Logs → System.
Filter by Critical events and look for entries from source BugCheck.
Note the stop code and the faulting module (e.g., rtusba64.sys, ntfs.sys, iastorav.sys).

Alternatively, open PowerShell as Administrator and run:

Get-EventLog -LogName System -EntryType Error -Newest 20 | Where-Object {$_.Source -eq 'BugCheck'} | Format-List

You can also use WinDbg or the free WhoCrashed tool to analyze minidump files located at C:\Windows\Minidump\.

Step 2: Boot Into Safe Mode (If You Can't Reach Desktop)

If your Lenovo laptop blue screens on startup:

Force-shutdown the laptop 3 times in a row during the Windows logo — this triggers Automatic Repair mode.
Select Advanced Options → Startup Settings → Restart.
Press 4 for Safe Mode or 5 for Safe Mode with Networking.

Alternatively, hold Shift while clicking Restart from the login screen.

On Lenovo ThinkPads, you can also press F1 during POST to enter BIOS and verify boot order, or press F12 to select boot device.

Step 3: Fix DPC_WATCHDOG_VIOLATION on Lenovo

This is the most common BSOD on Lenovo IdeaPad, Legion, and ThinkPad models. The primary cause is a conflict between the Intel Rapid Storage Technology (IRST/RST) driver and Windows.

Fix A: Update Intel RST Driver

Visit Lenovo Support Drivers and enter your model.
Download the latest Intel RST or Intel VMD driver.
Install and reboot.

Fix B: Switch SATA Mode in BIOS

Restart and press F1 (ThinkPad) or F2 (IdeaPad/Legion) to enter BIOS.
Navigate to Configuration → Storage → Controller Mode.
If set to RST with Optane, try switching to AHCI.

Warning: Switching SATA modes without preparation can cause INACCESSIBLE_BOOT_DEVICE. Enable AHCI in Windows first via bcdedit /set {current} safeboot minimal, reboot into BIOS to switch mode, then reboot again and run bcdedit /deletevalue {current} safeboot.

Step 4: Fix SYSTEM_SERVICE_EXCEPTION and WDF_VIOLATION

These stop codes typically indicate corrupt system files or a driver misbehaving within the Windows kernel.

Fix A: Run System File Checker and DISM Open Command Prompt as Administrator:

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

Reboot after completion.

Fix B: Update or Uninstall Lenovo-Specific Drivers

Open Device Manager (Win + X → Device Manager).
Look for devices with a yellow warning icon.
For WDF_VIOLATION, check Human Interface Devices, System Devices, and Network Adapters.
Right-click the flagged driver → Update driver or Uninstall device.

Step 5: Fix rtusba64.sys Blue Screen on Lenovo

The file rtusba64.sys belongs to the Realtek USB card reader or USB 3.0 controller driver. It commonly causes BSODs on Lenovo IdeaPad 330, IdeaPad 3, and similar models.

Boot into Safe Mode.
Open Device Manager.
Expand Universal Serial Bus controllers or Smart Card Readers.
Find any Realtek device, right-click → Uninstall device (check "Delete the driver software" box).
Reboot normally.
Visit Lenovo Support or Realtek's site to download the latest compatible driver version.

Step 6: Fix INACCESSIBLE_BOOT_DEVICE on Lenovo

This BSOD usually appears after a Windows Update or BIOS update changes how the storage controller operates.

Fix via Windows Recovery Environment:

Boot from a Windows 10/11 USB installer.
Select Repair your computer → Troubleshoot → Advanced options → Command Prompt.
Run the following commands:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Then run:

chkdsk C: /f /r /x

Reboot.

If this fails, the storage driver mode mismatch (IDE vs AHCI vs RST) in BIOS is likely the culprit. Enter BIOS and verify the controller mode matches what Windows expects.

Step 7: Address Blank Blue Screen with Cursor (Display/GPU Driver)

Common on Lenovo Legion 5, Legion Blue Screen scenarios, and IdeaPad Gaming 3:

Boot into Safe Mode.
Open Device Manager → Display adapters.
Right-click the GPU (NVIDIA or AMD) → Roll Back Driver if recently updated.
If no rollback option: Uninstall device (check "Delete the driver software").
Download the latest driver directly from NVIDIA or AMD — NOT Windows Update.
Use DDU (Display Driver Uninstaller) in Safe Mode for a clean reinstall.

Step 8: Test RAM and Disk Hardware

If BSODs are random and change stop codes, hardware failure is likely.

RAM Test:

Press Win + R → type mdsched.exe → Restart now and check for problems.
For thorough testing, boot MemTest86 from a USB drive and run for 2+ passes.

Disk Health:

wmic diskdrive get model,status
chkdsk C: /f /r

Or use CrystalDiskInfo (free tool) to check S.M.A.R.T. data for drive health indicators.

Step 9: Use Lenovo Vantage for System-Wide Updates

Lenovo Vantage (pre-installed on most Lenovo laptops, or downloadable from Microsoft Store) can automatically detect and install the correct BIOS, firmware, and driver updates for your specific model — often resolving BSOD issues caused by version mismatches.

Open Lenovo Vantage.
Go to Device → System Update.
Click Check for Updates and install all critical updates.
Reboot.

For ThinkPad users, Lenovo System Update (a separate tool) is the equivalent solution.

Frequently Asked Questions

powershell

# ============================================================
# Lenovo Blue Screen Diagnostic & Fix Script
# Run PowerShell as Administrator
# ============================================================

# --- 1. View recent BugCheck (BSOD) events from Event Log ---
Write-Host "=== Recent BSOD Events ==="
Get-WinEvent -LogName System -MaxEvents 50 | Where-Object { $_.Id -eq 41 -or $_.Id -eq 1001 } | Select-Object TimeCreated, Message | Format-List

# --- 2. List minidump files for analysis ---
Write-Host "`n=== Minidump Files ==="
Get-ChildItem -Path "C:\Windows\Minidump\" -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 Health Restore ==="
DISM /Online /Cleanup-Image /RestoreHealth

# --- 5. Check disk for errors (schedule for next reboot) ---
Write-Host "`n=== Scheduling CHKDSK on C: for next reboot ==="
echo Y | chkdsk C: /f /r

# --- 6. Check driver verifier status ---
Write-Host "`n=== Driver Verifier Status ==="
verifier /query

# --- 7. List recently installed drivers (last 30 days) ---
Write-Host "`n=== Recently Installed Drivers ==="
Get-WmiObject Win32_PnPSignedDriver | Where-Object { $_.DriverDate -gt (Get-Date).AddDays(-30).ToString('yyyyMMdd') } | Select-Object DeviceName, DriverVersion, DriverDate, InfName | Format-Table -AutoSize

# --- 8. Check for problematic drivers with issues ---
Write-Host "`n=== Devices with Driver Issues ==="
Get-WmiObject Win32_PnPEntity | Where-Object { $_.ConfigManagerErrorCode -ne 0 } | Select-Object Name, ConfigManagerErrorCode | Format-Table -AutoSize

# --- 9. Identify faulting .sys file from last crash (requires symbols) ---
# Install WinDbg from Microsoft Store, then analyze with:
# windbg -z C:\Windows\Minidump\<filename>.dmp
# In WinDbg console: !analyze -v

# --- 10. Safe AHCI mode switch preparation (for DPC_WATCHDOG fix) ---
# Uncomment ONLY if switching SATA mode in BIOS from RST to AHCI
# bcdedit /set {current} safeboot minimal
# [Reboot, change BIOS SATA mode to AHCI, reboot again, then run:]
# bcdedit /deletevalue {current} safeboot

# --- 11. Boot Repair Commands (run from WinRE Command Prompt via USB) ---
# bootrec /fixmbr
# bootrec /fixboot
# bootrec /scanos
# bootrec /rebuildbcd
# bcdboot C:\Windows /s C: /f ALL

# --- 12. Uninstall rtusba64.sys driver (Realtek USB) ---
Write-Host "`n=== Searching for Realtek USB Drivers ==="
Get-WmiObject Win32_PnPSignedDriver | Where-Object { $_.DeviceName -like "*Realtek*" -and $_.DeviceName -like "*USB*" } | Select-Object DeviceName, DriverVersion, InfName | Format-Table -AutoSize
# To remove: pnputil /delete-driver <InfName> /uninstall /force

Write-Host "`n=== Diagnostic Complete. Review output above. ==="

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps and SRE engineers with 10+ years of experience diagnosing Windows kernel errors, driver conflicts, and hardware failures across enterprise and consumer environments. Specializing in actionable, command-driven troubleshooting guides for real-world BSOD and system crash scenarios on Lenovo, Dell, HP, and custom-built systems.

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.