Issue caused by Nvidia Drivers?

After the last Update, the Issue of my Nvidia 970 dGPU losing the Display Signal returned when playing Games.

Civ:Beyond Earth: Rising Tide works fine on Windows. But I’m thinking that something is wrong with the Driver itself.

In any case I have Replacement Fans on the way and that might fix the Problem.

Is anything relevant in the journal (journalctl -b0)? Alternatively, start journalctl -f in a terminal, then run the game, and after the problem occurs, check if it printed anything relevant. In any case, post the output of inxi -Gazy.

Here is the output of

journalctl -b0

– Journal begins at Sun 2021-04-11 16:22:55 CDT, ends at Fri 2021-04-30 20:51:39 CDT. –
Apr 30 17:29:20 william-pc kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12
Apr 30 17:29:20 william-pc kernel: Linux version 5.12.0-1-MANJARO (builduser@LEGION) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Mon Apr 26 22:09:28 UTC 2021
Apr 30 17:29:20 william-pc kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.12-x86_64 root=UUID=1a0a0cfd-5864-4f2c-a234-2c68123345f3 rw quiet apparmor=1 security=apparmor resume=UU>
Apr 30 17:29:20 william-pc kernel: x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
Apr 30 17:29:20 william-pc kernel: x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
Apr 30 17:29:20 william-pc kernel: x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
Apr 30 17:29:20 william-pc kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Apr 30 17:29:20 william-pc kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using ‘standard’ format.
Apr 30 17:29:20 william-pc kernel: BIOS-provided physical RAM map:
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000c8c1efff] usable
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000c8c1f000-0x00000000c8c25fff] ACPI NVS
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000c8c26000-0x00000000c981bfff] usable
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000c981c000-0x00000000c9d1cfff] reserved
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000c9d1d000-0x00000000dcecdfff] usable
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000dcece000-0x00000000dd0d3fff] reserved
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000dd0d4000-0x00000000dd110fff] usable
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000dd111000-0x00000000dd1b8fff] ACPI NVS
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000dd1b9000-0x00000000ddffefff] reserved
Apr 30 17:29:20 william-pc kernel: BIOS-e820: [mem 0x00000000ddfff000-0x00000000ddffffff] usable
lines 1-23

journalctl -b0 will open a pager with the journal since the last boot. You should use the timestamps in the left column to find the entries which were saved when the issue occurred and see if any of them are relevant. (You may specify -b-1, -b-2, etc. to get the journal for previous boots.)

Nevermind I replace the Fans on the Card and that fixed the Issue.