So I have ran into some random freezing issues, when setting up a Ryzen 1700X system for server-like (headless, unattended, ECC RAM, no OC) 24/7/365 operation. Not good at all.
I have written a small stress testing utility that can reproduce this issue quite reliably in less than 48 hours. It consists a copy of the Intel Linpack benchmark utility, that has been modified to run on AMD CPUs (just hexedited the binary and replaced some strings) and a small bash script that consists of a loop alternating between idling, single core load and 8 core load. You can download it HERE
This will stress create a very large number of transitions between idle, single core boost and all core clocks and voltages, thus stressing the reliability of power management/power saving features on the CPU and the motherboard. In my case (Asrock x370 Taichi) the test reproducibly induced a complete system lockup in less then 48h.
If you are also affected by this issue, the solution that worked for me is a UEFI setting: Advanced > AMD CBS > Zen Common Options > Power Supply Idle Control
This should be set to Typical Current Idle. The default/auto setting seems to be Low Current Idle, that saves an additional couple of watts when completely idle, but also seems to cause some sort of power glitching, that results in occasional freezes. From what I can tell, this setting disables Package C6 state, while leaving all other power saving features such as Core C6 state enabled (you may have to update your UEFI for this setting to appear, for the x370 Taichi I would recommend UEFI version 4.40, the later versions may or may not have regressions)
I doubt it is “always” a faulty motherboard. I have a system that would reliably freeze, but after applying the PSIC tweak it does not, it has spent at least 8 days completely idle without issues.
Not conclusive of course, but one hell of an improvement.
Lol? Aren’t we talking about system crashes at “idle” Only? System crashes at idle are always due to faulty motherboards and has been confirmed by manufacturers.
Memory errors, drivers mostly crashes during stress not idle.
Let’s not beat around the bush. Everyone who has had this “idle crash” problem has fixed it by changing the motherboard either by RMA or just buying a different board. It’s a flaw with faulty voltage regulators.
People should stop wasting time on researching and just RMA their boards.
This is the second thread I have seen where you completely disregarded all given information and proclaim faulty mother boards with no evidence.
It may have been a problem for you, you are not everyone. You also state this is an idle problem, where the OP literally states “Stress Test” which cycles between idle, single core load and all core load so you cannot possibly put it down to idle problems with out considering the other two.
I have no problem with you providing information and helping out but blindly shouting the same thing will get you no where.
Edit: insulting people is also not helpful to anyone.
And do you mean a shop called Gigabyte, or the company gigabyte because as far as I know they do not have physical stores.
Lmao. So you deleted my entire post consisting of all the evidence I provided because of some insults and now you say I provided no evidence? HAHAHA… level 1 tech forum for sure.
Yes Gigabyte has physical stores in many Asian countries and they handle RMA directly. and even Asrock has this problem.
Did you read what OP actually wrote??
I’ll quote him: "This should be set to Typical Current Idle. The default/auto setting seems to be Low Current Idle, that saves an additional couple of watts when completely idle, but also seems to cause some sort of power glitching, that results in occasional freezes. From what I can tell, this setting disables Package C6 state, while leaving all other power saving features such as Core C6 state enabled (you may have to update your UEFI for this setting to appear, for the x370 Taichi I would recommend UEFI version 4.40, the later versions may or may not have regressions)
The problem OP is having is the same as idle crash. Jeez people just do a google search!!! ASROCK has this problem. lemme do it for you : http://bfy.tw/L6LR
I’m just stating that future people who have crashes in idle with ryzen should just go and RMA their boards. There can’t be any other cause for crashes at idle except faulty mobo.
It really isn’t always a defective motherboard. If you have an asrock ab350m pro4 then yes, it’s probably the motherboard. but there are freezing issues that can be resolved with some settings changes and updates. My dad’s 2400g was having issues until I updated the bios, set the recommended change in the op, and updated the video drivers.
It is always a faulty motherboard if it crashes on idle at default settings. The issue isn’t limited to ab350m but a lot of Asrock b350,x370,asus b350 prime and gigabyte b450 ds3h. The power supply idle control is just a workaround which doesn’t work 80% of the time for most people. just check google. I can’t spoon feed you guys anymore.
You claim that its a faulty board with some articles about certain issues.
Which is a good thing, and you might be right.
However you can’t say for sure, because there are gazillion other possibilities that,
could be the root cause of the issue.
I would add at least one crash at idle for me on Ryzen was on a Linux box with a bad power supply. Actually the power supply was totally fine but not designed for low idle current.
It was resolved with a bios update that offered a “typical” standby current option. This increased power draw by 5 watts. It took a few months to work this out tho. I disabled c states and manually set the speed and voltage before the bios updates as a work around
The typical current at idle is still a non default option, though. Weirdly. So a few users here have reported crashes fixed after this. One guy I helped said that this only happened about every 3 days, interestingly.
I have read reports of some asrock boards having a buggy fix … a kill a watt for measuring current usage helps for making sure you are actually getting higher power usage at idle. It’s easy to spot with a kill a watt.
Ryzen idle crash is always a motherboard problem. Period. There are no other possibilities. I have researched for a month when it happened to me and the only way people solved is by changing the motherboard. It even crashes in BIOS,linux,windows and everything. It’s definitely a mobo problem IF YOU HAVE CRASHES AT IDLE. That’s all.
I’m done with this thread and forum. People here have no idea about how the issue is so much widespread but still they sight at other problems but NO ONE in this thread has been able to provide any other sources about other ideas about the “idle crash”. All I hear people say is “there maybe other possibilities” but can’t you say what other component can cause CRASHES ONLY AT IDLE AND NOT DURING STRESS TEST?? Lol this thread is so unlike level 1 techs. i’m done. removing notifications. I don’t want to be part of an incompetent,adamant and ignorant community.
If it crashes while idling in the bios that’s not a power management issue. I think the others in this thread think when you say idle you mean entering low power states.
Bioses generally don’t use the idle states of the CPU. Idle refers to a power management state not “not doing anything” most bioses run at a conservative clock profile in case an unstable oc would corrupt your bios settings btw.
So you can literally read wenells post, and I would wager he knows more about all of this than any of us, and you still refuse to accept you are wrong.