==============================================================
BUG REPORT: Crimson Desert 1.04.01 crashes on launch
under all Proton versions — Wine/VKD3D-Proton regression
Date: 2026-04-23

SUMMARY

Crimson Desert build 22924815 (v1.04.01, released 2026-04-23)
crashes on launch under all tested Proton versions on Linux.
The crash is caused by unimplemented D3D12/DXGI interfaces in
Wine and VKD3D-Proton, introduced as a regression by patch 1.04.
The game calls these APIs for its new rendering features (colorblind
mode, chromatic aberration, improved DLSS/FSR integration), receives
failure or stub returns, and subsequently dereferences a null pointer,
triggering EXCEPTION_ACCESS_VIOLATION. Version 1.03 worked correctly.

SYSTEM INFORMATION

OS: Ubuntu 24.04.4 LTS
Kernel: 6.8.0-110-generic
CPU: 11th Gen Intel Core i7-11700F @ 2.50GHz
Mainboard: Gigabyte B560M AORUS PRO (BIOS F13, 2023-12-19)
RAM: 31.20 GiB
GPU: NVIDIA GeForce RTX 5060 Ti (Blackwell / GB206)
Driver: 590.48.01 Linux / 155.35 Windows (WDDM)
Steam: Native build 1776812172
App ID: 3321460
Build ID: 22924815 (v1.04.01, released 2026-04-23)
BuildKey: BlackSpace_CD_Cert_ReleaseSteam_x64_cd_alpha_2026_04_23_09_58_09

PROTON VERSIONS TESTED (all produce identical crash)

• Proton Hotfix 10.1000-200 (Steam default for this title)
• Proton-GE Latest (installed via ProtonPlus)
• proton-cachyos-10.0-20260420-slr-x86_64

CRASH EXCEPTION (confirmed via Crashpad sentry-event)

ExceptionCode: STATUS_ACCESS_VIOLATION (0xc0000005)
ExceptionAddress: 0x00000001431EE9A4 (CrimsonDesert.exe+0x31EE9A4)
Operation: Read at address 0x30 (null pointer + field offset)
DumpKey: 5r4751891_340_00000001431EE9A4_LIVE_20260423_201351842

Note: Crashpad automatically uploaded minidumps to pentry-relay.pearlabyss.io.
Two dumps available locally (approx. 1 GB each):
0ccfa96c-b101-4fd3-a591-7ba59a4cdfa7.dmp (2026-04-23 16:49)
c8d1bdcb-fe51-4b06-be00-be171204a5d8.dmp (2026-04-23 17:13)

WINE/VKD3D-PROTON LOG EVIDENCE (steam-3321460.log)

Captured with: WINEDEBUG=+vulkan,+vkd3d PROTON_LOG=1

Key lines confirming unimplemented interfaces in the crash path:

[line 1342] warn: DxgiAdapter::QueryInterface: Unknown interface query

[line 7755] err: DxgiFactory: RegisterAdaptersChangedEvent: Stub

[line 10361] warn:vkd3d-proton:d3d12_device_QueryInterface:
{3febd6dd-4973-4787-8194-e45f9e28923e} not implemented,
returning E_NOINTERFACE.

[line 10362] warn:vkd3d-proton:d3d12_device_QueryInterface:
{10b90151-4435-4004-9fad-19361488899a} not implemented,
returning E_NOINTERFACE.

[line 10363] warn:vkd3d-proton:d3d12_device_QueryInterface:
{db6f6ddb-ac77-4e88-8253-819df9bbf140} not implemented,
returning E_NOINTERFACE.

[line 32436] warn:vkd3d-proton:d3d12_device_QueryInterface:
{0742a90b-c387-483f-b946-30a7e4e61458} not implemented,
returning E_NOINTERFACE.

[line 32520] warn:vkd3d-proton:d3d12_command_queue_QueryInterface:
{db6f6ddb-ac77-4e88-8253-819df9bbf140} not implemented,
returning E_NOINTERFACE.

Full WINEDEBUG log attached: steam-3321460.log (11 MB, 126,796 lines)
Filtered relevant lines: winedebug_relevant.txt

CRASH TIMELINE (from Pearl Abyss launcher log — all sessions identical)

[17:13:21] Logger initialized — Game v1.04.01 (build 4751891)
[17:13:23] WARN: NGX Updater not available — OTA disabled (non-critical)
[17:13:24] NVIDIA Streamline: DLSS 2.10.3, DLSS-RR 2.10.3, Reflex OK
[17:13:25] GPU: NVIDIA GeForce RTX 5060 Ti — DriverVersion: 155.35
[17:13:27] Displays: LG ULTRAGEAR, C27FG7x — HDR: False
[17:13:29] Data modules loading...
[17:13:33] All 13/13 data modules loaded successfully
[17:13:33] PoolManager: FieldPoolValue, PartyManager, GuildManager OK
[17:13:48] Language changed: 14 -> 11
[17:13:51] RunThread begin — rendering thread started
[17:13:51] Memory report: 85% usage, 4.60 GB free of 31.20 GB
[17:13:51] *** LOG ends abruptly — process silently terminated ***

12 launcher log sessions attached in launcher_logs/ folder.
All sessions show identical behavior regardless of Proton version.

WHY THIS BROKE IN 1.04

Patch 1.04 added colorblind mode, chromatic aberration, photosensitive
mode, and improved FSR/XeSS/DLSS integration. These rendering features
rely on D3D12 interfaces and DXGI adapter queries that are not yet
implemented in Wine/VKD3D-Proton. Version 1.03 did not use these APIs
and worked correctly under Proton (ProtonDB Gold tier, 574 reports).

WHAT WAS RULED OUT

• Anti-cheat (HARUM): ruled out — process completes full game
  initialization before crashing; HARUM blocks occur much earlier.
  Confirmed: Elden Ring (EAC, DX12) runs normally on this machine.
• GPU/driver: ruled out — RTX 5060 Ti + driver 590.48.01 functions
  correctly with other DX12 titles under Proton.
• Memory exhaustion: ruled out — first crash occurred at 44% RAM usage.
• Shader/pipeline cache: ruled out — clearing all caches had no effect.
• Proton version: ruled out — 3 different builds crash identically.

RESOLUTION PATH

1. Wine/winevulkan: implement NtGdiDdDDIOpenSyncObjectFromNtHandle
   (currently a stub — https://bugs.winehq.org)

2. VKD3D-Proton: implement the unimplemented D3D12/DXGI interfaces
   listed above in the log evidence section.
   (https://github.com/HansKristian-Work/vkd3d-proton)

3. Pearl Abyss (fastest path): add null-check on sync object and
   interface query results so the game falls back gracefully instead
   of dereferencing null on stub/E_NOINTERFACE returns.

AFFECTED SCOPE

This issue affects all Linux users on all Proton versions, all GPU
vendors (NVIDIA and AMD), and all distributions. It is a platform-wide
regression introduced exclusively by the 1.04 patch.

ATTACHED FILES

bug_report_EN.txt <- this file
bug_report_PT.txt <- Portuguese version
launcher_logs/ <- 12 launcher sessions (all crashes)
crash_attachments/
crash1_screenshot.png <- screen state at crash time
crash2_screenshot.png
crash1_sentry_event.bin <- Crashpad event (exception confirmed)
crash2_sentry_event.bin
crash2_launcher.log
user_engine_options.xml <- game graphics settings
system/
system_info.txt <- hardware, driver, exception details
steam_content_log_3321460.txt <- Steam state log for this app
steam_compat_log_3321460.txt <- Proton compatibility log
winedebug_relevant.txt <- filtered Wine/VKD3D warnings+errors
steam-3321460.log <- full WINEDEBUG output (11 MB)

==============================================================