Kernel panic: not syncing fatal machine check after upgrading the system

I recently upgraded my system from AMD FX 8320 (with DDR3 RAM and M5A97 mobo) to Intel i7-9700K (with DDR4 RAM and a z-390 mobo).

I have 2 different SSDs, one with Windows 10 installation and another with archlinux. After the said upgrade, I am able to boot into Windows without any issues, however the EFI bootloader does not list the drive with archlinux. Using a trial version of EasyUEFI, I added an entry for my archlinux installation to the UEFI firmware bootloader.

So far, so good. I understand that my GPT id's would have changed, and the boot might fail horribly, but I anticipated that it should atleast fallback to a rescue shell.

I boot into the newly created/restored arch entry, select my linux for boot and it fails with different messages related to kernel panic (screenshots below).

I also tried creating a USB bootable to check if I can recreate my fstab, but the bootable drive also fails with a microcode udev error.

Any ideas on how to cleanup my boot configuration for the arch bootloader?

Following the steps from comment by @VarunNarravula:

I tried creating a bootable from the windows machine itself. Downloaded arch-netinstall bootable iso, created a flash drive using unetbootin, and when I reboot to the usb interface, it also fails with similar messages.

1 Answer

So when you replace your computer’s crucial hardware like your CPU, usually a reinstallation is Windows solves it for UNetbootin. Besides, a periodic reinstallation for Windows always solves things with Windows. But don’t use UNetbootin, it only configures hardware support for the machine Windows was initially installed on. Use Rufus.

When you use Rufus instead, it uses the current Windows kernel, unlike UNetbootin. So any Linux ISOs imaged onto a USB should work because the image now reflects the different microcode used in the CPU.