How to Fix REGISTRY_FILTER_DRIVER_EXCEPTION (0x00000135) Blue Screen Error

CONTENT

Quick Answer

REGISTRY_FILTER_DRIVER_EXCEPTION (0x00000135) is a Windows Blue Screen of Death (BSOD) error that occurs when a registry filtering driver encounters an exception it cannot handle. These drivers operate in kernel mode and monitor or process Windows Registry operations.

To troubleshoot this error, review recently installed drivers and applications, install applicable Windows updates, and investigate software that interacts with the registry. If the blue screen continues, analyze the crash dump using WinDbg to identify the driver involved. Do not delete registry entries or driver files without confirming the cause.

What Does REGISTRY_FILTER_DRIVER_EXCEPTION Mean?

Windows uses registry filtering drivers to monitor or process registry operations. These drivers may be installed by security applications, backup utilities, endpoint protection products, and other system management software.

Microsoft identifies bug check 0x00000135 as an unhandled exception in a registry filtering driver's notification routine. Windows stops operating to protect system stability.

The error does not necessarily mean that the Windows Registry is corrupted. A faulty, incompatible, or malfunctioning driver is an important area to investigate, but the exact cause must be established using diagnostic evidence.

See the official Microsoft documentation for Bug Check 0x135.

Common Causes

The following are possible causes, not confirmed explanations for every occurrence of this error.

• Faulty registry filtering driver: A kernel-mode driver may encounter an exception that it cannot handle.
• Incompatible software: Security software, backup utilities, or system management applications may install drivers that do not work correctly with the installed Windows version.
• Recent driver updates: An updated driver may introduce a defect or compatibility problem.
• Software installation or removal: Changes to applications that use system-level drivers may coincide with the beginning of the crashes.
• Driver conflicts: Interactions between kernel-mode components may contribute to the failure.
• Windows compatibility issues: An operating-system update may expose a problem in an existing third-party driver.

Do not assume that antivirus software, a specific driver, or registry corruption is responsible without supporting evidence. Crash dumps and the timing of recent changes can help narrow the possibilities.

Symptoms of Error 0x00000135

Common symptoms may include:

• A blue screen displaying REGISTRY_FILTER_DRIVER_EXCEPTION.
• The stop code 0x00000135 or 0x135.
• Unexpected restarts or repeated blue screens.
• Crashes during startup or shortly after signing in.
• Blue screens that begin after installing or updating an application or driver.
• Repeated crashes during specific activities.

Record the exact stop code and any recent system changes. If Windows creates a crash dump, preserve it for further analysis.

How to Fix REGISTRY_FILTER_DRIVER_EXCEPTION (0x00000135)

1. Restart Windows and Check Whether the Error Returns

If the blue screen occurred only once, restart Windows normally if possible and check whether the problem recurs.

1. Allow Windows to restart.
2. Save important files and back up essential data.
3. Record recent application installations, driver updates, and Windows updates.
4. Observe whether the same stop code appears again.

A single crash does not necessarily establish an ongoing driver problem. Repeated crashes, particularly after the same activity, provide more useful diagnostic evidence.

2. Install Applicable Windows Updates

Windows updates may contain reliability improvements and compatible driver updates. Installing available updates is a general troubleshooting step, not a guaranteed fix for this stop code.

1. Open Settings.
2. Select Windows Update. In Windows 10, open Update & Security and then Windows Update.
3. Select Check for updates.
4. Install applicable updates and restart the computer if requested.
5. Check whether the blue screen returns.

For optional driver updates, review the device and driver information before installing them. Prefer compatible drivers from the computer manufacturer or relevant hardware manufacturer.

If the crashes began immediately after a particular update, record the update details before considering a rollback.

3. Review Recently Installed Drivers and Applications

If the error began after a software or driver change, investigate that change before attempting broader repairs.

1. Open Settings > Apps and review recently installed applications.
2. Open Device Manager if a hardware driver was recently changed.
3. Check the relevant manufacturer's website for a compatible update or documented rollback procedure.
4. If crash evidence points to a specific application, use its official repair, update, or uninstall procedure.
5. Restart Windows and check whether the error occurs again.

Security products, endpoint protection applications, backup tools, and system utilities may install kernel-mode components. Their presence does not prove that they caused the crash.

Do not manually delete driver files or permanently disable security protection. If removing a security product is necessary for diagnosis, follow the vendor's instructions and ensure that suitable protection is restored.

4. Start Windows in Safe Mode

Safe Mode starts Windows with a limited set of drivers and services. It can help determine whether the problem is associated with software loaded during normal startup, although a driver that remains active in Safe Mode may still cause a crash.

1. Open Windows Recovery Environment (WinRE) using the recovery options available on your device.
2. Select Troubleshoot > Advanced options > Startup Settings > Restart.
3. After the restart, select the Safe Mode option displayed on screen, commonly option 4 or F4.
4. If Windows starts successfully, investigate recent driver and application changes.

If Windows cannot start normally, compatible Windows recovery media may be needed to access recovery tools. The available menus vary by Windows version and device configuration.

If BitLocker device encryption is enabled, certain recovery operations may require the recovery key. Make sure it is available before proceeding.

See Microsoft's Windows recovery options documentation.

5. Run DISM and System File Checker

DISM and System File Checker (SFC) can identify and repair certain Windows component and system-file problems. They are not specific fixes for registry filtering driver exceptions, so use them when system-file corruption is suspected or other evidence supports the check.

Open Windows Terminal or Command Prompt as an administrator in the Windows installation you intend to repair.

First, run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

This command checks and repairs the Windows component store. It may use Windows Update or another configured repair source to obtain required files.

After DISM finishes, run:

sfc /scannow

This command scans protected Windows system files and attempts to repair integrity problems.

Review the completion messages from both commands. If repairs are reported, restart Windows and check whether the blue screen returns. If a command fails, investigate its error message rather than repeatedly running it without addressing the underlying problem.

These commands are intended for an online Windows installation. In a recovery command prompt, the /Online option may refer to the recovery environment rather than the installed Windows system.

Advanced Troubleshooting

6. Analyze the Crash Dump Using WinDbg

If the blue screen continues, analyzing the crash dump can help identify the registry filtering driver involved in the failure.

Depending on the configured dump settings, Windows may create files in these locations:

• C:\Windows\Minidump — small memory dump files, if created.
• C:\Windows\MEMORY.DMP — a larger crash dump file, if configured and created.

These files may be missing if dump collection is disabled, the system could not write the dump, or a different location is configured.

1. Install or open WinDbg using Microsoft's official debugging tools.
2. Open the relevant crash dump file in WinDbg.
3. Allow the debugger to load available symbols and analyze the dump.
4. Enter the following command in the debugger command window:

!analyze -v

This command displays detailed bug-check information and diagnostic clues. Review the bug-check parameters, stack information, and identified modules together.

Microsoft identifies the third parameter of bug check 0x135 as the address of the driver's callback routine. This information can help an experienced debugger investigate the driver involved in the crash.

A driver appearing in the analysis is not necessarily proof of the underlying defect. Additional evidence may be required to determine why the exception occurred.

Official documentation:

• Microsoft Learn: Bug Check 0x135
• Microsoft Learn: Opening a crash dump file using WinDbg
• Microsoft Learn: !analyze debugger extension

7. Understand the Bug-Check Parameters

Microsoft documents the following parameters for REGISTRY_FILTER_DRIVER_EXCEPTION:

Parameter	Meaning
Parameter 1	Exception code.
Parameter 2	Address of the exception context record.
Parameter 3	Address of the driver's callback routine.
Parameter 4	Reserved.

These values are diagnostic information, not instructions to modify the registry or remove a driver. Identifying a driver from an address may require debugger symbols and additional analysis.

For escalation to an IT technician or software vendor, preserve the crash dump, debugger output, Windows version, and details of recent driver or application changes. Remove sensitive information from logs before sharing them publicly.

What to Do If Windows Cannot Start

If Windows repeatedly crashes during startup, use Windows Recovery Environment instead of repeatedly forcing normal startup.

1. Enter WinRE using the device's recovery options or compatible Windows recovery media.
2. Try Startup Repair if Windows cannot start correctly.
3. If the problem began after a recent system change, consider System Restore if a suitable restore point exists.
4. If the problem continues, preserve important data where possible and investigate the crash dump or seek technical assistance.

Startup Repair and System Restore address different types of problems and are not guaranteed fixes for this bug check. Review the effects of each recovery option before proceeding because some recovery and reset operations can cause data loss.

Refer to Microsoft's recovery options for Windows.

How to Verify the Fix

After making a targeted change, verify whether the original problem has stopped.

• Restart Windows normally and confirm that it reaches the desktop.
• Repeat the activity that previously triggered the blue screen, where practical.
• Check whether the same 0x00000135 stop code returns.
• If another crash occurs, preserve the new dump and compare it with the earlier analysis.
• Record the driver or application change and the observed result.

If the crash continues after updating or rolling back the suspected driver, revisit the diagnostic evidence. Avoid repeating unsuccessful repair steps without new information.

Frequently Asked Questions

Is REGISTRY_FILTER_DRIVER_EXCEPTION caused by registry corruption?

Not necessarily. The documented meaning is an unhandled exception in a registry filtering driver. The stop code alone does not establish that registry data is corrupted.

Can antivirus software cause error 0x00000135?

A security product may install a registry filtering driver, so it can be one area to investigate. However, the stop code does not identify antivirus software as the cause. Use crash-dump evidence and recent change history to narrow the problem.

Will SFC and DISM fix error 0x00000135?

They may help if Windows component or system-file corruption contributes to the problem. They are not specific fixes for a defective third-party registry filtering driver.

Can I delete the suspected driver manually?

No. Manually deleting a driver file may destabilize Windows or prevent startup. Identify the driver first, then use the vendor's supported update, rollback, repair, or uninstall procedure.

What does parameter 3 mean in this bug check?

Microsoft documents parameter 3 as the address of the registry filtering driver's callback routine. Debugger analysis can help identify the relevant driver, but the address alone does not establish the underlying cause.

What should I do if the blue screen keeps returning?

Preserve the crash dumps, analyze them using WinDbg, review recent system changes, and use Windows Recovery Environment if startup is affected. If the responsible driver remains unclear, consult a qualified technician or the relevant software vendor.

Sources

• Microsoft Learn: Bug Check 0x135 — REGISTRY_FILTER_DRIVER_EXCEPTION
• Microsoft Learn: Opening a crash dump file using WinDbg
• Microsoft Learn: !analyze debugger extension
• Microsoft Support: Recovery options in Windows