protonscr

Proton games freeze randomly

protonopen
ValveSoftware/Proton#9218 · opened 2025-11-14 by Choosechee · updated 2026-07-30 · 13 comments · github
1 matching comments, n / p to jump
CChoosechee 2025-11-14 github

Games

Baldur's Gate 3, DELTARUNE, likely every other game I could play using Proton on my system

System Information

  • GPUs:
    • AMD Radeon 680M
    • NVIDIA GeForce RTX 3060 Laptop GPU
  • Video driver version: nvidia-driver-580-open
  • Kernel version: 6.17.0-6-generic
  • Link to full system information report: Gist:
  • Proton version: Proton Hotfix

I confirm:

  • [✓] that I have checked whether there are updates for my system available.

Symptoms

All Proton games will freeze at seemingly random times, with no way to unfreeze them. When closing the window, the OS says the application is not responding. This seems to happen more often when I am not focused on the game window, but it can happen even while actively playing the game.

Log

bg3_proton.log.gz

This problem is likely specific to my system. How can I fix this?

Ggentoomaniac 2025-11-14 github

Not sure if related, but I see the same symptom in ARC Raiders.
I haven't had the issue in DeepRock Galactic though (the only two I excessively played using proton).
6.12.41-gentoo, AMD 7900 GRE, Proton in different versions

Aageisen2000 2025-11-16 github

Same on arc raiders, checked journalctl and got this:

Nov 15 19:39:21 bazzite systemd-coredump[101434]: [🡕] Process 100227 (GameThread) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 100229:
                                                  #0  0x00007f7d769eaf00 save_context (/var/home/adam/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib/wine/x86_64-unix/ntdll.so + 0x49f00)
                                                  #1  0x00007f7d769ee184 segv_handler (/var/home/adam/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib/wine/x86_64-unix/ntdll.so + 0x4d184)
                                                  #2  0x00007f7d76ac22c0 n/a (/91/e32e445c0a4ac9fedd1f0aea89326e796740254cff0bcd7a520adf355f0678.file + 0x1a2c0)
                                                  ELF object binary architecture: AMD x86-64
Nov 15 19:39:23 bazzite systemd[1]: systemd-coredump@3-2-101433_101434-0.service: Deactivated successfully.

Also not sure if these are related:

Nov 15 19:36:09 bazzite steam[3290]: Adding process 100220 for gameID 1808500
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:bcf08f di:ffffffffff600000
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:c18a4a di:ffffffffff600000
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:c494af di:ffffffffff600000
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:c35aac di:ffffffffff600000
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:c3a4d7 di:ffffffffff600000
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:c3e249 di:ffffffffff600000
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:c396af di:ffffffffff600000
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:c3befe di:ffffffffff600000
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:c46aad di:ffffffffff600000
Nov 15 19:36:13 bazzite kernel: PioneerGame.exe[100227] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000008ec6ec cs:33 sp:b9bce8 ax:b9bd50 si:c463ae di:ffffffffff600000

I do get these freezes on CS2 as well, it's not just arc raiders, but CS2 is native linux so i have no idea... might be a kde issue, wayland issue, or something else...

Rrobby250 2025-11-16 github

I've also had the OP's issue and solved it. I believe it's caused by a combination of 2 factors:

  • having a system with an integrated AMD GPU and dedicated NVIDIA GPU (a gaming laptop) and not running the gpu in exclusive NVIDIA performance mode
  • using a multi-monitor setup (most likely in the case where the laptop doesn't have a mux switch and it's forced to use integrated graphics for the laptop display and NVIDIA gpu for the external one)

I'm pretty sure it's some sort of driver conflict between the AMD and NVIDIA drivers. I no longer have the freezes at all after running in nvidia exclusive performance mode and single monitor.

For reference I use AMD 5800H CPU and NVIDIA 3070 laptop GPU, Linux Mint 22.2.

PPoltergeisen 2025-11-16 github

@robby250, I have a 5950x and a 3090 so it's definitely not an issue with driver conflicts as the 5950x doesn't have an igpu

The real common theme here might just be nvidia

Rrobby250 2025-11-16 github

@robby250, I have a 5950x and a 3090 so it's definitely not an issue with driver conflicts as the 5950x doesn't have an igpu

The real common theme here might just be nvidia

Other people getting freezes from other causes is obviously a very high probability. But my issue was extremely similar to OP's issue, and we have very similar gaming laptop setups, so it might just solve the problem for them, just like it was solved for me.
There could be like 100 more completely different causes for freezes with different setups, I just mentioned what worked in my case.

CChoosechee 2025-11-17 github

Replying to https://github.com/ValveSoftware/Proton/issues/9218#issuecomment-3538462389

I am not using a second monitor.

AArAM1db33tz 2025-12-02 github

Been having this issue at points in Arc Raiders. Feels like a driver crash that sometimes locks out kwin as well as the game and requires a restart. Although other times you can just close the game. I've trimmed the proton log as it was 800mb but it doesn't show much to my simple brain, the journal shows some more.

I do have a second screen connected but disabled.

steam-1808500_11.log
ARC_RAIDERS_CRASH_JOURNAL.log

I'm using proton-cachyos-slr for this but the crashes happen with experimental or hotfix as well. If anything it's harder to recover from the crash on Hotfix or Experimental.

Kernel: Linux 6.17.9-2-cachyos
CPU: AMD Ryzen 7 7800X3D (16) @ 5.05 GHz
GPU 1: AMD Radeon RX 9070 XT [Discrete]
Proton CACHYOS-SLR - Version | 1:10.0.20251120-1
Mesa Version | 26.0.0_devel.214498.e3404af0ed9-1
DE: KDE Plasma 6.5.3
WM: KWin (Wayland)

Launch options: mangohud PROTON_LOG=1 PROTON_FSR4_UPGRADE=1 PROTON_ENABLE_WAYLAND=1 FORCE_GRAB_CURSOR=1 %command%

Is there anywhere else I should post these?

Ssomeone2060 2025-12-04 github

I have the same issue right now. With any game in my library, the game freezes after an unknown amount of time without rhyme or reason. This is the case for both non-intensive and more intensive games.

I got my system information through hw-probe, which is linked here: https://linux-hardware.org/?probe=8e8d7d6c3c

I don't believe that the issue is related to my hardware, as I can run the same games on the same device on Windows 10. I'm less versed in software, so any help would be appreciated.

MMJorink 2026-02-09 github

I don´t know if you are still having this issue but I do, adding %command% -vulkan seems to fix it for me. But I have only tested this on one game! I just thought it would be a good idea to share, I will also try more games later that I had issues with and tell if it also worked for those.

Aageisen2000 2026-02-09 github

I did have this happen once to me yesterday

MMitztheKat 2026-02-25 github

Figured out a solution for the issue that may work for some people. If your laptop has 2 different GPUs (IE NVIDIA & Intel) Set your GPU to the dedicated one. It seems this issue is related to your laptop / GPUs swapping & proton not handling it well.

ZZwnow 2026-02-27 github

Had this issue today while trying the new Resident Evil. I am on Ubuntu and have a Nvidia RTX 4070. When running prime-select query it was set to on-demand, switched it with sudo prime-select nvidia and rebooted my system. Now I was able to play for longer than 20 seconds.

Mind, I am running the flatpak version of steam with this launch command:

alias steam='flatpak run \
  --device=all \
  --env=__NV_PRIME_RENDER_OFFLOAD=1 \
  --env=__GLX_VENDOR_LIBRARY_NAME=nvidia \
  com.valvesoftware.Steam'

As steam wasnt able to detect my card at all.

Mmciiee 2026-07-30 github

Had this happen to me as well, pretty much the same "vsyscall" error:

Game: THE FINALS
Distro: Arch Linux
Kernel: Linux 7.1.5-zen1-2-zen
Proton: GE-Proton11-1
CPU: AMD Ryzen 9 7950x
GPU: AMD Radeon RX 6750 XT
Mesa: 26.1.5-1
WM: Hyprland

Proton versions

Launch options

Launch lines