Is This Game Down
Browse games
You can fix thisReported

Dragonwilds fatal error crash on launch (D3D12 fix)

RuneScape: Dragonwilds server status →RuneScape: Dragonwilds servers →

Written by

IsThisGameDown

Last checked

October 15, 2026

Steam Discussions — "Fatal Error crash at launch" ↗

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. A third variant, reported after the 1.0.1 update (October 14, 2026), crashes right after the developer logo with an AsyncLoading2.cpp "Bad export index" fatal error.

Also appears as: dragonwilds fatal error, runescape dragonwilds crash on launch, dragonwilds crashing on startup, dragonwilds d3d12 fatal error, dragonwilds wont launch, dragonwilds crashing, runescape dragonwilds fatal error on startup, dragonwilds crash after logo, dragonwilds crash after 1.0.1 update, dragonwilds Bad export index, dragonwilds AsyncLoading2.cpp fatal error, dragonwilds mods crash after update, dragonwilds delete mods folder

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.

After 1.0.1 shipped on October 14, 2026, three Steam Discussions threads describe the game crashing right after the logo, one quoting "Bad export index 4866/17" from AsyncLoading2.cpp. Players there say leftover pak mods from before the update are the cause, and two say deleting the "~mods" folder fixed it. Not everyone in those threads uses mods, and no Jagex reply appears.

Fix it, step by step

  1. Crash after the logo since 1.0.1 with pak mods? Delete the ~mods folder

    If you have pak mods installed and the game crashes right after the developer logo since the 1.0.1 update, delete the whole "~mods" folder inside the Paks folder of your install (the thread gives no full path). A player in the Steam thread "Anyone have this problem?" who says a pak mod caused it advises doing this after every update and warns: "Do not delete the 'LogicMods' Folder just the '~mods' Folder." Another player there, who first deleted the mods and still crashed, reports that deleting the empty "~mods" folder itself is what worked. A third poster (Jsteeed) says removing their one mod fixed it. The crash text in that thread points at game files ("AsyncLoading2.cpp ... Bad export index 4866/17"), and no one there explains why the folder matters. Not every reporter uses mods: another thread, "New update crashes the game at starting", has one poster with no mods installed whose game loaded on the third attempt and another who verified and reinstalled the game without success.

  2. Add -vulkan to the game's Steam launch options

    Add -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.

  3. Try -dx11 in the launch options if Vulkan does not help

    If Vulkan doesn't help or your GPU doesn't support it well, try -dx11 in the same launch options field instead.

  4. Update your GPU drivers

    Update 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.

  5. Note

    If 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

  6. Delete the EOS folder and verify the install if Play just resets

    If 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.

Hit this error? Leave a comment

Say where you are, what you see on screen, and whether any fix worked for you.

No links. Anonymous, no account. Keep it about the game.

What people are saying

Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.

  • Nothing reported here yet.
← FAILED-TO-LOAD-PLAYER-STATESERVER-NOT-SHOWING-UP →

Other RuneScape: Dragonwilds error codes

Recently added