Good morning!
So i installed a fresh copy of Pure OS on my L14 V1 laptop. During certain workflows my system has fully locked up and I’m unable to do anything on the machine until i hard reset my device.
Any troubleshooting ideas? or thoughts on what may be the issue.
What OS before installing a fresh Pure OS? What Bootloader?
PureOS 10 (Byzantium) (Latest)
Using Pureboot.
Im not sure what could be happening, there could be several reasons to freeze. Can it describe what type of workflow make Pure OS freeze?
May be @FranklyFlawless could help too…
Thanks.
First, I would try to roll back to the situation before you noticed the problem - either a restore of a backup of your previous software/OS before you installed the fresh copy; and/or a pureboot rollback if you did upgrade recently. This would rule out hardware problems if everything works as before - or hint at some hardware component failing if you experience the same random freezes.
Provide your hardware configuration and explain your “certain” workflows in more detail if this behavior is consistently reproducible.
I simplified things this morning just running memtester. Depending on the size of the memory test will effect how fast it will crash… when I test close to 32gb of RAM the system will crash within a few mins. With 8… the test will run longer… but… still very odd.
Try reseating the RAM, then use memtester again.
@Muadi I experience similar lockups when using Firefox with many memory-heavy tabs open. I thought this was only fixable with a hard-reboot until I discovered the issue is in GNOME and not the system being unrecoverable in it of itself.
I’ve found going to a different tty by using Ctrl+alt+fN (try 2 or 3) allows me to recover to a terminal and then restart gnome. Sometimes doing so won’t work right away, I have to hit it, wait a couple minutes, then tap the power button to put the computer in standby, reawaken it, and all is good again. Alt+F2 also sometimes allows me to kill Firefox and go back to a working state.
This won’t fix the problem itself but at least allows you to recover without a reboot.
So replaced the RAM and looks like all is good!! Annoying little issue, but geez… Thank you all for your help on this!!
Great, mark either of our posts as a solution.
Is “replaced” the same as “reseated”? To my mind, they are not - but both of them are plausible solutions given the symptoms.
So if the OP just reseated the RAM, your post is the solution.
If the OP actually removed the existing RAM and installed different RAM, which also, confusingly, has the side-effect of reseating the RAM, her post is the solution. Sort of. 