DRIVER_VERIFIER_DMA_VIOLATION (e6) issue.

[Frank_Caragiulo]

Been trying to wrap my head around a problem i've been running into repeatedly for the past months (roughly 6 months) that hopefully someone with a bit more tech knowledge will be able to look at and provide some insight or even a solution. Like a handful of other similar posts, I've been running into this bluescreen for the last couple of weeks along (3 times total), my audio driver not recognizing any audio devices plugged into USB ports, and my mouse or keyboard disconnecting as well.

Specs:
Operating System
Windows 11 Pro 64-bit
CPU
Intel Core i7-13700KF 3.4 GHz 16-Core Processor
RAM
Silicon Power XPower Turbine 32 GB (2 x 16 GB) DDR4-3200 CL16 Memory
Motherboard
MSI Pro Z790-P WIFI DDR4 ATX LGA1700
GPU
NVIDIA RTX 4070 Ti 12 GB
Storage
Crucial P5 Plus 1 TB M.2-2280 PCIe 4.0 X4 NVME SSD
Audio
Realtek HD Audio



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

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 718

Key : Analysis.Elapsed.mSec
Value: 1472

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: 108

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xe6

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0xE6_26_nt!IvtHandleInterrupt

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

Key : WER.OS.Branch
Value: ni_release_svc_prod3

Key : WER.OS.Version
Value: 10.0.22621.1928


BUGCHECK_CODE: e6

BUGCHECK_P1: 26

BUGCHECK_P2: 0

BUGCHECK_P3: 4057d73e

BUGCHECK_P4: 4

FILE_IN_CAB: 101723-7296-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff804`37c92ec8 fffff804`3432a5ba : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`4057d73e : nt!KeBugCheckEx
fffff804`37c92ed0 fffff804`34312b6b : fffff804`34a619c0 fffff804`34a619c0 fffff804`34b0d800 fffff804`37c83a70 : nt!IvtHandleInterrupt+0x20a
fffff804`37c92f20 fffff804`340ae6dc : fffff804`34b0d750 ffff8001`b9922830 fffff804`34b0d800 fffff804`34b0d750 : nt!HalpIommuInterruptRoutine+0x4b
fffff804`37c92f50 fffff804`3421476c : fffff804`37c83a70 fffff804`34b0d750 fffff804`34b4d6c0 fffff804`3421bb30 : nt!KiCallInterruptServiceRoutine+0x9c
fffff804`37c92f90 fffff804`34214cf7 : 00000083`f7f573c0 ffffa708`00000000 00000083`f78c1265 00000000`00000000 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff804`37c839f0 fffff804`342174fa : 00000000`00000000 fffff804`30fcc010 00000000`00000000 fffff804`34b4d6c0 : nt!KiInterruptDispatchNoLock+0x37
fffff804`37c83b80 00000000`00000000 : fffff804`37c84000 fffff804`37c7d000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


SYMBOL_NAME: nt!IvtHandleInterrupt+20a

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.2428

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 20a

FAILURE_BUCKET_ID: 0xE6_26_nt!IvtHandleInterrupt

OS_VERSION: 10.0.22621.1928

BUILDLAB_STR: ni_release_svc_prod3

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner



Here is a copy to the minidump file on a Google Drive.

Minidump – Google Drive

drive.google.com

I have already tried updating my bios to the current version for the MSI motherboard, uninstalling/reinstalling the chipset drivers, i've ran a 4 hour Memtest with no results, and factory resetting the computer. At the time of writing this post I have already stopped "plug and play" as suggested on another post from 2022.

Any help/insight is appreciated as I know I'm not the only one who has been dealing with this sort of issue. I am certain it has to do with an audio driver of some sort but I'm not sure what.

 

[kerberos_20]

did you enabled driver verifier just to see which driver is causing it? driver verifier shouldnt be used in normal operation

it shows anyway that it isnt driver fault, but hardware fault (device disconnected)

so you can disable driver verifier
in command line type : verifier /reset
then reboot

 

[Frank_Caragiulo]

I did not activate the verifier until after the first bluescreen. I have reset the verifier after reading your reply.