FatsharkLev

@BuckyDucky, unfortunately the crash report isn’t bringing up any data our side.

Instead, could you please provide us with your most recent console logs so we can take a look?

Hi @Beco0001

Sorry to hear this.

This specific crash is on our radar and due to be fixed in our next update. This is occurring due to an issue with a specific sound device being set, it being disconnected with Darktide closed, and the device then not being recognised when launching again.

In the meantime, you can resolve this by removing your Darktide Appdata directory (please note, by doing so you will lose any custom settings/configurations e.g. keybindings).

To do so:

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
5. Restart Darktide as normal

Please let me know how you get on.

Hi @Bzoargh

This specific crash is on our radar and should be fixed in our next update. As I understand it, this crash is occurring due to a specific sound device being set, then if the device is removed/disconnected after Darktide has been closed, upon relaunching it isn’t recognising the selected sound device and is crashing.

In the meantime, you should be able to resolve this crash by removing your Darktide Appdata directory (please note, by doing so you will lose any custom settings/configurations e.g. keybindings).

To do so:

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
5. Restart Darktide as normal

Hi @theb,

Sorry to hear this.

This specific crash is on our radar and should be fixed in our next update. As I understand it, this crash is occurring due to a specific sound device being set, then if the device is removed/disconnected after Darktide has been closed, upon relaunching it isn’t recognising the selected sound device and is crashing.

In the meantime, you should be able to resolve this crash by removing your Darktide Appdata directory (please note, by doing so you will lose any custom settings/configurations e.g. keybindings).

To do so:

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
5. Restart Dark...

Hi @MrMero,

Sorry to hear this.

This specific crash is on our radar and should be fixed in our next update. As I understand it, this crash is occurring due to a specific sound device being set, then if the device is removed/disconnected after Darktide has been closed, upon relaunching it isn’t recognising the selected sound device and is crashing.

In the meantime, you should be able to resolve this crash by removing your Darktide Appdata directory (please note, by doing so you will lose any custom settings/configurations e.g. keybindings).

To do so:

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
5. Restart ...

Hi @PureSightt,

Sorry to hear this.

Could you please provide us with your recent console logs and launcher log files so we can take a look?

Hm okay could you please provide us with your recent console logs, launcher log and your user_settings.config file?

These can all be located in your Darktide AppData directory:

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

Thanks in advance!

Hi @hep,

To confirm, do you have Steam overlay enabled?

It may be that your Anti-Virus/Firewall is blocking access to store content from our CDN. Please ensure that you have appropriate exceptions in place for Darktide for both your Anti-Virus and Firewall.

You’ll need to add the following exceptions:

• Darktide.exe in \SteamLibrary\steamapps\common\Warhammer 40,000 DARKTIDE\binaries
• EasyAntiCheat_EOS.exe in \Program Files (x86)\EasyAntiCheat_EOS

A GPU-related crash appears to be occuring. Please try our solutions here:

I’ve looked up this crash in our database, and previous reports have occurred due to some kind of streaming webcam driver hooking into the game. Unfortunately, nothing we could do to permanently resolve this from our side.

If this is something that could apply to you, then I recommend to either try disabling the webcam, or to try updating any drivers for it/any streaming software.

Failing this, you could also try a Selective Startup -

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

If the error no longer occurs after having performed the Selective Startup, try re-introducing your programs one-by-one to determine which is the culprit.

No worries! Glad to hear your characters are fine

Hi @Mave,

Please check out a potential solution, here:

Hi @THAT1BOUNCER

I’m having trouble locating your account in the backend with the ID provided.

Could you please let me know your Gamertag so I can take a look at this for you?

Thanks for trying and letting me know. Unfortunate that this didn’t do the trick

It may also be worth running through other potential solutions, here:

This error code is certainly one of those headaches!

That would be super useful! Would be good to confirm the error on both platforms, and I’m currently collating PC player console logs with Error 2014 occurrences to help the developers with their investigation. Thank you in advance!

Hi @Valhallmure,

Could you please try a clean reinstallation of your GPU drivers?

Please see:

Glad to hear the connectivity issue has seemingly resolved itself!

As for iCUE crashing, I’m genuinely stumped as to why this may be happening. I’ll pass this information on to the team to see if we can recreate the issue. Though this may not be looked at for some time.

I’m unsure if this will help, but you could try a clean reinstallation of both Darktide and your iCUE software. I appreciate that it’s quite a length to go to though without any guarantee of it resolving the issue though:

Hi @JFlav,

Sorry to hear this.

Error code 2014 is a complicated error and our developers are working to resolve this as soon as possible.

We’re currently trying to identify reliable troubleshooting steps which can help to resolve this for PC, and for Xbox this is limited even further sadly.

It’s possible that the error could be due to an ISP-related problem, and your ISP may be able to identify any fault in the connection if you were to contact them.

I apologise that I don’t have an immediate solution to this for you

Hi @M3dr3sh,

Sorry to hear this.

Can you please try the following -

Flush Your DNS
Flushing your DNS will clear your PC’s DNS cache, and can resolve a variety of connectivity-related issues.

1. Run the Command Prompt as an administrator
2. Enter the command:
   ipconfig /flushdns
3. Restart your PC

Change Your DNS to 8.8.8.8 (Google)
When clearing the PC’s DNS cache has been unsuccessful, we recommend changing the DNS. Instructions on how to switch to Google DNS can be seen here: ...

Hi @Aldebaransk,

Sorry to hear this.

This specific crash is on our radar and should be fixed in our next patch. As I understand it, the crash is occurring due to a specific sound device being set, then if the device is removed/disconnected after Darktide has been closed, upon relaunching it isn’t recognising the selected sound device and is crashing.

In the meantime, you should be able to resolve this by removing your Darktide Appdata directory (Please note, by doing so you will lose any custom settings/configurations e.g. keybindings)

To do so:

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
5. Restart...