Welp, sorry for wasting your time with the RAM. Looks like you have gotten farther into the boot process before a boot loop though and the machine check exception no longer shows up?
In which case, best bet to proceed is to chroot into the machine and see if logs have any hints at the issue:
and look at something along the lines of: journalctl -b -1 -p 0-3