Hi @Arahan666,
I have also been “lectured” about this, but one shouldn’t do that to a computer/laptop. (Well, a laptop is a kind of computer, so yeah…)
Instead, rather look here, and go with this:
We can look in the logs if there are any clues as to the cause of this behavior. Run the following on a successful boot, right after the problem:
journalctl --boot=-1 --priority=3
That should give you all errors from the previous boot.