Question driver verifier dma violation

[Genarus]

Been trying to fix this for awhile now.

Issue coincides with a sound issue I have with my head set where it would do a loud static sound and goes away when unplugging the usb for the headset and putting it back in.

Thought it was discord for awhile until recently got the sound issue then BSOD at the same time and past several BSODS been the same "driver verifier dma violation".

Tried disabling the driver verifier and no go. Updated and purged sound drivers and no go. Tried to disable kernal on bios for it and its already off.

OS: Windows 10
Mobo: Rog maximus Z790 hero

 

[ubuysa]

Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

Why Was Driver Verifier enabled at all? It's a troubleshooting tool that is designed to cause BSODs, so you never normally have it enabled.

To be sure it's disabled open a command prompt and enter the command verifier /reset.

 

[Genarus]

Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

Why Was Driver Verifier enabled at all? It's a troubleshooting tool that is designed to cause BSODs, so you never normally have it enabled.

To be sure it's disabled open a command prompt and enter the command verifier /reset.

<<Link removed by moderator>>

When I did verifier /reset said no settings were changed

 

[ubuysa]

Driver Verifier was already disabled then.

Can you please make the Google Drive file public (anyone with the link)?

 

[Genarus]

Ok this should work now https://drive.google.com/file/d/1TN4Drj7X8rryfvfA56549ge4nC0Wxe2J/view?usp=sharing

 

[ubuysa]

Thanks. I think this might well be bad RAM.

The four dumps are all DMA failures but the physical memory addresses that are failing are all very close together. In addition, in your Application log I can see more application error messages than I would normally expect, and most of them are failing for memory access reasons (0xC000005 and 0xC0000409 exceptions).

You have two 32GB sticks so the easiest (and most reliable) way to test your RAM is to remove one stick for a few days (or until you get a BSOD). Then swap the sticks over and run on just the other stick for a few days (or until you get a BSOD).

If it BSODs on each stick on its own then it's unlikely to be RAM.

 

[ex_bubblehead]

The question no one has yet asked. Are ALL DIMM's from the same package (factory matched) or are they from separate purchases? Mismatched memory is the single most common problem encountered. And as a comment to the previous post it is very likely to be RAM in this case.

 

[ubuysa]

The question no one has yet asked. Are ALL DIMM's from the same package (factory matched) or are they from separate purchases? Mismatched memory is the single most common problem encountered. And as a comment to the previous post it is very likely to be RAM in this case.

Indeed and I did look at that in the dumps. Both sticks are exactly the same part number; G.Skill F5-5600J2834F32G running at the SPD speed of 4800MHz.

 

[Genarus]

I'll have to check that tomorrow and see if it does anything I haven't had a BSOD since i made the post so its rare for it to do so but... I think I know how to trigger it so I'll attempt that.