I am gettings hardware errors during the FixCommonPlugin scan.

t1000-diagnostics-20251026-1107.zip

Can someone help to identify if this is a real error please.

Thank you.

Yes – your diagnostics clearly show Machine Check Events (MCEs). That’s exactly what the Fix Common Problems plugin is warning you about.

mce: [Hardware Error]: Machine check events logged

[Hardware Error]: Corrected error, no action required.

Fix Common Problems: Error: Machine Check Events detected on your server

mcelog: ERROR: AMD Processor... Please use the edac_mce_amd module instead.

What this means:

• These are corrected hardware errors reported by the CPU.

• The system didn’t crash, but it indicates a potential hardware issue that shouldn’t be ignored if it becomes frequent.

• On AMD systems, mcelog is basically unreliable and often throws useless messages — the Linux kernel recommends using the edac_mce_amd module instead.

Most common causes:

• Too aggressive memory settings (EXPO/XMP)

• Slight system instability (RAM, CPU, PSU)

• Outdated BIOS with older AMD microcode

Recommended steps:

• If EXPO/XMP is enabled → try disabling it for a while
  This alone fixes most MCE reports on AMD systems.

• Update BIOS
  Many AMD MCE issues are microcode bugs fixed in BIOS updates.

• Run a full Memtest86 overnight (4+ passes)
  If errors show up → RAM or memory controller issue.

• Check PSU quality & voltages
  Weak/unstable PSUs can trigger MCEs.

Bottom line:

Your server is not in immediate danger, but the CPU is reporting corrected hardware faults. Keep an eye on it. If these messages become more frequent, then it’s time to take action.

Your system is running an AMD Ryzen 5 5600X.
This CPU is known to occasionally report corrected Machine Check Events under Linux, especially when:

• EXPO/XMP memory profiles are enabled,

• BIOS is outdated,

• or the system is slightly undervolted/unstable.

This isn’t unique to your hardware – it’s a common behavior on Zen 3 CPUs. Many users with 5600X/5800X/5900X/5950X see the same warnings when memory tuning is too aggressive or when the board’s early BIOS revisions had microcode issues.