Windows BSOD 0x0000011B — DRIVER_RETURNED_HOLDING_CANCEL_LOCK — What It Means & How to Fix It

What Does This Error Mean?

Windows BSOD 0x0000011B — DRIVER_RETURNED_HOLDING_CANCEL_LOCK — means a device driver released control back to Windows while still holding an internal I/O cancel lock. This is a programming error in the driver — the driver forgot to release a lock it was holding. Windows detects this as a critical error and crashes to prevent the system from becoming unstable. The most common trigger is an incompatible, outdated, or corrupted driver.

Affected Models

Windows 10 all versions
Windows 11 all versions
Systems after driver updates or Windows updates
Systems with third-party hardware with custom drivers
Network printer connections over SMB

Common Causes

Outdated or buggy device driver returning from an I/O operation without releasing its cancel lock
Incompatible driver installed after a recent Windows update changed internal driver interface requirements
Network printer driver bug — this BSOD famously appeared on Windows 10 and 11 systems connected to network printers after a Windows update
Third-party security software with kernel-mode drivers causing a lock management error
Corrupted driver installation with missing or modified driver files

How to Fix It

If this BSOD appeared after a Windows Update, uninstall the recent update. Go to Settings, Windows Update, Update History, Uninstall Updates. Look for the most recent update and uninstall it, then restart.

Microsoft released a Windows update in early 2022 (KB5008212, KB5005565, and related) that caused widespread 0x0000011B crashes on systems with network printers. Uninstalling these updates immediately resolved the issue for most users.
Update all device drivers — especially network adapter, printer, and storage drivers. Go to Device Manager, right-click each device, and select Update Driver. Or download the latest drivers directly from each hardware manufacturer.

An older version of a driver may contain the locking bug. Updated drivers from manufacturers often fix these issues.
Disconnect any network printers and test for stability. If the BSOD stops occurring when the printer is disconnected, the printer driver is the source. Reinstall the printer using the latest driver from the printer manufacturer's website.

Network printers use SMB (file sharing) protocols on Windows. Driver conflicts with Windows SMB updates commonly trigger 0x0000011B.
Temporarily disable third-party antivirus or security software to test whether its kernel driver is causing the lock error. Replace it with Windows Defender if the BSOD resolves after disabling the third-party security product.

Security software uses deep kernel hooks that interact with Windows I/O. A poorly updated security driver can trigger this exact BSOD.
Run SFC and DISM to repair corrupted system files. Open Command Prompt as Administrator. Run: sfc /scannow and then DISM /Online /Cleanup-Image /RestoreHealth. Restart after both complete.

Corrupted Windows driver support files can cause previously working drivers to develop locking errors.

When to Call a Professional

This BSOD is almost always caused by a driver issue that resolves through software steps. If rolling back drivers and uninstalling recent Windows updates does not help, a technician can analyze the crash dump to identify the specific faulty driver.

Frequently Asked Questions

Why did this BSOD start after a Windows Update?

Windows updates sometimes change internal kernel interfaces that drivers rely on. If a driver was written against an older interface that changed in an update, it may now return from operations incorrectly. Microsoft's own printer-related updates in 2022 caused widespread 0x0000011B crashes. Uninstalling the problematic update restores stability until an updated driver is available.

How do I find out which driver caused 0x0000011B?

Download WhoCrashed (free) and point it at the crash dump file in C:\Windows\Minidump. It will show you the driver name and description that caused the crash. Once you know the driver, you can update, roll back, or replace it.

Is 0x0000011B a hardware failure?

Not typically. It is almost always a software driver error. The driver has a programming bug — it forgot to release a lock. Hardware failures have different BSOD codes. Focus on driver updates and Windows update rollbacks before suspecting hardware.