March 10, 20215 yr This has been happening since I did a boardswap from a Z490 to a B560. I'm seeing this in syslog at boot: Mar 10 09:24:24 BeepServ kernel: smpboot: CPU0: Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz (family: 0x6, model: 0xa5, stepping: 0x3) Mar 10 09:24:24 BeepServ kernel: mce: [Hardware Error]: Machine check events logged Mar 10 09:24:24 BeepServ kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a Mar 10 09:24:24 BeepServ kernel: mce: [Hardware Error]: TSC 0 ADDR fef20080 MISC 3880000086 Mar 10 09:24:24 BeepServ kernel: mce: [Hardware Error]: PROCESSOR 0:a0653 TIME 1615397046 SOCKET 0 APIC 0 microcode e0 and then this after boot: Mar 10 09:32:58 BeepServ root: mcelog: Family 6 Model 165 CPU: only decoding architectural errors Mar 10 09:32:58 BeepServ root: mcelog: warning: 8 bytes ignored in each record Mar 10 09:32:58 BeepServ root: mcelog: consider an update The same processor & ram (i3 10100, crucial ballistix) did not generate any mce errors on the previous z490 motherboard. I've tried dinking around with the BIOS and also tried BIOS defaults. I removed the CPU and inspected both the cpu and motherboard pins. I'm not seeing any stability problems so far nor any other errors, but the system generally idles and lightly transcodes stuff on a Geforce 1050ti. Does this look like a BIOS thing? Asrock said they don't support Linux, so try Windows. Not very helpful for this. Just wondering if there is something wrong with the motherboard that may warrant more tests and if I should consider returning or just ignore this error.
April 5, 20215 yr The same error message just showed up without any hardware swaps on my part. Have you been able to solve this?
April 9, 20215 yr Author Similar hardware? I've updated the BIOS to the latest but it still hasn't gone away. It's not causing any crashes though either. I'm just ignoring it for now.
April 9, 20215 yr Without the diagnostics, assuming that it's very early in the boot process when it's initializing the cores, it's not a problem and safe to ignore.
August 16, 20214 yr Although I am not using unraid I stumbled across this post because you sharing practically the same error I just started receiving. This is on boot with proxmox.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.