I see. My concern was with security scanning tools often put on computers by enterprise IT departments but it sounds like that’s not the case here.
In your situation, assuming you’re not finding what you seek with journalctl, I think I would use a tool like vmstat or sar to collect periodic snapshots of CPU, memory, and io. You can tell it to collect data every X seconds and tee that to a file. After you reboot you can see what happened leading up to the crash. You should be able to import the data into a spreadsheet or something for analysis, but it’s not very intuitive and you’ll need to consult man pages for the options and how to interpret them.
There are a lot of good suggestions in this thread. I would lean towards a hardware or driver issue, maybe bad RAM. Unfortunately these things take a lot of trial and error to figure out.





This was the first thing that came to mind when they mentioned a program. I very rarely create programs that don’t need to be updated later, unless they’re single use throwaways.
I’ve inherited support for programs that we had lost the source code for, though, and that sucks.
So that’s a no from me.