[2022] KNOWN ISSUE: Backend Error

We have made substantial improvements since the Closed Beta Test, however we anticipate a small number of players may continue to experience Backend Errors.

Please help us out by including the information listed below in your report:

Issue Description:

Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

1. Play Chasm Logistratum as Ogryn (Skullbreaker)
2. Attempt to pick up the second Grimoire
3. Observe Backend Error

Platform:
[Steam/Microsoft Store]

Player ID:
[Steam ID/Steam Profile URL/GamerTag]

Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]

Upload Console Log:

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
5. Upload here

Existing reports may be merged here, to help us keep track of the issues being reported.

I understand this has worked well for some of you. Keen to hear if this resolves anybody else’s issues.

Just wanted to emphasise before I clock out for the night that we are very much aware of how critical this issue is (in addition to the internal_error), and it may seem like we’re being quiet on the matter - but the reality is we’re deep in investigation.

As soon as I have more information to share, I will!

I understand some players have been able to work around this by changing their DNS or using a VPN but I appreciate this isn’t ideal.

I’m merely the communicator, nothing will change if I head to bed. The smart people are still working.

They are also working on the current downtime as we speak.

We’re looking for somebody that is encountering the Backend Error and has Deadline exceeded in their console logs to help us with our investigation. You would need to be quite confident in working with your PC and willing to set a Windows Environment Variable though. Please reach out!

IMPORTANT! Our developers are asking if anybody with the Backend Error (NOTE: NOT the internal_error (Error Code: 2007) or any other error) can try the experimental branch in Steam, and see if that resolves their issue.

PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.

1. Open the Steam client
2. Right-click Darktide in your Steam library
3. Select ‘Properties’
4. Select ‘Betas’
5. Enter the password cTYPtKTsfMDsLHAV
6. Select ‘Check Code’
7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
8. Select experimental - Experimental Builds
9. Close the pop-up window
10. A 20mb download should now start
11. Play!
12. Post here to let us know the outcome

Thank you for trying, and for the detailed account. I’ve let our developers know.

Super! Seems we’re making some progress.

NOTE: The experimental branch in Steam has been updated to include logging for other issues. The experimental branch now includes:

• POTENTIAL Backend Error FIX. We understand this hasn’t worked for everybody, and are continuing to investigate
• Additional logging for internal_error (Error Code: 2007)
• Additional logging for nonexisting_channel (Error Code: 2001)
• Additional logging for various GPU-related crashes, AND A POTENTIAL FIX!

Please note that the additional logging supports our investigation and will not necessarily solve the underlying issue for you at this time. We encourage anybody with these issues to use this branch, so we can continue work on addressing these issues as quickly as possible.

PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.

1. Open the Steam client
2. Right-click Darktide in your Steam library
3. Select ‘Properties’
4. Select ‘Betas’
5. Enter the password cTYPtKTsfMDsLHAV
6. Select ‘Check Code’
7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
8. Select experimental - Experimental Builds
9. Close the pop-up window
10. A 1.8GB download should now start
11. Play!
12. Post here to let us know the outcome

Still experiencing Backend Error and have non-alphabetical characters, including spaces, in your character’s name? Try without!

Hyphens are OK.

An update has been pushed to the experimental build to address GPU-related crashes, in addition to internal_error (Error Code: 2007) and nonexisting_channel (Error Code: 2001).

Please let us know if you observe any adverse behaviour.

Were you able to play on the previous experimental build or not at all?

Servers are down for maintenance prior to launch. The incorrect error is being displayed.

One of our Backend Engineers mentioned seeing more and more references to Kaspersky, so I load up this post and it appears @Quegon has already hit the nail on the head!

Any luck if you simply exclude the Darktide.exe (Steam\steamapps\common\Warhammer 40,000 DARKTIDE\binaries) in Kaspersky as opposed to closing it down entirely?

FYI: This also applies to Norton.

Kaspersky people, can you tell me which version you’re using? As in, the version number?

For Microsoft Store/Game Pass users, please make sure you are logged in to the same account as your Xbox app on the Microsoft Store app also.

Hi @InquisitorPetel,

Sorry to hear this. We are currently investigating a recent spike in occurrences of this Backend Error.

May I ask, what ISP do you use? and which region are you playing from?

Thanks!

Noted, I’ll let our developers investigating know. Thank you!

If you are using the ISP CenturyLink or Verizon, or located in the Midwest and experiencing this error, please see:

Try switching to Windows Defender, and disable your third party Anti-Virus/Firewall.