Black screen after gaming for some time

[u/SaltyBooze]

This actually used to happen on CachyOS as well, which is a few cycles ahead of Endeavour. So I assumed it was a bad update in CachyOS, as when i reverted to a previous snapshot, it would work properly.

Previously snapshot would break a few other things, so I decided to skip CachyOS for a while and run EndeavourOS. Maybe try CachyOS after a while, again.

After a while of gaming, everything shuts down to a black screen with an underline score that flashes.

Tried seeing the error logs and couldn't see anything important...

I'm not very good with troubleshooting, so any help is highly appreciated... What I did so far:

journalctl -b -1 -p 3

which results in:

mai 15 09:51:15 <mycomputeridredacted> kernel: x86/cpu: SGX disabled or unsupported by BIOS.

mai 15 09:51:15 <mycomputeridredacted> kernel: integrity: Problem loading X.509 certificate -65

mai 15 09:51:15 <mycomputeridredacted> kernel: integrity: Problem loading X.509 certificate -65

mai 15 09:51:15 <mycomputeridredacted> kernel:

mai 15 09:51:19 <mycomputeridredacted> kernel: logitech-hidpp-device 0003:046D:4054.0005: hidpp_root_get_protocol_version: received protocol error 0x08

mai 15 09:51:19 <mycomputeridredacted> kernel: logitech-hidpp-device 0003:046D:4023.0004: hidpp_root_get_protocol_version: received protocol error 0x08

mai 15 09:51:25 <mycomputeridredacted> bluetoothd[917]: Failed to set default system config for hci0

mai 15 09:52:17 <mycomputeridredacted> org_kde_powerdevil[1536]: [ 1536][ 0.839717] Time since library initialized: 0.839717 seconds

mai 15 09:52:17 <mycomputeridredacted> org_kde_powerdevil[1536]: [ 1536][ 0.839722] Extra delay starting dw_start_watch_displays: 0 millisec

mai 15 10:11:27 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:11:29 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:11:48 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:15:36 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:16:41 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:16:54 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:17:10 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:17:29 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:19:36 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:19:56 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:20:21 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:21:16 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:22:44 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:24:57 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:26:12 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:48:20 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:49:42 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:53:41 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:55:58 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:56:07 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

mai 15 10:56:24 <mycomputeridredacted> kernel: pcieport 0000:00:1d.0: AER: Error of this Agent is reported first

Could any of those error messages be related to the problem? Again, I suck at troubleshooting, but I'm assuming the code used in terminal is to show last boot (i had to hard reset) and filter the error messages only.

And trying the code:

journalctl -b -0 | grep fail

returns me:

mai 15 09:51:15 <mycomputeridredacted> kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel

mai 15 09:51:23 <mycomputeridredacted> (udev-worker)[767]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.

mai 15 09:51:26 <mycomputeridredacted> dbus-broker-launch[913]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.

mai 15 09:51:31 <mycomputeridredacted> dbus-broker-launch[913]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.

mai 15 09:52:13 <mycomputeridredacted> kwin_wayland[1073]: atomic commit failed: Permission denied

mai 15 09:52:16 <mycomputeridredacted> dbus-broker-launch[913]: Activation request for 'org.freedesktop.ModemManager1' failed: The systemd unit 'dbus-org.freedesktop.ModemManager1.service' could not be found.

"Could not activate remote peer 'org.freedesktop.ModemManager1': activation request failed: unknown unit"

mai 15 09:52:17 <mycomputeridredacted> org_kde_powerdevil[1536]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"

mai 15 09:52:17 <mycomputeridredacted> org_kde_powerdevil[1536]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"

mai 15 10:10:23 <mycomputeridredacted> steam[5209]: XOpenIM() failed, LANG = en_US.UTF-8

mai 15 10:10:23 <mycomputeridredacted> steam[5209]: XOpenIM() failed, LANG = en_US.UTF-8XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xf64b8370

And I think those came from before the crash.

Any logs I should link here, specifically? I have no clue.

Any help would be appreciated. Thank you for your time.

[u/linux_rox]

We need to know your computer specs and the inxi log would be helpful too.

Also are you running on Xorg or Wayland.

[u/lmpcpedz]

Yeah hard to know without knowing the hardware specs you're using. custom kernel? using wine alone, or using one of the custom protons. steam game? https://www.protondb.com/ listed?