Same thing happens for me. Just refunded it :( Will buy again if this gets fixed.
@mirfalltnixein nvidia 396.54 is from 2018, your log shows your actual driver version is 595.45.4.
Given your description I'm guessing your crash comes before an early music video gets a chance to play, is that correct?
If so, can you try running this in your terminal steam steam://unlockh264/ and try to play the game again?
I tried the game on a rx 9070 with mesa 26.0.3, linux 6.19.8, and proton 10 and experimental, and the only issue I've run into so far is that battleeye will sometimes fail and prevent the game from running, but closing it and opening the game again will allow it to work again.
@gshipley you should also share information about your setup. It's hard to narrow things down otherwise.
Sorry :( I already uninstalled got a refund. I am running Bazzite with 595.45.04 on a 5090 at 4k.
.',;::::;,'. gshipley@bazzite
.';:cccccccccccc:;,. ----------------
.;cccccccccccccccccccccc;. OS: Bazzite x86_64
.:cccccccccccccccccccccccccc:. Host: MS-7D91 (4.0)
.;ccccccccccccc;.:dddl:.;ccccccc;. Kernel: Linux 6.17.7-ba28.fc43.x86_64
.:ccccccccccccc;OWMKOOXMWd;ccccccc:. Uptime: 2 days, 1 hour, 10 mins
.:ccccccccccccc;KMMc;cc;xMMc;ccccccc:. Packages: 2922 (rpm), 66 (flatpak-system), 20 (flatpak-user), 35 (brew), 1 (brew-cask)
,cccccccccccccc;MMM.;cc;;WW:;cccccccc, Shell: zsh 5.9
:cccccccccccccc;MMM.;cccccccccccccccc: Display (GBT3215): 3840x2160 @ 1.5x in 32", 240 Hz [External]
:ccccccc;oxOOOo;MMM000k.;cccccccccccc: DE: KDE Plasma 6.6.2
cccccc;0MMKxdd:;MMMkddc.;cccccccccccc; WM: KWin (Wayland)
ccccc;XMO';cccc;MMM.;cccccccccccccccc' WM Theme: Breeze
ccccc;MMo;ccccc;MMW.;ccccccccccccccc; Theme: Breeze (Light) [Qt], Vapor [GTK2/3]
ccccc;0MNc.ccc.xMMd;ccccccccccccccc; Icons: breeze [Qt], breeze [GTK2/3/4]
cccccc;dNMWXXXWM0:;cccccccccccccc:, Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
cccccccc;.:odl:.;cccccccccccccc:,. Cursor: breeze (24px)
ccccccccccccccccccccccccccccc:'. Terminal: Ptyxis 49.3
:ccccccccccccccccccccccc:;,.. Terminal Font: Monospace (16pt)
':cccccccccccccccc::;,. CPU: 13th Gen Intel(R) Core(TM) i9-13900K (32) @ 5.80 GHz
GPU 1: NVIDIA GeForce RTX 5090 [Discrete]
GPU 2: Intel UHD Graphics 770 @ 1.65 GHz [Integrated]
Memory: 26.69 GiB / 62.55 GiB (43%)
Swap: 4.55 GiB / 16.00 GiB (28%)
Disk (/): 41.39 MiB / 41.39 MiB (100%) - overlay [Read-only]
Disk (/etc): 644.56 GiB / 1.82 TiB (35%) - btrfs
Disk (/var/mnt/games): 1.66 TiB / 1.83 TiB (91%) - ext4
Disk (/var/mnt/sata2tb): 260.18 GiB / 1.79 TiB (14%) - ext4
Local IP (enp5s0): 192.168.0.214/24
Locale: en_US.UTF-8
Unknown file version (screamer/Content/Paks/pakchunk0-Windows.pak) Screamer (2814990)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9623.
@NyraHema posted on 2026-03-27T20:34:01:
After a few minutes of playing the game, it eventually after 4-5 minutes will stop and show the error
Attempted validation of game files, attempted switching to Proton Experimental, and attempted switching off and on again
Playing the game for a few minutes causes the error message to come up at which point the game closes when clicking OK.
@mirfalltnixein nvidia 396.54 is from 2018, your log shows your actual driver version is 595.45.4.
Oh whoops no idea how I came up with that number. Yep my driver is up to date.
Given your description I'm guessing your crash comes before an early music video gets a chance to play, is that correct? If so, can you try running this in your terminal
steam steam://unlockh264/and try to play the game again?
The first intro video actually plays just fine. The game plays a video file, shows a few logos and then tries to load the main menu. That is the loading screen that fails.
I tried the game on a rx 9070 with mesa 26.0.3, linux 6.19.8, and proton 10 and experimental, and the only issue I've run into so far is that battleeye will sometimes fail and prevent the game from running, but closing it and opening the game again will allow it to work again.
Yes I can provide a bit more info after looking into it deeper.
I also ran into the exact same problem with Toxic Commando. I realized that the proton log for both games showed a failure to use Kerberos and NTLM:
1638.191:020c:0210:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
1638.192:020c:0210:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
After googling, my understanding is that this is an issue with EasyAntiCheat, however for some reason only I and veeery few others online ran into this problem. I tried verifying and reinstalling the EAC runtime, deleting compatdata, etc. But I had done all of that before, including just fully formatting everything and starting again with cachyos and bazzite. The games also started just fine on my partners Fedora PC with a 2070 Ti.
In the end I resolved this for myself by getting an RX 9070 XT. Installed it a few hours ago and now everything works perfectly, without any other changes to hardware or software.
Someone else reported the same issue in Toxic Commando here: https://github.com/ValveSoftware/Proton/issues/9536
Interestingly, they are on an AMD card so it's not actually nvidia exclusive.
@gshipley at least knowing your gpu vendor hints towards something to look at, you were both on nvidia, so there's a chance it's related to that.
@mirfalltnixein those lines are red herrings, those are normal to appear even in working games. The fact it works just by swapping the gpu reinforces the possibility it's related to nvidia
@mirfalltnixein nvidia 4060 mobile, 619.9, nvidia 590.48, proton 10. For the tournament part I played until I got to the tutorial which, if I understood what you wrote, you were crashing before this point.
I've also been playing on arcade mode without crashing @NyraHema
@simifor yes, I was crashing on the step before reaching the main menu. I can't re-test anymore though as I sold my 5070 Ti, sorry.
ge-proton10-34x1 2026-03proton experimentalx1 2026-03PROTON_LOGx1 2026-03
System Information
I confirm:
Symptoms
The game goes through the intro videos and crashes around 10-18% on the loading screen. An error box pops up with the message "fatal error!"
Proton Log:
For some reason, when enabling PROTON_LOG, the game does not launch but proton spams insane amounts of logs (4gb in less than a minute). The failure to launch at all ONLY happens when logging proton.
I know this is technically out of scope here but proton-cachyos manages to launch and log the game, and since proton-cachyos with logging crashes in the same way as official proton without logging, I am including this log here for you:
steam-2814990.log
Reproduction
Happens to me reliably on every launch. (without PROTON_LOG)