i pretty much never got any BSOD in years and today it already happened twice, the error was "DPC WATCHDOG VIOLATION" both times
#BSOD
weak veldt
We would need the actual dump files, but because of how DPC crashes work we often don't get enough information from minidumps.
Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.
flint fern
weak veldt
I have a post here talking more about DPC crashes and what we usually need, but we'll cross that bridge when we get there. https://www.reddit.com/r/techsupport/comments/1g9y9qv/comment/ltbou7d/?utm_source=reddit&utm_medium=usertext&context=3&utm_name=techsupport
@flint fern Do you want me to look at the ones from October, May and January or do you know that those are not related?
flint fern
they are probably not related but go ahead
weak veldt
I only see one BSOD from the today, the second most recent is from the 24th of november.
flint fern
doesn't it overwrite if its from the same day or something?
weak veldt
Sorry, brainfart. It's January first
Wait, no, that's just the debugger using my timezone. I just see one from today
flint fern
idk it happened twice
flint fern
once was like 9 something pm december 31, the second was after midnight jan 1st
flint fern
dw
weak veldt
The first DPC crash doesn't really point to anything, but the interrupt used was Out Of Sync Processor. So it could suggest a CPU issue.
The second one was a process getting stuck, but the interesting point is what got stuck.
It was trying to process a WHEA event.
WHEA means a hardware issue with the CPU or a PCIe device.
If it didn't get stuck, you would likely have gotten a WHEA Uncorrectable Error BSOD instead.
B450 TOMAHAWK MAX, Ryzen 5 3600?
flint fern
ye
weak veldt
There have been some BIOS updates since your last updated.
So doing that could be worth a shot.
flint fern
im pretty sure I haven't updated bios since i bought this pc in like 2020 ☠️
weak veldt
I would want to see if you have any WHEA events in Event Viewer I could look at though.
You are on version 3.70 which isn't that out of date.
Oh, it begins on version 3.0
So it's not great.
Let's look at the WHEA events first though.
flint fern
idk if it matters but like around a year ago i had to change gpu because my old one had a lot of issues
weak veldt
We have two options. We can manually grab them from Event Viewer or on a different tech support server I am on, we made a tool that grabs a bunch of different diagnostic data, events being one of them.
The tool could find other possible causes as well, but I completely understand that running random software isn't appealing to a lot of people.
So it's completely up to you.
weak veldt
idk if it matters but like around a year ago i had to change gpu because my old ...
The WHEA events will hopefully tell us if it's a PCIe issue.
flint fern
The tool could find other possible causes as well, but I completely understand t...
yeah...
weak veldt
Ok, so manual?
Open Event Viewer → Windows Logs → System.
Click Filter Current Log on the right hand side.
In the Event Sources dropdown menu, find "WHEA-logger".
Click Ok to apply the filter.
flint fern
The WHEA events will hopefully tell us if it's a PCIe issue.
idk if it matters this too but the card had issues even when i plugged it into other computers
weak veldt
If you have any WHEA events, highlight them and save. Upload them in the chat.
weak veldt
idk if it matters this too but the card had issues even when i plugged it into o...
It could be the card, the event will give us more info. It's a pain in the ass to manually decode the error packet so it might take a few minutes and these often have less info than we would like.
But hopefully it will give us something specific.
If you even have WHEA events :P
weak veldt
Bleh
Then we don't really have any other suspects than the CPU or a PCIe device. And remember that most things on the motherboard uses PCIe. Audio, network, SATA controller, etc.
Though the Out of Sync Processor error makes me lean towards the CPU.
I would absolutely first test updating the BIOS, chipset driver and checking temps.
flint fern
i have a network card or whatever its called on my pcie but i don't use it
weak veldt
i have a network card or whatever its called on my pcie but i don't use it
I mean even the integrated LAN port. It uses PCIe.
But if you have stuff on PCIe you can just remove, then by all means, do that as a troubleshooting step.
weak veldt
https://www.amd.com/en/support/download/drivers.html
This is where you get the Chipset driver.
Sidenote: Do NOT get AMD's storage driver if the update tool asks. They suck ass.
Pain in the ass to make the PC work again as well if it starts crashing from those.
flint fern
is there a particular way i should update what i currently have installed, for example like uninstalling graphics drivers with DDU
weak veldt
Because it's a WHEA error it's rarely a driver issue. The CPU monitors itself and PCIe devices and when it finds an error, it reports it to the OS.
The sort of exception to that is the motherboard.
Chipset driver is really rarely a fix these days, but it's easy to do.
And DDU is a bit of a special case when it comes to driver reinstalls. It does the annoying ones like GPU driver and audio. The other drivers don't leave much trash lying around.
Though both AMD and Nvidia have a "clean install" option now. AMD's at least is pretty good.
flint fern
Though both AMD and Nvidia have a "clean install" option now. AMD's at least is ...
even for chipset drivers?
weak veldt
The Chipset driver has no removal tools. You just install the latest version.
flint fern
ah ok even if i already have one installed?
weak veldt
Yep
flint fern
aight
well now its like 3 am for me so ill do all this stuff tomorrow
do you mind if i ping you if this happens again?
weak veldt
That's fine.