AnimaLibera

Yeah, I would give it a few hours to most of the day to test and then move on with something else. I really recommend journalctl though. Of course it depends on how long it stays on and how fast you can read the logs.

If it’s freezing regularly, you could try booting a live usb of any Linux distro and see if it does the same thing. That will tell you relatively quickly if it’s a hardware problem or a software problem.

Command line is your friend. It might not seem like it at first, but it is very helpful.

Use the journalctl command in a terminal.

Command Purpose Example
journalctl -u [SERVICE] View logs for a specific systemd unit/service. journalctl -u nginx.service
journalctl -b Show logs from the current boot. journalctl -b
journalctl -b -[N] Show logs from a previous boot (ee.g., -1 for the last boot). journalctl -b -1
journalctl --list-boots List all recorded boot sessions. journalctl --list-boots
journalctl -p [PRIORITY] Filter by priority level or a range. Levels are 0 (emerg) to 7 (debug). journalctl -p err…warning (shows errors, critical, alerts, and warnings)
journalctl --since=“[TIME]” --until=“[TIME]” Filter by time range. Supports absolute (YYYY-MM-DD HH:MM:SS) and relative times (1 hour ago, yesterday). journalctl --since “20 min ago”
journalctl -n [LINES] Show only the last N entries. journalctl -n 20
journalctl -k Show only kernel messages (equivalent to dmesg output). journalctl -k```

I spent a couple of days trying to figure out why I couldn't install any variant of Arch Linux or Fedora Linux on my laptop.  That command helped me narrow things down.

I thought the same. Pretty sure that’s a selling point.