Skip to content
PCDecoder
0x00000135REGISTRY_FILTER_DRIVER_EXCEPTIONStop codeWidely reported

REGISTRY_FILTER_DRIVER_EXCEPTION (0x135): what it means and how to fix it

Updated Nov 5, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

This error occurs when a registry filtering driver fails to handle an unexpected event, causing Windows to stop for safety. It is often triggered by software that monitors or modifies system configuration settings. To fix it, start by booting into Safe Mode to identify and remove recently installed programs or drivers.

What it means

Understanding the Error

When you see the REGISTRY_FILTER_DRIVER_EXCEPTION stop code, Windows is telling you that a specific type of software, known as a registry filter driver, has encountered a problem it did not know how to handle.

What is a Registry Filter Driver?

The Windows Registry is a central database where the operating system stores configuration settings for hardware, software, and user preferences. A registry filter driver is a piece of software that sits between your applications and this database. Its job is to monitor or intercept requests to change these settings. Common examples include antivirus software, backup tools, or security programs that need to ensure no unauthorized changes are made to your system.

Why the Crash Happens

Because these drivers operate at a very low level of the system, they must be perfectly written. If the driver encounters an unexpected situation—such as a corrupted data request or a conflict with another program—and it does not have a set of instructions for how to handle that specific scenario, it triggers an exception. To prevent potential data corruption or system instability, Windows immediately halts the computer, resulting in the blue screen you see. This is a protective measure designed to keep your files safe.

Common causes

  • A recently installed program or driver is conflicting with the Windows registry.
  • A security or antivirus application is malfunctioning during a registry scan.
  • System files have become corrupted, preventing the driver from communicating correctly.
  • Hardware instability is causing data errors that the registry driver cannot process.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Boot into Safe Mode

    Use this if your computer is stuck in a loop and cannot reach the desktop.

    1. Restart your computer while holding the Shift key to enter the Windows Recovery Environment.
    2. Select Troubleshoot, then Advanced options, and then Startup Settings.
    3. Click Restart and press 4 or F4 to start in Safe Mode.
    4. If you can reach the desktop, proceed to uninstall recently added software.
    Did this fix it?

  2. Uninstall recently added software

    Use this if you recently installed a new program or updated an existing one before the crashes began.

    1. Open the Settings app and go to Apps, then Installed apps.
    2. Sort the list by Date installed to see the most recent additions.
    3. Select the program you suspect is causing the issue and click Uninstall.
    4. Restart your computer normally to see if the error persists.
    Did this fix it?

  3. Run the System File Checker

    Use this to repair missing or corrupted system files that might be causing the driver to fail.

    1. Open the Start menu, type cmd, right-click it, and select Run as administrator.
    2. Type sfc /scannow and press Enter.
    3. Wait for the process to complete and report whether it found and repaired any files.
    4. Restart your computer.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Nov 4, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Is my hard drive failing because of this error?

Not necessarily. While hardware issues can cause this, it is more commonly caused by a software conflict or a buggy driver.

Can I fix this by reinstalling Windows?

You can, but it is a last resort. Try removing recent software or using Safe Mode first, as those steps often resolve the issue without needing to wipe your data.

What should I do if I cannot get into Safe Mode?

If you cannot access Safe Mode, you may need to use Windows installation media to perform a Startup Repair or restore the system to a previous point.

More stop codes decoded