RuneScape: Dragonwilds fatal error crash on launch — D3D12 fix
Written by
Last checked
September 23, 2026
The game crashes immediately on or shortly after launch with a "Fatal error" dialog referencing D3D12RHI/D3D12Util.cpp and "CopyCommandList->Close() failed," or, in a separate variant, the Play button simply resets with no error text at all while Epic Online Services fails to initialize in the background.
Also appears as: dragonwilds fatal error, runescape dragonwilds crash on launch, dragonwilds crashing on startup, dragonwilds d3d12 fatal error, dragonwilds wont launch
A Steam Discussions thread quotes the exact crash text: "Fatal error: [File:D:\buildAgent\vcs\dominion\staging\ue\Engine\Source\Runtime\D3D12RHI\Private\D3D12Util.cpp] [Line: 903] Interfaces.CopyCommandList->Close() failed with error E_INVALIDARG" — a DirectX 12 command-list failure in the game's Unreal Engine 5 renderer, not a corrupted save or account problem. In that thread, switching the game's renderer resolved it for at least one player. A separate, EOS-related launch failure looks different from the outside but shows up in the same "won't launch" searches: the Play button resets itself with no error dialog while Epic Online Services fails to initialize, usually tied to a conflict between EOS, the Epic Games Launcher and the Steam version of the game. No Jagex staff reply appears in either community thread; the fixes below are what players report actually working, split by which variant you're hitting.
What to try
- 01Add -vulkan to the game's Steam launch options (right-click the game in your library > Properties > General) to switch off DirectX 12 rendering. Multiple players in the official Steam Discussions thread confirm this stopped the launch crash for them.Reported
- 02If Vulkan doesn't help or your GPU doesn't support it well, try -dx11 in the same launch options field instead.Reported
- 03Update your GPU drivers to the latest version. An outdated or mismatched D3D12 driver is the most commonly cited cause of the "CopyCommandList->Close()" fatal error specifically.Reported
- 04If you're on a 13th- or 14th-Gen Intel desktop CPU, be aware the game's Discord has reportedly acknowledged crashes are more common on that hardware — this is community-sourced secondhand, not something this page verified directly, so treat it as context rather than a fix to apply.Unconfirmed
- 05If instead the Play button just resets with no error text and Epic Online Services is the suspect, delete the EOS folder inside the game's install directory, verify/repair the install through Steam, and confirm your Steam and Epic accounts are actually linked.Reported
Did this fix it for you?
Your answer helps the next player know whether these steps are worth trying first.
What people are saying
Notes from players who've hit this one — no time limit, an answer from months ago is still an answer. Say where you are and what you see on screen.
No links. Anonymous, no account. Keep it about the game.
- Nothing reported here yet.