Resident Evil 2
Hello @osheepoh, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
steam-883710.log
Done, both in OP and here.
I'm having trouble with constant random freezing of this title on my Steam Deck. At random points it will freeze, go to a black screen, come back (but frozen with audio still playing), and then it restarts my system. Currently running it with ProtonGE-53, but have also tried the latest Proton for the Deck.
I'm having this issue with all RE Engine titles as well.
RE2 crashes after 5/15 minutes on Proton 7, Proton 8 and Proton 8 Experimental
Arch Linux here, happens in my RX 560 and RX 6600
Hello @kassindornelles, this is more of a blind guess than anything, but can you check how the game behaves with a 6.1.x kernel instead of 6.2?
Hello @kassindornelles, this is more of a blind guess than anything, but can you check how the game behaves with a 6.1.x kernel instead of 6.2?
I can confirm that going from linux 6.2.x to 6.1.x fixes it
I've been suffering that issue since i bought the game 4 months ago. Crashed using mesa 22.3 / 23.0 & 6.1 / 6.2 kernels.
Game never crashes now using mesa 23.1 and kernel 6.3.
Archlinux / Navi 22.
Got another crash on 6.1.x too, but the crash takes way more time to happen now
Having a similar issue as OP except for Resident Evil 7, cinematics won't play. I install wmp11 through protontricks and then the game won't run when launched. Once I delete compatdata for the game then I can launch it again just fine.
Just tried this with Resident Evil 2 as well and same result.
PROTON_LOG=+module,+vulkan %command%
Mesa 23.1.7
Driver: AMD AMD Radeon RX 6600 (navi23, LLVM 16.0.6, DRM 3.52, 6.4.15-200.fc38.x86_64)
steam-883710.zip
Here are eight crash logs I saved from some weeks ago. I've been having the same crash problem fairly regularly since then while trying to reproduce GPU hangs, but I also added a fresh one from today just in case. Let me know if there's any other kind of log info I can try to fetch.
- GPU: RX 7600
- Kernels: 6.4.7-arch1-1 - 6.5.3-arch1-1
- RADV 23.1.4 - 23.1.7
Forgot to include the vkd3d logs, so here are those as well. Also tested 6.1.53-1-lts and 6.3.7-1-amd-staging-drm-next-git-g3a2fb905145e, so I also included those logs.
RE2_crash_logs.zip
Found other issues regarding RE2 crashes, but they have all been closed, and whatever in-game settings I tried to tweak, so far hasn't helped. Still struggling to find the cause.
For me I can reproduce the crash constantly in a particular area of the game (sewer area, "red tunnel" with the 3 G-Adults, for those who are familiar with the game), either when passing a certain point or returning.
I have absolutely no knowledge about hardware related stuff, drivers or proton, so even though I can see some errors in logs, I am completely in the dark as to how to interpret them; is it a software error, is it a hardware error, beats me.
What's weird that this is the only RE Engine based game I have this sort of problem with.
As far as I can tell from the Steam overlay, nothing is overheating, plenty of reserve RAM, plenty of reserve VRAM.
basic info about my machine:
OS: Garuda Linux x86_64
Kernel: 6.19.6-zen1-1-zen
CPU: AMD Ryzen 7 5800X3D (16) @ 4.552GHz
GPU: AMD Radeon RX 9070 XT
Memory: 3894MiB / 31995MiB
I enabled PROTON_LOG=1 for this game, and in steam log I see this at the end
639.462:0140:0298:trace:seh:RtlUnwindEx handler 00006FFFFC8B6DE0 returned 1
639.462:0140:0298:trace:seh:RtlRestoreContext calling consolidate callback 00006FFFFC8BA47C (rec=00000001100CE1A0)
639.462:0140:0298:trace:seh:RtlRestoreContext returning to 00006FFFFC329C91 stack 00000001100CF7E0
639.463:0140:0298:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 000000006b720080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
639.463:0140:0298:err:vkd3d-proton:vkd3d_memory_transfer_queue_wait_semaphore: Failed to wait for timeline semaphore, vr -4.
639.463:0140:0298:err:vkd3d-proton:vkd3d_memory_transfer_queue_wait_semaphore: Failed to wait for timeline semaphore, vr -4.
639.463:0140:0298:err:vkd3d-proton:vkd3d_memory_transfer_queue_wait_semaphore: Failed to wait for timeline semaphore, vr -4.
639.463:0140:0404:err:vkd3d-proton:d3d12_command_queue_wait_idle: Failed to wait for virtual queue idle, vr -4.
639.463:0140:0404:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 000000006b720080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
648.163:00f4:040c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
648.180:0030:0410:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
648.181:0030:0414:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
648.181:0030:0418:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
648.182:0030:041c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
648.182:0030:0420:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 66295 != 66294, skipping destruction (fork without exec?)
I also did journalctl -b -l and found this - lots of amdgpu logs at the end and most of them are red, which means errors
mar 11 21:46:29 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: Dumping IP State
mar 11 21:46:29 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: Dumping IP State Completed
mar 11 21:46:29 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
mar 11 21:46:29 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
mar 11 21:46:29 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=549880, emitted seq=549882
mar 11 21:46:29 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: Process re2.exe pid 66375 thread vkd3d_queue pid 66452
mar 11 21:46:29 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: Starting gfx_0.0.0 ring reset
mar 11 21:46:31 kvhost systemd[1]: Started Daily Cleanup of Snapper Snapshots.
mar 11 21:46:31 kvhost systemd[1]: Starting DBus interface for snapper...
mar 11 21:46:31 kvhost systemd[1]: Started DBus interface for snapper.
mar 11 21:46:31 kvhost systemd-helper[79558]: Running cleanup for 'root'.
mar 11 21:46:31 kvhost systemd-helper[79558]: Running number cleanup for 'root'.
mar 11 21:46:31 kvhost systemd-helper[79558]: Running timeline cleanup for 'root'.
mar 11 21:46:31 kvhost systemd-helper[79558]: Running empty-pre-post cleanup for 'root'.
mar 11 21:46:32 kvhost systemd[1]: snapper-cleanup.service: Deactivated successfully.
mar 11 21:46:32 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: MES(1) failed to respond to msg=RESET
mar 11 21:46:32 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: failed to reset legacy queue
mar 11 21:46:32 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: reset via MES failed and try pipe reset -110
mar 11 21:46:32 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: The CPFW hasn't support pipe reset yet.
mar 11 21:46:32 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: Ring gfx_0.0.0 reset failed
mar 11 21:46:32 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset begin!. Source: 1
mar 11 21:46:33 kvhost coolercontrold[3831]: Failed to disable Zero RPM Mode for amdgpu: Error applying 0 to Zero RPM Enable: Device or resource busy (os error 16)
mar 11 21:46:33 kvhost coolercontrold[3831]: Error applying Graph/Mix Profile calculated duty - Error settings PMFW fan duty of 30 on amdgpu - Error applying '0 25 30' to Fan Curve: Device or resource busy (os error 16)
mar 11 21:46:33 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: MES(1) failed to respond to msg=INVALIDATE_TLBS
mar 11 21:46:36 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: MES(1) failed to respond to msg=INVALIDATE_TLBS
mar 11 21:46:40 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: failed to suspend display audio
mar 11 21:46:43 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
mar 11 21:46:43 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: failed to unmap legacy queue
mar 11 21:46:46 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
mar 11 21:46:46 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: failed to unmap legacy queue
mar 11 21:46:48 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
mar 11 21:46:48 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: failed to unmap legacy queue
mar 11 21:46:51 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
mar 11 21:46:51 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: failed to unmap legacy queue
mar 11 21:46:52 kvhost kdeconnectd[5596]: No uuids found for "D4:8A:3B:11:EE:17"
mar 11 21:46:54 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
mar 11 21:46:54 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: failed to unmap legacy queue
mar 11 21:46:56 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
mar 11 21:46:56 kvhost kernel: amdgpu 0000:0c:00.0: amdgpu: failed to unmap legacy queue
mar 11 21:46:57 kvhost kernel: [drm:gfx_v12_0_hw_fini [amdgpu]] ERROR failed to halt cp gfx
@kristaps777 Sounds like this issue we're currently looking into here https://gitlab.freedesktop.org/mesa/mesa/-/issues/14812
@kristaps777 Sounds like this issue we're currently looking into here https://gitlab.freedesktop.org/mesa/mesa/-/issues/14812
Thank you, I did not come across that one, will make sure to follow it.
@kisak-valve I just tested this with Proton Experimental and I'm getting the pre-rendered videos wit the "test" footage as shows OP. I have shader downloading and pre-compilation enabled. Am I missing something? The game has the verified tag for Steam Deck
@kisak-valve I just tested this with Proton Experimental and I'm getting the pre-rendered videos wit the "test" footage as shows OP. I have shader downloading and pre-compilation enabled. Am I missing something? The game has the verified tag for Steam Deck
I think only Proton GE has a solution for this. Most of my games run fine on Experimental, but for RE2 specifically I use GE.
@kisak-valve I just tested this with Proton Experimental and I'm getting the pre-rendered videos wit the "test" footage as shows OP. I have shader downloading and pre-compilation enabled. Am I missing something? The game has the verified tag for Steam Deck
I think only Proton GE has a solution for this. Most of my games run fine on Experimental, but for RE2 specifically I use GE.
Pretty sure Proton GE can fix it, but either I'm doing something wrong or the game shouldn't be verified?
@kisak-valve I just tested this with Proton Experimental and I'm getting the pre-rendered videos wit the "test" footage as shows OP. I have shader downloading and pre-compilation enabled. Am I missing something? The game has the verified tag for Steam Deck
I think only Proton GE has a solution for this. Most of my games run fine on Experimental, but for RE2 specifically I use GE.
Pretty sure Proton GE can fix it, but either I'm doing something wrong or the game shouldn't be verified?
Well, except for the videos, the game runs perfectly fine on Experimental. Also, on Experimental, it does not have that sewer level crash, I tested it.
I don't know who at Valve checked this, bu just got a 2GB preloaded shaders update and videos are working again. Thanks a lot :D
Any idea as to what this is?
I noticed Experimental just got an update and boom, this pops up when attempting to launch the game.
UPDATE
I figured out the cause.
I use .sh files in launch options just to organize environmental variables better.
The variable that was causing the error is an enabler for loseless scaling.
#!/bin/bash
export WINEDLLOVERRIDES="d3dcompiler_47=n;dxgi=n,b;dinput8=n,b"
export PROTON_ENABLE_WAYLAND=1
export PROTON_ENABLE_HDR=1
#export DXVK_HDR=1
#export ENABLE_HDR_WSI=1
#export LSFG_PROCESS="common" <--- this line caused the issue
exec "$@"
My game crashes when getting the garage door key with:
wine: Call from 00006FFFFFF9C100 to unimplemented function MFPlat.DLL.MFCreateDXGIDeviceManager, aborting
pid 20978 != 20977, skipping destruction (fork without exec?)
Game Recording - game stopped [gameid=883710]
Hello @Sur3, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Additionally, it'd be best to also share a save file close to where the issue happens
I cant find the save file in the filesystem but here is the proton_log:
steam-883710.log
trace:loaddll:build_module Loaded L"S:\\common\\RESIDENT EVIL 2 BIOHAZARD RE2\\MFPlat.DLL" at 00006FFFFC1C0000: native in your Proton log is suspicious. It doesn't look like that's game bundled or from Proton.
@Sur3 as for the save file, you look for your main steam library, there'll be a userdata folder, ~/.local/share/Steam/userdata/<userid>/883710/remote that'll haev your save file
trace:loaddll:build_module Loaded L"S:\\common\\RESIDENT EVIL 2 BIOHAZARD RE2\\MFPlat.DLL" at 00006FFFFC1C0000: nativein your Proton log is suspicious. It doesn't look like that's game bundled or from Proton.
Thanks I had a look at that file it was created on 08.10.2023 (probably when I installed the game) and it's version is 12.01.2018. So probably some outdated file from when the game came out. After removing that file the game seems to work again.
Proton versions
proton experimentalx4 2026-03
Launch options
PROTON_LOG=1x3 2026-06DXVK_HDR=1x1 2026-06PROTON_ENABLE_HDR=1x1 2026-06PROTON_ENABLE_WAYLAND=1x1 2026-06WINEDLLOVERRIDES="d3dcompiler_47=n;dxgi=n,b;dinput8=n,b"x1 2026-06PROTON_LOG=+module,+vulkanx1 2023-09
DLLs
mfplat.dllx3 2026-06
Error codes
0x887a0005x1 2026-03
Compatibility Report
System Information
Symptoms
Pre-rendered citnematics, such as the opening one with the trucker don't work, instead I get a calibration screen as seen below:
with the bottom-right corner being white noise. This screen shows for a couple of seconds(I'd assume while the game is loading in the background) while playing the audio, then the game starts and in-engine cutscenes work without issues. I've tried adding wmp11 through protontricks but it didn't solve the issue.
steam-883710.log