REGISTRY_FILTER_DRIVER_EXCEPTION
Code: 0x135 (309)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x0135 (309)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x0135 (309)
Parameters
| Parameter | Description |
|---|---|
| 1 | Exception Code |
| 2 | Address of the context record for the exception that caused the bugcheck |
| 3 | The driver's callback routine address |
| 4 | Reserved |
Description
The REGISTRY_FILTER_DRIVER_EXCEPTION bug check has a value of 0x00000135. This bugcheck is caused by an unhandled exception in a registry filtering driver.
Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
Cause
This bugcheck indicates that a registry filtering driver didn't handle an exception inside its notification routine.
Resolution
The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause. Identify the offending driver by using the 3rd parameter.
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| EventCreate.exe | 0x135 | 78.11011 | %1 |
| KernelBase.dll | 0x135 | 78.1 | The specified file already has a notification GUID associated with it. |
| kernel32.dll | 0x135 | 78.11011 | The specified file already has a notification GUID associated with it. |
| microsoft-windows-system-events.dll | 0x135 | 1011 | %1 |
| webservices.dll | 0x135 | 78.11011 | The xml document could not be read because it was larger than expected. The data did not fit within the buffer size of '%1' bytes. |
| 5 entries | |||