Fix Driver Verifier DMA Violation BSOD in Windows 11

If you are seeing a “DRIVER_VERIFIER_DMA_VIOLATION� blue screen on Windows 11, the fix is to identify which driver is causing the violation, update or remove it, and then turn off Driver Verifier if it is no longer needed. This error occurs when Driver Verifier, a built-in diagnostic tool, detects that a driver has performed an illegal direct memory access (DMA) operation. The steps below will help you resolve the issue and prevent it from recurring.

What Is Driver Verifier and Why Does It Cause BSODs?

Driver Verifier is a Windows tool that stresses drivers by injecting invalid parameters, simulating low memory, and tracking memory allocations. It is designed to catch driver bugs before they cause system instability in normal use. When a driver violates a rule, Windows immediately stops the system with a bug check (BSOD) to prevent data corruption. The DMA violation specifically means a driver attempted to access physical memory without proper permissions or used a malformed DMA descriptor.

This error is almost always triggered by a faulty third-party driver, often a network adapter, graphics card, storage controller, or virtualization software. It can also appear if you enabled Driver Verifier manually and a driver that was previously fine fails under the stricter scrutiny.

How to Enter Safe Mode to Fix the Issue

Since the BSOD may happen during boot, you need to start Windows in Safe Mode to disable Driver Verifier or remove the offending driver. Here is how:

Restart your PC and press the power button repeatedly to interrupt the boot process until you see the Windows Recovery Environment (WinRE).
Select Troubleshoot > Advanced options > Startup Settings.
Click Restart and then press F4 (or 4) to boot into Safe Mode.

If you cannot reach WinRE, you can create a Windows 11 installation USB on another PC and boot from it, then choose Repair your computer.

Step-by-Step Fix: Disable Driver Verifier

Once in Safe Mode, open Command Prompt as administrator and type the following command to turn off Driver Verifier:

verifier /reset

This clears all Driver Verifier settings and stops the checks on the next boot. If you still get the BSOD after this, the problem driver is still loaded, but now it will not be caught by Verifier. Instead, you need to identify and update or remove the driver.

Identifying the Problematic Driver

To find which driver caused the violation, check the minidump files created during the crash. You can use the Windows Event Viewer or a debugging tool like WinDbg, but a simpler method is to review the Driver Verifier log:

In Safe Mode, open Event Viewer (eventvwr.msc).
Go to Windows Logs > System and look for a BugCheck event with source BugCheck.
Note the bug check code and the parameters; the driver name is often listed in the event details.

Alternatively, you can use the verifier /querysettings command to see which drivers are being verified. If you enabled Verifier for all drivers, you can narrow it down by disabling it and then re-enabling it for a subset of drivers (e.g., only unsigned drivers or only specific vendor drivers) until the BSOD reappears.

Updating or Removing the Faulty Driver

Once you know the driver, take these steps:

Visit the hardware manufacturer’s website and download the latest driver for your Windows 11 version.
Use Device Manager to uninstall the device and then reinstall the new driver.
If the driver is for a peripheral you rarely use, consider disabling the device in Device Manager.

If the problem started after a recent Windows update, you can also try rolling back the driver to a previous version via Device Manager (Properties > Driver > Roll Back Driver).

Common Misconceptions and Mistakes

A frequent mistake is assuming that the BSOD means your hardware is failing. In most cases, it is a driver bug, not a hardware defect. However, if you have recently installed new RAM or a new SSD, faulty hardware can also cause DMA-related errors. Run Windows Memory Diagnostic (mdsched.exe) to rule out RAM issues.

Another misconception is that disabling Driver Verifier permanently fixes the problem. It only stops the checks; the underlying driver issue remains. You should still update or remove the offending driver to avoid data corruption or other crashes.

Alternatives to Driver Verifier

If you are a developer or advanced user, you can use Driver Verifier with specific settings to target only suspected drivers, rather than all drivers. This reduces the chance of a BSOD from unrelated drivers. You can also use the Windows Driver Kit (WDK) tools, such as Driver Verifier’s Driver Isolation feature, to test a single driver in isolation.

For regular users, the best alternative is to keep your drivers up to date via Windows Update or the manufacturer’s update utility. If you are troubleshooting a specific device, you can also use the Driver Verifier GUI (verifier /standard) to enable only standard tests, which are less aggressive than the default settings.

Frequently Asked Questions

Will disabling Driver Verifier harm my PC?

No. Driver Verifier is a diagnostic tool, not a security feature. Disabling it simply stops the extra stress tests. Your PC will run as it did before you enabled it, but you may have an undetected driver bug that could cause other issues later.

Can I fix the BSOD without Safe Mode?

If you can boot normally, you can open Command Prompt as administrator and run verifier /reset from there. If the BSOD happens immediately after boot, you will need Safe Mode or the Windows Recovery Environment.

How do I know which driver is causing the DMA violation?

Check the minidump file with a debugger like WinDbg, or look in Event Viewer under System logs for the BugCheck event. The driver name is often included in the event details. You can also use the !analyze -v command in WinDbg to get a detailed analysis.

Is this BSOD a sign of a hardware problem?

Usually not. It is most often a driver bug. However, if you have recently changed hardware, especially RAM or storage, it is worth running memory diagnostics and checking disk health with tools like CHKDSK or the manufacturer’s utility.

Should I re-enable Driver Verifier after fixing the driver?

If you are a developer testing drivers, yes. For everyday users, it is not necessary. If you do re-enable it, use the /standard settings and enable it only for the driver you are testing, not for all drivers.

What if the BSOD continues after updating all drivers?

If the error persists, try a clean boot to isolate third-party services and drivers. If that does not help, consider using System Restore to a point before the issue started, or perform a repair installation of Windows 11 using the installation media.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →