DRIVER_VERIFIER_DETECTED_VIOLATION
Code: 0xc4 (196)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x00c4 (196)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x00c4 (196)
Parameters
| Parameter | Description |
|---|---|
| 0x00 | Current IRQL |
| 0x01 | Current IRQL |
| 0x02 | Current IRQL |
| 0x03 | |
| 0x10 | Bad Address |
| 0x11 | Current IRQL |
| 0x12 | Current IRQL |
| 0x13 or 0x14 | Reserved |
| 0x15 | Timer entry |
| 0x16 | Reserved |
| 0X17 | Resource entry |
| 0x30 | Current IRQL |
| 0x31 | Current IRQL |
| 0x32 | Current IRQL |
| 0x33 | Current IRQL |
| 0x34 | Current IRQL |
| 0x35 | Current IRQL |
| 0x36 | Current IRQL |
| 0x37 | Current IRQL |
| 0x38 | Current IRQL |
| 0x39 | Current IRQL |
| 0x3A | Current IRQL |
| 0x3B | Current IRQL |
| 0x3C | Handle passed to routine |
| 0x3D | 0 |
| 0x3E | 0 |
| 0x3F | Object address |
| 0x40 | Current IRQL |
| 0x41 | Current IRQL |
| 0x42 | Current IRQL |
| 0x51 | Base address of allocation |
| 0x52 | Base address of allocation |
| 0x53 | Base address of allocation |
| 0x54 | Base address of allocation |
| 0x59 | Base address of allocation |
| 0x60 | Bytes allocated from paged pool |
| 0x61 | Bytes allocated from paged pool |
| 0x62 | Name of the driver |
| 0x6F | MDL address |
Description
The DRIVER_VERIFIER_DETECTED_VIOLATION bug check has a value of 0x000000C4. This is the general bug check code for fatal errors found by Driver Verifier. For more information, see Handling a Bug Check When Driver Verifier is Enabled.
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
See the description of each code in the Parameters section for a description of the cause. Further information can be obtained by using the !analyze -v extension.
Resolution
This bug check can only occur when Driver Verifier has been instructed to monitor one or more drivers. If you did not intend to use Driver Verifier, you should deactivate it. You might also consider removing the driver that caused this problem.
If you are the driver writer, use the information obtained through this bug check to fix the bugs in your code.
For full details on Driver Verifier, see Driver Verifier.
Remarks
The _POOL_TYPE codes are enumerated in Ntddk.h. In particular, 0 (zero) indicates nonpaged pool and 1 (one) indicates paged pool.
(Windows 8 and later versions of Windows) If DDI compliance checking causes a bug check, run Static Driver Verifier on the driver source code and specify the DDI compliance rule (identified by the parameter 1 value) that caused the bug check. Static Driver Verifier can help you locate the cause of the problem in your source code.
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 |
|---|---|---|---|
| EventCreate.exe | 0xc4 | 78.11011 | %1 |
| KernelBase.dll | 0xc4 | 78.1 | The operating system cannot run this application program. |
| USBHUB3.SYS | 0xc4 | 1011 | USB device draining system power when system is idle. USB Device: VID: %3 PID: %4 REV: %5 Removal action failed: %2 |
| dsreg.dll | 0xc4 | 10 | MDM enrollment for Azure SecureVM succeeded. MDM Enrollment URL: %1 |
| dsreg.dll | 0xc4 | 11 | MDM enrollment for Microsoft Entra SecureVM succeeded. MDM Enrollment URL: %1 |
| kernel32.dll | 0xc4 | 78.11011 | The operating system cannot run this application program. |
| nslookup.exe | 0xc4 | 78.11011 | %1!d! hours |
| webservices.dll | 0xc4 | 78.11011 | There was an error binding the TCP listen socket. |
| 8 entries | |||