#PC Hard Freezing Randomly (reseted CMOS but still freezing)

1 messages · Page 1 of 1 (latest)

rich summit
#

Hello, currently I have a problem with my PC and it’s freezing on me in the login screen, during boots and even in safe mode. I don’t know what’s wrong or how to fix it and I’m a bit scared on how to proceed.

rich summit
#

It’s freezing on the screen that shows my motherboard manufacturer when I turn on my PC too

kind umbra
#

More info will help others give more exact guidance. What kind of PC is this? Do you know how to get to the BIOS setup screen?

rich summit
#

Yes I do and its a PC I built during covid

#

I recently tried CMOS resetting via jumper but its still freezing and I have to force shut down by holding power button

#

When it blue screened I got the stop code DPC_WATCHDOG_VIOLATION

#

It seems to not freeze when I'm configurating BIOS, but when I turn it on it freezes on the motherboard manufacturer screen, I think its called splash screen but im not sure

#

PC Hard Freezing Randomly (reseted CMOS but still freezing)

rich summit
quasi tendon
rich summit
quasi tendon
#

Sure

rich summit
#

its still freezing unfortunately

quasi tendon
#

@rich summit And it freezes on DRAM every time?

#

The debug LEDs

rich summit
#

i checked again and i didnt have it fully seated i thought it was seated because the clips went down, anyway the new information is that i tested both ram sticks and it froze on both

quasi tendon
#

@rich summit Ok, does it freeze if you just let it sit in the BIOS?

rich summit
#

it hasnt so far but for some reason its more likely to freeze in safe mode

quasi tendon
#

@rich summit So you are able to boot and be in Windows at least for a while now?

#

If yes, let's see if there are any clues in the dump files. 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.

#

Dump files are crash logs from the BSODs.

rich summit
#

ok ill try doing that

#

just minidump or minidumps too?

quasi tendon
#

Windows randomly uses one name or the other, it's the exact same thing. No idea why.

rich summit
#

i have both so ill just give you both

quasi tendon
#

The Minidumps one is from May and 2024

#

So I'll skip those

#

@rich summit The dump files don't point to anything. So we have two possibilities here (Sorry if this is going to be a long and confusing read)

#

  1. You are getting DPC_Watchdog_Violation crashes. This crash type means an error in one of the DPC queues which you can think of as the execution queue of the CPU. Each thread has its own queue (With a 5900x that means 24 queues) and with minidumps, we can only check the queue Windows shows us because the other queues are removed. And Windows shows us the wrong queue quite often. So it could just be Windows being stupid and showing us the wrong queue.

  2. We have seen a lot of voltage issues with 5000 series CPUs and the higher end ones like yours fairly often get DPC crashes when the CPU doesn't like the voltage.

#

We can try some voltage tweaks to see if we can get it to behave.

  • 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. So the second one is the most likely to help here.

#

@rich summit What makes this more uncertain though is the freezing.

#

I wouldn't expect freezing from this issue

rich summit
#

is this setting in bios or on the physical motherboard, sorry im not that tech savvy

#

i’m thinking these?

quasi tendon
#

@rich summit BIOS

#

VDDCR CPU and SOC

rich summit
#

so i should change it from auto to offset and enter the values 1.3v for cpu voltage and 1.1v for soc voltage?

rich summit
#

ok so i did the manual one and ran sfc /scannow and i guess it repaired some files that were damaged/corrupted