Occasional crashes during reboots following the 5800X3D upgrade

C

CarmellaYT
Junior Member

13

12-17-2022, 05:35 AM

#1

Seeking suggestions on alternative approaches to address this issue. Since I moved from 3700X to 5800X3D three months ago, I've been experiencing rare BSODs with error code DPC_WATCHDOG_VIOLATION (0x00000133). These crashes only happen under light usage—like streaming or browsing—and not during full operation or any moderate-to-heavy tasks (games tested with Prime95, OCCT, AIDA64). Initially, I suspected the problem was related to my PBO curve or RAM timings, but neither seems responsible—the crashes persist even when BIOS is set to "Enabled" and RAM runs at 2133 MHz with auto-timing. I've also reset BIOS settings to defaults and installed a fresh Windows 11 on a separate drive with minimal apps (GPU, chipset, audio drivers, Steam, Discord), which also failed with the same error. My system specs: ASRock X570 Phantom Gaming 4 (BIOS L5.01 - AGESA V2 1.2.0.8), 32GB RAM at 3600 MHz CL18, RTX 3070 Ti, Corsair RM550x. Could the CPU be faulty or is there another solution I should try? OS: Windows 11 22H2 x64, system age about three years since upgrade, with the oldest part being the PSU, which is seven years old. Installation was about six months ago.

N

nathanspike
Member

171

12-17-2022, 07:12 AM

#2

T

taeranghee
Member

148

01-03-2023, 04:42 AM

#3

I believe you're referring to Clock_Watchdog versus DPC_Watchdog. Please send the dump files.

L

lololPower
Junior Member

32

01-04-2023, 11:08 PM

#4

Attached are the three latest dumps.
File names: 061823-6453-01.dmp, 060223-5140-01.dmp, 060923-5812-01.dmp

G

GaZeVII
Member

141

01-09-2023, 10:42 AM

#5

Are you using an Insider version of Windows? I'm encountering symbol errors and can't locate the right symbols on Microsoft's servers. Symbols essentially act like a dictionary for drivers, helping the debugger understand commands. It's typical for Insider builds to lack complete symbols since they're still being finalized. After major Windows updates (large patches or new releases), there may be periods where symbols aren't updated yet. TL;DR: I can't debug these files because the required files aren't available on Microsoft's servers.

T

thingul
Member

136

01-11-2023, 12:05 AM

#6

It's a lighter version of Windows 11, built around the 22H2 update, not an internal release. That might explain it.

D

DaNiggaSWAG
Senior Member

539

01-18-2023, 05:14 PM

#7

Yes, you can try using the Windows Media Creation Tool to create a fresh installation USB and see if the full Windows 11 setup resolves the problem.

U

Ultraviolence
Junior Member

6

01-25-2023, 04:37 PM

#8

Also confirmed it wasn't changed, just verified the test.

J

Jesuss_
Member

154

01-25-2023, 08:01 PM

#9

Retrieve the dump file from the installation.

U

Usnia
Junior Member

22

01-25-2023, 10:59 PM

#10

I’ll need to send back a dump file in a few days, as I’ve already removed that Windows instance. I wasn’t sure the dump would be helpful at first. Changing the memory dump settings to kernel/complete/automatic/active might make it more useful.