Crimson Desert Ray Reconstruction Crash on Multi-Monitor PC

What is the Crimson Desert Ray Reconstruction Crash?

Crimson Desert players running multi-monitor setups (2 or more displays connected, even when the game is played on one) are hitting a hard freeze, black screen, or DXGI_ERROR_DEVICE_HUNG crash within seconds of loading any open-world area when DLSS Ray Reconstruction (RR) is enabled. The issue surfaced en masse after the Windows 11 KB5094126 cumulative update (June 10, 2026) interacted badly with NVIDIA's DLSS 4 RR pipeline on Game Ready Driver 576.88 and the new Studio 576.92.

Logs show one of three signatures: DXGI_ERROR_DEVICE_HUNG referencing nvngx_dlssd.dll, a Windows Event Viewer nvlddmkm Event ID 153, or the Crimson Desert crash reporter complaining about D3D12 Removed: HUNG (0x887A0006). The crash is reproducible — it is not a random thermal event.

When does it occur?

• Within 5–60 seconds of entering the open world after a cutscene
• Immediately when opening the map or fast travel menu
• When alt-tabbing back to the game with RR enabled
• After applying graphics preset changes mid-session
• More frequently with HDR enabled on the primary display
• On RTX 40 and RTX 50 cards — RTX 30 (RR not available) is unaffected

Common causes

• DLSS Ray Reconstruction + multi-monitor desktop composition bug — the DWM presents to the secondary monitor mid-frame, corrupting the RR denoiser state
• KB5094126 DXGI runtime change — Microsoft adjusted the swap-chain present pacing in this update, exposing the RR race condition
• NVIDIA driver 576.88 / 576.92 — both ship the DLSS 4.5.0 DLL that contains the regression
• HDR + mixed-refresh-rate displays — e.g., 240 Hz primary + 60 Hz secondary triggers the bug faster
• G-SYNC enabled on the inactive monitor — keeps the secondary display compositor active
• **Outdated nvngx_dlssd.dll shipped with the game** — version 310.2.1.0, replaced by 310.3.0.0 in NVIDIA's June 14 hotfix
• Frame Generation enabled together with RR — doubles the crash rate

Step-by-step fixes

1. Install NVIDIA Hotfix Driver 576.94 — Download from nvidia.custhelp.com/app/answers/detail/a_id/5601 (the "June 14 2026 hotfix"). It replaces the broken DLSS DLL and adds an explicit multi-monitor present barrier for RR. Use GeForce Experience > Drivers > "Custom Install > Clean Install" or DDU before installing.

1. Toggle Ray Reconstruction OFF inside Crimson Desert — In-game: Settings > Graphics > Upscaling > DLSS Super Resolution = Quality, then DLSS Ray Reconstruction = OFF. Apply and restart the engine. This is the fastest workaround if you cannot update drivers right now.

1. Manually update the DLSS DLL — Close the game. Navigate to Steam\steamapps\common\Crimson Desert\CrimsonDesert\Binaries\Win64\ and rename nvngx_dlssd.dll to nvngx_dlssd.dll.bak. Download nvngx_dlssd.dll version 310.3.0.0 from techpowerup.com/download/nvidia-dlss-dll/ and drop it into the same folder. This works even on older drivers.

1. Unplug or disable the secondary monitor — Press Win+P > PC screen only, or physically disconnect the secondary cable before launching. This eliminates the DWM cross-monitor present path entirely. Confirmed by Pearl Abyss community managers as the official workaround.

1. Disable HDR and lock both monitors to the same refresh rate — Settings > System > Display > HDR > Off on all monitors. Then Advanced display > Refresh rate — set every monitor to the same value (e.g., both 120 Hz). Mixed refresh rates aggravate the present-pacing crash.

1. Disable G-SYNC on the inactive monitor — NVIDIA Control Panel > Display > Set up G-SYNC. Uncheck "Enable for windowed and full screen mode" on all monitors except the one you actually play on. Click Apply.

1. Force Vulkan renderer (RTX 50 only) — Launch options in Steam: right-click Crimson Desert > Properties > Launch Options > paste -vulkan -nodlssrr. The Vulkan path uses a different denoiser and is currently stable on multi-monitor. Expect ~8% lower FPS but no crashes.

1. Roll back KB5094126 if you still crash — Open PowerShell as admin and run wusa /uninstall /kb:5094126 /quiet /norestart, then reboot. Pause Windows Updates for 7 days in Settings > Windows Update. Microsoft and NVIDIA are coordinating a permanent fix expected in the next cumulative.

If it still doesn't work

If the crash persists after the hotfix driver and DLL replacement, disable Frame Generation alongside RR — the two features share an internal motion-vector buffer and the buffer ownership conflict is the secondary crash path. Set Settings > Graphics > DLSS Frame Generation = OFF, then re-enable RR alone to confirm it's the FG interaction.

If you have an RTX 5070 Ti or RTX 5090 with the missing-ROPs hardware defect, RR will *always* crash because the denoiser exceeds the ROP budget — see the related RTX 50 series article for RMA criteria. As a last resort, drop Upscaling preset to "Balanced" and run native TAA: Settings > Graphics > Upscaling > Off > Anti-Aliasing > TAA. You lose image quality but eliminate every DLSS-side crash vector while the official patch ships.