ah proton log didnt get added for some reason, but its in the drive link too
edit: i realize my mesa version is bit old. i'll update and see if it still reproduces

updated mesa to latest available in arch repos. GPU still crashes.
[ 173.395274] i915 0000:0d:00.0: [drm] GPU HANG: ecode 12:1:84dfd7f7
[ 173.395278] i915 0000:0d:00.0: [drm] GPU error state saved to /sys/class/drm/card1/error

You can run with export ANV_QUEUE_OVERRIDE=c=0,b=0 to rule out transfer/compute queue issues.

DXVK_CONFIG="dxvk.enableDescriptorBuffer=True" worked around hang in wow

apitrace caused gpu hang too. (assuming i did it correctly)

alchemist cards use i915 by default, battlemage+ uses xe by default

You can run with export ANV_QUEUE_OVERRIDE=c=0,b=0 to rule out transfer/compute queue issues.

Still crashing.

Sorry. Made a mistake. Proton 11 in steam is crashing too. Proton 10 is last good version of proton that's working on steam. xe and i915 behaved identically.

if it helps:

4b0795359f470804a53fa3b7852e47bc9b72633d is the first bad commit
commit 4b0795359f470804a53fa3b7852e47bc9b72633d
Author: Robin Kertels [email protected]
Date: Thu Sep 11 00:45:40 2025 +0200

[d3d9] Enable FF ubershaders by default

:D

src/d3d9/d3d9_options.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

edit: i realize that wasnt prob useful so

f5b82033ede38adddb9c51c70410a26a3bdab648 is the first bad commit
commit f5b82033ede38adddb9c51c70410a26a3bdab648 (HEAD)
Author: Robin Kertels [email protected]
Date: Wed Sep 10 19:10:36 2025 +0200

[d3d9] Hook up fixed function vertex ubershader

Same commit that broken a bunch of older Intel GPUs.

The main difference between legacy & descriptor_buffer/descriptor_heap is the update-after-bind being required in the later extensions.

We'll try to promote UBOs to the HW fast path if possible. If there is a bug in dxvk in that area that could explain it.

One way to can test that hypothesis is running with export ANV_DEBUG=bindless, this will prevent any promotion on legacy descriptors. If it works wit that option, it means there is likely a bug somewhere in dxvk.

One way to can test that hypothesis is running with export ANV_DEBUG=bindless, this will prevent any promotion on legacy descriptors. If it works wit that option, it means there is likely a bug somewhere in dxvk.

Same behaviour.
There's easier reproduce way to reproduce too: either have "Full Screen Glow Effect" turned on or "Hardware Cursor" off. Game settings can be modified without having to log into any account. Will cause gpu to hang nearly instantly.

proton log with VVL:
https://www.upload.ee/files/19484953/steam-14374311965495394304.log.html

Yeah, hang occurs with MSAA off too.

I tried it on windows too with DXVK. There it only seems to crash the game intermittently. Like 1/10 loading into game world ends with a crash.

err: Exception on CS thread!
err: Failed to allocate descriptor set: VK_ERROR_OUT_OF_POOL_MEMORY_KHR

Linux trace played fine under windows. Made 2 traces under windows: https://drive.google.com/drive/folders/19mCkqWO0cPvkIwrZ2y4WMkZXrbyuoqn_ they crash under linux.

I suppose it's just some weird hardware bug?

I faced the same problem in D3D9 games(TES IV Oblivion, Silent Hill 2) after upgrading to 3.0, with DXVK outputting infinite err: DxvkSubmissionQueue: Command submission failed: VK_ERROR_DEVICE_LOST when starting/loading the game.

Jun 30 15:40:48 Arch-PC kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
Jun 30 15:40:48 Arch-PC kernel: i915 0000:00:02.0: [drm] sh2pc.exe[10208] context reset due to GPU hang
Jun 30 15:40:48 Arch-PC kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dfffff, in sh2pc.exe [10208]
Jun 30 15:40:48 Arch-PC kernel: i915 0000:00:02.0: [drm] GPU error state saved to /sys/class/drm/card1/error

the earlier advice to run with DXVK_CONFIG="dxvk.enableDescriptorBuffer=True" worked!.

glxinfo -B
Device: Mesa Intel(R) HD Graphics 530 (SKL GT2) (0x1912)
Version: 26.1.3

Any useful logs I can post?

EDIT: For some reason, it seems to happen only in D3D9, D3D11 games like Skyrim Anniversay Edition work fine.
EDIT2: I tried out https://github.com/doitsujin/dxvk/actions/runs/28396913460 without any parameters, didn't work.

@Erwin-Iosef Just curious, if you try proton-ge (you can easily install it with 'protonup-qt'), does it still gpu hang or just crash with wine error in proton logs?

@understyx Tried it, I don't think it works for regular wine, I don't use steam much as well.
Edit: The bug I produced was with regular wine + DXVK.

warn:  D3D8WrappedObject::QueryInterface: Unknown interface query
warn:  22222222-1c77-4d40-b0cf-98fefdffffff
warn:  D3D8WrappedObject::QueryInterface: Unknown interface query
warn:  11111111-1c77-4d40-b0cf-98fefdffffff
warn:  D3D8WrappedObject::QueryInterface: Unknown interface query

@understyx do you get this message spammed when you run with DXVK_CONFIG="dxvk.enableDescriptorBuffer=True"?
EDIT:Nvm, it seems it's when d3d9 runs in d3d8 compat mode.

@understyx Tried it, I don't think it works for regular wine, I don't use steam much as well. Edit: The bug I produced was with regular wine + DXVK.

yeah all good. just was curious since i don't get as many gpu hangs with that. (is very rng though)

In the end I guess it doesn't matter that much either way. With mesa 26.2 ANV will enable descriptor heap by default and that should work around this too? I guess I'll close the issue when that happens.

Sorry I couldn't help, and yeah hopefully I suppose, looks like a tricky bug for the devs.

minimal vibecoded repro if its useful
https://gist.github.com/understyx/fc134ad99d262ddbf64a89b5b08e6d57

Would you be able to give a go at https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/42665 see if it helps?

Would you be able to give a go at https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/42665 see if it helps?

Doesn't seem to fix it unfortunately.

Hang shifted few d3d9 calls down.

96104 @0 IDirect3DDevice9::SetTransform(this = 0x42d8b40, State = D3DTS_VIEW, pMatrix = [{m = [[-0.587636, -0.455379, -0.668815, 0], [0.809125, -0.330724, -0.485734, 0], [-3.34249e-09, 0.82659, -0.562804, 0], [0, 0, 0, 1]]}]) = D3D_OK

@understyx what app are you using for the log?(Sorry GitHub app glitched)

steam-14374311965495394304.log

I swapped to GE proton and running with wow64, but that shoudn't make a difference, right?

For what it's worth, I think the MR is fixing the issue on my side, running without the MR and replaying the trace from the initial comment I get a hang, with the MR it's not hanging.

I unfortunately can't apply the patch for mesa 26.1.4 and looks like your
commit needs rebasing.

Here is a backport, but for some reason it's not triggering the issue on 26.1

https://gitlab.freedesktop.org/llandwerlin/mesa/-/commits/review/anv-limit-vs-push-constant-data.26.1

Just tested, can still reproduce on Silent Hill 2.
GPU: Intel® Graphics (RPL-P)

There is also original Silent Hill 2 using D3D8.

I meant the original Silent Hill 2, there's an Enhanced Edition mod which lets it play using d3d9, although in my experience the bug also happened in its native d3d8 mode(maybe d3d9->8 compat mode)

tried latest mesa git with dxvk 3.0.2 &
info: Effective configuration:
info: dxvk.hideIntegratedGraphics = True
info: dxvk.enableDescriptorHeap = false
info: dxvk.enableDescriptorBuffer = false

and seems to not crash the gpu anymore for me.

Can also confirm issue fixed in Silent Hill 2 original.