I sold a computer to this guy and i made sure to run all the tests i usually run for all my PCs and it ran fine with no crashes or errors. But when he tries to play games he gets the DPC_WATCHDOG_VIOLATION error. I looked it up online and it said its a driver issue (or at least most of the forums said fixing the drivers was the solution) so I had him just reinstall windows and redo all the driver downloads. But hes still getting the errors while he plays. Does anybody know of any other things that could cause it? the PC is a 3700X paired with a 3070.
#PC Getting Watching Error Blue Screen
full cargo
tender grove
I sold a computer to this guy and i made sure to run all the tests i usually run...
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. To know which driver is doing it, you would open the dump file from the BSOD in a debugger.
These are a bit extra annoying as you often can't debug them with minidumps, you often have to manually check each DPC queue of several kernel dumps and see which driver is loaded in all of them. With minidumps, Windows often discards the other threads, only keeping the thread it thinks the issue happened in. And it's wrong quite often.
This is annoying because Windows only saves one kernel dump because they can be huge. So you have to move it out after each crash and once you have 2-4, you can compare them.
Which also requires knowing how to use the debugger and read these things
full cargo
Which also requires knowing how to use the debugger and read these things
what if i have no idea what each error means
should i do what you said and open it in the debugger and try my best?
search up each one online probably
tender grove
@full cargo If the person can send you the dump files, I can have a look
Instructions: 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.
full cargo
Instructions: Go to C:\Windows\Minidump and check if you have any minidump files...
ill ping you when they get back home from work and i have them follow these steps
when you say copy like just right click the minidump file and select copy, then go to the downloads folder and right click and paste?
tender grove
No
tender grove
when you say copy like just right click the minidump file and select copy, then ...
Windows is really weird with stuff inside the Windows folder. If you copy each file like that, it will often create a shortcut instead of a copy
So from the Windows folder, right click and copy on the actual Minidump folder
full cargo
So from the Windows folder, right click and copy on the actual Minidump folder
i dont have a minidump on my pc i assume he will from what u said
but like that right
tender grove
It gets created when you get a dump file, but yes, like that
So hopefully has has gotten some dump files
full cargo
he hasnt responded isk whats up 😭
full cargo
So hopefully has has gotten some dump files
he just got back to me and said that he moved it to a room with better wifi (hes been playing in a room with really spotty and crapy wifi) and the problem hasnt been happening? do you think that could be a reason for this or is that an outlier
the pc has one of those asus cards im not sure which model since he got it himself
tender grove
he just got back to me and said that he moved it to a room with better wifi (hes...
Or that something got loose in transport. So moving the PC made it move around and randomly get better contact.
I haven't seen WiFi BSOD from bad reception before
full cargo
interesting
well hes been fine for now so
i might get him to still send the minidump if he has it
tender grove
@full cargo I have seen lots of new features on routers cause BSODs on older WiFi cards so it could be some new feature for re-connecting if it loses connection that causes the BSOD.
Oh, there is also some network cards that don't like that both bands are on the same SSID. Like 5GHz and 2.4GHz having the same name so it's supposed to automatically pick the best one, some older network cards can BSOD from that.
So if it lost connection to 5GHz, and tries to connect to the 2.4Ghz which has longer range → BSOD
full cargo
ah ok