Windows 10: DRIVER_VERIFIER_DMA_VIOLATION e6 IOMMU detected DMA violation

Discus and support DRIVER_VERIFIER_DMA_VIOLATION e6 IOMMU detected DMA violation in Windows 10 Software and Apps to solve the problem; 0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis **... Discussion in 'Windows 10 Software and Apps' started by TCP_PB, Aug 23, 2024.

  1. TCP_PB Win User

    DRIVER_VERIFIER_DMA_VIOLATION e6 IOMMU detected DMA violation


    0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_VERIFIER_DMA_VIOLATION e6An illegal DMA operation was attempted by a driver being verified.Arguments:Arg1: 0000000000000026, IOMMU detected DMA violation.

    :)
     
    TCP_PB, Aug 23, 2024
    #1
  2. MJ_STAR Win User

    Enabled the "DMA remapping" for my device driver but I still get the "IOMMU detected DMA violation" error

    Hi,

    I have enabled the DMA remapping for my device driver but I still get the "IOMMU detected DMA violation" error whenever I try to perform any DMA transactions on my PCI device connected via Thunderbolt 3.

    I have updated the UEFI firmware. The DMA Kernel Protection is ON.

    The driver shows "DMA remapping policy" enabled.

    Also, set the group policy 'Disable new DMA devices when this computer is locked' for the BitLocker to "Disabled".

    Driver Verifier is running.

    Any idea why still get the error DRIVER_VERIFIER_DMA_VIOLATION? The device get enumerated but it fails on DMA operations. Curiously enough, I thought I wouldn't be able to access to my device only when the system was asleep AND my device driver was not compatible with DMA remapping? Otherwise it should function normally according to this:

    "By default, peripherals with DMA Remapping incompatible drivers will be blocked from starting and performing DMA until an authorized user signs into the system or unlocks the screen."

    Any idea what's going on?

    Thanks,

    MJ

    PS.

    FYI:



    Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff802`5fe00000 PsLoadedModuleList = 0xfffff802`60a2a2d0

    Debug session time: Wed Dec 1 16:59:57.956 2021 (UTC + 0:00)

    System Uptime: 0 days 0:02:25.818

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    ........................................

    Loading User Symbols



    Loading unloaded module list

    .............................

    For analysis of this file, run !analyze -v

    0: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    DRIVER_VERIFIER_DMA_VIOLATION (e6)

    An illegal DMA operation was attempted by a driver being verified.

    Arguments:

    Arg1: 0000000000000026, IOMMU detected DMA violation.

    Arg2: 0000000000000000, Device Object of faulting device.

    Arg3: 0000000000000001, Faulting information (usually faulting physical address).

    Arg4: 0000000000000006, Fault type (hardware specific).



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.mSec

    Value: 3327



    Key : Analysis.DebugAnalysisManager

    Value: Create



    Key : Analysis.Elapsed.mSec

    Value: 3334



    Key : Analysis.Init.CPU.mSec

    Value: 3187



    Key : Analysis.Init.Elapsed.mSec

    Value: 312916



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 82



    Key : WER.OS.Branch

    Value: vb_release



    Key : WER.OS.Timestamp

    Value: 2019-12-06T14:06:00Z



    Key : WER.OS.Version

    Value: 10.0.19041.1





    BUGCHECK_CODE: e6



    BUGCHECK_P1: 26



    BUGCHECK_P2: 0



    BUGCHECK_P3: 1



    BUGCHECK_P4: 6



    BLACKBOXBSD: 1 (!blackboxbsd)





    BLACKBOXNTFS: 1 (!blackboxntfs)





    BLACKBOXPNP: 1 (!blackboxpnp)





    BLACKBOXWINLOGON: 1



    PROCESS_NAME: System



    STACK_TEXT:

    fffff802`630a1ea8 fffff802`602db447 : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx

    fffff802`630a1eb0 fffff802`602c730b : 00000000`00000000 00000000`00000000 fffff802`60a49cf0 fffff802`60a49cf0 : nt!IvtHandleInterrupt+0x1a7

    fffff802`630a1f10 fffff802`600de055 : fffff802`60af3bc0 fffff802`63092a50 fffff802`60af3c70 fffff802`630a1fc0 : nt!HalpIommuInterruptRoutine+0x4b

    fffff802`630a1f40 fffff802`601f8c1c : fffff802`63092a50 fffff802`60af3bc0 00000000`00000ec4 fffff802`601fdf90 : nt!KiCallInterruptServiceRoutine+0xa5

    fffff802`630a1f90 fffff802`601f9027 : fffff802`63092af0 00000000`00000001 00000000`00040046 fffff802`60017138 : nt!KiInterruptSubDispatchNoLock+0x11c

    fffff802`630929d0 fffff802`601fadca : 00000000`00000000 fffff802`60b27a00 ffffdf05`78106080 00000000`00000ec4 : nt!KiInterruptDispatchNoLock+0x37

    fffff802`63092b60 00000000`00000000 : fffff802`63093000 fffff802`6308c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a





    SYMBOL_NAME: nt!IvtHandleInterrupt+1a7



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 1a7



    FAILURE_BUCKET_ID: 0xE6_nt!IvtHandleInterrupt



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {2cafa897-b47c-7b20-cee6-b1b68f30ec38}



    Followup: MachineOwner

    ---------
     
    MJ_STAR, Aug 23, 2024
    #2
  3. phelanka7 Win User
    BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)

    I have been getting this error (BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)) typically while playing video games but have seen it occur simply idling. The thing that I find strange is that I don't even have the Driver Verifier turned on. I have done the "verifier /reset" command which was one of the first things I tried to do to fix it after Googling the error. I have tried a number of things to try and fix this. A non-exhaustive list includes:

    • Reinstalling GPU drivers using DDR (Display Driver Remover)
    • Meticulously updating every single driver for every device
    • Clean out the registry using CCleaner
    • Flashing BIOS
    • Ran Memtest86 (RAM stress test)
    • Ran Prime95 (cpu stress test)
    • chkdsk

    I'm far from computer illiterate but this has me completely stumped. So I come to you, the experts, hat in hand. Please help me. You're my only hope.
     
    phelanka7, Aug 23, 2024
    #3
  4. DRIVER_VERIFIER_DMA_VIOLATION e6 IOMMU detected DMA violation

    Mysterious Shutdowns

    Hi!

    I’m sorry that the blue screen log information you provided did not specifically locate a driver.

    Analyze error codes:

    DRIVER_VERIFIER_DMA_VIOLATION (e6)

    An illegal DMA operation was attempted by a driver being verified.

    Arguments:

    Arg1: 0000000000000026, IOMMU detected DMA violation.

    Arg2: 0000000000000000, Device Object of faulting device.

    Arg3: 00000000001d89f3, Faulting information (usually faulting physical address).

    Arg4: 0000000000000005, Fault type (hardware specific).

    In order to better help you solve the problem, perform this operation, the blue screen log will be more detailed:



    1. Enter verifier in start-run, press Enter, and the verifier interface will pop up. Select the second item Create custom settings (for code developers), the next step.

    2. Select Enable predefined settings>Select all>Next>Next.

    3. Select the driver name> Next from the list.

    4. Then, select all from the list of drivers displayed on the interface, and then click Finish.

    If the blue screen appears again, I suggest you send it to us in the private mailbox again, and we will try our best to help you solve it.

    Sincerely

    Rebecca | Microsoft Community Support Expert
     
    Rebecca -MSFT, Aug 23, 2024
    #4
Thema:

DRIVER_VERIFIER_DMA_VIOLATION e6 IOMMU detected DMA violation

Loading...
  1. DRIVER_VERIFIER_DMA_VIOLATION e6 IOMMU detected DMA violation - Similar Threads - DRIVER_VERIFIER_DMA_VIOLATION IOMMU detected

  2. DRIVER_VERIFIER_DMA_VIOLATION e6 IOMMU detected DMA violation

    in Windows 10 Gaming
    DRIVER_VERIFIER_DMA_VIOLATION e6 IOMMU detected DMA violation: 0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_VERIFIER_DMA_VIOLATION e6An illegal DMA operation was attempted by...
  3. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Gaming
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello, I have gotten this BSOD a couple times now while playing a game. Its not all the time and seems to be random. Any help would be greatly appreciated because i cannot seem to figure out what is causing this issue and its starting to frustrate me. I have tried clean...
  4. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Software and Apps
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello, I have gotten this BSOD a couple times now while playing a game. Its not all the time and seems to be random. Any help would be greatly appreciated because i cannot seem to figure out what is causing this issue and its starting to frustrate me. I have tried clean...
  5. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 BSOD Crashes and Debugging
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello, I have gotten this BSOD a couple times now while playing a game. Its not all the time and seems to be random. Any help would be greatly appreciated because i cannot seem to figure out what is causing this issue and its starting to frustrate me. I have tried clean...
  6. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Gaming
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello Guys,maybe somebody can help me, i am receiving an Bluescreen very often.I have uploaded the Minidumps which was stored in the Minidump Folder I tried to analyze the dumps with windbg but the only process which crash is follow ntkrnlmp.exe.Maybe anybody can check this...
  7. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Software and Apps
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello Guys,maybe somebody can help me, i am receiving an Bluescreen very often.I have uploaded the Minidumps which was stored in the Minidump Folder I tried to analyze the dumps with windbg but the only process which crash is follow ntkrnlmp.exe.Maybe anybody can check this...
  8. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 BSOD Crashes and Debugging
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello Guys,maybe somebody can help me, i am receiving an Bluescreen very often.I have uploaded the Minidumps which was stored in the Minidump Folder I tried to analyze the dumps with windbg but the only process which crash is follow ntkrnlmp.exe.Maybe anybody can check this...
  9. BSOD - DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 BSOD Crashes and Debugging
    BSOD - DRIVER_VERIFIER_DMA_VIOLATION e6: Hello One of our Lenovo P53 Notebooks threw this bluescreen today, out of nowhere the user was typing in notepad. It is not reproducable. Driver verifier is disabled. I have a minidmup and a memorydump, please tell me what's needed. I tried analyzing them using WinDBG...
  10. BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)

    in Windows 10 BSOD Crashes and Debugging
    BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6): I have been getting this error (BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)) typically while playing video games but have seen it occur simply idling. The thing that I find strange is that I don't even have the Driver Verifier turned on. I have done the "verifier /reset" command...