dx9 game throw Mapping memory failed

[xinye0123]

Please describe your issue as accurately as possible. If you run into a problem with a binary release, make sure to test with latest master as well.

Important: When reporting an issue with a specific game or application, such as crashes or rendering issues, please include log files and, if possible, a D3D11/D3D9 Apitrace (see https://github.com/apitrace/apitrace) so that the issue can be reproduced.
In order to create a trace for D3D11/D3D10: Run wine apitrace.exe trace -a dxgi YOURGAME.exe.
In order to create a trace for D3D9: Follow https://github.com/doitsujin/dxvk/wiki/Making-a-Trace.
Preferably record the trace on Windows, or wined3d if possible.

Reports with no log files will be ignored.

Software information

Name of the game, settings used etc.

System information

• GPU:14600KF
• Driver:
• Wine version: proton-ge-10-4
• DXVK version: 1.11.0

Apitrace file(s)

• Put a link here

Log files

• d3d9.log:

limbo_d3d9.log

• d3d11.log:
• dxgi.log:

[WinterSnowfall]

This is a known issue that occurs due to address space exhaustion with 32-bit applications. Upstream dxvk has a workaround in place, but I doubt it can/will be backported. If patching the executable to be LAA aware does not work (see here for an easy way to do that), then you're out of luck.

P.S.: It could also be a problem with how the driver is allocating memory, as I see you are using a MTT S80.

[xinye0123]

This is a known issue that occurs due to address space exhaustion with 32-bit applications. Upstream dxvk has a workaround in place, but I doubt it can/will be backported. If patching the executable to be LAA aware does not work (see here for an easy way to do that), then you're out of luck.

P.S.: It could also be a problem with how the driver is allocating memory, as I see you are using a MTT S80.

yes! all dx9 game failed, but some dx10 and dx11 game run fine

[xinye0123]

the patch I tried, but failed

[pythonlover02]

So far this and #25 look like driver issues, since everything works as intended on other target GPUs, both on Windows and on Linux.

What driver are you using on Linux?

Could you test with Wine and older DXVK versions, such as 1.10.1 or earlier, to see if any of them work with your GPU? The idea is to check whether an older DXVK version happened to work on your setup.

To clarify, this is just to determine if I can implement some type of patch in case this situation turns out to be a regression for that GPU, similar to what happened with #26.

If that’s not the case, then unfortunately i can’t do anything, as i don’t have access to that GPU or its drivers to try to create a patch for DXVK-Sarek.

[khanh-it]

@pythonlover02

Could you test with Wine and older DXVK versions, such as 1.10.1 or earlier, to see if any of them work with your GPU? The idea is to check whether an older DXVK version happened to work on your setup.

My Specs:
Orange Pi 5 (RK3588) - Mali G-610
Armbian 25.5.1 - Ubuntu 24.04 Noble
Box64 Box64 arm64 v0.3.7 with Dynarec
PanVk mesa 23.0
Wine 10-15

[BOX64] Box64 arm64 v0.3.7 5bfb27d3 with Dynarec built on Sep 19 2025 07:02:26
info: Game: D3D9_x32.exe
info: DXVK-Sarek: v1.11.0
wine: Unhandled page fault on write access to 48E6DF0A at address 7BA62E73 (thread 0024), starting debugger...

BOX64] Box64 arm64 v0.3.7 5bfb27d3 with Dynarec built on Sep 19 2025 07:02:26
info: Game: D3D11_x32.exe
info: DXVK-Sarek: v1.11.0
wine: Unhandled page fault on write access to 5B75FC52 at address 7B2DD9E3 (thread 0024), starting debugger...

---

Summary:

Game/App	DXVK 1.x	DXVK 2.x	DXVK-Sarek 1.11.0
D3D9_x32.exe	OK	OK	ERR
D3D9_x64.exe	OK	OK	OK
--------	-------	-------	-------
D3D11_x32.exe	OK	OK	ERR
D3D11_x64.exe	OK	OK	OK

Sorry, I can't check with older DXVK-Sarek 1.x versions rn.

[pythonlover02]

@pythonlover02

Could you test with Wine and older DXVK versions, such as 1.10.1 or earlier, to see if any of them work with your GPU? The idea is to check whether an older DXVK version happened to work on your setup.

My Specs: Orange Pi 5 (RK3588) - Mali G-610 Armbian 25.5.1 - Ubuntu 24.04 Noble Box64 Box64 arm64 v0.3.7 with Dynarec PanVk mesa 23.0 Wine 10-15

[BOX64] Box64 arm64 v0.3.7 5bfb27d3 with Dynarec built on Sep 19 2025 07:02:26 info: Game: D3D9_x32.exe info: DXVK-Sarek: v1.11.0 wine: Unhandled page fault on write access to 48E6DF0A at address 7BA62E73 (thread 0024), starting debugger...

BOX64] Box64 arm64 v0.3.7 5bfb27d3 with Dynarec built on Sep 19 2025 07:02:26 info: Game: D3D11_x32.exe info: DXVK-Sarek: v1.11.0 wine: Unhandled page fault on write access to 5B75FC52 at address 7B2DD9E3 (thread 0024), starting debugger...

Summary:
Game/App DXVK 1.x DXVK 2.x DXVK-Sarek 1.11.0
D3D9_x32.exe OK OK ERR
D3D9_x64.exe OK OK OK

---

D3D11_x32.exe OK OK ERR
D3D11_x64.exe OK OK OK

Sorry, I can't check with older DXVK-Sarek 1.x versions rn.

This its probably a different issue, also what games are you testing?

[khanh-it]

@pythonlover02

This its probably a different issue, also what games are you testing?

I used the D3D test tools

[pythonlover02]

That's strange, since i mainly play 32-bit D3D9 games and i haven't seen issues. Could you check if DXVK-Sarek 1.10.6 has the issue? And if not, does 1.10.7 presents it? I remember making changes to the thread wrapper in that version.

[khanh-it]

@pythonlover02
I just recently tested the Hades game, and the same results as the D3D test tools.

That's strange, since i mainly play 32-bit D3D9 games. Could you check if DXVK-Sarek 1.10.6 has the issue? I remember making changes to the thread wrapper in that version.

The official DXVK-Sarek builds won't work with the PanVk driver (as the PanVk is still missing some required features/extensions).
I have to build a custom stripped version for it, so I can't test with the older DXVK-Sarek versions for now.
(I will try to build + check later)

[pythonlover02]

@pythonlover02 I just recently tested the Hades game, and the same results as the D3D test tools.

That's strange, since i mainly play 32-bit D3D9 games. Could you check if DXVK-Sarek 1.10.6 has the issue? I remember making changes to the thread wrapper in that version.

The official DXVK-Sarek builds won't work with the PanVk driver (as the PanVk is still missing some required features/extensions). I have to build a custom stripped version for it, so I can't test with the older DXVK-Sarek versions for now. (I will try to build + check later)

Open another issue to keep this one focused on the MTT S80 problems. Also, include the missing extensions there, i don’t mind making them optional on my repo.

[khanh-it]

@pythonlover02

That's strange, since i mainly play 32-bit D3D9 games. Could you check if DXVK-Sarek 1.10.6 has the issue? I remember making changes to the thread wrapper in that version.

I have checked way back to the DXVK v1.10.4, still error
[BOX64] Box64 arm64 v0.3.7 5bfb27d3 with Dynarec built on Sep 19 2025 07:02:26
esync: up and running.
info: Game: D3D9_x32.exe
info: DXVK-Sarek: v1.10.4
wine: Unhandled page fault on write access to 4F3115C0 at address 7BA7D7CE (thread 0024), starting debugger...

What could have gone wrong?
https://github.com/khanh-it/dxvk/compare/v1.10.x-sarek...khanh-it:dxvk:v1.10.4-sarek-zeyada-malifix?expand=1

[WinterSnowfall]

It's highly likely the 32-bit MTT driver is the issue here, largely because I think they've focused on making 64-bit functional first. This isn't something that can be addressed in dxvk except with workarounds like memory unmapping, which has been done in upstream dxvk, but would not be easily portable onto the dxvk-sarek backend. Even it were ported, I doubt it would fix all instances of crashing. This needs to be addressed by MTT at some point, there are no shortcuts to take.

[khanh-it]

@pythonlover02
But the DXVK 1.10.3 is working. So, something must have gone wrong between DXVK 1.10.3 ~ DXVK 1.10.4 sarek

#24 (comment)