The BSOD error code 0x135 (KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL) on Windows 10 is a bug check that occurs when the kernel tries to acquire an auto-boost lock while running at an elevated interrupt request level (IRQL). This is a relatively uncommon crash, but it is almost always tied to a faulty driver, especially storage, network, or anti-cheat drivers, and the fix typically involves updating, rolling back, or removing the offending driver.
What Does Error 0x135 Actually Mean?
The bug check code 0x135 is formally named KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL. To understand it, you need a bit of Windows internals background. Windows uses locks to protect shared data structures. An “auto-boost” lock is a special type of spinlock that temporarily raises the priority of a thread holding the lock to prevent priority inversion (a low-priority thread holding a lock that a high-priority thread needs).
Every lock in Windows has a rule about the maximum IRQL at which it can be acquired. IRQL is a priority level for interrupts; higher IRQL means the code can block lower-priority interrupts. The auto-boost lock is only allowed to be acquired at DISPATCH_LEVEL or below. If a driver attempts to acquire this lock while running at a higher IRQL (like DEVICE_LEVEL or above), the system detects the violation and crashes with bug check 0x135 to prevent data corruption.
In plain terms: a driver is doing something it shouldn’t, and Windows halts to protect your data. The crash is not a hardware failure; it is a software bug in a kernel-mode driver.
Common Causes of the 0x135 Bug Check
Because the bug check is tied to IRQL rules, the root cause is almost always a poorly written or incompatible kernel-mode driver. The most frequently implicated categories include:
- Storage drivers (SATA, NVMe, RAID controllers) – outdated or buggy firmware/drivers can trigger this when handling I/O requests.
- Network adapters – especially Wi-Fi and Ethernet drivers that fail to handle interrupts correctly.
- Anti-cheat and DRM software – kernel-level anti-cheat (e.g., for games) and DRM drivers are known to cause IRQL violations when they interact with other drivers.
- Virtualization software – hypervisors or virtual machine monitors that hook into the kernel.
- System utilities – older versions of overclocking tools, fan control software, or registry cleaners that install kernel drivers.
Windows Update can also introduce a driver that is incompatible with your existing hardware or other drivers, so the crash may appear after an update.
Step-by-Step: How to Fix BSOD 0x135
Before you start, make a note of when the crash happens. Does it occur during boot, while gaming, or when waking from sleep? That context helps narrow down the driver. Follow these steps in order, testing after each one.
- Boot into Safe Mode. Restart your PC and press
F8(or use the Shift+Restart method) to enter Safe Mode. If the system boots without crashing, a third-party driver is almost certainly the culprit. - Check the minidump files. Use the free tool BlueScreenView to open the .dmp files in
C:\Windows\Minidump. It will show which driver was loaded at the time of the crash. The driver name (e.g.,nvlddmkm.sys,e1i65x64.sys) tells you exactly what to update or remove. - Update the identified driver. Go to the manufacturer’s website (not Windows Update) and download the latest driver for your exact hardware model. For storage controllers, check the motherboard or laptop manufacturer’s support page.
- Roll back a recent driver update. If the crash started after a driver update, open Device Manager, right-click the device, go to Properties → Driver → Roll Back Driver.
- Uninstall recently added software. If you installed a new game with anti-cheat, or a system utility, uninstall it. Use the vendor’s official removal tool if available.
- Run Windows Memory Diagnostic. Although 0x135 is a driver bug, memory corruption can cause weird crashes. Type “Windows Memory Diagnostic” in the Start menu, choose “Restart now and check for problems.”
- Use System Restore. If the crashes started recently, restore your system to a point before the problem began.
- Check for Windows updates. Install all pending updates, as Microsoft sometimes ships fixes for bug check codes.
What If the Crash Happens During Boot?
If you cannot reach the desktop to run the above steps, you need to use Windows Recovery Environment (WinRE).
- Force shutdown three times (hold the power button) to trigger automatic repair.
- Go to Advanced Options → Troubleshoot → Advanced Options → Startup Settings → Restart.
- Select Enable Safe Mode (option 4).
- Once in Safe Mode, follow steps 2-8 above.
If Safe Mode also crashes, the problem may be a driver that loads very early, such as a storage or filter driver. In that case, try Disable driver signature enforcement from the same Startup Settings menu. If that works, the driver is unsigned or has a bad signature, and you should uninstall it from Safe Mode.
How to Prevent Future 0x135 Crashes
Once you have resolved the immediate issue, take these precautions to avoid a recurrence:
- Keep drivers updated – but only from official manufacturer sources. Use Windows Update for optional driver updates only if you trust them.
- Uninstall unused kernel-level software – if you no longer play a game, remove its anti-cheat driver. Many anti-cheat drivers remain active even after the game is closed.
- Avoid beta drivers unless you know they are stable. Beta drivers are more likely to have IRQL bugs.
- Check for firmware updates for your SSD or NVMe drive. Storage firmware bugs can trigger this bug check.
- Create a restore point before installing any new driver or system utility.
Comparing 0x135 to Other IRQL Bug Checks
You may have heard of IRQL_NOT_LESS_OR_EQUAL (0x0000000A) or DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1). These are different: 0x0A and 0xD1 occur when a driver accesses paged memory at too high an IRQL, while 0x135 specifically involves the auto-boost lock. The fix approach is similar, but 0x135 is less common and often points to a very specific driver bug, not a general memory access problem. If you see 0x135, focus on the driver that is named in the minidump; if you see 0x0A, you might also want to run a memory test.
Frequently Asked Questions
Can a hardware failure cause error 0x135?
It is extremely unlikely. The bug check is a software-detected IRQL violation. However, faulty RAM can cause a driver to behave erratically and trigger this crash, so a memory test is a reasonable secondary step if driver fixes do not help.
Will reinstalling Windows fix the 0x135 BSOD?
Often yes, because it removes all third-party drivers. But if the issue is a hardware-specific driver that Windows automatically installs, the crash could return. A clean install is a last resort, but it is effective in most cases.
Is error 0x135 related to overclocking?
Not directly, but overclocking tools (like MSI Afterburner or Intel XTU) install kernel drivers that can conflict with other drivers. If you have overclocking software, try uninstalling it and see if the crashes stop.
How do I read the minidump file if I don’t have a tool?
You can use the built-in Windows Debugger (WinDbg) from the Microsoft Store, but it is complex. For most users, BlueScreenView is the simplest free tool. It automatically parses the dump and shows the driver that caused the crash.
Why does the crash happen only when I play a specific game?
That strongly suggests the game’s anti-cheat driver. Games like Valorant or Fortnite use kernel-level anti-cheat that loads at boot. If the anti-cheat driver is incompatible with your system, it can cause 0x135. Check for game updates or anti-cheat updates, or contact the game’s support.
Should I disable driver signature enforcement permanently?
No. That weakens Windows security and can allow malware to load. Only use it as a temporary diagnostic step. If you need an unsigned driver, consider a signed alternative or contact the vendor for a signed version.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Set a Google Play Budget & Stop Accidental Purchases
- Destiny 2 Error Code Anteater: Fixes & Causes
- View Android Photos on Chromebook: Step-by-Step
- Fix Windows Could Not Prepare the Computer to Boot
- Windows 11 Security Settings: Best Config Guide
- Install Custom Recovery on Samsung Galaxy Trend