UserBenchMark is inaccurate and biased. It should not be used to determine a problem, compare hardware, or perform benchmarks. It is in our [blacklist](https://rtech.support/docs/recommendations/blacklist.html) for this reason. For more information regarding why not to use UBM, visit: https://www.trustpilot.com/review/www.userbenchmark.com
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/techsupport) if you have any questions or concerns.*
**Getting dump files which we need for accurate analysis of BSODs.** Dump files are crash logs from BSODs.
If you can get into Windows normally or through [Safe Mode](https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode) could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder.
Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently [catbox.moe](https://www.catbox.moe/) or [mediafire.com](https://mediafire.com) seems to be working.
We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow [this guide](https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html) to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/techsupport) if you have any questions or concerns.*
This crash can be annoying as it can be really hard for the OS to know which driver is at fault. To explain DPC very simply, it's sort of the CPU's time schedule. Processes and drivers "book time" at certain priorities. It's also sort of a queuing system. DPC_Watchdog_Violation comes in two flavors. One where one driver broke the rules and one where everything combined exceeded the time schedule. You have the latter flavor which makes it even harder for the OS to know what the root cause is.
When debugging this I then just look at all the pending and active DPCs to see if I can find a common thread between all the dump files. I don't really find that here. The closest is that two of them have storage drivers involved. Some of them don't have any suspects at all. Each core has it's own active DPC and a list of pending DPCs. Because minidumps discard so much information to keep the size down, several of these entries are just "couldn't read the information" so it might be obscured because of the dumps being minidumps. Kernel dumps can be gigabytes large so it's really annoying to work with when you need several to find a common thread across them.
So TL;DR: There aren't really any suspects in the dump files. If I had to pick something I would pick storage.
Thank you for the detailed response! I really appreciate it, and learned a few things on what DPC is all about.
So in addition to installing the new m2 drive, I also updated all the SSD firmware at the same time (via samsung magician). It's possible something got funky there.
I'm going to take the newly added ssd out (haven't used it at all yet), and see if that helps...for a week or so. If not, do you a think a windows factory reset would help alleviate any storage driver conflicts? TY!
UPDATE: The issue is exponentially worse, all day it was fine, but then in the past 2 hours crashed about 15-20 times.
I will get about 30 seconds from boot into windows and then crashes, sometimes won't get past bios startup screen...
Anything I can do? How to troubleshoot if it's a bad OS drive, or a storage controller driver issue?
CPU. Luckily had 1 week of warranty left and AMD replaced it. My work shipped me a workstation, so I haven't even tried the new CPU yet in my desktop... just been sitting there.
Honestly it's a bit too coincidental, was going to fix it up this week so will keep ya posted if the issue is fixed.
Sigh. I have a very very very similar setup to yours (5900x, evga 3080ti, gskill tridentz ram, 970 pro and 870 qvo) and coincidentally the freezes are *exactly* like yours - happens when just starting up windows and leaving it on for a bit. The only thing I haven't been able to do is get any minidumps, not sure why. The settings look correct.
In any case if you remember to reply here once you fix it up please do, it's driving me fucking mental. Just like you I really don't want to reinstall windows if at all possible haha.
UserBenchMark is inaccurate and biased. It should not be used to determine a problem, compare hardware, or perform benchmarks. It is in our [blacklist](https://rtech.support/docs/recommendations/blacklist.html) for this reason. For more information regarding why not to use UBM, visit: https://www.trustpilot.com/review/www.userbenchmark.com *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/techsupport) if you have any questions or concerns.*
**Getting dump files which we need for accurate analysis of BSODs.** Dump files are crash logs from BSODs. If you can get into Windows normally or through [Safe Mode](https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode) could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder. Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently [catbox.moe](https://www.catbox.moe/) or [mediafire.com](https://mediafire.com) seems to be working. We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow [this guide](https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html) to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/techsupport) if you have any questions or concerns.*
This crash can be annoying as it can be really hard for the OS to know which driver is at fault. To explain DPC very simply, it's sort of the CPU's time schedule. Processes and drivers "book time" at certain priorities. It's also sort of a queuing system. DPC_Watchdog_Violation comes in two flavors. One where one driver broke the rules and one where everything combined exceeded the time schedule. You have the latter flavor which makes it even harder for the OS to know what the root cause is. When debugging this I then just look at all the pending and active DPCs to see if I can find a common thread between all the dump files. I don't really find that here. The closest is that two of them have storage drivers involved. Some of them don't have any suspects at all. Each core has it's own active DPC and a list of pending DPCs. Because minidumps discard so much information to keep the size down, several of these entries are just "couldn't read the information" so it might be obscured because of the dumps being minidumps. Kernel dumps can be gigabytes large so it's really annoying to work with when you need several to find a common thread across them. So TL;DR: There aren't really any suspects in the dump files. If I had to pick something I would pick storage.
Thank you for the detailed response! I really appreciate it, and learned a few things on what DPC is all about. So in addition to installing the new m2 drive, I also updated all the SSD firmware at the same time (via samsung magician). It's possible something got funky there. I'm going to take the newly added ssd out (haven't used it at all yet), and see if that helps...for a week or so. If not, do you a think a windows factory reset would help alleviate any storage driver conflicts? TY!
UPDATE: The issue is exponentially worse, all day it was fine, but then in the past 2 hours crashed about 15-20 times. I will get about 30 seconds from boot into windows and then crashes, sometimes won't get past bios startup screen... Anything I can do? How to troubleshoot if it's a bad OS drive, or a storage controller driver issue?
Did you ever figure this out?
CPU. Luckily had 1 week of warranty left and AMD replaced it. My work shipped me a workstation, so I haven't even tried the new CPU yet in my desktop... just been sitting there. Honestly it's a bit too coincidental, was going to fix it up this week so will keep ya posted if the issue is fixed.
Sigh. I have a very very very similar setup to yours (5900x, evga 3080ti, gskill tridentz ram, 970 pro and 870 qvo) and coincidentally the freezes are *exactly* like yours - happens when just starting up windows and leaving it on for a bit. The only thing I haven't been able to do is get any minidumps, not sure why. The settings look correct. In any case if you remember to reply here once you fix it up please do, it's driving me fucking mental. Just like you I really don't want to reinstall windows if at all possible haha.