Attaching log files from a successful startup with 2.7.1 to compare against.
Made an apitrace, it's really small because it crash's to desktop.
https://drive.google.com/file/d/1QurKPEnHsORWqunCR0OwPuXuNLGY1JW7/view?usp=sharing
This is the client log from the apitrace startup.
There is a recent shift from proprietary AMD compiler for RDNA3/4 towards LLPC for LLVM, DXVK has issues with this compiler under WIN AMD drivers. To mitigate the issue u can use "AMD_ENABLE_LLPC" & "0" in system variables, but be aware! This might cause BSOD on WIN 11 and break many other games even under DX12. Since the shift towards LLPC, many DX9-11 games work better now, not actually needing DXVK. Give it a try, you'll see 👍
Game runs fine on Proton for me (on RADV) and I'm not seeing any Vulkan validation errors or invalid shaders that would explain issues. Can confirm that apitrace isn't working though, might have something to do with the insane D3D10/11 mixture that's going on here.
There is a recent shift from proprietary AMD compiler for RDNA3/4 towards LLPC for LLVM
Ironically, if we ignore GPL and atrocious compile times for a second then LLPC used to work a lot better with DXVK when AMDVLK was still being maintained.
Grrr this is why I really wish I could fully move to linux. Setting environment variables locally in a startup script is easy there, not so much on Windows. Let me see if I can set that value just for the launcher executable and it's children. Or better yet, is that a DXKV config file entry that could acomplish this?
DDO gets a pretty significant performance bump from using DXVK, it's one of those older 32-bit DX9 games from 2006 that later had a DX11 engine bolted up, then even later was upgraded to have a 64-bit client.
Ok tried the environment variable and it didn't help, DDO still crashed after logging in and clicking start.
Putting aside that it's pretty easy to set envvar on windows, you can find a great deal of the old git builds here.
Whoosh.
Those are system / user level environment settings and not application level. Making that setting system wide would effect every single other program instead of just DDO.
"Version 2.7.1 works flawlessly "
This indicates I already have version 2.7.1, along with 3.0, 3.0.1 and so forth. This is a bug report because there is a regression between versions 3.0 and those prior to it. Seems to be something known with the new compiler and AMD GPUs on Windows.
2.7.1 is from 2025, those are the nightlies from all this year leading up to 3.0 (when interestingly they stopped).
0xc0000005x1 2026-08
Software information
Dungeons and Dragons online FTP MMO. It has a DX11 engine but is rather old and DXVK allows it to run more stable on newer GPUs. Version 2.7.1 works flawlessly but 3.0 and beyond causes an instant crash on start with the following error messages.
000000000.000: Program fault: ACCESS_VIOLATION (0xc0000005) trying to read from 0x000001ACDC87C3CC
Attached log has the full crash dump info.
System information
Apitrace file(s)
For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace
Log files
dndclient64.log
dndclient64_d3d11.log
dndclient64_dxgi.log