Windows 10: DPC_WATCHDOG_VIOLATION error caused BSOD. What's causing it and how do I prevent this error...

The only new thing I did today was download ModAPI.exe for the "The Forest" game from here https://modapi.survivetheforest.net and update NVIDIA GeForce drivers. The BSOD that happened twice both happened while I was playing "The Forest". Also, idk if this is related to the DPC_WATCHDOG_VIOLATION error but I had Discord, Microsoft Teams, RivaTuner, and MSI Afterburner open while installing the update. The update force quitted my Discord and froze the NVIDIA GeForce Experience for a bit but the update was still a success.Here is a link to my .dmp files.

:)

 

Possible Causes of atikmdag errors

I was courious to see how many different causes there are to the infamous atikmdag.sys error that strikes widely across and has so for a long time, I am getting it myself also and it is really starting to wear me out. It is pretty annoying having a $520 Readeon 3870x2 card if you can't use it without errors.

So first of all, here is the apparant reason for my atikmdag error:

When I play a game, regardless of settings, clocks or anything else, the fan speed wil not be adjusting and the card will get hotter as it performs. As soon as the card gets hot enough, my system will attempt to speed up the fan and as soon as they do, I get the atikmdag error. I never hear the fan of my card go beyond 30% fan speed unless I push it using Rivatuner.

Anyone else got other apparant reasons?

By the way, here are the steps I have been trying to fix it

• Renaming atikmdag.sys to "atikomdag.sys(old)
• Set fan speed profiles in Rivatuner depending on temeprature thresholds
• Setting fixed fan speed in Rivatuner
• Installing only the ATI drivers without Catalyst Control Centre
• Replacing RAM blocks
• Trying older drivers

I have probably tried a few

 

BSOD Hardware Caused???

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD

 

BSOD Hardware Caused???

It is not overheating - CPU runs 60*C in games.
Short Circuit - EXTREAMLY UNLIKELY