Lately my PC has started crashing while it plays videos. It freezes completely, screen frozen and not responding to any input (keyboard, mouse), I mean I cannot change TTY (alt + ctrl + F(1-2-…)), and it cannot even respond to alt + PrntScr + REISUB. I have to force power off by holding down the power button.
After I reboot I have tried checking all logs available and I cannot find anything logged right before the incident. Last entries are always different and not indicating anything.
I suspect it has to do with the graphics card but I’m looking for ways that I can dig deeper on that and confirm it or not.
What else should I check? How can I find more info?
OS: Lubuntu 22.04.3 LTS (latest updates) I’m using the nvidia proprietary drivers (nvidia-driver-390)
UPDATE:
First of all thank you all for your input and fresh ideas. Now I’ve already tried some of them and I will continue with the other ones until I get some results.
till now I have tried
- memtest and it didn’t show any errors.
- boot from a live distro and see if problem also occurs. Well it didn’t occur but on the live distro you cannot change the graphics driver. So it was using the open source nouveau driver, also it didn’t happen during the 1 hour I let it play. The thing is that it never was punctual even before. It could happen during the first hour or the third or sometime later.
Next steps are to
- open the case and clean it up to remove the possibility of high temp because of that,
- change my drivers to be the nouveau and try again,
- try with only the onboard GPU on,
- remove extra disks to reduce the load of the PSU
thank you all again.
yes. As I wrote
Just to be certain, you have checked journalctl too?
isn’t this a unified way to present logs that also exist in var/log ? I mean if the logs are saved in var/log I’ve checked them. If there is a possibility that journalctl has more entries, then I need to check this too.
Maybe for some logs but no, systemd logs are stored in binary format and can only be accessed with journalctl. I would definitely give that command a shot.
will check this too then. Thanks
Seems you might know more than me. When I had an obscure crash related to my pc going into C-sleep state, I managed to find a pattern viewing the logs in reverse from the time of the crash.
On my system there is no traditional log files like
kern.logormessage(Not sure about Ubuntu 22.04), I would say it’s worth a try.Try
journalctl --boot -1 -xeorjournalctl --boot -1 -xep3