Also, non blocking and pressing OK will make the game just run fine, but this message appears on boot.
Game started crashing for me when interacting with the save spot after the patch on DX12. DX11 seems to work fine.
@zr00da Are you able to provide a Proton log of a crash? Just add PROTON_LOG=1 %command% to the game's launch options and
attach the steam-$APPID.log that'll appear in your users home folder as a file.
Also when you say save spot what do you mean more specifically?
It seems I cannot actually, for some reason it doesn't crash anymore when I'm using the same save spot (the red sword) that crashed before everytime (~5 times in a row until I switched to DX11). I'll keep playing with DX12 and post the log if/when it happens again.
Game crashed for me with this error. I never know where to report this issues.... Here? VKD3D? Mesa? AMD Drm?
mar 28 23:46:38 artorias kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=13051563, emitted seq=13051565
mar 28 23:46:38 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process BBQ-Win64-Shipp pid 93047 thread vkd3d_queue pid 93212
mar 28 23:46:38 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
mar 28 23:46:38 artorias kernel: [drm:gfx_v11_0_bad_op_irq [amdgpu]] *ERROR* Illegal opcode in command stream
mar 28 23:46:40 artorias kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=RESET
mar 28 23:46:40 artorias kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
mar 28 23:46:40 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset failure
mar 28 23:46:40 artorias kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
mar 28 23:46:44 artorias kernel: amdgpu 0000:03:00.0: amdgpu: failed to suspend display audio
mar 28 23:46:46 artorias kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
mar 28 23:46:46 artorias kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
mar 28 23:46:47 artorias kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
@kisak-valve Do you know where to report this kind of issues? Keeps happening but after playing a while, not in the same spot.
Hello @alosarjos, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
kernel: [drm:gfx_v11_0_bad_op_irq [amdgpu]] *ERROR* Illegal opcode in command stream hints that the video driver asked the video card hardware to do something it doesn't support. That's something for the video driver devs to ponder.
Thanks, https://gist.github.com/alosarjos/8b7f0bb1300ae3bad3d6d69025739309#file-gistfile1-txt-L228-L242 hints that the 64 bit Vulkan render path on your system isn't healthy. Can you try disabling or removing MangoHUD and check if that helps at all?
Thanks, https://gist.github.com/alosarjos/8b7f0bb1300ae3bad3d6d69025739309#file-gistfile1-txt-L228-L242 hints that the 64 bit Vulkan render path on your system isn't healthy. Can you try disabling or removing MangoHUD and check if that helps at all?
Sure, will give it a try and let you know if it crashes again
@kisak-valve Same error with Magohud disabled:
Log:
mar 29 14:50:57 artorias kernel: umip_printk: 177 callbacks suppressed
mar 29 14:50:57 artorias kernel: umip: BBQ-Win64-Shipp[20127] ip:148b8f1e3 sp:b9b3b8: SGDT instruction cannot be used by applications.
mar 29 14:50:57 artorias kernel: umip: BBQ-Win64-Shipp[20127] ip:148b8f1e3 sp:b9b3b8: For now, expensive software emulation returns the result.
mar 29 14:52:06 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
mar 29 14:52:06 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
mar 29 14:52:06 artorias kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=3161960, emitted seq=3161962
mar 29 14:52:06 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process BBQ-Win64-Shipp pid 20127 thread vkd3d_queue pid 20238
mar 29 14:52:06 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
mar 29 14:52:06 artorias kernel: [drm:gfx_v11_0_bad_op_irq [amdgpu]] *ERROR* Illegal opcode in command stream
mar 29 14:52:08 artorias kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=RESET
mar 29 14:52:08 artorias kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
mar 29 14:52:08 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset failure
mar 29 14:52:08 artorias kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
mar 29 14:52:12 artorias kernel: amdgpu 0000:03:00.0: amdgpu: failed to suspend display audio
mar 29 14:52:14 artorias kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
mar 29 14:52:14 artorias kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
mar 29 14:52:15 artorias kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
mar 29 14:52:15 artorias kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000).
mar 29 14:52:15 artorias kernel: [drm] VRAM is lost due to GPU reset!
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0xa700000 from 0x83e0000000 for PSP TMR
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x00505300 (80.83.0)
mar 29 14:52:15 artorias kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
mar 29 14:52:16 artorias kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
mar 29 14:52:16 artorias kernel: [drm] DMUB hardware initialized: version=0x07002D00
Current Steam Runtime gist: https://gist.github.com/alosarjos/6ea48e6d09a148c3e77c36e8fdb11d94
Been playing for a few hours on DX11 mode, 0 issues so far. Maybe the issue is related to VKD3D?
@alosarjos I got past yetuga (the spiky yeti) on my rx 6600 without any hangs or crashes, how often were you getting hangs with dx12? what graphics settingare you using?
All highest settings, no upscaling. I can't remember the exact levels it was happening but rather seemed to be every 20 - 30 minutes or so. I've been playing on Dx11 since then and 0 issues. Maybe something on mesa sending invalid params on RDNA3?
I ran this game without issues at all on my RX 7900 XTX until I'd played around 15 hours. Then I got my first crash. Didn't think that much about it, but after that it started getting more and more frequent, and now I can't even get half an hour in the game without a full GPU crash. DX11 and DX12 make no difference, maxed settings otherwise. This is what I can see in my journal:
`Apr 09 22:23:21 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Apr 09 22:23:21 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Apr 09 22:23:21 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=6016850, emitted seq=6016852
Apr 09 22:23:21 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process BBQ-Win64-Shipp pid 57824 thread dxvk-submit pid 57934
Apr 09 22:23:21 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Apr 09 22:23:23 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=RESET
Apr 09 22:23:23 daniel-manjaro kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] ERROR failed to reset legacy queue
Apr 09 22:23:23 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset failure
Apr 09 22:23:23 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
[...a bunch of other applications also crashing]
Apr 09 22:23:25 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
Apr 09 22:23:25 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
Apr 09 22:23:25 daniel-manjaro kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
`
And then I have to reset my system. The same thing happens with both DXVK (this printout is from when I ran DX11) and VKD3D. A bug in the AMDGPU drivers?
Other info:
Kernel: 6.14.1-1-MANJARO
Mesa: 25.0.3-1
Proton 9.0-4
I recommend putting system info also, mesa version, kernel, Proton....
I recommend putting system info also, mesa version, kernel, Proton....
Sorry, I was gathering info to add in an edit, you were too fast :) Added proton version too, forgot that...
Maybe give it a try using Proton Experimental? Haven't had an issue with it + Dx11 mode
Maybe give it a try using Proton Experimental? Haven't had an issue with it + Dx11 mode
Tried that and the game did last an hour without crashing...but we'll see if it sticks... :)
Maybe give it a try using Proton Experimental? Haven't had an issue with it + Dx11 mode
Tried that and the game did last an hour without crashing...but we'll see if it sticks... :)
Nope, it did not stick. Had another hard GPU crash just now with Experimental + DXVK. Same error.
I'm not sure whats going on now, but after maybe 15 hours without a single crash, now it's crashing a lot, with Dx11 :S
abr 12 14:58:10 artorias kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=3183825, emitted seq=3183827
abr 12 14:58:10 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process BBQ-Win64-Shipp pid 6350 thread dxvk-submit pid 6455
abr 12 14:58:10 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
abr 12 14:58:12 artorias kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=RESET
abr 12 14:58:12 artorias kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
abr 12 14:58:12 artorias kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset failure
abr 12 14:58:12 artorias kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
abr 12 14:58:16 artorias kernel: amdgpu 0000:03:00.0: amdgpu: failed to suspend display audio
abr 12 14:58:18 artorias kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
abr 12 14:58:18 artorias kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
abr 12 14:58:18 artorias kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Maybe something on mesa 25.0.3?
Have the same problem on 7900XTX+5950X+Proton Experimental. In DX12 mode so vkd3d-proton. GPU freeze for a couple of seconds and then crash with the same:
amdgpu 0000:0c:00.0: amdgpu: Process information: process BBQ-Win64-Shipp pid XXXX thread vkd3d_queue pid XXXX
[drm:gfx_v11_0_bad_op_irq [amdgpu]] *ERROR* Illegal opcode in command stream
That was on 6.14.0 and 6.14.1 kernels, 20250311 linux-firmware and mesa 25.0.3.
For me it happened mostly in boss fights. Reese boss fight crashed like 10 times in a row, one time even caused full hard reset. Also most of the game I played on different system with 6700XT+7950X and there are for over 40 hours I crashed only once (at inventory which is supposedly game bug which was fixed in the recent patch). Though there I played on 1080p with 60fps limit due to old monitor so it was less demanding on GPU.
Tried to downgrade kernel to 6.12.23, didn't help. Downgraded mesa to 24.3.4 and linux-firmware to 20250109 and fought 3phases Ozma for a couple of hours without any crashes. After that upgraded to 6.14.2 kernel, linux-firmware 20250408, and mesa 25.0.3 again. No crashes so far for hours but maybe I'm just lucky.
I noticed that in cutscenes, some characters do not have mouth movements. Im testing on steam deck oled on the stable branch. Ive tested on Proton Experimental and Proton 9.0-4.
@singha95 can you point out any early videos where the issue is visible?
@simifor
Elamein mouth does not move, Phraugh Village, after defeating the Volbaino (I noticed after the boss fight is done, but it could also be before) (Third boss I believe)
Rangkus mouth does not move, in Palemion Citadel. This is an interesting case, cus the other characters in the cutscene are fine, but Rangkus is not.
@simifor
I need to look into this more, but It could be related to Medium preset, found another way, to easily reproduce.
Go to the crevice, Talk to Daphrona / Elamein, their mouths dont move.
With the High it seems to work in Proton.
Edit: I double checked this, this was the issue. Using the High preset fixes the issue, even in cutscenes, in proton.
@singha95 So just to make sure I'm understanding properly, in this place you're seeing this character not move her mouth, right?
@simifor That is the correct place.
I have also found the exact setting causing this. It the Mesh, being set to low. This does not happen in Windows. Tested on Proton 9.0-4, Proton Experimental, ( GE-Proton10-10 ). Both DX11 and DX12 does the same thing.
@singha95 Looks like this is a specific change from the developers.
On my amd desktop it doesn't happen, but on my deck it does, so I ran it on desktop with SteamDeck=1 and then it happened here as well. So it looks like the devs are checking for deck itself and then disabling some things for it, so it's not really a proton issue, but a change made by the developer for specific devices.
The EXACT same thing has been happening to me. No one else online is reporting this, but with EVERY DX12 game it crashes then boots me back to the login screen. I'm also getting the same errors as OP! Hopefully someone can finally look at this issue and fix it, so i can play DX12 games again without any crashing!
The EXACT same thing has been happening to me. No one else online is reporting this, but with EVERY DX12 game it crashes then boots me back to the login screen. I'm also getting the same errors as OP! Hopefully someone can finally look at this issue and fix it, so i can play DX12 games again without any crashing!
I'm trying to see if limiting the framerate to 60 might fix the problem. Doesn't make sense as to why this would do anything, but so far it's helping. Will update after more testing...
@codewizkid what gpu and drivers are you using? what graphics settings are you using in the game? how often does it crash? does lowering graphics settings help prevent the issue?
You can grab steam logs by adding this as launch parameter on steam: PROTON_LOG=1 %command%. This will generate a file called steam-2680010.log in your home folder.
After the game crashes, and before yo reboot, you can get kernel logs by running this in your terminal: sudo desmg, you can store it into a text file by doing sudo dmesg > dmesg.log
he first berserker Kazan - Steamdeck launch failure
Issue transferred from https://github.com/ValveSoftware/Proton/issues/10100.
@8rgvgz7z9c-sudo posted on 2026-08-28T10:30:23:
Compatibility Report
Name of the game with compatibility issues: The First Berserker: Khazan
Steam AppID of the game: 2680010
System Information
Symptoms
The game no longer launches on Steam Deck.
When pressing Play, Steam briefly shows that the game is starting, but the game does not launch and returns to the Steam library.
The issue occurs with multiple Proton versions:
I also verified the integrity of the game files, but this did not resolve the issue.
I additionally tested:
PROTON_NO_ESYNC=1 %command%
with no change.
Reproduction
Proton log
The attached steam-2680010.log shows an EXCEPTION_ACCESS_VIOLATION involving mf.dll shortly after Vulkan initialization.
Relevant error:
EXCEPTION_ACCESS_VIOLATION
mf.dll + 0x34243
The attached Proton log was generated using:
PROTON_LOG=1 %command%
Additional information
The game previously worked correctly on this Steam Deck, so this appears to be a regression or compatibility issue rather than an initial installation problem.
Game files have been verified through Steam.
@8rgvgz7z9c-sudo The game is launching fine on my steam deck with steamos stable, proton 11 and experimental.
If you are on either steamos beta/preview or main, it'd be good to point it out. Otherwise I'd look into verifying game files, if that changes nothing, I'd try cleaning the game's prefix, if you have developer options enabled then selecting the cog icon in the game's library page will give you: Developer > Delete proton files. Then the next time you start the game, it'll recreate the prefix, it'd be good to know if this changes anything on your end.
proton experimentalx8 2026-08proton 9.0-4x3 2025-08ge-proton10-10x1 2025-08PROTON_LOG=1x3 2026-08PROTON_NO_ESYNC=1x1 2026-08PROTON_NO_ESYNC=1 %command%x1 2026-08mf.dllx1 2026-08
Compatibility Report
System Information
I confirm:
Symptoms
Game runs without major issues but Steam shows as compatible with my DualSense, but game won't recognize the gamepad and I have to enable Steam Input (Using bluetooth)