Hello @nmds98f9sv-coder, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/4834#issuecomment-5516480032.
proton experimentalx1 2026-09proton hotfixx1 2026-09MANGOHUD=0`)x1 2026-09PROTON_ENABLE_HDR=1x1 2026-09PROTON_ENABLE_WAYLAND=1x1 2026-09PROTON_LOGx1 2026-09PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%x1 2026-09SteamDeck=1 %command%x1 2026-09
Compatibility Report
System Information
I confirm:
steam-1465360.log
Symptoms
SnowRunner reliably hangs and crashes before or immediately at the main menu (background renders, but no UI elements ever appear, then the process dies). Reproducible across every Proton version tested: Proton Experimental (multiple builds over several weeks, including the current one as of this report), Proton-CachyOS latest, GE-Proton 11, Proton 10, Proton Hotfix. Also reproduces after updating the game to Patch 43.0.
The game runs fine on Steam Deck (same Steam account/library), so this appears specific to desktop Linux and/or RDNA4 GPUs.
The attached PROTON_LOG shows a consistent pattern across every crash, regardless of Proton or game version:
fixme:d3dkmt:NtGdiDdDDIQueryStatistics (...): stubhundreds/thousands of times in a tight loop.RtlpWaitForCriticalSection ... wait timed out ... blocked by <spinning thread>, retrying (60 sec)..NET-side exceptions follow:System.ComponentModel.Win32Exception: Invalid window handle(repeated).dbghelp:SymCleanup this process has not had SymInitialize() called for it!suggests a crash reporter (possibly EOS SDK) attempting to generate a dump and failing.Reproduction
Additional information
Already ruled out during troubleshooting:
MANGOHUD=0)amdgpuring timeout/reset/fault entries in kernel log at time of crash)SteamDeck=1 %command%launch flagPROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%(crash timing varies slightly but issue persists)Issue has been present since the system was first assembled and CachyOS installed (~3 weeks ago), not a regression from a specific update on my end.
Transparency note: I used an AI tool (Claude, Anthropic) to help investigate this issue and draft this report. All technical details (log excerpts, versions, test results) were manually verified by me against my own system and logs before submitting.