Hello @sashakosti, a GPU hang reads like something that should also be mentioned to your video driver vendor. I wouldn't put much weight on that invalid opcode since it's well after something's already gone awry on the GPU side.
Setting the game's launch options to --rendering-driver opengl3 might be interesting to test as a workaround (from https://steamcommunity.com/app/2868840/discussions/0/802341195824173232/#c802341528343322086).
Setting the game's launch options to
--rendering-driver opengl3might be interesting to test as a workaround (from https://steamcommunity.com/app/2868840/discussions/0/802341195824173232/#c802341528343322086).
oh god, that completly solved it for me, thank you very much!
MESA_LOADER_DRIVER_OVERRIDE=crocusx1 2026-03PROTON_USE_WINED3D=1x1 2026-03
Compatibility Report
System Information
I confirm:
Symptoms
The game consistently crashes to desktop during the initial loading screen or in the main menu.
The crash is accompanied by a GPU HANG and a trap invalid opcode in the kernel logs (dmesg).
Error signature:
[ 5582.242237] i915 0000:00:02.0: [drm] GPU HANG: ecode 8:1:8ed9fff2, in SlayTheSpire2 [11457]
[ 5582.243293] i915 0000:00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0
[ 5582.243366] i915 0000:00:02.0: [drm] SlayTheSpire2[11457] context reset due to GPU hang
[ 5582.568572] traps: SlayTheSpire2[11457] trap invalid opcode ip:1371389 sp:7ffe1d308db0 error:0 in SlayTheSpire2[f71389,407000+347a000
The instruction pointer (ip:1371389) is consistent across all crash instances, suggesting an unsupported CPU instruction (possibly related to AVX2/BMI2 or modern compiler optimizations) being executed on the Broadwell architecture.
Reproduction
Workarounds tested (none worked):