PSA: testing for and solving random freezes on Ryzen

Yeah kinda i guess.
Atleast start to disable all power saving features and go from there.

1 Like

Hello, sorry for bumping this thread up again, i am kinda lost and hope you guys can help me out here.

I experience freezes on a 2700X X370 Taichi system.

The system ran fine for weeks with 4*8GB G.Skill SniperX Digital Camouflage at 3200MHz. Then i went and installed one 8GB Kingston KSM24ES8/8ME ECC and everything was fine as well. After adding three more it went bad. I tried all three of the new ones with the one that ran fine for weeks and all froze (2 sticks total). I tested the RAM on said system and another X399 system for 2,5h each without any errors. I am on the newest recommended BIOS version 5.60 for that CPU and also tried bumping the DRAM voltage from 1.2 to 1.22. I could not find the power supply idle control option in my BIOS nor did i find anything saying C6 but i set 3 manual frequency states being 3600MHz, 3200MHz and 2200MHz. Is it sufficient for it not to draw too little power?

Can you point me to any other settings i could try? Is the RAM bad although it ran fine in memtest86?

In summary:

  • 32GB G.Skill SniperX @ 3200MHz (4 sticks) is fine
  • more than 8GB of Kingston ECC (1 stick) @ 2133/2400 freezes

Thanks in advance, cheers

Do you have the gear down mode option ? If so disable that.

You could run that kit as high as 1.35 without issue.

Thank you for the prompt reply! I will look into that tonight. Would you recommend running 24/7 at this voltage?

I might have read somewhere that later UEFI versions removed the Power Supply Idle Control option. If you really cannot find it where I described it should be, than you may have to downgrade your firmware. Unfortunately downgrading on this board is not officially supported and may be a huge pain in the ass to do without an external flash programmer.

@wendell

So i set the voltage to 1.335 which shows as 1.352 in the hardware monitor and also disabled gear down mode. Lets see how it plays, 3 days are to beat.

@methylzero

Thanks for your input, i hope though i don’t have to go doen that road.

That should be ok 24/7 for at least a few years.

I am fine with that, should it be stable now i’ll try to find the minimum stable voltage. Maybe even just the gear down mode was the culprit.

So far it looks good, day number 2.

On another X399 system i could find the settings advertised in the first post and i also disabled gear down mode there as well.

I am not entirely sure but i think since that this machine does not occassionally stall when running a mac VM anymore.

@wendell unfortunately it froze again, do you have some other settings to try?

You said you didn’t see an option for c6/7 stare? What about global c states? If you have that set it to disabled?

Also:
Advanced > AMD CBS > Zen Common Options > Power Supply Idle Control
This should be set to Typical Current Idle .

Do you not have this option??

No didn’t see that, global c states are disabled. I now put back in the old RAM which was working fine and now even that one freezes. It must be the board then.

What video card do you have? Ever since I upgraded my 1060 to a 5700xt I have been getting freeze every once in a while. I narrowed it down to the card, because once I switched back to my 1060 it quit happening.

It is a Radeon HD R5 230 (device-id: 0x6779). I am not sure if updating to 5.60 was a good idea. It was perfectly fine before and now i cannot get the original setup working without a freeze. That same graphics card was in there before. I guess i’ll try to reset the BIOS and if nothing helps get a new motherboard.

Also is the dude pulling power from wall or extension cable shared with other devices?

If you have a good PSU the extension cable should not matter. BTW a flaky PSU may also cause random freezes.

You can try using ZenStates to disable Package C6. I think it is more or less equivalent to the BIOS setting you cannot find. If that does not help you might have to jump though the hoops and downgrade to 4.xx BIOS version where you still have the BIOS option that helped me.

I got 2 Phanteks Revolt Pro 1000 connected together for redundancy. Connected to a UPS with a network switch, a router and a LCD display, together drawing about 140W and it is rated for 700W if i recall correctly. I will try ZenStates, is this fine?

P0 - Enabled - FID = 94 - DID = 8 - VID = 36 - Ratio = 37.00 - vCore = 1.21250
P1 - Enabled - FID = 80 - DID = 8 - VID = 59 - Ratio = 32.00 - vCore = 0.99375
P2 - Enabled - FID = 84 - DID = C - VID = 76 - Ratio = 22.00 - vCore = 0.81250
P3 - Disabled
P4 - Disabled
P5 - Disabled
P6 - Disabled
P7 - Disabled
C6 State - Package - Disabled
C6 State - Core - Disabled

It froze, i’ll return this motherboard, thanks for all the help!

So i couldn’t give up just yet.

I found that whenever i try to change some RAM settings, i have to manually set the frequency from auto to some value first. Even when i change it to the currently running speed (without touching any other settings and with setting every other setting possible to auto and to its current value), the board would reboot 3-4 times with an error code F9 before it successfully would boot up, no matter which kit i used. Frequency wise i tried 2133, 2400 and 3200 and got the same result every time.

When i set the frequency to auto, it boots up just fine the first time without errors. It is the fourth day up now with disabling C6 states with ZenStates and RAM frequency on auto.

I cannot recall having this issue with earlier BIOS versions, but then i am also not sure if i have ever changed the auto frequency.

Would you call it a day should it be stable now or would you consider a motherboard or BIOS broken if you cannot set any of the RAM settings yourself and get a replacement?

wow, after trying many many things, i believe this (OP) has fixed it for my 1700X and 2Q20 B450M Pro4 (i have an ancient PSU, a PC Power and Cooling 370 watt)

1 Like

Thread closed as it was outside the guidelines for thread revival. Please PM me or another moderator if you feel the thread was closed in error. See the FAQ for more information.

Feel free to create a new thread if you wish to continue this thread’s conversation.