I’m rolling back to 26.1.1 (Release Date: 2026-01-21), which I previously used with FSR Frame Generation and no crashes before Darktide 1.11.0.
Current version: 26.1.1
Available update to 26.3.1 (had to turn off autoupdate).
My launcher settings (FSR 3.1 Frame Generation: On)
The game still crashes:
GUID: 44ca7464-b588-4cf2-b238-7045f6a27dec
Log File:
Info Type:
-----------------------------------------------
[Engine Error]: HRESULT: 0x887a0005 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DRIVER_INTERNAL_ERROR, assert: ``
At `D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570` in function `stingray::aftermath::d3d_assert`
-----------------------------------------------
[Crash Link]:
crashify://44ca7464-b588-4cf2-b238-7045f6a27dec
I’m rolling back to 25.12.1 (Release Date: 2025-12-10), which @bornw states work properly on RX 9070XT with AMD FSR Frame Generation turned On. I previously used it as well in december 2025 with FSR Frame Generation and no crashes before Darktide 1.11.0.
Current version: 25.12.1
Available update to 26.3.1 (had to turn off autoupdate) as with 26.1.1. Launcher settings are same.
The game still crashes:
GUID: 9f04e0e7-f926-4c40-a124-88aac971ebef
Log File:
Info Type:
-----------------------------------------------
[Engine Error]: HRESULT: 0x887a0005 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DRIVER_INTERNAL_ERROR, assert: ``
At `D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570` in function `stingray::aftermath::d3d_assert`
-----------------------------------------------
[Crash Link]:
crashify://9f04e0e7-f926-4c40-a124-88aac971ebef
I wonder how the hell @bornw is able to play it with AMD FSR Frame Generation on RX9070XT for 3 hours without a crash.
Moreover, with driver 26.3.1 the game run without crashes on patch 1.11.1. The FSR Frame Generation was not working as intended (no fps gain, stuttering), but there were no crashes. After game update to 1.11.2 the game starts crashing everytime I run it with FSR Frame Generation turned on. I don’t see how it is related to drivers.
I have further downgraded my driver to 25.8.1 and the game still crashes. Proof:
GUID: c6755a5d-6fa8-4104-bc01-3c7c6df63ab8
Log File:
Info Type:
-----------------------------------------------
[Engine Error]: HRESULT: 0x887a0005 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_INVALID_CALL, assert: ``
At `D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570` in function `stingray::aftermath::d3d_assert`
-----------------------------------------------
[Crash Link]:
crashify://c6755a5d-6fa8-4104-bc01-3c7c6df63ab8
For me it’s enough. I’ve lost few hours doing clean gpu drivers reinstalls every time with no result.
This is no fun, I haven’t bought the game to do QA jobs with no payment, after my regular job. I have bought this game and invest my time to have fun and relax. If the Fatshark studio cannot afford 600$ GPU for devs to debug the code, and asks end users to debug for them, I can only feel sorry for such employer.
I’m changing my steam review to negative and will advise my friends against purchasing the game until the issue is solved.
I digged deeper. I know probable cause why @bornw game stopped crashing and why his crashes resumed. Also I discovered how to use FSR without crashes.
The boundary condition for crashes is to enable simultaneously:
- In the game’s video settings: “AMD FSR 3.1 Frame Generation”
- In the driver’s settings: “AMD FSR Frame Generation: Switch to the latest FSR version with machine learning in supported games”
The game uses AMD FSR 3.1 Frame Generation. On AMD RX 90xx graphic cards, the Adrenaline Software tries to switch to the latest FSR version (FSR4 or FSR Redstone, depending on the game), which is better than FSR 3.1.4 both in quality and performance.
However, the game engine, likely due to an unhandled or incorrectly handled exception, treats the FSR change as an AMD driver failure. It would likely be sufficient to force pause rendering for 10-500 milliseconds and then resume - this would handle the exception and allow the driver to switch to the newer FSR version.
From what I have read, FSR 3.1.4/4.x/Redstone is backwards compatible and has same interface for game engines, so the issue is not related with driver version. The crashes stem from the errors in FSR implementation in darktide.
So.. after downgrade @bornw probably didn’t reboot the PC. After downgrade the Adrenaline Software hasn’t set HYPER-RX nor any other profile, so he had “AMD FSR Frame Generation: Switch to the latest FSR version with machine learning in supported games” off in gpu driver settings.
Indeed with this setting set to off there are no crashes. Moreover, it enables FSR 3.1.4 in-game. To replicate the setting in driver 26.3.1 I set up HYPER-RX profile and turn off “AMD FSR Frame Generation” in the profile settings. The game runs with FSR 3.1.4 and AMD FMF 2.1 using the latest driver version which results in…
~90 fps min in mourning star @ 100W (40% gpu usage)
~440 fps max in mourning start @ 270W (99% gpu usage)
~120 fps in menus @ 100W (40% gpu usage)
~220 fps in missions @ 270W (99% gpu usage)
Something is still strange in the way FSR works in this game. The fps min-max range should be ~20 fps, not ~350 fps. Will try to hard limit to 185 fps.
Something new for people with this issue to try. FSR 3.1.4 is the version included with the game and while it should be compatible with FSR 4 driver stuff, there’s still bugfixes included in newer DLLs that the game hasn’t updated to. No promises but the version right after the one included in the game files includes a crash fix for framegen.
Try manually updating the FSR files by downloading them from AMDs github
You need:
- amd_fidelityfx_upscaler_dx12.dll
- amd_fidelityfx_framegeneration_dx12.dll
- amd_fidelityfx_loader_dx12.dll (not .lib!)
You have to make one change for the newer versions to work.
Go to {game library}/Warhammer 40,000 DARKTIDE/binaries/ and delete/rename/whatever the old amd_fidelityfx_dx12.dll
Copy/paste the three DLLs you downloaded into the binaries folder and then rename amd_fidelityfx_loader_dx12.dll into amd_fidelityfx_dx12.dll
If this does fix the crashes, be aware the game will replace the loader DLL acting as amd_fidelityfx_dx12.dll with the actual amd_fidelityfx_dx12.dll every time the game updates.
AMD split FSR into multiple DLLS so devs only have to include what they’re using and load a single DLL
The loader DLL will load whatever the game is asking for and is backwards compatible per AMD:
amd_fidelityfx_loader_dx12.dll: A small loader DLL, not containing any effect code. This DLL only manages the loading of effect type DLLs to provide the effects to the calling application. It is interface- and behavior-compatible with amd_fidelityfx_dx12.dll.
Luckily the game only looks to load the file named amd_fidelityfx_dx12.dll but doesn’t do any check on what it actually is so as long as you rename the loader file to that it Just Works TM
@FatsharkJulia any update from devs? Will it be patched next hot fix? @DashHandsome gave some hint what and where to patch. However I would preffer official solution by game developers rather than shuffling dll’s by myslef.
@DashHandsome can you confirm switching dlls according to your post solves the crashes?
I’ve since swapped to linux which isn’t officially supported so whether or not it works for me wouldn’t matter (and tbh I hate framegen, even with FPS in the hundreds the latency is too noticeable)
I’m just using what I know to suggest things to try for those that are having issues currently
Even if my suggestion doesn’t help it’s still useful info to help the devs narrow down what the issue could be
We’re still working on this, I’ll update as soon as I’m able to. Thank you for your patience 
I got 800 hours in this game and recenlty did an upgrade to my hardware because my old SSD and RTX 3070 weren’t performing as well as I liked, frequent studders, poor graphics. Found a new xt9070 and read the reviews of how it was beating out the Nvidia 5070’s so felt confident. Can’t even play the game I own now and the optimization is so abysmal again I find myself here wondering how this is even possbile. I’ve never had such a difficult or infuriating experience just geting a game to WORK PROPERLY or in an acceptable/playable state. As someone who is trying to push Havoc and play daily it’s a bit of a slap to the face tbh.
Somehow I completely skipped over this part. There are indeed two toggles, with FSR4 upscaling on by default.
It’s not ideal but FSR4 upscaling with FSR3.1 framegen is still wildly better than using
3.1 for both.
May or may not be related but the FSR4 framegen stuff was added the same time the FFX DLLs were split up and that was for FSR 3.1.6 rather than the 3.1.4 the game comes with.
3.1.4 is the minimum required version for FSR 4 framegen but I imagine it’s different for Darktide now that Fatshark owns Stingray again and can change engine behavior every update.
Just FYI it might be best to leave Darktide on the default profile in Adrenaline. FSR4 is on globally anyway. Adrenaline doesn’t point to the right exe most of the time which is why the overlay reports FSR4 as not working even when it is.
No doubt due to the very “unique” way the launcher runs multiple exes before starting the game or how it runs the shader cache builder after starting the game according to the logs. Can’t get behavior like this anywhere else
Well, I’m not using upscaling because I lose hud information if not runing native resolution (numbers just disapear). Indeed AMD FSR Upscaling option can be left enabled in Adrenaline and causes no issues.
When runing 3440x1440, no rtx, most high settings, I have 350-450 fps in physkanium and 160-260 during auric missions. What I have noticed is that in physkanium my GPU runs on 250-275W (undervolted + 90% PL), but during missions it sometimes drops power draw to 120-160W while CPU usage is at ~60% (i5-14600k undervolted, ~24 000 pts in Cinebench R23, temps ~80C so below throttling).
@FatsharkJulia Patch 1.11.5 here, turned AMD FSR Frame Generation in Adrenaline. The game doesn’t crash anymore in the operative selection screen or in the Mourningstar. Good job!
I have observed that steam overlay shows FG in game and FPS in menus. This switch of FG or non-FG is transparent for a player. In menus I have stable 60 fps with 1% lowest 58 fps.
I have played a little with in-game settings. Implementation of FSR Frame Generation 4.0.0 is superior to 3.1.4 or no frame generation. What bothers me is that AMD Adrenaline shows that frame generation is off even if it’s clearly on.
I experience:
- 140-350 fps in the Moruningstar
- 240-410 fps in the Meat Grinder
- 110-260 fps in missions
The gameplay feels much smoother now, except when fps drops in mission under generated 140 fps (under 35 real fps). I have noticed that when this happens my GPU draws around 100W (full load power draw is 270W), gpu usage is reported at ~80% and cpu usage is ~60%. I wonder what this power draw drop is related to.
More or less, I am happy with the fix. Will change my review on steam back to positive. Would love if you can optimize the game even more for AMD GPUs. However I’m aware that the team may be delegated to other tasks now.
