You are not logged in.

#1 2025-08-31 20:19:59

carmik
Member
Registered: 2025-08-31
Posts: 21

[SOLVED] Fresh install with dmesg hardware errors

System specs: MSI Tomahawk B450 board
GPU: Nvidia 3060ti
Used to have a Ryzen 3600 with 2x8Gb Gskill memory, on a Windows setup. Rock for years, no crashes, no BSODs.

A couple of weeks ago a replaced CPU/RAM with the following:
CPU: Ryzen 5600X (bought used a couple of weeks ago)
RAM: 2x8 Kingston DIMMs at 3200 (XMP), supported as per MSI (bought from the same guy)

Apart from XMP, no overclocking is configured (never was).

I've spent the last 8 hours taking notes and prepping the subvolumes, my cryptsetup etc. Had not even time to install KDE.

So, after installing nvidia-open and nvidia-open-lts I had the time to see some error messages logged, regarding the CPU and memory. I've uploaded dmesg at https://paste.rs/HbKoM

For your convenience, the offending entries are the following:

...
[    0.828605] NET: Registered PF_PACKET protocol family
[    0.829582] x86/amd: Previous system reset reason [0x00800800]: internal CPU shutdown event occurred
[    0.829592] microcode: Current revision: 0x0a201211
[    0.829593] microcode: Updated early from: 0x0a20120a
[    0.829619] mce: [Hardware Error]: Machine check events logged
[    0.829621] Memory failure: 0x549a22010: memory outside kernel control
[    0.829623] [Hardware Error]: Uncorrected, software containable error.
[    0.829628] fbcon: Taking over console
[    0.829630] [Hardware Error]: CPU:1 (19:21:2) MC0_STATUS[Over|UE|-|AddrV|-|-|SyndV|UECC|Deferred|Poison|Scrub]: 0xe43cfd2ebdcbcd7d
[    0.829645] [Hardware Error]: Error Addr: 0x002d549a22010480
[    0.829649] [Hardware Error]: IPID: 0x001000b000000000, Syndrome: 0x0000000000000000

[    0.829656] [Hardware Error]: Load Store Unit Ext. Error Code: 11
[    0.829657] [Hardware Error]: cache level: L1, tx: RESV
[    0.829666] mce: [Hardware Error]: Machine check events logged
[    0.829667] [Hardware Error]: Uncorrected, software containable error.
[    0.829671] [Hardware Error]: CPU:1 (19:21:2) MC1_STATUS[Over|UE|-|AddrV|-|TCC|-|UECC|-|Poison|-]: 0xf58faacaddca6bb8
[    0.829682] [Hardware Error]: Error Addr: 0x0090000000000000
[    0.829685] [Hardware Error]: IPID: 0x000100b000000000
[    0.829688] [Hardware Error]: Instruction Fetch Unit Ext. Error Code: 10
[    0.829689] [Hardware Error]: cache level: RESV, tx: GEN
[    0.829697] [Hardware Error]: System Fatal error.
[    0.829700] [Hardware Error]: CPU:1 (19:21:2) MC2_STATUS[-|UE|-|-|PCC|-|SyndV|UECC|-|Poison|Scrub]: 0xa236afb063140760
[    0.829710] [Hardware Error]: IPID: 0x000200b000000000, Syndrome: 0x0000000000000000

[    0.829716] [Hardware Error]: L2 Cache Ext. Error Code: 20
[    0.829716] [Hardware Error]: cache level: RESV, tx: INSN
[    0.829723] [Hardware Error]: Uncorrected, software containable error.
[    0.829727] [Hardware Error]: CPU:1 (19:21:2) MC6_STATUS[-|UE|-|AddrV|-|-|SyndV|UECC|Deferred|-|Scrub]: 0xb42177e40c7db641
[    0.829737] [Hardware Error]: Error Addr: 0x0000000000000000
[    0.829740] [Hardware Error]: IPID: 0x000600b000000000, Syndrome: 0x0000000000000000

[    0.829746] [Hardware Error]: Floating Point Unit Ext. Error Code: 61
[    0.829747] [Hardware Error]: cache level: L1, tx: INSN
[    0.829754] [Hardware Error]: Uncorrected, software containable error.
[    0.829758] [Hardware Error]: CPU:4 (19:21:2) MC2_STATUS[Over|UE|-|-|-|-|-|UECC|-|Poison|-]: 0xe001ece2b75710dd
[    0.829768] [Hardware Error]: IPID: 0x000200b000000000
[    0.829772] [Hardware Error]: L2 Cache Ext. Error Code: 23
[    0.829772] [Hardware Error]: cache level: L1, tx: RESV
[    0.829779] [Hardware Error]: Deferred error, no action required.
[    0.829783] [Hardware Error]: CPU:4 (19:21:2) MC6_STATUS[-|-|-|-|PCC|-|SyndV|UECC|Deferred|Poison|Scrub]: 0x9327bde8cc7659ce
[    0.829793] [Hardware Error]: IPID: 0x000600b000000000, Syndrome: 0x0000000000000000

[    0.829799] [Hardware Error]: Floating Point Unit Ext. Error Code: 54
[    0.829800] [Hardware Error]: cache level: L2, tx: RESV
[    0.829807] [Hardware Error]: System Fatal error.
[    0.829810] [Hardware Error]: CPU:7 (19:21:2) MC6_STATUS[Over|UE|-|-|PCC|-|-|UECC|-|Poison|-]: 0xf35a2c9f82f5e526
[    0.829820] [Hardware Error]: IPID: 0x000600b000000000
[    0.829824] [Hardware Error]: Floating Point Unit Ext. Error Code: 53
[    0.829825] [Hardware Error]: cache level: L2, tx: DATA
[    0.830297] Console: switching to colour frame buffer device 128x48
...

I'm not experienced in Linux (and especially the kernel). Is there something I could look for here? Is it CPU, RAM or both? Do note that I did not receive any kernel panic, the system booted (with the exception of those errors).

My windows install does have a couple of similar issues, but specifically inability to boot, after installing this CPU and RAM. From a very few tests, on Windows disabling XMP allowed the system to start. However, memtests86+ and Windows memory diagnostics have not reported any mem issues, running for hours with the newly installed CPU/RAM combo operating in XMP mode.

On Windows either the system does not  boot at all, or works like a champ (no app crashes and no BSODs once logged in). Personally I don't care about it, I'll be moving my Windows related work to my Arch NVMe, once I've completed the setup, so just saying in case it helps here.

Could these dmesg errors indicate that there are processor issues as well?

My apologies for having my first post, one like this one sad

EDIT: It's rather late, but I did a couple of boots with XMP disabled and the errors are gone.

Last edited by carmik (2025-10-16 07:26:08)

Offline

#2 2025-09-01 11:00:05

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,315

Re: [SOLVED] Fresh install with dmesg hardware errors

XMP equals overclocking memory .

[    0.000000] DMI: Micro-Star International Co., Ltd MS-7C02/B450 TOMAHAWK (MS-7C02), BIOS 1.I0 07/25/2022

https://www.msi.com/Motherboard/B450-TOMAHAWK/support shows 4 (beta) releases after yours.
Does the motherboard offer functionality to revert to previous bios if something goes wrong ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2025-09-01 11:08:33

carmik
Member
Registered: 2025-08-31
Posts: 21

Re: [SOLVED] Fresh install with dmesg hardware errors

Thanks for the response mate. Yes it does, and it was my next plan of action TBH. Install the BIOS "closest" to 1.I0 and check if microcode is also loaded as well.

MSI itself does not recommend going over this version though for 5600X; rather funny, considering this the same version that 5600x support was introduced in....

Offline

#4 2025-09-01 13:08:30

carmik
Member
Registered: 2025-08-31
Posts: 21

Re: [SOLVED] Fresh install with dmesg hardware errors

Some info. Replaced the 2x16 Kingston rM with the 2x8 gskill I had on my 3600-based setup. Using xmp again, no issues at all in 10 out of 10 attempts. Furthermore, my Linux LTS kernel booted just fine, whereas it wouldn't on the Kingston DIMMs...

Offline

#5 2025-09-01 15:19:56

LuxFerre
Member
Registered: 2010-03-01
Posts: 92

Re: [SOLVED] Fresh install with dmesg hardware errors

carmik wrote:

Thanks for the response mate. Yes it does, and it was my next plan of action TBH. Install the BIOS "closest" to 1.I0 and check if microcode is also loaded as well.

MSI itself does not recommend going over this version though for 5600X; rather funny, considering this the same version that 5600x support was introduced in....

I would ask MSI for support. I once had similar issues with an asrock x470 board and they sent me a beta bios that fixed it (it slightly increased RAM voltage to make it stable).
But I'm pretty sure you can try the latest beta without risks too, or use the RAM without expo enabled.

Offline

#6 2025-10-16 07:27:25

carmik
Member
Registered: 2025-08-31
Posts: 21

Re: [SOLVED] Fresh install with dmesg hardware errors

Issue was solved by updating to the latest (beta atm) UEFI/BIOS. Did not expect it to be solved, since no mention of memory compatibility was in the changelog, however I am happy that it did.

Offline

Board footer

Powered by FluxBB