Question DRIVER_VERIFIER_DMA_VIOLATION Issue

[thethrowsf]

o I've been running into this bluescreen for the last couple of weeks along with short freezes, my audio driver disconnecting, and my mouse or keyboard briefly disconnecting as well.

I've had this computer for over two months and it recently started doing this.

Ever since this started happening, I updated my BIOS, reinstalled my audio drivers, updated my GPU drivers, got the recent windows update and intel updates, and updated my SSD firmware. After doing all that, I still have this problem. So I'm kind of stump so I would like some help.

Specs:
Operating System
Windows 11 Pro 64-bit
CPU
Intel Core i7-12700KF @ 3.60GHz
RAM
32.0GB Dual-Channel GSkill @ 3600MHz
Motherboard
MSI z690-A DDR4
GPU
NVIDIA GeForce GTX 1070
Storage
Samsung SSD 980 PRO 1TB
Audio
Realtek High Definition 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: 0000000040313cf3, Faulting information (usually faulting physical address).
Arg4: 0000000000000004, Fault type (hardware specific).

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1171

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1176

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

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

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

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE: e6

BUGCHECK_P1: 26

BUGCHECK_P2: 0

BUGCHECK_P3: 40313cf3

BUGCHECK_P4: 4

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
fffff8055096eec8 fffff8055252add1 : 00000000000000e6 0000000000000026 0000000000000000 0000000040313cf3 : nt!KeBugCheckEx
fffff8055096eed0 fffff80552513cfb : fffff80552c4bd40 fffff80552c4bd40 ffff9501b9747100 fffff80500400a02 : nt!IvtHandleInterrupt+0x1d1
fffff8055096ef20 fffff80552221440 : fffff80552cf8090 fffff80552cf8140 ffff9501b97471f0 fffff8055096ef40 : nt!HalpIommuInterruptRoutine+0x4b
fffff8055096ef50 fffff8055241846c : fffff8055095fa70 fffff80552cf8090 ffff950100000000 fffff80550953000 : nt!KiCallInterruptServiceRoutine+0xa0
fffff8055096ef90 fffff805524188a7 : 0000000150650000 00000000ffffffff 000000313dea5d2f 0000000000000000 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff8055095f9f0 fffff8055241a89a : 0000000000000000 fffff80552d35bc0 ffffdf8d94da0080 00000000000009be : nt!KiInterruptDispatchNoLock+0x37
fffff8055095fb80 0000000000000000 : fffff80550960000 fffff80550959000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a


SYMBOL_NAME: nt!IvtHandleInterrupt+1d1

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1d1

FAILURE_BUCKET_ID: 0xE6_nt!IvtHandleInterrupt

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner
---------

Link to minidump
https://drive.google.com/file/d/1mN_LzAuUXo8n6DHSWh2HaWS9wiayUhZy/view?usp=sharing

 

[thethrowsf]

Nothing listed for today. Is it because of the driver verifier?

 

[johnbl]

Nothing listed for today. Is it because of the driver verifier?

just have to wait for a bugcheck. turning on verifier causes the tested code to run slower. This can make it harder to find bugs that are caused by timing related problems.
verifier should not prevent the dump from being saved.
unless the bugcheck was in the storage driver. Then you might have to move where the .dmp file gets saved to a different controller and drive.

 

[thethrowsf]

So it crashed and didn't produce a dump file again. Event viewer doesn't see it as a bug check but it did say Driver Verifier DMA violation on the bluescreen. It's so weird.

 

[johnbl]

So it crashed and didn't produce a dump file again. Event viewer doesn't see it as a bug check but it did say Driver Verifier DMA violation on the bluescreen. It's so weird.

only thing i can think of would be to delete the old dump files, empty the recycle bin. google how to force a memory dump via keybaord, set the registry settings then reboot and use the keyboard to force the memory dump when verifier is running. then confirm it is being made.

 

[thethrowsf]

I did the force bsod, it did not create a dump file. with driver verifier on.

When I turned off the driver verifier and did the force bsod, it created the dumpfile.

 

[johnbl]

I did the force bsod, it did not create a dump file. with driver verifier on.

When I turned off the driver verifier and did the force bsod, it created the dumpfile.

what is the command you are running?
maybe try turning on the standard flags which includes the dma checking.

run
verifier.exe /standard /all

and see if you can force a memory dump.
-------------
found someone saying that they could not get a memory dump if driver verifier was turned on. the were able to exclude all of the drivers that started with the word dump..... and they could then get a memory dump via keyboard. could have been related to a smart defrag tool they had installed at the time. not clear since they removed the tool and excluded the drivers at the same time and got it working. (old info from 2012)

 

[thethrowsf]

I did a custom settings with dma checking.

Ill try what you said next.

 

[thethrowsf]

what is the command you are running?
maybe try turning on the standard flags which includes the dma checking.

run
verifier.exe /standard /all

and see if you can force a memory dump.
-------------
found someone saying that they could not get a memory dump if driver verifier was turned on. the were able to exclude all of the drivers that started with the word dump..... and they could then get a memory dump via keyboard. could have been related to a smart defrag tool they had installed at the time. not clear since they removed the tool and excluded the drivers at the same time and got it working. (old info from 2012)

I ran the verifier.exe /standard /all, did a force bsod and does not produce a bsod. should i exclude all of the drivers that started with the word dump?

 

[johnbl]

I ran the verifier.exe /standard /all, did a force bsod and does not produce a bsod. should i exclude all of the drivers that started with the word dump?

if you can get a .dmp then go ahead and include all the drivers

 

[thethrowsf]

didn't work. :/

 

[johnbl]

didn't work. :/

didn't work. :/

well the whole reason you get this bugcheck is most likely some driver is directly programming a DMA chip without going through the normal windows interface. I would next try to remove the headset and driver (remember to show hidden devices and remove the software driver from device manager) Then see if you still get the same DMA bugcheck without the headset driver installed. Do a kernel dump with no flags set.

 

[thethrowsf]

Hello, I don't know if this is part of the problem but apparently, the motherboard is having sleep/hibernating issues according to this post.

https://forum-en.msi.com/index.php?threads/pro-z690-a-ddr4-wifi-owners-thread.370399/page-8

I don't know if this ties into the usb drivers malfunctioning because of that.

Today is also a unique day because all my usb devices decided to stay off after reboot. I had to wait about 5 minutes before rebooting for it to stay on. Should I return my motherboard and get a different one?

I still have the problem, but if I restart my computer after turning it on for the first time, the problem does not occur.

 

[johnbl]

Hello, I don't know if this is part of the problem but apparently, the motherboard is having sleep/hibernating issues according to this post.

https://forum-en.msi.com/index.php?threads/pro-z690-a-ddr4-wifi-owners-thread.370399/page-8

I don't know if this ties into the usb drivers malfunctioning because of that.

Today is also a unique day because all my usb devices decided to stay off after reboot. I had to wait about 5 minutes before rebooting for it to stay on. Should I return my motherboard and get a different one?

I still have the problem, but if I restart my computer after turning it on for the first time, the problem does not occur.

I once isolated a problem where a computer would bugcheck every morning but only one time per day. We then found it would happen if you powered down the machine for 35 minutes and figured out it actually was dependent on the temperature. Bugcheck if the machine was under a certain temperature when booted. No bugcheck if above that temp. No bugcheck if booted into bios for 30 seconds before booting into windows from a cold temp.

It turned out to be a manufacturing defect. A pin on a chip did not have any solder on it. When the computer was cold the pin did not touch the circuit board. After the chip got power it would heat up ,expand and the chip leg would touch the pad and it would start working correctly. Caused crazy problems for windows and took me a month to find the problem. The chip was under a heat sink, spring clips on the heat sink helped keep the connection. I had to remove the sink and look at the chip connection using a stereoscope to verify the defect. These type of errors tend to pass QA tests.

You can also get the same type of issue with bad connections of cables, but you can replace cable with bad connectors.

Most people just give up and exchange the board if they can. people with proper tools would test with heat gun and freon canister to cool to try to find the bad circuit.
for example, heat gun to warm the cold machine then boot to see if the problem goes away.
or use the freeze spray to cool a circuit to see if you get the problem again. (to find the bad circuit)

I would replace the board if I could, even with the same one. Bios can fix some issues if they are on all the motherboards. You will never get a good fix if the problem is only on a small percentage of the boards. Sometimes talking to the vendor they will just exchange the board or offer a replacement. (they don't admit a defect but if they know of a problem they offer the exchange very quickly) Happened with me about a SATA port that would disconnect. When I talked to asus and even started to mention the problem, they offered to pay shipping both ways and sent me a better board model in exchange for the bad one. I always assumed there was a known defect.

problem with sleep is that I have seen machines that seem to work perfectly with sleep modes with a clean install but later stop working correctly after updates.
It is like Microsoft WER thinks there is some defect and applies some patch to "fix" and it stops working. I have seen this happen on a few machines but never tracked it down fully. (only reinstalled and found everything working, did updates and stopped working, it was not the regular updates)

 

[thethrowsf]

I think ill try returning the board since I only had it for a couple of months. I'm still confounded why this problem happened after a month of usage.

 

[Matija47]

Hey thethrowsf, I am having the same exact issue you had in this thread. (Same events in the eventviewer, same bugcheck). It is INSANELY annoying and I am not sure what to do. I can only think it is a motherboard issue. It would happen randomly every couple days. Same thing as you. I have a very similar build as you too.

CPU: Intel Core i5-12600K 3.7 GHz 10-Core Processor
Motherboard: MSI PRO Z690-A DDR4 ATX LGA1700
PSU: Corsair RMx (2021) 750 W 80+ Gold Certified Fully Modular ATX

Since it's been months, I'd hope you found a fix to this issue by now. My next step was to literally just replace the motherboard because that is the only thing that makes sense to me right now. What did you do exactly?

Thanks a lot!

 

[Colif]

I would suggest making your own question and if you follow the steps in the top post here, and show me a link, I will see what I can do.

How To - Handy details to include in Blue Screen of Death posts

If you make a post asking for help with Blue Screen of Death errors, can you please do the following: 1.Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in...

forums.tomshardware.com

I hope op has fixed it now too