Machine Check Events detected on your server, unknown cause

[suchamoneypit]

Been running unraid for several years, been using my 5950x CPU for several months now. Fix common issues plugin just notified me of a Machine Check Events detected, and to post on the forums with logs. I think I see the several errors in the logs; is there enough info here for something to explain what the issue was? Notably I think these all occurred during a parity check which is currently 87% complete. 

 

Apr 7 01:23:49 S-Cartographer kernel: mce: [Hardware Error]: Machine check events logged

Apr 7 01:23:49 S-Cartographer kernel: [Hardware Error]: Corrected error, no action required.

Apr 7 01:23:49 S-Cartographer kernel: [Hardware Error]: CPU:1 (19:21:2) MC21_STATUS[-|CE|-|-|PCC|-|-|Poison|Scrub]: 0x839d8de800015080

Apr 7 01:23:49 S-Cartographer kernel: [Hardware Error]: IPID: 0x0000000000000000

Apr 7 01:23:49 S-Cartographer kernel: [Hardware Error]: Bank 21 is reserved.

Apr 7 01:23:49 S-Cartographer kernel: [Hardware Error]: cache level: RESV, tx: INSN

 

Apr 8 16:26:44 S-Cartographer kernel: mce: [Hardware Error]: Machine check events logged

Apr 8 16:26:44 S-Cartographer kernel: [Hardware Error]: Corrected error, no action required.

Apr 8 16:26:44 S-Cartographer kernel: [Hardware Error]: CPU:1 (19:21:2) MC23_STATUS[-|CE|-|AddrV|-|-|UECC|-|-|-]: 0x854824048b480084

Apr 8 16:26:44 S-Cartographer kernel: [Hardware Error]: Error Addr: 0x0000000000000000

Apr 8 16:26:44 S-Cartographer kernel: [Hardware Error]: IPID: 0x0000000000000000

Apr 8 16:26:44 S-Cartographer kernel: [Hardware Error]: Bank 23 is reserved. Apr 8 16:26:44 S-Cartographer kernel: [Hardware Error]: cache level: RESV, tx: DATA

 

Apr 14 04:30:07 S-Cartographer root: Fix Common Problems: Error: Machine Check Events detected on your server

Apr 14 04:30:07 S-Cartographer root: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead.

 

s-cartographer-diagnostics-20240415-1227.zip

[bmartino1]

 

run a memtest most times this is due to faulty memory or ecc messaged that memory address has been corrected.

unraid currently doesn't have the tools for amd... and the Unraid devs / other more capable will need the diagnostic you gave to shift through to see what up and what may have caused this.