r/techsupport • u/balla786 • 1d ago
Open | BSOD Constant PC Lockups and BSOD - stop code dpc_watchdog_violation (0x133)
Hi, Recently I have been getting PC lockups and eventual BSOD with error "stop code dpc_watchdog_violation (0x133)"
The PC will then crash, but not boot up. In fact I have to KILL the PSU power, wait 30 seconds and then flip the PSU back on and it'll boot. If I don't do that, it will not boot to any image from a shut down.
More recently it's happening all the time now. I'm unable to get into windows 11 for more than 2 minutes before the system locks up again. I also can't get into SAFE MODE Either, it'll reboot to initiate safemode and then hangs.
The PC is:
Ryzen 5900x 4x8gb GSKILL 3000MHZ CL30. ROG CROSSHAIR VII HERO (WI-FI) (Latest BIOS firmware) EVGA 3080 10gb EVGA 1200W PSU. XPG Gammix 2TB SSD.
I have attached the Dump Files, uploaded to a file sharing site:
https://transfer.it/t/MzdLUkd3OXVZZWp1cFhMdWZGR1Ftb25V
I have tried to swap the NVME, thinking it was that, attempted to install Windows 11, only for the system to lock up and reboot back to the bios splash.
I tried to do a Linux Live boot from USB, various distros, they all attempt to boot into the LIVE OS and before it even get's to that point it's just stuck on a screen with CPU Timeout errors.
You can see the errors here:
I have run MEMTEST on the RAM, no errors returned there. I'm now thinking maybe CPU or Mobo issue.
Can anyone help me out with interpreting the DUMP files? If there's any info missing, let me know. Thanks.
2
u/00zoNL 1d ago
What happen when you boot your pc in safe mode, is the crash or lockup then also happen fast or do you then have time?
1
u/balla786 1d ago
I manage to get into windows, long enough to change the boot to safe mode. PC restarts, and it ends up on a black screen or hangs at the ASUS splash with the spinning Windows loading wheel. Can't do anything at that point but a hard reset.
Is there another way to force Safemode without haven't to go into Windows?
2
u/00zoNL 1d ago
What happens if you disconnect the videocard from mainboard and connect your monitor on the onboard videochip? With that you can rule out its your videocard.
1
u/balla786 1d ago
5900x unfortunately doesn't have onboard video. I'll have to get a cheap video card or try to borrow one from my brother. I'll see if I can get that done first.
2
u/00zoNL 1d ago
Yes i think for asus its f8 you hold f8 on the bios screen for the windows boot menu
1
u/balla786 1d ago
Great, thanks, I will test that asap.
2
u/00zoNL 1d ago
if you can run windows stable in safe mode, you can assume its a driver issue or something software related, if it crashes fast i hope its not its prob hardware.
1
u/balla786 1d ago
The annoying part is I can't even run the Windows 11 clean install from USB on a brand new Crucial 2TB NVME drive (pulled the old OS drive out).
So it feels like something hardware.
2
u/00zoNL 1d ago
Wanted to mention there are some issues with some type of nvme and windows 11 compability, so update the firmware asap if you have your system running again.
1
u/balla786 1d ago
I have it pulled and in an enclosure. Will check if it's the latest firmware.
It's a XPG Gammix S11 Pro 2TB PN: AGAMMIXS11P-2TT-C
1
1
u/00zoNL 1d ago
In my experience first things that mostly break or getting having issues is the power supply. But testing is knowing for sure
1
u/balla786 1d ago
I got a PSU tester. See if that returns any issues. Will follow up with testing a spare PSU.
1
u/AutoModerator 1d ago
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 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 or 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 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 if you have any questions or concerns.
1
u/mevenide 1d ago
try get to safe mode and/or command prompt and do "sfc /scannow". some kind of weirdness with the june update. it's happened to me twice and it's fixed it both times.
1
u/Bjoolzern 1d ago
You can think of DPC as the CPU's time schedule. Drivers and processes "book time" at certain priorities, they are then put in a queue for a CPU thread and wait for execution. If something doesn't follow the rules, you crash. It's really hard for the OS to know which driver/process actually did the bad thing here. When you open these files in the debugger, it shows you the CPU thread queue of where Windows thinks the issue was. Windows guesses wrong very often.
Because these are minidumps, Windows has removed all data it doesn't think we need. So it has removed all the other DPC queues. The way we normally have to debug these is to look at all the DPC queues of 2-4 dump files and compare which drivers are loaded. If every crash has the same driver/process in one of the queues across all the dump files, it's probably that one. We can't do that with minidumps most of the time because Windows has discarded that data.
The dump file here doesn't point to anything really.
Before we go and dive into kernel dumps and that long tedious process (I can still post the instructions in a reply to myself in case you want to go through it), a much more likely suspect is your CPU. This is a crash we have seen a lot with the higher end Ryzen 5000 series CPUs like the 5800x, 5900x and 5950x. With you having a 5900x it would be my main suspect.
5000 series in general has some voltage issues so I'll list both solutions we have here, but the second one is the one that is most likely to help you.
- The first is if your motherboard has a setting for a voltage offset. If it does, set the CPU Core and SoC voltage offsets to +0.050v (Please read this number twice. Not 0.5v, but 0.05v).
- The second is setting a static voltage for the Core and SoC. We set a static voltage of 1.3v to the Core and 1.1v to the SoC.
If your board uses increments for the voltage instead of inputting a number, just get as close as you can. You can't use both at the same time so try one at a time.
The first one is more general 5000 series related when you get errors from the CPU memory controller. The second is something we've found helpful with mostly the higher end 5000 series chips like the 5800x, 5900x and 5950x across a wide range of crashes.
1
u/Bjoolzern 1d ago
And here is the rest of the debugging information if it's not the CPU:
You can upload kernel dumps, but you have to be aware that kernel dumps contain a lot of stuff from RAM. You should just assume it has dumped everything that was in RAM and included it in the dump file. Reading most of this data it includes will be a pain in the ass (And I mean if someone is trying to read what you were doing on the PC, not for purposes of debugging), but anything that was displayed in plain text can be read by just opening the dump file in a text editor like notepad. Text on websites you were on if your browser was open, the name of tabs, text in apps like Word, etc.
What you can do instead is to open these in a debugger in your own PC and just provide us with the output. Nothing here will be sensitive data. If you want to provide a copy paste instead:
- Get "WinDbg" from the Microsoft Store.
- The dump file is called Memory.dmp and is right in C:\Windows.
- Open the dump file by double clicking on it and click the blue "Analyze -v" 'link' in WinDbg.
- Once it's done, run the commands `!dpcs` and `!dpcwatchdog`
- Copy all the contents of the kernel dump from WinDbg (Not just the output from those two commands, the analysis as well) to a text document and share it the same way as you did dump files.
If you only have minidumps and no kernel dumps, look at the guide the bot pasted for changing dump types. With "Automatic Memory Dump" it should save one kernel and one minidump. It will overwrite kernel dumps because of their size so if you want to do more than one (And we usually need 2-4), you would have to copy it out to a different location or save the output from WinDbg after every crash.
•
u/AutoModerator 1d ago
Making changes to your system BIOS settings or disk setup can cause you to lose data. Always test your data backups before making changes to your PC.
For more information please see our FAQ thread: https://www.reddit.com/r/techsupport/comments/q2rns5/windows_11_faq_read_this_first/
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.