F5F Stay Refreshed Software Operating Systems Hardware issue detected during Ubuntu 19.04 installation. Please check physical components.

Hardware issue detected during Ubuntu 19.04 installation. Please check physical components.

Hardware issue detected during Ubuntu 19.04 installation. Please check physical components.

M
Matesoman
Junior Member
12
09-19-2018, 03:01 AM
#1
I've experienced a few times recently where my daily driver kept freezing. I reset the BIOS, re-applied thermal paste, and switched kernels—currently using Linux 5.2.x—but sometimes it stays up for days. Last night it restarted once and then locked itself hard later. I'm running memtest now... one pass completed without problems so far. What's missing? My setup is Ubuntu 19.04 Ryzen 7 1700X, 3.4Ghz, Asus Prime X470-PRO motherboard, 32GB RAM (16GB x2), Corsair CMK32GX4M2A26 with PC3-21300 DDR4 at XMP 2666Mhz. It's connected to an LG 4K HDR monitor via DP, and a 1TB Samsung Evo 970 NVMe SSD with CoolerMaster 212 EVO Black fans on the CPU. Temperatures are usually in the low 40s, but they drop about 5°C after reapplying paste.
M
Matesoman
09-19-2018, 03:01 AM #1

I've experienced a few times recently where my daily driver kept freezing. I reset the BIOS, re-applied thermal paste, and switched kernels—currently using Linux 5.2.x—but sometimes it stays up for days. Last night it restarted once and then locked itself hard later. I'm running memtest now... one pass completed without problems so far. What's missing? My setup is Ubuntu 19.04 Ryzen 7 1700X, 3.4Ghz, Asus Prime X470-PRO motherboard, 32GB RAM (16GB x2), Corsair CMK32GX4M2A26 with PC3-21300 DDR4 at XMP 2666Mhz. It's connected to an LG 4K HDR monitor via DP, and a 1TB Samsung Evo 970 NVMe SSD with CoolerMaster 212 EVO Black fans on the CPU. Temperatures are usually in the low 40s, but they drop about 5°C after reapplying paste.

I
ilpera99
Junior Member
38
09-25-2018, 06:37 AM
#2
I encountered issues with versions 5.2.x and 5.1.x of the kernel. It seems to be a software-related problem.
I
ilpera99
09-25-2018, 06:37 AM #2

I encountered issues with versions 5.2.x and 5.1.x of the kernel. It seems to be a software-related problem.

S
SquiggyGamer
Member
72
09-25-2018, 08:22 AM
#3
I’m planning to try that @Apasz. I ran a MemTest86 test all day, and it completed successfully. It started with the older 4.x kernel version, but that shouldn’t affect the outcome.
S
SquiggyGamer
09-25-2018, 08:22 AM #3

I’m planning to try that @Apasz. I ran a MemTest86 test all day, and it completed successfully. It started with the older 4.x kernel version, but that shouldn’t affect the outcome.

K
kelusky101
Member
181
10-11-2018, 04:00 PM
#4
It remains challenging to unlock. I’ll attempt to start from Windows to check for further problems.
K
kelusky101
10-11-2018, 04:00 PM #4

It remains challenging to unlock. I’ll attempt to start from Windows to check for further problems.

K
Kqwqii_Is_Sin
Junior Member
8
10-13-2018, 02:01 AM
#5
[deleted]
K
Kqwqii_Is_Sin
10-13-2018, 02:01 AM #5

[deleted]

M
Mare_Cro
Junior Member
1
10-13-2018, 06:44 AM
#6
It seems there might be an issue with C-states on Ryzen processors. I checked the forum link you provided, but no further details were available. You managed to resolve it by disabling them in the BIOS, which worked well for several months.
M
Mare_Cro
10-13-2018, 06:44 AM #6

It seems there might be an issue with C-states on Ryzen processors. I checked the forum link you provided, but no further details were available. You managed to resolve it by disabling them in the BIOS, which worked well for several months.

A
Avollon
Junior Member
21
10-19-2018, 06:49 PM
#7
There are no problems with the Ryzen here. It might be a kernel or motherboard issue. Make sure you have amd-ucode installed. I'll look at dmesg | grep error and journalctl | grep "hardware error". If you're okay with C-States turned off, it shouldn't cause any issues.
A
Avollon
10-19-2018, 06:49 PM #7

There are no problems with the Ryzen here. It might be a kernel or motherboard issue. Make sure you have amd-ucode installed. I'll look at dmesg | grep error and journalctl | grep "hardware error". If you're okay with C-States turned off, it shouldn't cause any issues.