Windows 10: BSOD when playing game with USB controller - DRIVER_VERIFIER_DMA_VIOLATION e6

MEMORY DUMP FILE: https://drive.google.com/file/d/1H6z1ZSQve7jR-ueTVv-vWnyjMTSSuICY/view?usp=sharingWas playing Fortnite with friends, I had a USB controller plugged in that had some cable issues wouldn't turn on at certain cable angles but I assumed that it'd be fine. All of a sudden, after some small controller issues, I get a BSOD. I realize it's probably likely from this faulty USB controller but, can anyone confirm? Obviously I have the controller disconnected now ********************************************************************************

:)

 

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.

 

BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)

Might have figured it out. Played video games nearly all weekend with no issues. What I did was drop my audio quality down one notch from 48000Hz to 44100Hz. I played stuff on Ultra quality. Even ran some VR with no problems.

Attachment 216812

Then tonight while watching an NFL stream on my laptop monitor while I was playing a game on my HDMI monitor and crashed again. After rebooting and coming back I found that something had set my bitrate had been set back to 48000Hz from 44100Hz.

Also, this time it looks like the BSOD gave the paging file time to cooperate so I feel like this memory.dmp won't be corrupt. I think that procedure you suggested in the previous did the trick. I'm hoping anyway.

100% sure that the issue is something audio related. Whether its hardware or software issue I don't know. I'm hoping this dmp file will suggest some sort of fix.

Dropbox - MEMORY.DMP

 

BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)

Check this out... Audiodg.exe crash right before the e6 bug BSOD:

Attachment 216484Attachment 216485

I have found some different audio drivers I am going to try and see if that resolves the issue.