Fix Driver Verifier DMA Violation BSOD in Windows 11

This guide walks you through fixing the DRIVER_VERIFIER_DMA_VIOLATION Blue Screen of Death (BSOD) in Windows 11. This error typically appears when Driver Verifier (a built-in diagnostic tool) detects a driver attempting an illegal DMA (Direct Memory Access) operation. We’ll show you how to identify the offending driver, disable Verifier if needed, and apply permanent fixes.

What You’ll Need

Access to Windows 11 (Safe Mode may be required if the BSOD loops).
Administrator account privileges.
A backup of important files (BSODs can sometimes indicate failing hardware).
Optional: Another working PC to download drivers or create a bootable USB if Windows won’t start.

Step-by-Step

Boot into Safe Mode. If Windows 11 starts normally, skip to step 2. If you’re stuck in a BSOD loop, force restart your PC three times (power off/on) to trigger the Windows Recovery Environment. Then go to Troubleshoot > Advanced options > Startup Settings > Restart and press 4 or F4 to boot into Safe Mode.
Open Driver Verifier. Press Win + S, type verifier, right-click the result, and select Run as administrator.
Check current settings. In Driver Verifier Manager, select Show information about currently verified drivers and click Next. Note which drivers are being tested and what settings are active. This tells you if Verifier is even enabled.
Disable Driver Verifier temporarily. If you need to stop the BSOD loop immediately, select Delete existing settings and click Finish. Restart your PC. This stops Verifier from running, but the underlying driver issue may still exist.
Identify the problematic driver. If you want to keep Verifier on to find the culprit, you need to analyze the crash dump. Open Event Viewer (Win + S, type eventvwr). Navigate to Windows Logs > System and look for critical errors with source BugCheck around the time of the BSOD. The error details often list the driver name (e.g., nvlddmkm.sys). Alternatively, use a tool like WinDbg to open the .dmp file in C:\Windows\Minidump.
Update or roll back the driver. Once you have the driver name, go to Device Manager (Win + X > Device Manager). Find the device (e.g., display adapter, network card), right-click it, and choose Update driver > Search automatically. If that doesn’t help, try Properties > Driver > Roll Back Driver if the issue started after a recent update.
Uninstall and reinstall the driver. If updating/rolling back fails, right-click the device and select Uninstall device. Check Delete the driver software for this device if available. Restart your PC – Windows will reinstall a basic driver automatically. Then download the latest driver from the manufacturer’s website (not via Windows Update).
Run hardware diagnostics. DMA errors can also stem from faulty RAM or storage. Run Windows Memory Diagnostic (Win + S, type mdsched.exe, restart). Also check your drive’s health with chkdsk /f /r in an elevated Command Prompt.
Re-enable Driver Verifier (optional). After fixing the driver, you can re-enable Verifier to confirm stability. Open it as administrator, choose Create custom settings (or Standard settings), select all drivers, and finish. If the BSOD returns, the driver is still bad – repeat steps 5-7.
Perform a clean boot. If the error persists, use msconfig to disable all non-Microsoft services and startup items. This isolates third-party conflicts. If the BSOD stops, re-enable items one by one to find the culprit.

Common Mistakes

Disabling Verifier permanently without fixing the root cause. This hides the problem; the faulty driver can still cause other crashes or data corruption.
Ignoring the driver name in the BSOD. The error screen often shows a file (e.g., xxx.sys) – that’s your biggest clue. Write it down.
Using generic driver update tools. These often install wrong or outdated drivers. Always download from the hardware manufacturer’s official site.
Assuming it’s always a driver issue. DMA violations can indicate failing hardware, especially RAM or SSD. Don’t skip diagnostics.
Not backing up before making changes. Driver updates can sometimes make things worse, so have a restore point or backup ready.

Tips

Create a restore point first. Type rstrui in the Start menu, then Create a restore point. This gives you an undo option.
Use the manufacturer’s driver utility. For GPUs (NVIDIA, AMD, Intel), use their official update tools instead of Windows Update.
Check for Windows updates. Sometimes Microsoft pushes driver fixes via Windows Update. Go to Settings > Windows Update > Check for updates.
Monitor your system temps. Overheating can cause random BSODs. Use a free tool like HWMonitor to check CPU/GPU temperatures.
Keep a USB recovery drive. If Windows becomes unbootable, a recovery drive lets you access Safe Mode and command prompt tools.

Troubleshooting

If the BSOD happens before you can open Driver Verifier: Boot into Safe Mode as described in Step 1. If Safe Mode also crashes, use the Windows Recovery Environment’s Command Prompt to run verifier /reset (this disables Verifier). You can also use sfc /scannow and dism /online /cleanup-image /restorehealth to repair system files.

If you can’t identify the driver from Event Viewer: Look for a file named MEMORY.DMP in C:\Windows or C:\Windows\Minidump. Use the free WinDbg tool from Microsoft Store to open it – the !analyze -v command usually points directly to the faulty driver.

If the error persists after updating all drivers: Run a full hardware diagnostic. Use sfc /scannow to check system file integrity. Test your RAM with MemTest86 (bootable USB). If you have multiple RAM sticks, try removing one at a time.

If you’re using an external device (USB, Thunderbolt): Unplug all non-essential peripherals and see if the error stops. If it does, reconnect them one by one to find the problematic device, then update its driver or firmware.

If you recently installed new software: Uninstall it. Some antivirus or low-level system utilities (like overclocking tools) can trigger DMA violations because they install kernel drivers.

Frequently Asked Questions

What does DRIVER_VERIFIER_DMA_VIOLATION mean?

It means Driver Verifier detected a driver performing a DMA operation that violates Windows memory protection rules. This is often caused by a buggy or incompatible driver, but can also indicate failing hardware.

Is Driver Verifier safe to use?

Yes, it’s a built-in Microsoft diagnostic tool. However, it intentionally stresses drivers, so it can cause BSODs – that’s how it finds problems. Only use it when troubleshooting, and disable it after you’ve fixed the issue.

How do I disable Driver Verifier without booting into Windows?

Boot into the Windows Recovery Environment (WinRE) and open Command Prompt. Type verifier /reset and press Enter. This clears all Verifier settings.

Can a faulty RAM stick cause this BSOD?

Yes, DMA errors can be caused by memory corruption. Run Windows Memory Diagnostic or MemTest86 to test your RAM.

Will reinstalling Windows fix the problem?

It might, if the issue is software-related. But if the cause is a hardware driver that Windows reinstalls automatically, the error could come back. Always identify the root cause first.

How do I find which driver is causing the crash?

Check the BSOD screen for a file name (like driver.sys). Alternatively, use Event Viewer or WinDbg on the minidump file. The !analyze -v command in WinDbg is the most reliable method.

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 →