never seen this before, still learning every day haha
I misunderstood you. English is not my native language and I was probably reading too fast, sorry 
This is certainly also possible
I’ll have another look at the BIOS later or tomorrow to see if all the functions have been retained or if I need to adjust anything again.
1 Like
Yes, BIOS was resetted.
Reboot doesnt work.
Boot after Power off worked for the last three times i have checked.
So the original problem is solved but now you can’t reboot? What happens when you try to reboot?
1 Like
It shows me the Gigabyte Aorus logo with the selection, boot menu, bios and another selection. After that, only the logo is visible and nothing else happens
Has now rebooted three times after power-off. I hope it works again.
i started the boot process 5 more times and again the same problem. 4 times to aorus logo, the 5th time I got to the uefi login screen where I could select the kernels.
So the orignal issue is not fixed either
Something is wrong.
It is hard to say from what only you are seeing but this doesn’t sound like a software issue to me.
1 Like
Mm it could be one of a few things i guess:
Something is wrong with your disk/ssd (this would be nvme0n1), uefi has trouble finding the disk, maybe try with another ssd
Or the bios has a bug that prevents proper booting, if it is possible try to downgrade bios to an earlier one (no beta versions!)
Or your motherboard has a hardware issue, like i said before in my experience this happened with Gigabyte motherboards
Maybe a bios setting like raid mode is enabled (perhaps through the reset)
1 Like
i’m pretty sure the error occurred one or two days later when systemd was updated to 255
I have checked the BIOS settings after the reset.
if it is not due to systemd ver 255, I think this is most likely
perhaps downgrade systemd in chroot, it is worth a shot as you said it happened after update of systemd
1 Like
F12 was on the MB when I bought it new. The update to F14 was actually quite stable.
I will downgrade to F14 again
However, I would need step-by-step instructions for such an action. I don’t have the knowledge for that.
First I try a downgrade to F14
There are much newer bios versions available so maybe you try those?
I agree that there is no mention of any system stability updates so it might be not helping, although motherboard manufactures not always mention every issue.
I have no/little experience with downgrade, especially with systemd, which is a core system part so may be others can help you with that.
1 Like
If problems persist after a BIOS downgrade, I will start a new topic. Thank you very much for your time and help
To downgrade systemd you need to downgrade all the systemd packages at the same time and to the same version.
You can find all the systemd packages with pacman -Q | grep systemd. You should see that they all have the same version.
Then pass them all to downgrade like this:
sudo downgrade lib32-systemd systemd systemd-libs systemd-sysvcompat
That being said, it doesn’t look like it is even getting far enough that it would be a systemd issue. It also seems strange that a systemd issue would be intermittent like that.
2 Likes
i agree with @dalto that it is very unlikely that systemd is the problem, i think it is more a hardware problem.
I noticed that you have samsung 980 m2 ssd in your system, there are firmware issues with those drives so you could be affected by that
1 Like
It may be pure coincidence that the error occurred exactly when systemd was updated to 255.
The longer I think about it and also thanks to your page from toms hardware you linked aboveabout the errors on a samsung nvme 980 pro, I have more and more the feeling that it is a hardware error
Just to confirm, is CSM support in BIOS enabled or disabled?
2 Likes
I dont know, i need to have a look.
What should be the default setting?