KNOWN ISSUE: AMD 7000 Series GPU Hang Crash '[Engine Error]: HRESULT: 0x887a0005[...]'

is this game or amd driver related ?

GUID: 14117090-65f0-4707-a4af-6a184cf3b60b

Log File:
Info Type:

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

At D:\a\d\eng\darktide\release\2026_08_11_Patch1.13.x\s\runtime\d3d12_render_device\d3d12_debug.cpp:1634 in function stingray::aftermath::d3d_assert


hope some update about topic in monday or tuesday, because its unplayable, and newest amd driver seems not fix it

Im sending ctd reports to amd since weeks about this bug. they either dont care or are so slow.

edit: yea confirm 26.10.2 changes nothing. ctds still occur.

Sorry to hear that driver version 26.10.2 is unstable too. We’re in communication with AMD, but it’s my understanding that we’re in a spot currently that we can’t do anything further from our side - and we’re also awaiting updates from AMD.

Issue Type (Required):

Crash - During Play

Issue Description (Required):

The game keeps crashing mid-mission. I already tried the below:

My hardware:

  • AMD Radeon RX 7800 XT, 16 GB
  • AMD Ryzen 5 7600x
  • Kingston Fury 16GB (2x8GB) DDR5 6000MT/s CL40-40-40 1.35v MXP (KF560C40BBK2)

My setup:

  • Steam Cloud Sync off
  • Portrait rendering off
  • GPU is not overclocked: stock settings
  • Ray tracing is off
  • Frame generation is off
  • Framerate is capped to 120
  • Steam overlay disabled during my latest test (still crashed)
  • Windows 11, AMD mobo chipset drivers, BIOS and GPU drivers (AMD Adrenalin 26.10.1) at latest versions.
  • Darktide 1.13.0
  • Not modded
  • No other overlays/recording software is active (e.g. https://support.fatshark.se/hc/en-us/articles/7709667528349--PC-How-to-Resolve-GPU-Crashes-in-Darktide )
    Radeon Anti-Lag is disabled.
    Reproduction rate: very high. It’s rate to be able to complete a single mission without a crash. And often multiple crashes (>3) per mission.

Copilot analysis highlights (for details see: Loading Google Docs )):

  • “And there’s a particularly interesting clue: the renderer repeatedly waits for GPU fences, including a 6.9-second RI::wait_for_fence stall during shutdown, alongside unreleased D3D12 render targets. [ console-2026-10-30-21.31.59-9a98ff58-bd0d-451a-8641-5b2dba915d99.log]”
  • "There’s now a report from October 21, 2026 showing essentially your exact Darktide failure after the recent update:
    Patch1.13.x → d3d12_debug.cpp:1634 → DXGI_ERROR_DEVICE_HUNG
    That user has a Radeon RX 7900 XTX, and reports crashes every mission. [steamcommunity.com]
  • "Your final logged engine crash is actually an access violation (0xc0000005) during shutdown, after Darktide has already initiated quit_game. Immediately beforehand there are multi-second rendering stalls, unreleased render targets and GPU fence waits. [console-2026-10-30-21.31.59-9a98ff58-bd0d-451a-8641-5b2dba915d99.log]
    So you may actually have two symptoms:
  1. the device-hung events captured in the GUID reports; and
  2. a separate Darktide engine bug during resource cleanup/shutdown.
    That’s another reason I wouldn’t jump to “failing GPU.”

Darktide crash dump file from my %appdata% folder, “crash_dump-2026-10-30-21.31.59-9a98ff58-bd0d-451a-8641-5b2dba915d99.dmp” : https://drive.google.com/file/d/1Ef8EIg7lVtGWi0dcxWGJlzYARQN6I5Xx/view?usp=sharing

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

No, I don’t use mods

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

PC - Steam

Player ID (Optional):

[PC] Crash Report (Optional):

GUID: 37aec883-0768-440e-8a18-d5d511f4f4a3
Log File:
Info Type:

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

At D:\a\d\eng\darktide\release\2026_08_11_Patch1.13.x\s\runtime\d3d12_render_device\d3d12_debug.cpp:1634 in function stingray::aftermath::d3d_assert


====

GUID: c1b5eee7-1652-4aa6-b095-d74bcc7d8476
Log File:
Info Type:

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

At D:\a\d\eng\darktide\release\2026_08_11_Patch1.13.x\s\runtime\d3d12_render_device\d3d12_debug.cpp:1634 in function stingray::aftermath::d3d_assert


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

darktide_launcher.log (201 KB)console-2026-10-30-21.31.59-9a98ff58-bd0d-451a-8641-5b2dba915d99.log (93.1 KB)

try 26.3.1 drivers

Issue Type (Required):

Other

Issue Description (Required):

When playing Darktide I randomly crash, frames are smooth and no gittering, but without warning the game freezes on a frame, whatever audio que is played and then it boots me to desktop, I’ve seen that it might be related to my GPU being an AMD. This is the crash report I’m given when it happens.

GUID: 174b3dd4-f578-44a3-b6a3-3dc487f15d99
Log File:
Info Type:

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

At D:\a\d\eng\darktide\release\2026_08_11_Patch1.13.x\s\runtime\d3d12_render_device\d3d12_debug.cpp:1634 in function stingray::aftermath::d3d_assert


Steps to Reproduce (Required):

I can’t reproduce it on purpose, it’s randomly throughout missions, not the same place, action, or modifier, sometimes I can make it through an entire mission without crashing and sometimes I crash early in the mission.

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

No, I don’t use mods

Reproduction Rate (Required):

Often (<75%)

Platform (Required):

PC - Steam

Player ID (Optional):

Run705

ok. thank you for the updates. then its up to amd. darktide is a great game and my #1 in playtime. hope to get it crashfree soon again. :slightly_smiling_face:

Just so this doesn’t fly under the radar, something broke on your end too at the very least.
I’m aware that the 26.10.1 driver was available the night before your patch, but i was still on 26.9.2 when your patch went live and the crashing started.

And i had played darktide with that driver up to 12 hours prior to patch time with zero issues, and i also had to revert all the way back to 26.8.1 to get it working again which was two previously working driver revisions back.

Just had the same crashes as above on driver 26.8.1 with a 7800xt this is not an AMD issue, this is a Fatshark issue. Test your updates on AMD systems. This is crazy that this is still happening.

I was stable on drivers from August, I think 26.8.1 but I was forced to update to play the new cyberpunk 2077 content which requires 26.10.1 minimum. Now I’m crashing atleast once per havoc game (cp2077 is stable tho). Card is: SAPPHIRE PULSE AMD RADEON™ RX 7800 XT GAMING 16GB GDDR6

I’ve noticed several times that some amd driver updates have reduced performance or stability, so try to avoid updating where possible. I will go back to 26.8.1 which I believe was my last stable driver. I did not try 26.9.x

Edit

Maybe of note: I updated both the “amd software: adrenalin edition”, and the “amd chipset drivers”. Maybe both have to be rolled back for 26.8.1 to be stable.

throw back to the time when darktide was unplayble for 3 days for amd users when archivum was released
premiere quality

@FatsharkLev Can we get an update on this other than “waiting on AMD” based on actual events?
Again, a game update shouldn’t break 3+ driver revisions that were already working and force you to roll back to an august driver revision and have the conclusion be “the newest driver did it”.

It’s not the end of the world but it is fairly tedious to downgrade drivers and reboot every time i want to play Darktide vs something like PoE2 that throws a hissyfit if i don’t have the most recent drivers installed.

It’s fine doing that for a few days or even a week, but over two weeks with comms basically saying anything but “look at those guys over there!” isn’t ideal.

Not calling you out here as i get how the public facing account job works and i know what your actual statement said, but please push it up the chain if there’s still a belief internally that the 26.10.1 driver update caused this, because that provably isn’t it.

FWIW, I installed the new chipset drivers the day after the crash bonanza started, and i it worked fine on 8.1 out of the gate. I did however have to roll back to 8.1 right afterwards as the updater had ninja-reset my install preferences to “automatic” so it added 10.1 back for the GPU in the same go.

A lot of this can usually be mitigated by just checking “factory reset” when you update from one iteration to another if you don’t want to do a manual install/DDU every time.
Why this isn’t the default setting is anyone’s guess.

I just rolled back/reinstalled amd software: adrenalin edition 26.8.1 and left the chipset drivers up to date. It has not crashed since.

Hey @FatsharkLev ,
will come forward with an update or statement ?
26.10.1 /.2 drivers is not the issue. I play many titles, manyfold more demanding and not a pip… system is stable and the performance is top. I dare to run Darktide ( or better Crashtide at this point) with the October drivers, including the sub realease, and my PC acts like is going to die…
Is been 4 years since your release and on every single massive update the game turns unplayable for AMD GPUs owners.. at somepoint this stops being fun… and I will state it again IT IS NOT AMD THIS TIME…

reading through this thread makes me want to never buy AMD cards

Is there anything that is going to be done about this anytime soon? This is now the second event that I have missed due to this whole mess and as other people in this thread have mentioned I never had any issues before the October 20th patch and I was already on 26.9 drivers. I am not really willing to downgrade my drivers just to play Darktide when so many games demand the newer drivers.

New drivers.

But no mention of Darktide crashes.

Was about the ask if any luck on the 26.11.1 drivers.

Thanks! We notified AMD, but it seems we haven’t made their release notes list - which I’ve passed on internally.

We’re still investigating on our end, but no updates to share on this front just yet. For now, while this is figured out, I can still only recommend rolling back to prior stable driver versions.

We appreciate this is a very frustrating and inconvenient issue, and will continue doing all we can to get it resolved! Thank you all for your continued patience and understanding.