Suspected AMDGPU driver crash using gamescope

General system Kernel, boot, graphics & hardware
1

Since june I jumped ship into eOS, and it has mostly been a good experience, however I have been dealing recently with some GPU driver hangs/crashes that take my whole system down with them (completely unresponsive and need to shut down and back up again to regain functionality) and i cant seem to fix.

Specifically I play war thunder using gamescope with the following launch arguments for the force grab cursor command as i use 2 monitors:
gamescope -w 3840 -h 2160 -r 120 -o 120 -f --framerate-limit --adaptive-sync --force-grab-cursor – %command%

These are my current system settings

System:
  Kernel: 6.18.2-arch2-1 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc
  Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A wm: kwin_wayland vt: 1 dm: SDDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B660M DS3H AX DDR4 v: x.x
    serial: <superuser required> uuid: <superuser required> Firmware: UEFI
    vendor: American Megatrends LLC. v: F33 date: 09/19/2025
CPU:
  Info: 6-core model: 12th Gen Intel Core i5-12600KF bits: 64 type: MT MCP
    smt: enabled arch: Alder Lake rev: 2 cache: L1: 480 KiB L2: 7.5 MiB
    L3: 20 MiB
  Speed (MHz): avg: 3600 min/max: 800/4900 cores: 1: 3600 2: 3600 3: 3600
    4: 3600 5: 3600 6: 3600 7: 3600 8: 3600 9: 3600 10: 3600 11: 3600 12: 3600
    bogomips: 88473
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900
    XTX/7900 GRE/7900M] vendor: Sapphire NITRO+ driver: amdgpu v: kernel
    arch: RDNA-3 pcie: speed: 16 GT/s lanes: 16 ports:
    active: HDMI-A-1,HDMI-A-2 empty: DP-1,DP-2,Writeback-1 bus-ID: 03:00.0
    chip-ID: 1002:744c class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu d-rect: 5760x3240 display-ID: 0
  Monitor-1: HDMI-A-1 pos: top-right model: Samsung res: mode: 3840x2160
    hz: 60 scale: 150% (1.5) to: 2560x1440 dpi: 139
    size: 1872x1053mm (73.7x41.46") diag: 801mm (31.5") modes: max: 3840x2160
    min: 640x480
  Monitor-2: HDMI-A-2 pos: bottom-l model: HP 24es serial: <filter> res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 93
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: max: 1920x1080
    min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.2-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
    navi31 LLVM 21.1.6 DRM 3.64 6.18.2-arch2-1) device-ID: 1002:744c
    display-ID: :1.0
  API: Vulkan v: 1.4.335 layers: 7 surfaces: N/A device: 0
    type: discrete-gpu hw: amd driver: mesa radv device-ID: 1002:744c
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: amdgpu_top,corectrl wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Gigabyte driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403
  API: ALSA v: k6.18.2-arch2-1 status: kernel-api
  Server-1: sndiod v: N/A status: off
  Server-2: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:7af0 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 07:00.0 chip-ID: 10ec:8125
    class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: br-908f4b2cec18 state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 1-14:7 chip-ID: 8087:0033 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
Drives:
  Local Storage: total: 3.87 TiB used: 1.38 TiB (35.8%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SNV2S2000G size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: SBM02103
    temp: 37.9 C scheme: GPT
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WD BLACK SN770 2TB
    size: 1.82 TiB speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 731100WD temp: 45.9 C scheme: GPT
  ID-3: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB
    speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
Partition:
  ID-1: / size: 1.75 TiB used: 1.38 TiB (79.1%) fs: btrfs dev: /dev/nvme1n1p2
  ID-2: /home size: 1.75 TiB used: 1.38 TiB (79.1%) fs: btrfs
    dev: /dev/nvme1n1p2
  ID-3: /var/log size: 1.75 TiB used: 1.38 TiB (79.1%) fs: btrfs
    dev: /dev/nvme1n1p2
Swap:
  ID-1: swap-1 type: partition size: 68.88 GiB used: 9.3 MiB (0.0%)
    priority: -2 dev: /dev/nvme1n1p3
Sensors:
  System Temperatures: cpu: 40.0 C mobo: 25.0 C gpu: amdgpu temp: 51.0 C
    mem: 64.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 64 GiB note: est. available: 62.63 GiB used: 7.5 GiB (12.0%)
  Processes: 1083 Power: uptime: 12m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: systemd v: 259 default: graphical
  Packages: pm: pacman pkgs: 1349 Compilers: clang: 21.1.6 gcc: 15.2.1
    Shell: Bash v: 5.3.9 running-in: konsole inxi: 3.3.40

Reinstalling drives didn’t seem to work and searching on the driver and gpu issues list on github showed similar issues but I am incapable of troubleshooting what specifically is causing the crash, so I am here to ask for help.

2

Does it happen without gamescope?

When I was still using an AMD gpu I ran into this issue after a specific kernel which I think was 6.12+

The issue is still open. I’m not using an AMD gpu anymore but I would see if any of the workarounds mentioned there work for you if that’s the issue you are running into.

3

It is very random, used to be an issue a month or two ago but with a software update I believe it got patched. I had similar crashes very reliably while playing stalker 2 but switching to proton hotfix fixed it.
These issues with gamescope have just started happening to me specifically 2 days ago however. I gave that thread a read and the comments regarding DP were interesting as I have a DP cable connected to my powered off VR headset, I doubt it’ll do something but I have nonetheless disconnected this cable from my GPU.

4

Try switching to the “linux-lts” kernel to see if it happens then, does it happen when you don’t use gamescope?

5

I have switched to the LTS kernel and will monitor if I still have these crashes, unfortunately they are a little on the rarer side.
If it ends up being the “fix”, then do I just stay in the LTS kernel forever and switch to live every once in a while to see if its still crashing?
EDIT: just to add that these issues specifically happen only when using gamescope;

6

I’ve found, for my setup at least, that using gamescope in a Wayland session is more likely to crash my games (and session) than using gamescope in an X11 session.

It seems that Wayland just doesn’t need gamescope.

For reference: [SOLVED] Steam Games Work on Wayland, But Not X11

7

I don’t know if it’s related or not but I’ve been unable to use gamescope or mangohud in any Linux distribution at all, in any game so far. All AMD setup. I’ve tried Ubuntu, Fedora, Arch based etc - Not happening. Either won’t open, crashes, or becomes a slideshow. I’m not sure it’s got anything to do with Endeavour OS.

8

Which DE or WM/WC have you tried gamescope with? My comment, as well as two of the other comments above, suggest this is a DE/WM compatibility issue rather than a distro one. Basically, if you’re using a Wayland-based DE/WC, don’t use gamescope.

Of course, YMMV.

1 Like
9

I wouldnt use it if it werent for the fact i want the mouse cursor captured, but whenever i search its what i see people reccomend.
I’d use proton but the anti cheat gets disabled that way, and then it wont let me play :confused:

10

Well then, I’d suggest that you use gamescope in an X11 WM session.

Openbox is lightweight and pretty much straightforward. You’d use it just for gaming, so no real need to learn how it works. Just install it, launch Steam by right-clicking on the desktop, then finding it in the little menu. Then you can use gamescope the way you want/need.

To make things feel a little more like a DE, you can install XFCE’s panel so you can use its applications menu, see the time, system tray, etc.

sudo pacman -S openbox xfce4-panel

Note: If you are already using a full DE (KDE/Gnome/Cinnamon/etc.), please do not install another full DE, as this can cause issues with theming and general settings.

11

Also be sure you have all your games display settings set on “full-screen” and not “windowed border-less”. I have found the latter with a dual-monitor setup your mouse ends up on the secondary monitory as you describe.

12

This issue may be related:

Reproducible AMDGPU kernel crash triggered by gamescope when a game recreates the swapchain (e.g. switching to maximum resolution).Expected: game continues normally after resolution/swapchain change.

Actual: amdgpu gfxhub page faults occur, followed by MES failures and GPU reset. The issue is reproducible and happens consistently under gamescope.

13

For the time being using the LTS kernel hasn’t netted me any crashes, so i have marked this topic as solved and encourage this as a temporary fix for others encountering this specific crash.

14

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.