Debugging Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION

If Driver Verifier detects a violation, it generates a bug check to stop the computer. This is to provide you with the most information possible for debugging the issue. One of the more frequent bug checks Driver Verifier generates is Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION. This section describes some example strategies for debugging these violations.

When Driver Verifier issues a Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION, it uses the parameter 1 value (or subcode) to specify the specific cause of the violation. Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION detects over 200 violations.

In this section

• Debugging memory leaks - DRIVER_VERIFIER_DETECTED_VIOLATION (C4): 0x62
• Debugging deadlocks - DRIVER_VERIFIER_DETECTED_VIOLATION (C4): 0x1001
• Debugging DDI Compliance bugs - DRIVER_VERIFIER_DETECTED_VIOLATION (C4): 0x20002 - 0x20022
• Debugging NDIS/WiFi time-out errors - DRIVER_VERIFIER_DETECTED_VIOLATION (C4)

Prerequisites

• Run Driver Verifier on a computer reserved for testing.
• Enable kernel-debugging on the test computer.

For more information see Windows Debugging and Handling a Bug Check When Driver Verifier is Enabled.