Issue Type (Required):
Crash - During Play
Issue Description (Required):
These engine errors gotta get fixed somehow
Win 11 Clean Install
GPU clean install using DDU
All Latest Drivers
RTX 3050 Laptop
32 GB RAM
4GB VRAM
AMD Ryzen 5800h 8c 16t
Tried with and without mods
Tried setting 1 to 14 worker threads. Still crashes.
I face all kinds of errors including the general one and even backend errors just like everyone. I play Darktide for hours. Feels like it just overloads the GPU to cause this engine crash.
[PC] Do You Use Mods? (Optional):
Yes, and I’ve tried disabling them
Reproduction Rate (Required):
Constant (100%)
Platform (Required):
PC - Microsoft Store
console-2025-08-18-00.28.51-3a6b3044-299d-4f7d-b1d8-1881aea231bc.log (1.9 MB)
console-2025-08-18-00.09.21-48b7f50b-e0a9-469e-a931-105f96deeefc.log (321.3 KB)
console-2025-08-17-21.18.42-e100fb04-0b52-4b76-b4dc-2f9ded430533.log (1.7 MB)
console-2025-08-17-20.07.35-288c3063-69b9-4426-bfb5-6d2a9e4c1564.log (999.5 KB)
console-2025-08-16-21.49.42-2d07b5e5-61c6-444f-ac8f-9c9d86e97618.log (3.7 MB)
The logs are a bit wild due to the mods, but the most commonly occurring issue appears to be GPU-related. Could you run through any remaining solutions here, please?:
[PC] How to Resolve GPU Crashes in Darktide
Thank you for looking through all the logs submitted.
- Portrait Rendering: Disabled but still crashes
- [Microsoft Store] Delete Darktide AppData & Verify: Done
- Disable Overwolf Overlay: Not using Overwolf
- Lower ‘Worker Thread’ Count: Have tried all worker thread numbers. Still crashes
- Reinstall Your GPU Drivers: Latest clean install with DDU
- Disable Background Applications: Clean Windows 11 no bloatwares
- Disable Your Overclocks: No overclocks
- Check for Overheating: Temps under 81c
- Using a G-Sync Ultrawide Monitor: AMD Freesync Disabled 1080 laptop monitor
I can upload more console logs if it helps you figure this problem out
- As I was typing this I got hit with 2014:
console-2025-08-25-18.31.59-99bd15b0-2562-4482-8046-0497da59e3bf.log (462.1 KB)
-
Ran without mods and got a 4001 with Backend Error
-
Followed by 1016 error code 1
-
1005 right after completing the mission
-
Disconnected from mission 2001
-
After completing a mission, I got loaded back to the lobby. I opened Steam and got hit with: GUID: a7ffeced-0cc8-478c-843f-69656b358f77
Log File:
Info Type:
[Script Error]: scripts/utilities/profile_utils.lua:468: Expected colon but found T_OBJ_END at character 6864
Seems to be some dropped packets here, leading up to the disconnection. I’d recommend playing without mods now 1.8.6 is live, and seeing if there’s any improvement as this hotfix includes changes to maximum packet sizes.
Should the engine-related crashes persist, please be sure to share the crash report or corresponding console log here. 
Thank you so much again for sharing this information. I didn’t get Engine Errors after the appdata deletion, followed by verifying files which disabled all mods. Looks like Mods were behind my GPU crashes. However, if there are any crashes outside of engine errors. I will add it below
Wonder what causes Chat to stop working after a mission or randomly. It gets fixed sometimes when I leave team and join back or sometimes when I restart the game.
Not sure, but chat is a 3rd party service, so that complicates things!
Just now crashed GUID: d41d6993-2454-4ac8-aad3-47584c432ece
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\2025_04_29_Patch1.8.x\runtime\d3d12_render_device\d3d12_debug.cpp:1548 in function stingray::aftermath::d3d_assert
Not using any Mods
console-2025-08-25-22.06.34-e6da39f5-5935-4e32-8428-9634b83ff5d4.log (476.6 KB)
console-2025-08-26-20.49.16-0726ef75-ff12-4e3f-b359-4c671e5a0ba3.log (7.2 KB)
console-2025-08-26-19.29.23-d41d6993-2454-4ac8-aad3-47584c432ece.log (824.4 KB)
console-2025-08-26-02.17.17-60974906-addd-46ee-abcb-9e1e2f7fe682.log (158.8 KB)
console-2025-08-26-00.39.36-a7ffeced-0cc8-478c-843f-69656b358f77.log (945.3 KB)
Last 5 logs
Idk who controls the chat but the chat box needs some kind of refresh that would bring it up at aleast after 1 or 2 missions
Another 2014
There’s a couple of issues here, one being the dropped packets which would indicate some connection instability, and another being GPU-related issues. I understand you’ve ran though our solutions for this already but the crashes have persisted. As this must be having quite the impact on your experience in Darktide, would you like me to assist with a refund?
I mean, Thank you for the offer with refund but I love this game. No need to refund. Just out here sharing the logs trying to see if anything helps yall figure out the cause of these issues.
Right now I’m running MSI Afterburner at -339 core clock reduction with TdrDelay, TdrDdiDelay both set to 60 (Decimal Values). Also set TdrLevel to 0. Haven’t been getting Engine Crashes but whatever else causes the crash now (rarely) doesn’t come with any error code or pop up( like the Engine Error popup or D3D12 removed or hung or GPU Timeout). Now its 2014 and 2001 codes that pop up in game. If its my connection or packet loss, I understand.
Is there a way for me to check packet losses with Darktide servers?
What all I did to reduce these errors
Core clock is set to 1500 MHz and locked Voltage to 1000mV with L key on MSI Afterburner. Running at base clock I guess. Im not hitting my GPU temp throttles as HWinfo64 shows 87c is the max. Its lower than 80c when I look up the sensors. Memory clock is set to 6000 MHz. 7 worker threads set to the game Launcher. Disabled MPO. Reduced Refresh Rate from 144 to 60.
Links
https://dev.epicgames.com/documentation/en-us/unreal-engine/dealing-with-a-gpu-crash-when-using-unreal-engine
Nvidia Driver that im using now is 561.19 DDU/Nvclean/Optimus Install with Rbar force enabled.
I’m sure these dont guarantee a fix but if it helps it helps. I can continue to post logs under if its not too much headache for yall @FatsharkJulia
console-2025-09-03-17.59.22-acedc23c-155f-4cc8-aff7-5c9394896d9f.log (19.9 KB)
It sounds like you’ve been able to crack the case of the GPU-related crashes with the clock changes you’ve made which is super! 
The other errors you’ve been experiencing (2014, etc.) will be due to a separate cause.
You can use something like Wireshark to monitor dropped packets during play, but it is a bit of a learning curve admittedly.
I notice you’ve included your experience in INVESTIGATION: Disconnects (Error Code: 2001, 2014, 3013, 4001) & General Connectivity Issues which is particularly helpful as the team are monitoring this and aware of a recent increase in errors.
I’d still recommend continuing to investigate the dropped packets in case of a localised cause, and if you change your mind on wanting a refund I can easily help with that.
So I looked up a bit more bout this. I haven’t been getting the errors reports. Just that the game crashes and then freezes the system. Requires a forced restart.
I looked up event viewer and found out that 2 common errors have been poppin up when it crashes. I read some forums where 20 series 30 series and even 40 series are facing the same issue. No fix have been found so far for these Event IDs 14 and 153. I have tried so many drivers it just keeps crashing on all of them. Even on the one the factory ships with.
Temps are under 80 for the GPU and fixed 85 for the CPU. No overheating. I have been playing with -500 on both the core and memory clocks. Set on MSI Afterburner. -10 offset on each core using the PBO2 Tuner on the CPU. stress tested both cpu and gpu and both survived. Ran 2 tests, both from HP. One is done at the time of boot and the other with a software that enters another with graphical interface to do the diagnostics. Built in Diagnostics from HP showed PASSED on all check ups. Power/Board/Fan/CPU/Memory/Video. Same goes with the HP software with graphical interface.
I tried the Exitlag for faster route to the game server. It sure did bring down my ping from 270 plus to 208ms. Even with that set I did face some errors while matchmaking. However, the reconnect would instantly pop up after that and I had better experience. ISP routing/number of hops sucks I guess. Network error is still there for some reason even when Exitlag is showing 0 packets dropped.
I did see some vivox and pipeline based errors in the logs. I have no idea about it and not sure what its pointing to. Which happened on the latest log.
console-2025-09-09-17.39.14-7268773a-75b6-48c7-8fbc-b0dbf92e78e0.log (626.5 KB)
console-2025-09-09-19.12.51-52e77419-4df4-41c1-8625-685bab906bb7.log (4.7 MB)
console-2025-09-10-17.25.19-7ab3c70d-86fd-413a-8fd2-8fd5210376e9.log (1.3 MB)
console-2025-09-10-22.40.01-752de23b-cd9b-4214-8a38-739c83b779a8.log (1.9 MB)
console-2025-09-11-18.55.26-df733e2e-1253-4c01-a8af-e40dcda09b06.log (1.5 MB)
