Error AtlasError Documentation and Resolution

Windows blue screen DRIVER_VIOLATION

Bug Check 0x121: DRIVER_VIOLATION

Windows stopped with a DRIVER_VIOLATION bug check because a driver called a function at an invalid IRQL or broke another driver-contract rule. This points to a faulty kernel-mode driver rather than a user-space application problem.

DRIVER_VIOLATIONruntime
Bug Check 0x121: DRIVER_VIOLATION
  • A kernel-mode driver called a function at an IRQL level where that call is not allowed.
  • A recently updated or newly installed low-level driver introduced invalid kernel behavior.
  • A buggy hardware-management, filter, or device-stack driver violated driver contract rules.
  1. Identify the offending driver from the crash dump or debugger stack and prioritize that component for rollback or update.
  2. Review recent low-level driver changes first, especially around storage, networking, security, virtualization, or OEM hardware-management software.
  3. Update BIOS, chipset, and platform drivers if the issue appears after broader platform changes.
  4. If the same driver keeps appearing in repeated crashes, remove that driver or replace it with a stable vendor-supported release.
Bug Check 0x121: DRIVER_VIOLATION
DRIVER_VIOLATION BSOD: causes and fixes | Error Atlas