Experiencing a blue screen crash accompanied by the stop code REGISTRY_FILTER_DRIVER_EXCEPTION (Bugcheck 0x00000135) halts your system abruptly during software installations, antivirus definition updates, or system restarts. This critical kernel crash occurs when a third-party registry filtering driver throws an unhandled exception inside its registry callback routine. In the Windows NT kernel architecture, security software, virtualization tools, and system monitors register filter callbacks with the Configuration Manager (the kernel registry subsystem). If a filter callback crashes or dereferences an invalid memory pointer, Windows terminates execution to prevent irreversible registry hive corruption.
What Causes Error 0x00000135 in Windows 11?
The registry filter exception is almost always triggered by low-level security or virtualization software:
- Faulty Antivirus or EDR Filter Drivers: Third-party security suites (CrowdStrike, SentinelOne, Avast, McAfee, Kaspersky) intercepting registry write operations using buggy callback routines.
- Corrupted Registry Hive Manifests: Damaged system or software hives inside
C:\Windows\System32\config\causing registry API calls to return unexpected structure formats. - Virtualization and Sandbox Software Conflicts: Third-party sandboxing utilities or anti-cheat engines hooking registry keys with outdated kernel drivers.
- Corrupted Core Kernel Files: Damaged
ntoskrnl.exeorcng.sysfiles caused by incomplete Windows Update installations.
Step 1: Identify and Uninstall Conflicting Security Filter Software
Boot into Safe Mode to remove third-party kernel registry filter callbacks.
- Hold the Shift key while clicking Restart from the Windows Start menu.
- Navigate to: Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 or F4 to boot into Safe Mode (where third-party filter drivers are inhibited from loading).
- Press Win + R, type
appwiz.cpl, and press Enter. - Locate recently installed or updated third-party antivirus, anti-malware, VPN, or system tuning applications.
- Uninstall them cleanly, restart your PC, and allow Windows Defender to manage baseline security.
Step 2: Run DISM and System File Checker in Elevated Command Prompt
Restore authentic Windows Configuration Manager dynamic libraries.
- Press Win + S, type
cmd, right-click Command Prompt, and choose Run as administrator. - Execute the DISM component repair tool:
DISM /Online /Cleanup-Image /RestoreHealth - After DISM completes, execute the System File Checker:
sfc /scannow - Allow the scan to finish; if corrupted system files are replaced, reboot Windows to finalise changes.
Step 3: Check Registry Filter Callbacks Using FLTMC
Inspect active filter drivers registered on your workstation.
- In your elevated Command Prompt, execute:
fltmc filters - Review the list of active filter drivers. Look for unfamiliar driver names with high altitude levels.
- Check the driver vendor online and update or remove the corresponding parent application to eliminate unstable callbacks.