[Engine Error]: Access violation (0xc0000005) Excessive crashes during play and on Mourningstar

[Kuug]

Issue Type (Required):

Crash - During Play

Issue Description (Required):

I have played every day for the past 3 weeks or so and not a single day has gone by where my game has not crashed. In particular, one type of crash has repeatedly occurred: [Engine Error]: Access violation (0xc0000005). I have tried every solution I’ve found in the forums, including deleting the Darktide cache folder in Appdata, disabled portraits, verifying files in both the launcher & Steam, lowering the core count in the launcher, stop the use of FSR3.1/3.1 frame gen, reinstalling drivers, lowering settings, preventing Windows from being able to default to old drivers, etc. I’ve done literally everything. Whether I’m on the Mourningstar or in gameplay, the game will crash multiple times throughout the same session. Just now, I crashed twice in the span of only a few minutes.

Because I deleted the Appdata Darktide folder my crash dumps and console logs will be short on supply, but I was keeping a notepad of all the crashes my game has suffered since I became frustrated with this. The vast majority are (0xc0000005) and not driver failures.

My specs are 5800x3D, AMD 7900 XTX, 32gb of RAM running at XMP 3000 CL16

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

No, I don’t use mods

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

PC - Steam

Player ID (Optional):

Steam Community :: GringoSuave619

[PC] Crash Report (Optional):

GUID: 5ee71c5f-19f7-40da-93c5-2b9ad5b69407
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000000003F0817DE from 00007FF68CCD7058

GUID: ce12cff1-c53f-4bb9-80b5-07d297934f3f
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001640C1E36D0 from 00007FF7B44CEEFF

GUID: 893d48d4-bd56-4a4a-a7bf-85957b827324
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000014F0C0FCDD0 from 00007FF7B44CEEFF

GUID: 47d05693-c4d8-4971-bafa-e74817bb09cc
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000000000000000 from 00007FF7B457EED2

GUID: f5b6c88e-9d6d-4916-99d5-addf408a7e77
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000022764A48A20 from 00007FF68AADEEE6

GUID: a064398c-9197-46d6-a948-f3b30e7347fb
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000021F0672DB00 from 00007FF68AADEEFF

GUID: 254ea945-d95a-4d0b-9854-6d890f950122
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 00000000BEED6EA8 from 00007FF68A7DD128

GUID: bcdf8af9-d8f0-4043-83b2-5c8c918d87d6
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001CB3BF25CC8 from 00007FF68AADEEE6

GUID: c18b2eb0-5ddc-4703-91bc-82c9248a2b65
Log File:
Info Type:

[Engine Error]: Failed to decompress: C:\Steam\steamapps\common\Warhammer 40,000 DARKTIDE\binaries..\bundle\data/81/81fe51144f1cbd70.stream from package 00000000.

Make sure that your game files are not corrupt by in steam. Contact support if this still occur after verifying the game files.

GUID: ef29d6a6-af28-40d3-a377-c049cf7b5671
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000018CAC352F50 from 00007FF79679EEFF

GUID: 051d7b2b-d25c-400e-abac-f1b876efd632
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001BB0EA1708C from 00007FFCE5CE79E2

GUID: 51aeae67-e20e-42ac-ab8f-0cdbf2296a5f
Log File:
Info Type:

[Engine Error]: HRESULT: 0x887a0005 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DEVICE_HUNG

At D:\a\d\rel_engine_darktide\release\2024_10_23_Patch1.6.0x\runtime\d3d12_render_device\d3d12_debug.cpp:1550 in function stingray::aftermath::d3d_assert

---

GUID: b60d25af-2ee2-4d4e-bc27-cf157fce596e
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001E64AA82AE0 from 00007FF79679EEFF

GUID: b83810e6-bae8-4130-b369-141c688f7a2d
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000026C0B1BE940 from 00007FF79679EEFF

GUID: 8a9dda63-347a-429c-989d-bc5de77e47ef
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001E569D17508 from 00007FF79689C7A7

GUID: 5aa281d6-c85c-486c-b426-d6d7e8c5392f
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000019E61A92C20 from 00007FF7AF30EEE6

GUID: 8092361f-ca18-4a20-942f-b09c6cd75864
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000013E10FBD4C0 from 00007FF6F4BFEEFF

GUID: a0e96959-3c29-4417-a134-8459e380f478
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000028AF18D8538 from 00007FF760C0EEE6

GUID: 0b8e7b82-016c-45c8-8653-6d3d0ec5d7ae
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000014C21883018 from 00007FF760C0EEE6

GUID: b89c40b3-5a65-4cb7-bdc8-7894f52b0ad4
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000020A07E2D7B4 from 00007FF690A2EEE6

GUID: e635749a-dd27-4eff-9696-e63600203ec3
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 00000295FBF38950 from 00007FF690A2EEE6

GUID: 7fc501e7-9b7a-4aec-a6b4-340b8b9a0545
Log File:
Info Type:

[Script Error]: scripts/managers/ui/ui_view_handler.lua:206: attempt to index local ‘view_data’ (a nil value)

GUID: df289fe1-1511-47e4-a462-59253ea35a9f
Log File:
Info Type:

[Engine Error]: Failed to decompress: C:\Steam\steamapps\common\Warhammer 40,000 DARKTIDE\binaries..\bundle\8aaa27ad87976cf4 from package 8aaa27ad.

Make sure that your game files are not corrupt by in steam. Contact support if this still occur after verifying the game files.

GUID: e38a177e-2862-42b9-807d-38f3a9d165aa
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000002629172856C from 00007FF690A2EEE6

GUID: 9f80d3cb-ac8d-463d-813c-8c90ff56742f
Log File:
Info Type:

[Engine Error]: Not Implemented for type: ‘16825’

At D:\a\d\rel_engine_darktide\release\2024_10_23_Patch1.6.0x\runtime\engine\renderer\resources\render_resource_context.cpp:343 in function stingray::RenderResourceContext::dealloc

---

GUID: 3f4f594e-48bb-49e1-9f72-2edef8572401
Log File:
Info Type:

[Engine Error]: Invalid temporary variable marker 0x2b0dab5 (000001E739260000, 000001E739817A7C, 000001E73982002C, 000001E73981D67C)

At D:\a\d\rel_engine_darktide\release\2024_10_23_Patch1.6.0x\runtime\application\script\lua_environment.cpp:1328 in function stingray::LuaEnvironment::clear_temp_variables

---

GUID: f79ad429-bcfb-4baf-906e-d640defc15cb
Log File:
Info Type:

[Engine Error]: HRESULT: 0x887a0005 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DEVICE_HUNG

At D:\a\d\rel_engine_darktide\release\2024_10_23_Patch1.6.0x\runtime\d3d12_render_device\d3d12_debug.cpp:1550 in function stingray::aftermath::d3d_assert

---

GUID: ff460bdb-6592-4cc0-a349-db56522d8b58
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001EA08BA1288 from 00007FF6698B23B5

GUID: a50f2bc3-6e12-479a-a427-a5d4a78964a9
Log File:
Info Type:

[Engine Error]: Failed to decompress: C:\Steam\steamapps\common\Warhammer 40,000 DARKTIDE\binaries..\bundle\data/50/50ba335b511b7dbf.stream from package 00000000.

Make sure that your game files are not corrupt by in steam. Contact support if this still occur after verifying the game files.

GUID: 30b48802-e97a-4872-bc63-433add885778
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 00000213B88BB630 from 00007FF7D489EEFF

GUID: 48177eed-241a-4c8c-a56b-4abff30a92f1
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000002878B9A9120 from 00007FF7D489EEFF

GUID: 50977414-2340-433d-b357-8124b21bb9e6
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address FFFFFFFFFFFFFFFF from 00007FF7D487CB18

GUID: 375f5d22-7c02-477c-aec8-4f7a5caf192a
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001F02BCD0BE0 from 00007FF6C550EEFF

GUID: 34f7fe73-ecbd-43a7-bd3f-791f3dfe16bb
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000029EFAA39E20 from 00007FF6C550EEE6

GUID: 3ea2d1ef-d41f-468a-bb1b-d9c254bb40f9
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 00000207D48F8270 from 00007FF6C550EEE6

GUID: de81c1b2-135a-4287-aa5a-28d2314bebac
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001EE084F3B80 from 00007FF6C550EEFF

GUID: 453d35c3-4901-4009-b008-9ea4707a2b0f
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001D3897F0C80 from 00007FF7E94DEEFF

GUID: 6e44d3e1-0c8e-4a81-acfc-4af3ca3c3fe0
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000002308DAEE120 from 00007FF7E94DEEFF

GUID: 6bddbe5a-3245-4397-9652-0837bdcdfb07
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001FF31208294 from 00007FF7E94DEEE6

GUID: 9cdcc526-1327-4236-ab33-94697179e5cb
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000021FD969806C from 00007FF7E94DEEE6

GUID: e873f511-5a5f-4472-a4b7-ff13e68586ef
Log File:
Info Type:

[Engine Error]: Invalid temporary variable marker 0x2b0dab5 (00000243C4570000, 00000243C4EFADBC, 00000243C4EFDE3C, 00000243C4EFBC7C)

At D:\a\d\rel_engine_darktide\release\2024_10_23_Patch1.6.0x\runtime\application\script\lua_environment.cpp:1328 in function stingray::LuaEnvironment::clear_temp_variables

---

GUID: 8799bb46-9a41-4586-9300-38cc6b3535d0
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000023563F082B4 from 00007FF7E94DEEE6

GUID: 3de6c242-a4c8-4dab-8f25-dd9fbe0c31c7
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001C08902E950 from 00007FF7E94DEEFF

GUID: 1248be8c-e830-4729-9e26-40ccdd7f2a05
Log File:
Info Type:

[Engine Error]: Failed to decompress: C:\Steam\steamapps\common\Warhammer 40,000 DARKTIDE\binaries..\bundle\e35fb1b08010680d from package e35fb1b0.

Make sure that your game files are not corrupt by in steam. Contact support if this still occur after verifying the game files.

GUID: a10a54e9-5904-4f9a-b23d-06fd16bd6752
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001BF0C421550 from 00007FF7E94DEEFF

GUID: 44c2fd57-0d13-4ec9-8807-ab16dcf2d2ec
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001CE4CCC38C0 from 00007FF7E94DEEFF

GUID: d6797ec2-a891-44a5-afc3-4e0b2520110a
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000018DD2467130 from 00007FF7E94DEEE6

GUID: aad6fc7b-15d4-49ed-8fd7-7118140f80f8
Log File:
Info Type:

[Script Error]: …ents/player_panel_base/hud_element_player_panel_base.lua:1252: attempt to index local ‘definitions’ (a number value)

GUID: b382bb50-c551-4da7-a5ec-494c2f4529d4
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000000399749E10 from 00007FF7E95DCABC

GUID: 5a5eaf73-84c8-48f0-b28f-3bd3c4f7e8b2
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000000000000088 from 00007FF7E94DED73

GUID: f345516b-6ecd-4822-b395-dbdb689dfb5f
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000020F0BF824B0 from 00007FF7E94DEEFF

GUID: 37e62f01-950a-457d-ad54-fa9523f8b071
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address FFFFFFFFFFFFFFFF from 00007FF7E9318AD8

GUID: 45be74ca-bd18-4b64-88d5-bcd4f2457a55
Log File:
Info Type:

[Engine Error]: Invalid temporary variable marker 0x2b0dab5 (0000024484730000, 0000024484A199A0, 0000024484A1E8C0, 0000024484A1BFFC)

At D:\a\d\rel_engine_darktide\release\2024_10_23_Patch1.6.0x\runtime\application\script\lua_environment.cpp:1328 in function stingray::LuaEnvironment::clear_temp_variables

---

GUID: 05291866-6468-4b25-a77c-64d8aa87e676
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000000000000078 from 00007FF7E928BDD6

GUID: c832c029-6395-4828-a807-40584f58b34d
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000000000000006 from 00007FF6464A4BFC

GUID: 05b75701-9178-48b9-be8e-7052227b5bbf
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 000001C442021AC4 from 00007FF61541EEE6

GUID: 6f31b6dc-8c5e-45e3-ae87-c970192f1fbe
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build e73a45d5959dfc1c13e401cd6c1ddaa731f841e1
accessing address 0000021108BE7AE0 from 00007FF61541EEFF

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

crash_dump-2025-01-02-16.30.05-05b75701-9178-48b9-be8e-7052227b5bbf.dmp (915 KB)
crash_dump-2025-01-02-07.54.23-c832c029-6395-4828-a807-40584f58b34d.dmp (864 KB)
crash_dump-2025-01-02-17.11.13-6f31b6dc-8c5e-45e3-ae87-c970192f1fbe.dmp (1.24 MB)
console-2025-01-02-07.54.23-c832c029-6395-4828-a807-40584f58b34d.log (170 KB)
console-2025-01-02-08.15.22-ebb48ce8-2cf0-4dd8-a54a-fca217bbac0f.log (145 KB)
console-2025-01-02-07.48.24-649be44d-1d2d-428d-b46f-3e839560f68e.log (120 KB)
console-2025-01-02-17.11.13-6f31b6dc-8c5e-45e3-ae87-c970192f1fbe.log (72 KB)
console-2025-01-02-16.30.05-05b75701-9178-48b9-be8e-7052227b5bbf.log (214 KB)
console-2025-01-02-07.48.24-649be44d-1d2d-428d-b46f-3e839560f68e.log (120 KB)

[FatsharkJulia]

That’s a whole lot of crashes! I’ve raised this with our Engine Developers and will report back to you, but much of the crew are away until next week.

[Kuug]

Thanks, I just crashed twice and got the Havoc lockout penalty. Then just played a Damnation quickplay and it crashed again as soon as I moved on the Mourningstar. It’s getting worse the more I play the game.

[EddyTheLiar]

I’ve done the same where I keep a text document to paste all the crash messages into. Honestly man with everything I’ve done in an attempt to prevent this including reinstalling the game (including removing the AppData folders), reinstalling Graphics drivers, updating hardware and software. Even so far as to reinstall Windows on my PC! There comes a point where I have to accept that it’s not my PC, it’s the game and how it’s been developed.

[DashHandsome]

It might be a stretch but I have a hunch for why this might be happening:

• This thread timing lines up with when Microsoft was pushing out Windows 11 24H2 the update that breaks everything to more people
• With 24H2 they rewrote part of the graphics display interface in Rust
• GDI is old but is still part of WinAPI and the Windows DWM
• Direct2D can interact with both GDI and Direct3D
• some of OPs crashes mention Lua errors with Hud and view data

It’s worth mentioning that the part of GDI that was rewritten was Regions which can be used for getting the cursor location (sounds like UI and HUD to me).

Two other things stuck out when I got sucked down the wiki rabbit hole. From the Windows DWM page:

Writing the output of GDI to system memory is not hardware accelerated, nor is conversion to the DirectX surface. When a GDI window is minimized, invisible, or visible on the same monitor as a full-screen DirectX application, by limitation of GDI, the GDI bitmap buffer is no longer received by the application when requesting a device context during painting or updating (this can sometimes be seen when a GDI operation copying from one window to another output black or empty regions instead of the expected window content). Thus, DWM uses the last bitmap rendered to the buffer before the application was minimized.

Applications can mix either rendering techniques across multiple child windows, as long as both GDI and DirectX are not used to render the same window. In that case, the ordering between DirectX and GDI rendering cannot be guaranteed, and as such it cannot be guaranteed that the GDI bitmap from the system memory has been translated to the video memory surface. This means that the final composition may not contain the GDI-rendered elements. To prevent this, DWM is temporarily turned off, as long as an application that mixes GDI and DirectX in the same window is running.

From the Direct3D Page:

Direct3D implements two display modes:

• Fullscreen mode: The Direct3D application generates all of the graphical output for a display device. In this mode Direct3D automatically captures Alt-Tab and sets/restores screen resolution and pixel format without the programmer intervention. This also provides plenty of problems for debugging due to the ‘Exclusive Cooperative Mode’.
• Windowed mode: The result is shown inside the area of a window. Direct3D communicates with GDI to generate the graphical output in the display. Windowed mode can have the same level of performance as full-screen, depending on driver support.

I know the engine has been around for a while so it’s not impossible that it’s a GDI issue?

So either something breaks occasionally as a result of the Regions being updated, it interacts poorly with the DWM or doesn’t let the DWM doesn’t turn off when it should, or it’s a side effect of Darktide’s fullscreen option being borderless windowed (assuming it counts as Windowed for that last quote)

And just because I had to double check if it’s relevant, SpecialK does report two GDI DLLs as being loaded when booting Darktide: