Ask Your Question

Ryzen build locks up or freezes.

asked 2018-08-03 10:21:27 -0500

rajiihammr gravatar image

updated 2018-08-06 10:21:28 -0500

I've been running Fedora 28 with a Ryzen 3 1300x and it often freezes and is unresponsive within 1 week or sooner. A reset is required. I've experimented with Manjaro and haven't had the same problem occur. However, a build of Majaro that I ran in April for more than one month may have frozen too(vague memory). Point, Fedora builds lockup reliably and quite quickly. Anyone have clues here?

update: My Manjaro build SSD froze after nearly two weeks. Restarted the Fedora 28 SSD and it is freezing nearly daily. Whoa.

edit retag flag offensive close merge delete



Have you checked for recent firmware updates to the Motherboard?
You may also want to compare kernel versions of Manjaro and Fedora.

After a freeze, are you able to get kernel logs from the previous boot using journalctl -k -b -1?

m.p.kingsley gravatar imagem.p.kingsley ( 2018-08-03 11:13:16 -0500 )edit

Yes, motherboard firmware is latest, the Fedora kernel is newer than Manjaro but not by much. And no, I can't access the logs during a freeze, even if I knew what to look for( I'm not that sophisticated) Will investigate. See the update on post. edit: I ran your command, and am very much in the dark. RH

rajiihammr gravatar imagerajiihammr ( 2018-08-06 10:19:32 -0500 )edit

Do you get any output from the command? If not, what is the output of journalctl -p 3 -r -n 15 -b -1 after you reset your computer? This command looks at the last 15 lines of error (or higher) log entries from the last boot. (you can see other options for journalctl from )

m.p.kingsley gravatar imagem.p.kingsley ( 2018-08-06 12:42:48 -0500 )edit

Here is the output from your latest command:

Tue 2018-06-05 10:33:57 CDT, end at Mon 2018-08-06 16:04:24 CDT. -- Aug 05 12:02:11 localhost.localdomain kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled

Mean anything to you?


rajiihammr gravatar imagerajiihammr ( 2018-08-06 16:06:54 -0500 )edit

I ran across a Arch wiki post dealing with the sp5100-tco ---suggested creating a /etc/modprobe.d/sp5100-tco.conf and blacklist.. ...will monitor.

rajiihammr gravatar imagerajiihammr ( 2018-08-07 13:18:45 -0500 )edit

5 Answers

Sort by ยป oldest newest most voted

answered 2018-08-20 19:50:50 -0500

ed209 gravatar image

Ryzen 1300x i.e. old generation. I'm afraid it's hardware. See the discussion in

the solution was asking a cpu replacement to AMD. Usually the one built after week 25 i.e. starting from the code 1725 (that is, 25th week of 2017) are OK, but it's not an absolute rule. For a picture see

See also

If that is the case, no bios or firmware upgrade will fix it. Good luck.

edit flag offensive delete link more


I suspect the CPU, I have for some time. I'll look at that date of build tomorrow... Is AMD forthcoming with cpu replacements? I've swapped out every other part. This is good information to read. Thanks.

rajiihammr gravatar imagerajiihammr ( 2018-08-20 21:46:21 -0500 )edit

I've sent a request for service to AMD...I hope this is the fix...Thanks ed. RH

rajiihammr gravatar imagerajiihammr ( 2018-08-20 23:31:29 -0500 )edit

I received the new 1300x cpu Sept. 6, (build code 1745, though listed as 1741 on packaging). Disappointed that it locked/froze the first day, and then one week later. I'm at a lose to explain, could power supply be the culprit? RH

rajiihammr gravatar imagerajiihammr ( 2018-09-13 08:49:19 -0500 )edit

A new replacement CPU has not solved the problem. I've try disabling BIOS power settings to no avail. Out of frustration I've order an Athlon 200GE that will give me less processing power- I know Ryzen 1300x is nothing to brag about- but hopefully the 200GE will solve the freezing problem. All I want and expect is a computer that runs.

addendum: It appears the Athlon 200GE behaves in the same way, it too froze within 2hrs. May shop for Intel bases MB and CPU. Truly frustrated. 11/10/18

rajiihammr gravatar imagerajiihammr ( 2018-11-03 15:08:22 -0500 )edit

answered 2018-08-27 10:20:10 -0500

rajiihammr gravatar image

If the early Ryzen cpu's had a fault, replacing the cpu is the fix as suggested by 'ed209' in comments. I followed the email for a 'online service request'. AMD quickly responded, and I have sent them my 1300x CPU. I'm hoping this is the fix. (I've said that before, but I'm confident this will do the trick.)

edit flag offensive delete link more


AMD is sending a replacement CPU, I thank 'ed209' once again.

rajiihammr gravatar imagerajiihammr ( 2018-08-31 15:37:29 -0500 )edit

answered 2018-08-20 09:07:26 -0500

m.p.kingsley gravatar image

The watchdog hardware (if you're not familiar) will reboot the computer if it locks up after a given time. The sp5100-tco has been often mis-identified and the module loaded as an intel i2c chip. Does lsmod|grep i2c-piix4 give any output? If so, look to see which driver the watchdog has loaded (lspci -k should do the trick, though you may have to sort through the output of that.) I've run into this same issue with an earlier AMD chip and an Asus Motherboard. Blacklisting the i2c-piix4 module solved my problem, though in your case blacklisting sp5100-tco should work, disabling the watchdog.

edit flag offensive delete link more

answered 2019-02-06 14:59:54 -0500

rajiihammr gravatar image

Ok, The solution, (fingers crossed), is in the BIOS. A YouTube video, which belatedly I discovered dealt with a Windows bug, said to disable the 'Cstate' and disable all but one 'P-states'. There are a couple of other settings, but I suggest going to the YouTube and find that video. I have run an 8 day boot, and a 6 day boot and a 4 day boot with no feeze-ups. I'm not calling it fixed, I won't make that mistake again.

edit flag offensive delete link more

answered 2018-08-08 12:39:00 -0500

Sorry for posting link to asrock forum are several people having issues from different producers with Fedora 28 and AGESA Pinnacle Ridge update.

Even booting Live installer gangs up with udevd errors.

edit flag offensive delete link more


Am running a MSI B350 pc mate MB, but was running an Asrock MB with same issue (the reason I tried an MSI MB. Will investigate.

rajiihammr gravatar imagerajiihammr ( 2018-08-08 16:13:05 -0500 )edit

Question Tools

1 follower


Asked: 2018-08-03 10:21:27 -0500

Seen: 795 times

Last updated: Feb 06 '19