Some positive things here though, the GPU power consumption is low, and temperatures are under control, which tells me it’s extremely unlikely to be a power-supply fault as your system is very lightly loaded.
Unfortunately though it does look like you have an issue with your motherboard. Not much else can cause a system reboot under Linux like you describe.
I do see you have quite a few things running when it crashes, like firefox and spotify. Can you reproduce the crash without any applications running at all?
Another thing which might be useful but that I have to dig a bit more. It seems that when I’m in console (CTLR + ALT + F2), the system is stable and doesn’t suffer crashes.
Because when I was doing some tests. I’ve reached the point where I would instantly freeze after entering my password (never went after the KDE Plasma gear screen). However, if I logged in console mode, it would work.
I will try tonight to use the console for an extended period of time and provide a feedback on this.
A motherboard issue would be the best thing which could happen since it still is under garantee
It notes exactly what you have observed - runs OK in Windows, but reboots in Linux. Apparently, the OSes are running the CPU at slightly different voltages.
Random segfault in a random process, likly due to the CPU/MB issue.
Double check your CPU configuration in your bios is all auto, reset to defaults if needed. Do NOT undervolt.
Double check your RAM is not overclocked, disable XMP profiles, etc.
If it happens again, RMA the motherboard as it’s the more likely culprit.
Edit: @glenjo seems to be on the money here. While pushing the voltage up may resovle this, I personally would consider this a hardware failure and RMA the CPU.
The simple fact is NVIDIA still has issues with Wayland.
It’s very well known and is constantly discussed in the Arch sub reddit and other arch forums.
You aren’t going to get NVIDIA to work 100% with Wayland as there are numerous issues that arise every driver update. In every release, NVIDIA states more supported features for Wayland but it’s still spotty sometimes.
Then why are you posting suggestions that have ZERO impact on the issue here?. As stated numerous times, issues with a PCIe device of any kind CAN NOT cause a forced sudden system reboot.
Again, not the issue at hand here, the system is spontaneously rebooting.
This IS the definitive root cause of the problem, a MCE (Machine Check Exception) is a low level fault from the CPU, 100% a hardware issue and has nothing to do with software.
Windows seems to run the CPUs at higher voltage and lower peak frequencies, compared to the stock linux kernel, which depending on your draw from the silicon lottery could cause a host of random application crashes or hardware errors that lead to reboots. You will recognise those by dmesg logs that look like:
If switching to Wayland/Xorg “fixes it”, you might as well tell the OP to just run Windows to fix it. It provides no additional diagnostic information whatsoever.
There is no software case at all that would trigger a spontaneous system reboot based on the display server that the OP is running, the worst that should happen is loss of display output but still be able to remote into the PC via SSH. Anything more then this indicates a falure of hardware, be it CPU, RAM or Motherboard.
The fun never ends. I think my linux install ended up getting corrupted because I can’t boot to it anymore. I just get a black screen and nothing more. I can’t even access the console.
I tried booting on an another Ubuntu install I did for testing and dmesg doesn’t show any mce error.
Did you try the suggestion from the Arch wiki and push up your voltages a little? The MFC will be random as per the information provided as it’s based on peak loads and frequency.
Also edit the grub command line during boot and remove the quiet parameter.
Not needed under Linux, at a minimum the kernel should output informational messages during boot even if there is hdd corruption.
