KNOWN ISSUE: Crashing After Update 1.9.0 (Bound by Duty)

We’re looking in to a series of crashes that have arisen with the release of the 1.9.0 update (Bound by Duty).

If you encounter one of these crashes on PC, the crash reporter may display one of the errors listed below.

Active:

  • [Engine Error]: invalid index
    Assertion failed entry.index != d3d12_resource_context::NOT_INITIALIZED...

  • Access violation (0xc0000005) in build 3fbe5929f31adcda59ef6fbb3c058691328bbd83 accessing address 0000000000000A40 from 00007FFF1A293C33 The crash occurred in module 'amdxc64'. This module is related to AMD graphics driver. If this is a recurring issue... [Fixing in 1.9.2]

  • scripts/extension_systems/fx/fx_system.lua:182: attempt to index local 'template' (a nil value) [Fixing in 1.9.2]

Fixed:

  • scripts/foundation/utilities/table.lua:8: bad argument #1 to 'next' (table expected, got nil) [Fixed in 1.9.1]

  • ...buff/archetype_buff_templates/veteran_buff_templates.lua:2444: attempt to perform arithmetic on local 'amount' (a nil value) [Fixed in 1.9.1]

  • ...ension_systems/ability/player_unit_ability_extension.lua:747: attempt to index local 'ability' (a nil value) [Fixed in 1.9.1]

  • [Script Error]: scripts/foundation/utilities/table.lua:8: bad argument #1 to ‘next’ (table expected, got nil) [Fixed in 1.9.1]

We’ll provide updates in the comments below as soon as we have them, and link them here to keep everyone in the loop.

Thank you for your patience and understanding while we look in to this.

To keep things organised, we’ll merge all new and existing reports about these crashes here.

UPDATE 23/09

UPDATE 25/09

1 Like

Issue Type (Required):

Crash - During Play

Issue Description (Required):

It is a guaranteed crash if I go to the cosmetics tab. But the game will also crash after a few minutes. I have run the AMD CleanUp Utility and have reinstalled my drivers. I have also run a validation through steam and all came good but the crash remains. I can reproduce it 100% every time.

[PC] Do You Use Mods? (Optional):

No, I don’t use mods

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

PC - Steam

[PC] Crash Report (Optional):

GUID: ee1015c0-8250-4fc1-96c2-5eaa1f171359
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build 3fbe5929f31adcda59ef6fbb3c058691328bbd83
accessing address FFFFFFFFFFFFFFFF from 0000020E08556606

The crash occurred in module ‘amdxc64’. This module is related to AMD graphics driver. If this is a recurring issue you could try AMD Cleanup Utility tool Drivers and Support for Processors and Graphics to see if that helps.


[PC] Upload Console Log & darktide_launcher.log (Optional):

console-2025-09-23-11.36.11-ee1015c0-8250-4fc1-96c2-5eaa1f171359.log (94.8 KB)
console-2025-09-23-11.27.39-a1add498-9308-416e-a76c-c137c469f76b.log (100 KB)

Access violation (0xc0000005) in build 3fbe5929f31adcda59ef6fbb3c058691328bbd83 accessing address 0000000000000A40 from 00007FFF1A293C33 The crash occurred in module 'amdxc64'. This module is related to AMD graphics driver. If this is a recurring issue...

For anybody experiencing the crash above :up_arrow: please disable RTX Global Illumination in the meantime. This will be resolved in 1.9.2.

I’ve done this suggested fix and I’m still getting this error and crashing to desktop when visiting the Commadore’s Vestures.

On Windows 11:

GUID: 0712942e-7fb6-4a85-a738-640630870ee9

Log File:
Info Type:

[Script Error]: scripts/foundation/managers/package/package_manager.lua:436: Trying to unload resource #ID[72818d39a09e5350].#ID[eac0b497876adedf] that’s used elsewhere by the engine, refcount: 2
———————————————————————————–
GUID: 81a329c0-46a0-449c-bcdf-1ab33dbae63d
Log File:
Info Type:

[Script Error]: scripts/foundation/managers/package/package_manager.lua:436: Trying to unload resource #ID[72818d39a09e5350].#ID[eac0b497876adedf] that’s used elsewhere by the engine, refcount: 2


On CachyOS Linux (since I use dual boot):
Game runs into renderer error and cannot load past the character select screen. Unsure which proton version I should be using.

im having this same issue, i open the game, i play arbitrator, i open the mission terminal, which fails to load, and then i click show campaign missions and the game immediately crashes. i dont use mods, ive tried 5 times with the arbitrator, havent tried other classes. crash report:
GUID: a587b082-2b18-4613-b04b-b1ea41355d52
Log File:
Info Type:

[Script Error]: scripts/foundation/utilities/table.lua:8: bad argument #1 to ‘next’ (table expected, got nil)

1 Like

Crashing when turning on FSR 3. RX 9070xt GPU

GUID: 6b119dfc-9c5b-4eb3-a023-90ef2c89b07f

Log File:
Info Type:

[Engine Error]: HRESULT: 0x887a0005 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_INVALID_CALL, assert: ``

At D:\a\d\rel_engine_darktide\release\2025_08_20_Patch1.9.x\runtime\d3d12_render_device\d3d12_debug.cpp:1550 in function stingray::aftermath::d3d_assert


Crash during regular gameplay

Platform: Steam, Win11, no mods

GUID: b3c721ef-0b95-4d2f-adb3-f59fd721fb0b

Log File:
Info Type:

[Script Error]: …tension_systems/unit_data/player_husk_data_extension.lua:258: attempt to compare table with number

GUID: 7bc8b18d-ebee-4857-b59b-33016f782840

Log File:
Info Type:

[Script Error]: module ‘scripts/main’ not found:

no field package.preload[‘scripts/main’]scripts/main.lua:1: unexpected symbol near ‘char(2)’

Me: I have both removed all mod related folders, and put them back in and still get this response… Fix your game.. I bought this in 11/2022 to buy something that works.. not something that doesn’t work

You need to remove the old mod loader’s patch that you applied without understanding what it is doing.

1 Like

This has made the crashes occur less often but it’s still crashing. Always on the cosmetic tab.

I get the following error whenever mods are enabled:

GUID: b0405b8d-d1fe-4446-9a56-239465c1915d

Log File: 

Info Type: 

-----------------------------------------------

[Script Error]: module 'scripts/main' not found:

no field package.preload['scripts/main']scripts/main.lua:1: unexpected symbol near 'char(2)'

-----------------------------------------------

[Crash Link]:

crashify://b0405b8d-d1fe-4446-9a56-239465c1915d

I have the following mods:

DarkCache
LogMeIn
Perspectives
true_level
scoreboard
more_characters_and_loadouts
Ration Pack
ChatBlock
NoSkull
Spidey Sense
NumericUI
modular_menu_buttons
Lingering Death
FoundYa
show_crit_chance
PlayerOutlines
MergedTalentStats
TalentRefundBelow
buy_until_rating
guarantee_weapon_swap
InspectFromSocial

When the mods are disabled, the game launches just fine.

Does anyone know which mod might be the culprit so I can disable it until it’s fixed?

From what I can gather, it seems to have trouble getting some script.

@mirza There’s a discussion on this particular crash here:

1 Like

I’ve let 'em know!

1 Like

DarkCache hasnt been updated in over 2 years, thats probably some issues you are having. Also the mod loader itself needs an update if you havent updated it already.
https://www.nexusmods.com/warhammer40kdarktide/mods/19

1 Like

it happens when i play a match

GUID: e69a0be9-a8a6-4ef5-8f0c-ab2b31cb504b

Log File:
Info Type:

[Script Error]: scripts/foundation/managers/package/package_manager.lua:436: Trying to unload resource #ID[a3d828f9482fa132].#ID[eac0b497876adedf] that’s used elsewhere by the engine, refcount: 4

List updated to include the crashes Fixed now 1.9.1 is live. We hope that’s the last of them, but let us know if you spot any reoccurrences or new mysterious crashes.

1 Like

Yes I figured that out already. Still dissatisfied with the fact I have to install mods to quickswap weapons and skip the loading scene (and quickswapping was working about 2 years ago… until TencentShark decided to say “yeah, let’s make swapping weapons slower, this is something gamers universally ask for everywhere. Let’s intentionally make something that is supposed to be fast, slower.” Geniuses at work there.. and by geniuses I mean actual orangutans that don’t even know what what studio library is in C.

Can I use mods now so I can quickswap weapons and skip the dumb loading screen? Or is that still going to cause the game to crash?

It’ll likely still crash, until the mod’s author addresses the incompatibility.

2 Likes