Question Random BSODs Latest one was DRIVER_VERIFIER_DMA_VIOLATION caused by ntoskrnl.exe need some help

[gardenlight]

Hi.I have had a lot of problems after I updated my pc with random bsods that I just can't seem to find out why they appear.
I have upgraded to windows 11 and ddr5 memory and after that the problems came.
All the things I have tried:
-I have tried to scan my disk for errors
-I have updated my graphics card drivers and bios and cpu firmware
-I have checked memory for memory errors and I have tried different ram speeds with and without xmp profile
-I have removed the cmos battery and changed power supply but still it happends
-I have also tried two different ddr5 brands with the same results and I'm so frustrated right now and I don't know what to do anymore.

My pc spec are:

-Msi Rtx 4090 Suprim x
-Intel coreI9-12900kf
-Corsair Vengeance DDR5 5200MHZ 32 GB RGB
-WD Black SN850 2TB M2
-Asus ROG Strix B660-F Gaming WIFI
-NZXT Kraken X53 CPU cooler.
I use Windows 11 64bit and Dual monitors.

I hope someone can help me with this.Thanks in advance.

 

[Lutfij]

I have upgraded to windows 11 and ddr5 memory and after that the problems came.
So you performed a motherboard change? What did you upgrade from, if the above is the upgraded platform?

You forgot to add the make and model of the PSU. Include the age of the PSU as well. BIOS version for your motherboard?

 

[gardenlight]

I have upgraded to windows 11 and ddr5 memory and after that the problems came.
So you performed a motherboard change? What did you upgrade from, if the above is the upgraded platform?

You forgot to add the make and model of the PSU. Include the age of the PSU as well. BIOS version for your motherboard?

This is the new system yeah. The Psu is new and it's called Asus ROG Strix 1000w.
The Bios version is 2212

I upgraded from :

-Gigabyte Z390 Aorus Ultra socket 1151
-Evga Supernova 850w
-Msi Rtx 3080 ti Suprim x
-I9-9900k
-Corsair Vengeance LPX DDR4 3000mhz 32gb

 

[johnbl]

you should put the verifier enabled minidump on a server, share it for public access and post a link.
it should name the driver that is doing the DMA violation.
DMA = direct memory access. often this will be some sound driver that you are not even using.
make sure this motherboard sound driver has been updated:
Realtek Audio Driver V6.3.9600.2335 For Windows 10/11 64-bit.
from here:ROG STRIX B660-F GAMING WIFI | ROG STRIX B660-F GAMING WIFI | Gaming Motherboards｜ROG - Republic of Gamers｜ROG Global (asus.com)
old versions from 2019 and before had a bug were it would respond to other dma transfer requests and cause other sound drivers to crash. (GPU sound drivers)
you could also disable the sound hardware in BIOS if you do not have speakers connected to it.

if you put the minidump on a server I can tell you what driver verifier caught doing something wrong.

 

[gardenlight]

you should put the verifier enabled minidump on a server, share it for public access and post a link.
it should name the driver that is doing the DMA violation.
DMA = direct memory access. often this will be some sound driver that you are not even using.
make sure this motherboard sound driver has been updated:
Realtek Audio Driver V6.3.9600.2335 For Windows 10/11 64-bit.
from here:ROG STRIX B660-F GAMING WIFI | ROG STRIX B660-F GAMING WIFI | Gaming Motherboards｜ROG - Republic of Gamers｜ROG Global (asus.com)
old versions from 2019 and before had a bug were it would respond to other dma transfer requests and cause other sound drivers to crash. (GPU sound drivers)
you could also disable the sound hardware in BIOS if you do not have speakers connected to it.

if you put the minidump on a server I can tell you what driver verifier caught doing something wrong.

I updated my Realtek audio drviver and I ran the driver verifier and got a Whole lot of bsods Here is my minidump file minidump

 

[johnbl]

looking at some of the bugcheck: (newest first)
system running 46 seconds
030223-26359-01.dmp
first one was a verifier catching a driver
farflt.sys
Timestamp: Fri Jan 27 06:48:23 2023
allocation of a memory block with a size of zero
malware bytes was the running process, the driver was for
malwarebytes anti ransom ware.
stack corrupted, will see if I can see something on the raw stack
edit: raw stack had calls to farflt.sys guess it corrupted the stack.
note sure what this driver does:
keyscrambler.sys Fri Sep 7 22:33:17 2018
need to look up.

old version of Samsung Magician running
magdrvamd64.sys Wed Aug 26 04:30:12 2015
but you have newer:
SamsungRapidDiskFltr.sys Tue Jun 11 17:09:32 2019
SamsungRapidFSFltr.sys Tue Jun 11 17:09:35 2019
Samsung RAPID Mode Disk Filter Driver

 

[gardenlight]

looking at some of the bugcheck: (newest first)

first one was a verifier catching a driver
farflt.sys
Timestamp: Fri Jan 27 06:48:23 2023
allocation of a memory block with a size of zero
malware bytes was the running process, the driver was for
malwarebytes anti ransom ware.
stack corrupted, will see if I can see something on the raw stack

Thanks for checking it out

 

[johnbl]

second, and third one was just like the first bugcheck
malware bytes file filter stack corruption attempt to allocate a zero size memory block

looks like they are all the same bugcheck,
I would remove uninstall the malwarebytes software for
farflt.sys. the corruption was due to a call to a unknown function.
This could mean that some other filter driver corrputed the information, the malwarebytes program does not match the farflt.sys driver it is calling into. (or just a bug in farflt.sys)
I would uninstall and continue testing

strange about the dates of the samsung files. I am suspect about some files from 2019 and one from 2015.

I would remove the software and reinstall the current version. (also check for firmware updates for ssd)

note you can turn off verifier via
verifier.exe /reset
and you can have it skip a file by
using the drive.exclude option like:
verifier.exe /driver.exclude farflt.sys

 

[gardenlight]

second, and third one was just like the first bugcheck
malware bytes file filter stack corruption attempt to allocate a zero size memory block

looks like they are all the same bugcheck,
I would remove uninstall the malwarebytes software for
farflt.sys. the corruption was due to a call to a unknown function.
This could mean that some other filter driver corrputed the information, the malwarebytes program does not match the farflt.sys driver it is calling into. (or just a bug in farflt.sys)
I would uninstall and continue testing

strange about the dates of the samsung files. I am suspect about some files from 2019 and one from 2015.

I would remove the software and reinstall the current version. (also check for firmware updates for ssd)

note you can turn off verifier via
verifier.exe /reset
and you can have it skip a file by
using the drive.exclude option like:
verifier.exe /driver.exclude farflt.sys

I removed malwarebytes and subscribed to bitdefender and I removed samsung magician.As for keyscrambler that is a program that scrambles my keystrokes to hinder others to see what I type and I have used it for several yeras now so I'm not sure if that would suddenly make problems.

 

[johnbl]

I removed malwarebytes and subscribed to bitdefender and I removed samsung magician.As for keyscrambler that is a program that scrambles my keystrokes to hinder others to see what I type and I have used it for several yeras now so I'm not sure if that would suddenly make problems.

sounds good. be sure to turn off verifier via
verifier.exe /reset
after you are done testing or your machine will run slowly until you do. (across reboots)

 

[gardenlight]

sounds good. be sure to turn off verifier via
verifier.exe /reset
after you are done testing or your machine will run slowly until you do. (across reboots)

I turned it off by opening the verifier and then the delete all saved settings option so I'm not sure if that disabeled it or not.

 

[johnbl]

I turned it off by opening the verifier and then the delete all saved settings option so I'm not sure if that disabeled it or not.

that will work also.

 

[gardenlight]

I just got another driver_verifier_dma validation bluescreen so much for thinking the system is stable 🙁 ntoskrnl.exe+51d2cd this time..I don't know what to do anymore.