DRIVER_VERIFIER_IOMANAGER_VIOLATION (stop code 0x000000C9) on Windows 11 24H2 means one thing for certain: Driver Verifier is running. This blue screen cannot happen otherwise — Verifier is the component that detects the violation and deliberately crashes the system to report it. So your first question isn’t “which driver is broken” but “why is Verifier on, and is the violation real?” Answer those two questions in order, and the fix usually becomes obvious within minutes.

On 24H2, the common story is Verifier left enabled by an old diagnostic session, now flagging drivers under the new build’s changed I/O handling — drivers that passed quietly on 23H2 suddenly violate rules they never knew existed. Here’s how to sort it out.

Why this happens

  • Verifier was left enabled across the 24H2 upgrade. A previous troubleshooting session or diagnostic tool turned it on, and the setting survived.
  • 24H2’s changed I/O handling trips old drivers. Drivers that passed Verifier’s checks on 23H2 can violate the new build’s I/O manager rules.
  • The upgrade installed a buggy driver. New storage, network, or USB drivers pushed with 24H2 may mishandle I/O requests.
  • Filter drivers from security software. Antivirus, encryption, and backup tools install I/O filter drivers that are frequent Verifier violators on new builds.
  • Corrupted driver files. The 24H2 upgrade can damage driver files, turning correct I/O handling into violations.
  • Genuine hardware faults. Rare, but a failing storage controller produces I/O patterns that look like driver violations.

How to fix it

Work through these in order, from the quickest and safest fixes to the deeper ones. Stop once the crashes stop.

Fix 1: Check Verifier’s status and turn it off

The two-minute fix when Verifier was enabled accidentally.

  1. Press Win + R, type verifier, and press Enter.
  2. If it reports “No drivers are currently verified,” Verifier is off — skip to Fix 3.
  3. If drivers are listed, select Delete existing settings, click Finish, and restart. Alternatively, open an elevated Command Prompt and run verifier /reset, then restart.
  4. Use the laptop normally. If the crashes stop here, Verifier was the entire problem — a testing tool left running, flagging drivers that behave fine in real-world use.

Fix 2: Boot into Safe Mode to regain control

Verifier monitors from boot, so its crashes can loop.

  1. Interrupt the boot three times (hold the power button at the logo screen) to reach the Windows Recovery Environment.
  2. Go to Troubleshoot > Advanced options > Startup Settings > Restart and press 4 for Safe Mode.
  3. In Safe Mode, open an elevated Command Prompt and run verifier /reset, then restart normally.

Fix 3: Identify the violating driver

When Verifier was on deliberately — or crashes continue with it off.

  1. Press Win + X and open Event Viewer, then go to Windows Logs > System.
  2. Open the BugCheck error from the crash. The blue screen itself often shows “What failed: something.sys” — note the exact filename.
  3. Storage filter drivers, network drivers, and USB drivers are the usual suspects on 24H2.
  4. The post-update version of this violation covers the same identification process for other builds.

Fix 4: Update, roll back, or remove the driver

Fix the actual violation rather than the detector.

  1. Press Win + X and open Device Manager; find the device for your suspect driver.
  2. Right-click and choose Update driver > Search automatically for drivers. If 24H2 installed the bad driver, use Properties > Driver tab > Roll Back Driver instead.
  3. If the driver belongs to third-party software (antivirus, VPN, disk tools), uninstall that software completely from Settings > Apps > Installed apps — filter drivers rarely yield to simple driver updates.
  4. Install the latest version from the vendor or your laptop maker’s support site (Dell , HP, Lenovo ), choosing the 24H2-listed release, and restart.
  5. Related Verifier findings like driver verifier detected violations on 24H2 follow the same replace-the-driver pattern.

Fix 5: Repair system files and verify storage health

Eliminate corruption in the I/O path itself.

  1. Open an elevated Command Prompt (Win + S, type cmd, right-click, Run as administrator).
  2. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.
  3. Check the disk: chkdsk C: /f — type Y to schedule it and restart.
  4. In PowerShell (Admin), confirm drive health: Get-PhysicalDisk | Select FriendlyName, HealthStatus, OperationalStatus. I/O violations on an unhealthy drive point at storage hardware, not the driver.

Fix 6: Update the BIOS and chipset for 24H2

Firmware mediates the I/O Verifier monitors.

  1. Visit your laptop maker’s support site and download the latest BIOS for your exact model, checking it’s listed for 24H2.
  2. Flash it with the charger plugged in and nothing else running.
  3. Install the latest chipset driver from the same site.
  4. Restart and test. BIOS updates frequently include I/O handling fixes for new Windows builds.

Fix 7: Reset Windows as the final software step

When the violation survives everything else.

  1. Back up your files.
  2. Go to Settings > System > Recovery > Reset PC, choose Remove everything with Cloud download.
  3. After setup, install manufacturer 24H2 drivers first and test before adding third-party software — particularly whatever product owned the flagged filter driver.
  4. Persistent violations on a clean install indicate a storage controller or motherboard fault. Microsoft’s Windows support hub documents the recovery and repair options.

Closing

On 24H2, DRIVER_VERIFIER_IOMANAGER_VIOLATION starts with a simple check: is Driver Verifier even supposed to be running? Run verifier, and if it was left on accidentally, verifier /reset ends the crashes immediately. If the violations are genuine, the crash names the driver — update it, roll it back, or remove the software that installed it. Either way, this blue screen is Windows’ testing tools being diligent, not your hardware dying on you.

Frequently asked questions

What does DRIVER_VERIFIER_IOMANAGER_VIOLATION mean on 24H2?
It’s a blue screen (stop code 0x000000C9) that only occurs while Driver Verifier — Windows’ built-in driver stress-testing tool — is monitoring drivers. Verifier caught a driver breaking the I/O manager’s rules. On 24H2, this often means Verifier was left enabled by a diagnostic tool and is flagging a driver the new build handles differently.
I didn't enable Driver Verifier. Why is it running?
Some troubleshooting utilities and driver installers enable it silently, and the setting survives feature updates including the move to 24H2. Run verifier in the Run dialog — if it shows drivers being verified, that confirms it. Delete the settings or run verifier /reset to turn it off.
Is it safe to just turn Verifier off?
If it was enabled accidentally, yes — turn it off and the crashes stop. Verifier is a testing tool, not a protection feature; nothing in normal Windows depends on it running. But if you enabled it deliberately to diagnose crashes, the violation it found is real and the driver needs fixing.
Which drivers does Verifier flag most on 24H2?
Storage filter drivers (antivirus, encryption, backup tools), network drivers, and USB peripheral drivers lead the list. The blue screen or Event Viewer’s BugCheck entry names the .sys file, which identifies the exact product to update or remove.