Random restart happening

Hi,

After installing CachyOS, this is the second time a random restart happened.

First time I didnt capture, but I did now, at a glance, it’s similar.

Any idea what could be the cause of it?

Given the error, seems to be hardware related, could also be because when I decided to try CachyOS, I also updated the bios and re-did the BIOS tweaks, I suppose it could be a factor.

But, I decided to ask, just in case.

The error MC27_STATUSOverIUEMiscVI-IPCC and Ext. Error Code:2 suggest a hardware-related issue, possibly with the CPU and its interaction with the motherboard. Running early hook [udev] suggest this is an error early in the system initalization. Based on the error messages you posted, this most likely has nothing to do with software.

I have seen similar issues with the Intel 13 and 14th CPU’s. If you have one of those, send it back to Intel to get it replaced under the giant Intel recall, it is most likely defective and damaged.

The other issue might be something with the BIOS update or changes you made. I would first roll back your BIOS setting changes, if that does not resolve the issue, roll back the BIOS version to the one that was working.

Did you change your voltage settings for your CPU? If so, they might be wrong. Roll it back to default.

Unlikely, but it could be a memory issue with faulty or incompatible RAM. Run a memory diagnostic tool.

It is hard to narrow it down with just the error message. I am not sure what the hardware is or the changes you made to the BIOS, but I hope this gives you a place to start troubleshooting.

Sorta obvious given the error, that is related to the CPU and hardware.

Those all are the common things that someone would recommend regarding the issue.

Thanks, but unless there is something specific, maybe an actual experience with the issue, no point in discussing.

I’m already trying some other tweaks in the BIOS, I will know if there is a positive effect if it doesnt happen again.

In my perspective seems to be BIOS related or maybe something in the kernel triggering it, who knows.