#DPC WATCHDOG WATCHDOG VIOLATION + INTERMITTENT REBOOTING

1 messages · Page 1 of 1 (latest)

potent raven
#

SPECS:
AMD Ryzen 7 5800
Nvidia Rtx 3060
Asus B550-F mobo
32 gigs of ram. Unsure which kind off the top of my head but if it's important just
500 gb ssd used as root drive that i can't remember for the life of me. Its probably important and I'll update when I have the time

Issue:
I've been getting BSODs for most of today. I think what could have happened is one of two things. Either I updated to the most recent Nvidia driver, or I removed power without properly shutting down (the latter I'm suspecting is the straw that broke the camels back)

This pc was built around 2020-2021.

Steps I've taken so far in order:

  • reset pc using cloud save, installed Nvidia control pannel didn't fix
  • boot into safe mode. Installed DDU and cleared pc of Nvidia drivers. Booted normally and installed most recent Nvidia game ready driver. Screen goes black and does come back as an update normally does.
    *reset computer through push button on case. It turns on normally. But now resets after 10-15 minutes of running.
  • boot into safe mode run ddu and install secondmost recent driver version. Same issue.
  • do the same again but installed a build from October 2024. Still not working
  • open case. Clear out dust. Gpu does not feel warm to the touch. Unsure if there is a hardware issue at least gpu wise.

And that's all I've had so far? I've tried looking into the event logs and didn't really understand much. I did look into some other posts and saw the minidump files are important. Hopefully this can help in the troubleshooting process?

Any help is greatly needed/appreciated 🙏

#

One thing about the resets:

They aren't happening through the OS. And it's not acting like the screen freeze to bsod issue i was having. What will happen is.the screen will go black after a few minutes of runtime. And then the bios starts to boot and then the OS begins to boot.

sick arch
#

Use 7Zip to upload C:\Windows\Minidump on here. It's a log file that is created every time you get a BSOD. That might be able to tell me what exactly is causing the problem.

There's a few things you can do depending on what the Minidump says, but ultimately you might have to fresh install Windows.

potent raven
sick arch
#

I downloaded the Minidump and I'm planning on looking at it in a VM later, but I have to go to work, I won't be able to look at this until later today.

potent raven
#

All fine! Really appreciate you're doing it in the first place

sick arch
#

While I have a minute here; One thing I would try is to boot into safe mode with command prompt and run "sfc /scannow" in a Windows terminal.

woeful galleon
#

@potent raven You only had one dump file?

potent raven
#

I'm at work at the moment but I can check in 8 hours

sick arch
#

I think he's asking cause usually one is made every time you BSOD.

woeful galleon
#

@potent raven This was a DPC_Watchdog_Violation as you know. 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.

That being said, this points to the Avast antivirus.

#

If all of them point to Avast, we can be pretty certain that it's the culprit.

potent raven
#

I will try this when I get home. Thank you!

sick arch
#

I would still run sfc /scannow in a terminal as well, this will (hopefully) fix any issues related directly to Windows on your system as well.

potent raven
potent raven
#

Power cycling might still be an issue? Video cuts out after about 20 minutes of runtime. No AV signal being output. Unsure if it's BSOD or anything like it.

#

MOBO is stuck at the DRAM part of boot cycle unsure if this means my memory is probably saying goodbye?

#

This gives me a better idea of what could be happening. I bet removing it from power gave it some sort of issue in the hardware.

woeful galleon
woeful galleon
potent raven
#

Really really really hoping that's all

#

Ok so

#

Removing the one stick makes it post again

#

But it's still rebooting

#

Randomly

#

Event log had this to say

potent raven
#

Seems like I'm getting a WHEA logger event 18

woeful galleon
#

@potent raven These events are a bit of a pain in the ass to decode, you have to decode the huge RawData block manually.

#

It looks like the CPU to me, if I didn't fuck anything up.

#

So the question is, how likely is it that one stick of RAM died at the same time as the CPU.

#

Or could it be the motherboard.

#

I guess you could check if any of the CPU pins got broken/bent/burnt.

#

@potent raven And just to make it clear, the WHEA event is from the CPU ordering the reboot/shutdown because of an issue it detected.

potent raven
#

I'll probably try to update bios first

#

But it's quite literally rebooting in the matter of like 5 ish minutes with the ram removal

gleaming gyro
potent raven
potent raven
#

So. I don't believe it could be the mobo. But I also could be totally wrong

woeful galleon