Error 3013

Warhammer 40,000: Darktide Technical Support
1

Issue Type (Required):

Error - 3013

Issue Description (Required):

I try to load into server with my character and get kicked back with error 3013. After trying a few more times the error will change to 2004, 1005 and 2014. I have tried dns flush, using an alternative internet provider, tried my phones hotspot, updated graphics drivers, deleted the roaming darktide folder, turned off mods, nothing works. It has been 2 hours now of attempting different methods to solve this problem. Everything worked correctly before the patch that came out today. What is the solution to this problem?

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

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

PC - Steam

Player ID (Optional):

2

Sorry to hear this, which country are you playing from?

3

America.

4

Got it, could you share a couple of your most recent console logs with us please?:

  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

console-2026-03-26-15.17.31-122f6162-9814-48d1-a52f-fdbd0c935f77.log (156.9 KB)

This is the most recent log. Today @ 1030 central standard time in the USA.

6

Would you be able to produce a log without mods, please? :pray:

7

console-2026-03-26-15.48.15-817a7c10-5621-4027-9f65-c4588189fd45.log (39.7 KB)

Log without mods. Current time 1048 CST USA.

8

I am on a wired connection. I tried wireless as well. I tried resetting my internet by power cycling the router for more than 30 seconds.

9

Thank you, unfortunately, the latest log is truncated :grimacing: any others you could share?

10

console-2026-03-26-16.50.36-346908b4-4adc-4a34-8684-b515e4e81656.log (241.2 KB)

console-2026-03-26-16.40.06-bcf6cedf-6318-499a-b0ca-85d873285914.log (64.8 KB)

console-2026-03-26-16.33.21-d3477c12-8679-4b0e-937d-fd3dfdf9ff71.log (65.3 KB)

console-2026-03-26-15.48.15-817a7c10-5621-4027-9f65-c4588189fd45.log (129.2 KB)

11

I search for error in the log and is this what I am looking for? or is there something else I can search for?

16:50:52.693 [Lua] INFO [ErrorCodes] Crashify exception enabled from backend for error_code: “failed_handshake_timeout”
16:50:52.693 [Lua] INFO [ErrorCodes] Crashify exception enabled from backend for error_code: “nonexisting_channel”
16:50:52.693 [Lua] INFO [ErrorCodes] Crashify exception enabled from backend for error_code: “pong_timeout”
16:50:52.693 [Lua] INFO [ErrorCodes] Crashify exception enabled from backend for error_code: “failed_found_no_lobby”

12

Thank you very much! I can see a couple of consistent themes here, a buffer overflow and dropped packets.

It is indeed odd that this would start with a relatively small update that doesn’t include anything particularly networky, so I suspect there’s some sort of desync or corruption at play, something mishandling with the packets.

Could you try this?:

Step 1: Disable Steam Cloud Saving

If Steam Cloud saving is enabled for Darktide, this may automatically restore the AppData and consequently cause the issue to resurface.

  1. Navigate to your Steam library
  2. Right-click Darktide
  3. Select ‘Properties’
  4. On the ‘General’ tab, scroll down to ‘Steam Cloud’
  5. Disable ‘Keep game saves in the Steam Cloud for Warhammer 40,000: Darktide’

Step 2: Delete AppData

NOTE: By deleting your AppData, operative loadouts and custom keybindings will be reset. You may wish to make a back-up of the directory in the event deleting your AppData does not work to resolve the issue.

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to: AppData\Roaming\Fatshark
  4. Delete the entire ‘Darktide’ directory

Step 4: Close Steam via Task Manager & Re-Launch

Step 5: Verify Integrity of Game Files

You will then need to use the ‘Verify Integrity of Game Files’ option, which is accessible via the Steam client and will ensure the installation is complete.

  1. Right-click Darktide in your Steam library sidebar
  2. Select ‘Properties’
  3. Select the ‘Local Files’ tab
  4. Select the ‘Verify Integrity of Game Files’ button
  5. When complete, close and reopen Steam
13

After trying your solution I am still getting error 3013. I believe it may be a connection issue due to a possible internet outage or issue in my local area. Nothing else has worked, so I think that is the most likely issue considering those errors relate to connectivity problems. I will reach out to my provider. If you have any other information for me I would appreciate it. Otherwise I want to thank you for your help and quick responses. I appreciate it very much.

14

Well I have checked with my internet provider. There are no issues. I no longer know what to do to solve this issue.

15

Any other options?

16

Could you try a ‘Selective Startup’ to rule out any external interference?:

  1. Press the Windows key
  2. Type ‘msconfig’ and select ‘System Configuration’
  3. On the ‘General’ tab, select ‘Selective Startup’
  4. Deselect ‘Load Startup Items’
  5. Reboot your PC
  6. Launch Darktide as normal, and see if the issue persists
17

Hi i know im responding to an old thread im just wondering if you ever found a solution? My friend is having the same issue, one day playing like normal everything is fine then all of a sudden this error 3013 blocking them at character select. Weve tried everything suggested to no avail, if you or anyone else in this thread ever found a solution or have any suggestions it would be much appreciated, it has been weeks since they have been able to play

18

My friend is having this problem too can we find a solution of how to fix this problem. He try all of the solutions and its still didn’t work. Is Fatshark going to release a new patch so they fix these 3013 errors. I would like to play with my friend again. He’s having a hard time connecting to the UK server.

19

I had this error today now 2-3 times in a row when trying to login after lunch, then just trying once more so either 3rd or 4th try I got in.
Before this I’ve never seen this error on either fiber or 5G connection, with a play time of 4000+ hours, so something strange is going on with Fatsharks AWS backend

20

Had this issue since the last update, for whatever reason the only “fix” that works for me, so far, is to use a VPN, though I wish I didn’t have to with it slowing everything down…

Edit -I’m based in the UK, if that changes anything.