Share via

Driver Verifier DMA Violation

Anonymous
2023-10-01T14:39:11+00:00

I've been having frequent crashes for awhile now and many of the USB ports on my motherboard have stopped working. I've tried uninstalling and reinstalling the USB controller drivers thinking that may be the issue but that has done nothing to resolve my problem. I ran WinDbg on the dump file but I can't make sense of anything as it doesn't list anything under device of faulting object. Any help would be much appreciated.

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: 00000000403cb56d, Faulting information (usually faulting physical address). Arg4: 0000000000000004, Fault type (hardware specific).

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1999

Key  : Analysis.Elapsed.mSec
Value: 4916

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

Key  : Analysis.Init.CPU.mSec
Value: 217

Key  : Analysis.Init.Elapsed.mSec
Value: 1921

Key  : Analysis.Memory.CommitPeak.Mb
Value: 98

Key  : Bugcheck.Code.LegacyAPI
Value: 0xe6

Key  : Failure.Bucket
Value: 0xE6\_26\_nt!IvtHandleInterrupt

Key  : Failure.Hash
Value: {11608481-d56e-58cc-4b64-17c92254d2f4}

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: e6

BUGCHECK_P1: 26

BUGCHECK_P2: 0

BUGCHECK_P3: 403cb56d

BUGCHECK_P4: 4

FILE_IN_CAB: 100123-8046-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffcc8af12c5080 -- (.trap 0xffffcc8af12c5080) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=0000000000000000 rsp=0100000500000000 rbp=ffffcc8af12c5080 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di pl nz na pe nc 00000000`00000000 ?? ??? Resetting default scope

IP_IN_FREE_BLOCK: 0

STACK_TEXT:
fffff80619a84ea8 fffff806144dfaf7 : 00000000000000e6 0000000000000026 0000000000000000 00000000403cb56d : nt!KeBugCheckEx fffff80619a84eb0 fffff806144cb90b : 0000000000000000 0000000000000000 fffff80614c49c10 fffff80614c49c10 : nt!IvtHandleInterrupt+0x1a7 fffff80619a84f10 fffff806142a7765 : fffff80614cf3b40 fffff80619a75a90 fffff80614cf3bf0 fffff806142a7765 : nt!HalpIommuInterruptRoutine+0x4b fffff80619a84f40 fffff806143febdc : fffff80619a75a90 fffff80614cf3b40 0000000000000366 fffff806143fed0a : nt!KiCallInterruptServiceRoutine+0xa5 fffff80619a84f90 fffff806143ff117 : fffff80619a75b30 0000000000000001 0000000000040046 fffff80614243b28 : nt!KiInterruptSubDispatchNoLock+0x11c fffff80619a75a10 fffff8061440162a : 0000000000000000 fffff80614d27a00 ffffcc8af12c5080 0000000000000366 : nt!KiInterruptDispatchNoLock+0x37 fffff80619a75ba0 0000000000000000 : fffff80619a76000 fffff80619a6f000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a

SYMBOL_NAME: nt!IvtHandleInterrupt+1a7

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3448

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1a7

FAILURE_BUCKET_ID: 0xE6_26_nt!IvtHandleInterrupt

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {11608481-d56e-58cc-4b64-17c92254d2f4}

Followup: MachineOwner

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

14 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-10-01T15:12:53+00:00

    Hi, I am Dave, I will help you with this.

    Please upload any minidump files you have for analysis, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    0 comments
  2. Anonymous
    2023-10-01T15:39:24+00:00

    Hello Dave,

                   Thank you for offering to help, however, I just tried doing a fresh install of windows to see if that would help with my issue and it led to me loosing all of my old minidump files. My issue doesn't seem to have been resolved though so whenever my system crashes again I'll be sure to upload the minidump file.
    0 comments
  3. Anonymous
    2023-10-01T15:41:46+00:00

    Glad to help, I will be here!

    0 comments
  4. Anonymous
    2023-10-01T19:18:09+00:00

    Hi Dave,

              I managed to find and restore the old minidump reports from my pc. Here's a Google Drive link to the zip file containing them. Let me know if there's any trouble accessing them.

    https://drive.google.com/file/d/1Gk-qD8axEHWZkmijMcmPEq0bYwrLvgIn/view?usp=sharing

    0 comments
  5. Anonymous
    2023-10-02T06:31:12+00:00

    Sorry, I was offline.

    Temporarily uninstall the RGB Fusion software from your PC, then wait to see if your system is stable.

    0 comments