BSOD - DPC_Watchdog_Violation

Hello.
I have upgraded my PC and since then I am having BSODs at random times - one time it happens 5 minutes after I turn on my PC and sometimes after 1 day of uptime. The error code is often DPC_WATCHDOG_VIOLATION but once it was whea_uncorrectable_error and clock_watchdog_timeout. I tried to use Driver Verifier but once I turn it on - the PC won't start and it creates a ,,loop" and restarts over and over again.
I literally searched the whole internet and can't find any solution, so I beg you for help.
Below I attach logs from ,,Log collector v2" and .ZIP file with 5 minidumps.
Greetings,
Oliwier.

Windows Version: 20H2 (Os build 19042.630)

Update BIOS - MSI Polska
Send full memory dump (MEMORY.DMP from C:\Windows)

Hello.
I updated my BIOS to the latest one. Below is a screenshot from msinfo32.
Also below is a link to memory.dmp file, I uploaded it on google drive.
Thank you for your response.
Greetings,
Oliwier.

MEMORY.DMP - Google Drive

Attachment 308818

Update NVIDIA graphics driver - NVIDIA DRIVERS GeForce Game Ready Driver WHQL

MrPepka said:

Update NVIDIA graphics driver - NVIDIA DRIVERS GeForce Game Ready Driver WHQL

I updated them, even to the newer version that came out today - 457.51.
But I am having those BSODs for 4-5 months and that time the drivers were up to date. Are NVIDIA drivers the reason for those crashes?
Thanks for your response.
Oliwier.

Ztruker said:

As I said, what did the upgrade include? Almost a certainty that one of the upgraded parts is the cause of the problem.
Please list them.

You can try removing them one at a time and installing the old parts where possible to see if that resolves the problem.

Hi.
I am sorry for not responding to your first message but I didn't see it.
I firstly upgraded just my GPU and Monitor and then the whole rest so it is gonna be really hard to find out which part is faulty. I have also sold already my old parts and I don't have any other PC to test with. At first, I thought the faulty part was my GPU so it was on RMA, but it turned out to be good.
Greetings,
Oliwier.

Ztruker said:

Thanks Oliwier. Did you actually return the GPU for a replacement then?

By "rest of it" do you mean the motherboard, PSU, Hard drive (one or more), Network card, Memory, Mouse, Keyboard, Bluetooth, WiFi?

Are you overclocking? Arte you using memory XMP Profile? Please set everything to default, no OC and lets see what happens. If that works okay then you can start OC ion small steps till you find the settings that work for you.

Turn on Driver Verifier for non-Microsoft drivers a few at a time and let's see what that shows.

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

Hello.
The GPU was on RMA, but they sent it back and told me that nothing is wrong with it.
Yes, the rest of it is literally the whole rest of the hardware.
I am not overclocking anything, even my CPU that have ,,K" in the name. No, I am not using XMP and I have tested both - with ON and OFF, still BSODs.
I can't turn on the driver verifier. Every time I do it, my PC gets in an infinity loop and it doesn't turn on, no BSODs also so minidump files don't create. So I might be thinking the BSOD is caused by some drivers, but how can I check which one exactly?
Thanks and greetings,
Oliwier.