I had a similar experience with a workplace machine. It worked flawlessly. But, sometimes, I went to make myself coffee or to the bathroom, and when I was back,

I had a similar experience with a workplace machine. It worked flawlessly. But, sometimes, I went to make myself coffee or to the bathroom, and when I was back, the system just never woke up from sleep. I try setting the machine to sleep and manually waking it up. No problem. Later, I spent some time watching a long youtube video, then I opened the terminal and then the OS crashed. Dmesg? It showed nothing But, sometimes, when I tried to launch the terminal, I tried running htop and then the OS hanged. I had the feeling that it was something HD related. I restarted the machine, updated the kernel, asked the forums, everything. No answer. It was my work machine. They let me install Linux but I couldn't spend so much time with the OS. I need to have work done. Otherwise I need to bail and go back to Windows (ugh). I was about to delete Linux from the laptop, but I had an idea: The machine was a Thinkpad T1. I looked on the Arch Wiki about compatibility with that laptop. If the problem came from an incompatibility with the hardware, it will surely show up there. The machine showed up in a list and according to the wiki, there's nothing related to a crash or a freeze. Then, I looked up on lshw if there was any piece of hardware that was different of what the Thinkpad has by defaults. The result? A Kingston 1TB SSD. I googled "Linux Kingston ssd lock up", "Linux Kingston ssd crash". It turns out, some Kingston SSDs don't support all the deep sleep levels of energy saving. I needed to switch some off with a kernel parameter. I never had any problems with that machine again.