Question I cannot stop getting blue screens dude

[GearyGears]

So a few months ago, my motherboard died. I decided to upgrade my CPU, PSU, and RAM along with a new motherboard. I did not upgrade my GPU. Ever since then, whenever I game, it'll go 15-30 minutes before blue screening. Each time, the stop code has has been DRIVER_VERIFIER_DMA_VIOLATION. Most recently, it happened while streaming a chrome tab to my friends over Discord.

I've tried everything. I've reset the driver verifier over a dozen times (not that it matters, because I never turned the thing on to begin with). I've reinstalled Windows. Nothing is working.

Here's a bunch of dump files.

The most recent one is from after I reinstalled Windows, which somehow did not solve the problem.

Specs:
Motherboard - MSI Pro Z690-A ProSeries
CPU - 12th Gen Intel Core i7-12700K 3.60GHz
GPU - NVIDIA GeForce GTX 1070
RAM - DDR5 Kingston 2x16GB
PSU - NZXT C750
HDD - Western Digital Blue 1TB

Someone, God, tell me what to do to fix this.

 

[Darkbreeze]

If there are any steps listed here that you have not already done, it would be advisable to do so if for no other reason than to be able to say you've already done it and eliminate that possibility.

First,​

Make sure your motherboard has the MOST recent BIOS version installed. If it does not, then update. This solves a high number of issues even in cases where the release that is newer than yours makes no mention of improving graphics card or other hardware compatibility. They do not list every change they have made when they post a new BIOS release. In cases where you DO already have the latest BIOS version, simply resetting the BIOS as follows has a fairly high percentage chance of effecting a positive change in some cases so it is ALWAYS worth TRYING, at the very least.

Second,​

Go to the product page for your motherboard on the manufacturer website. Download and install the latest driver versions for the chipset, storage controllers, audio and network adapters. Do not skip installing a newer driver just because you think it is not relevant to the problem you are having. The drivers for one device can often affect ALL other devices and a questionable driver release can cause instability in the OS itself. They don't release new drivers just for fun. If there is a new driver release for a component, there is a good reason for it. The same goes for BIOS updates. When it comes to the chipset drivers, if your motherboard manufacturer lists a chipset driver that is newer than what the chipset developer (Intel or AMD, for our purposes) lists, then use that one. If Intel (Or AMD) shows a chipset driver version that is newer than what is available from the motherboard product page, then use that one. Always use the newest chipset driver that you can get and always use ONLY the chipset drivers available from either the motherboard manufacturer, AMD or Intel.


IF you have other hardware installed or attached to the system that are not a part of the systems covered by the motherboard drivers, then go to the support page for THAT component and check to see if there are newer drivers available for that as well. If there are, install them.

Third,​

Make sure your memory is running at the correct advertised speed in the BIOS. This may require that you set the memory to run at the XMP profile settings. Also, make sure you have the memory installed in the correct slots and that they are running in dual channel which you can check by installing CPU-Z and checking the Memory and SPD tabs. For all modern motherboards that are dual channel memory architectures, from the last ten years at least, if you have two sticks installed they should be in the A2 (Called DDR4_1 on some boards) or B2 (Called DDR4_2 on some boards) which are ALWAYS the SECOND and FOURTH slots over from the CPU socket, counting TOWARDS the edge of the motherboard EXCEPT on boards that only have two memory slots total. In that case, if you have two modules it's not rocket science, but if you have only one, then install it in the A1 or DDR4_1 slot.

Fourth (And often tied for most important along with an up-to-date motherboard BIOS),​

A clean install of the graphics card drivers. Regardless of whether you "already installed the newest drivers" for your graphics card or not, it is OFTEN a good idea to do a CLEAN install of the graphics card drivers. Just installing over the old drivers OR trying to use what Nvidia and AMD consider a clean install is not good enough and does not usually give the same result as using the Display Driver Uninstaller utility. This has a very high success rate and is always worth a shot.


If you have had both Nvidia and AMD cards installed at any point on that operating system then you will want to run the DDU twice. Once for the old card drivers (ie, Nvidia or AMD) and again for the currently installed graphics card drivers (ie, AMD or Nvidia). So if you had an Nvidia card at some point in the past, run it first for Nvidia and then after that is complete, run it again for AMD if you currently have an AMD card installed.

Graphics card driver CLEAN install guide using the Wagnard tools DDU



And last, but not least, if you have never done a CLEAN install of Windows, or have upgraded from an older version to Windows 10, or have been through several spring or fall major Windows updates, it might be a very good idea to consider doing a clean install of Windows if none of these other solutions has helped. IF you are using a Windows installation from a previous system and you didn't do a clean install of Windows after building the new system, then it's 99.99% likely that you NEED to do a CLEAN install before trying any other solutions.


How to do a CLEAN installation of Windows 10, the RIGHT way​

 

[Colif]

just helping @Darkbreeze

Driver verifer is always on, you don't have to enable it - though it is an option. In its default state its less likely to cause drivers to BSOD than if you ask it to check drivers yourself. Default state it just finds drivers that are misbehaving.

Conversion of dumps
results- click read as fiddle to see report

Spoiler

File: 091022-36812-01.dmp (Sep 11 2022 - 13:39:55)
BugCheck: [DRIVER_VERIFIER_DMA_VIOLATION (E6)]
Probably caused by: memory_corruption (Process: System)
Uptime: 1 Day(s), 21 Hour(s), 02 Min(s), and 05 Sec(s)

File: 071922-36656-01.dmp (Jul 20 2022 - 03:41:51)
BugCheck: [DRIVER_VERIFIER_DMA_VIOLATION (E6)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 23 Hour(s), 26 Min(s), and 34 Sec(s)

File: 071822-35390-01.dmp (Jul 19 2022 - 04:08:27)
BugCheck: [DRIVER_VERIFIER_DMA_VIOLATION (E6)]
Probably caused by: memory_corruption (Process: System)
Uptime: 1 Day(s), 23 Hour(s), 28 Min(s), and 51 Sec(s)

File: 071622-37765-01.dmp (Jul 17 2022 - 04:26:54)
BugCheck: [DRIVER_VERIFIER_DMA_VIOLATION (E6)]
Probably caused by: memory_corruption (Process: audiodg.exe)
Uptime: 1 Day(s), 3 Hour(s), 15 Min(s), and 07 Sec(s)

File: 071422-48562-01.dmp (Jul 15 2022 - 15:48:13)
BugCheck: [DRIVER_VERIFIER_DMA_VIOLATION (E6)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 10 Hour(s), 48 Min(s), and 42 Sec(s)

File: 071422-44296-01.dmp (Jul 15 2022 - 04:51:11)
BugCheck: [DRIVER_VERIFIER_DMA_VIOLATION (E6)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 6 Day(s), 14 Hour(s), 08 Min(s), and 45 Sec(s)

File: 070722-53187-01.dmp (Jul 8 2022 - 14:39:47)
BugCheck: [INTERNAL_POWER_ERROR (A0)]
Probably caused by: memory_corruption (Process: System)
Uptime: 8 Day(s), 10 Hour(s), 39 Min(s), and 59 Sec(s)

File: 062722-51718-01.dmp (Jun 28 2022 - 04:28:36)
BugCheck: [DRIVER_VERIFIER_DMA_VIOLATION (E6)]
Probably caused by: memory_corruption (Process: NordVPN.exe)
Uptime: 9 Day(s), 13 Hour(s), 00 Min(s), and 39 Sec(s)

File: 060222-35437-01.dmp (Jun 3 2022 - 10:13:47)
BugCheck: [DRIVER_VERIFIER_DMA_VIOLATION (E6)]
Probably caused by: memory_corruption (Process: System)
Uptime: 2 Day(s), 8 Hour(s), 36 Min(s), and 18 Sec(s)

One does blame Nvidia but a lot of them blamed windows, that doesn't happen. Windows files don't cause BSOD, they might be pushed but they don't cause them. Top 5 all say - *** WARNING: Unable to verify timestamp for win32k.sys
Generally if I see that timestamp warning for a file, it is cause of BSOD. For instance, the Nvidia crash says
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
but then it also mentions the win32k.sys file.

DDU might help but his current drivers newer than the ones that caused the BSOD.

Jul 22 2022

nvlddmkm.sys

Nvidia Graphics Card driver http://www.nvidia.com/

If you look at spoiler, the process named is the victim (also makes me wonder what happened to August, all the dumps are June, July, Sept)

User is on Bios 7D25vA3 and latest is 7D25vA7, they only 2 versions behind. It could help

Something tells me checking ram might be an idea

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

finding a new driver for his Bluetooth dongle might be fun

Aug 08 2013

bcbtums.sys

Broadcom Bluetooth Firmware Download Filter driver

 

[GearyGears]

I updated my BIOS a few months ago after this first started happening. I can try it again but I don't know it'll help.

I'll try testing my memory after I get home from work tonight.

 

[Darkbreeze]

What BIOS version are you currently running?

 

[Colif]

User is on Bios 7D25vA3 and latest is 7D25vA7, they only 2 versions behind. It could help

 

[Darkbreeze]

Right. If you're two versions back on BIOS then updating to the latest version could very well help and even if it doesn't help with this issue it may help to avoid other issues. Doing ANYTHING else to try and solve a problem when you are not on the latest BIOS version is always a good way to potentially waste your time since this resolves so many problems across the board. And, these days it should be kept up to date same as with drivers. I isn't always the answer, but it's never NOT possibly the answer.