Skip to content
PCDecoder
0x000000E6DRIVER_VERIFIER_DMA_VIOLATIONStop codeWidely reported

DRIVER_VERIFIER_DMA_VIOLATION (0xE6): what it means and how to fix it

Updated Oct 11, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

Stop code 0x000000E6 indicates that a device driver attempted an illegal Direct Memory Access (DMA) operation caught by Driver Verifier or system hardware. It most often happens when Driver Verifier is actively monitoring drivers or when a faulty driver writes outside its memory buffers. The primary fix is to turn off Driver Verifier or remove the malfunctioning driver.

What it means

Direct Memory Access (DMA) allows hardware devices like network cards, storage controllers, and graphics adapters to exchange data directly with system memory. Bypassing the processor during these transfers speeds up operations across the operating system. Because external devices gain direct access to RAM, Windows enforces strict rules on how memory buffers are allocated, mapped, and released.

When Windows halts with stop code 0x000000E6, a driver has violated those memory rules. Driver Verifier is a diagnostic tool built into Windows that tests drivers under stress to uncover hidden bugs. When DMA Verification is active, the tool scrutinizes every memory request. An IOMMU (Input-Output Memory Management Unit) can also trigger the 0xE6 bug check when hardware security detects illegal memory access, even if Driver Verifier is not enabled.

Why the crash occurs

The crash happens when a driver mismanages hardware memory channels or buffers. A driver might write data past the end of its allocated DMA buffer, corrupting adjacent system data. Other common triggers include double-free errors, where a driver attempts to release the same common buffer, adapter channel, or map register twice.

A driver can also trigger 0xE6 by attempting a transfer through an adapter that was already released, mapping a zero-length buffer, or calling memory routines at an incorrect Interrupt Request Level (IRQL). When Driver Verifier or the IOMMU detects these dangerous operations, Windows triggers a bug check immediately to prevent widespread data corruption.

Common causes

  • Driver Verifier is currently active on the system and detected an illegal memory operation.
  • A device driver wrote data outside its assigned DMA buffer space.
  • A driver freed the same DMA buffer, map register, or adapter channel more than once.
  • The system IOMMU detected an unauthorized memory access from connected hardware.
  • A driver executed DMA routines at an improper IRQL or used obsolete system functions.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Disable Driver Verifier

    Use this first if you enabled Driver Verifier for testing or if the computer entered a crash loop after using the verifier utility.

    1. Boot into Windows normally, or boot into Safe Mode if the blue screen appears during startup.
    2. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
    3. Type verifier /reset and press Enter to deactivate all Driver Verifier monitoring routines.
    4. Restart the computer.
    Did this fix it?

  2. Roll back or uninstall the faulting driver

    Use this if the crash began immediately after updating or installing a specific hardware driver.

    1. Right-click the Start button and select Device Manager.
    2. Expand the category containing the problematic hardware, such as Network adapters or Storage controllers.
    3. Right-click the device and select Properties.
    4. Open the Driver tab and select Roll Back Driver.
    5. If Roll Back Driver is unavailable, select Uninstall Device, check the prompt to attempt driver software removal, and restart the PC.
    Did this fix it?

  3. Install hardware updates via Windows Update

    Use this if Driver Verifier is already disabled but hardware or IOMMU protections continue to trigger DMA violations.

    1. Click Start and open Settings.
    2. Select Windows Update from the sidebar.
    3. Click Check for updates.
    4. Select Advanced options, then click Optional updates.
    5. Select and install any pending driver packages provided by hardware manufacturers, then restart your system.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 9, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What is Driver Verifier DMA Violation?

It is a Windows stop code indicating that a device driver performed an illegal Direct Memory Access operation, such as writing outside its memory buffer or freeing memory twice.

Can stop code 0x000000E6 happen if Driver Verifier is turned off?

Yes. The 0xE6 bug check can occur without Driver Verifier enabled if system IOMMU hardware detects an unauthorized memory access violation.

How do I stop Driver Verifier from crashing my PC on boot?

Start Windows in Safe Mode, open Command Prompt as an administrator, run the command verifier /reset, and reboot your computer.

More stop codes decoded