DRIVER_VERIFIER_DETECTED_VIOLATION_LIVEDUMP
Code: 0x1c4 (452)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x01c4 (452)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x01c4 (452)
Parameters
| Parameter | Description |
|---|---|
| 1 | The subclass of driver violation. See Values below. |
| 2 | See Values below. |
| 3 | See Values below. |
| 4 | See Values below. |
Description
The DRIVER_VERIFIER_DETECTED_VIOLATION_LIVEDUMP live dump has a value of 0x000001C4. This indicates that a device driver attempting to corrupt the system has been detected. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. For more information, see Driver Verifier.
See Also
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 |
|---|---|---|---|
| ESENT.dll | 0x1c4 | 8.11011 | %1 (%2) %3Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7. |
| EventCreate.exe | 0x1c4 | 78.11011 | %1 |
| kernel32.dll | 0x1c4 | 1011 | The application has not been provisioned. |
| webservices.dll | 0x1c4 | 78.11011 | The dictionary specified is NULL. |
| 4 entries | |||