I’ve shared this with development. Thank you for your report.

I put the request in to Easy Anti-Cheat to approve this DLL and they actioned it. If it doesn’t work after a second launch as mentioned by @PocketSand , let me know.

I’m not sure what’s happening here admittedly, the logs are truncated. Please see: https://support.fatshark.se/hc/en-us/articles/7709661288733--PC-How-to-Resolve-Crashes-in-Darktide

Sorry to hear that. I’ve pinged this over to development.

We are working on an issue where the ‘Worker Thread’ count defaults to a value that may be too high for some PCs, which consequently has a negative impact on your performance.

In the mean time, we recommend lowering your ‘Worker Thread’ count - this value may vary depending on your unique set-up, so we recommend to experiment with what works for you.

For example: on a Threadripper CPU, it will default to a whooping 61 Worker Threads. In this example, you may wish to lower it to 16.

I would say hold on until the release patch, but the error below indicates more of a localised GPU issue, as opposed to the errors that we would traditionally see when we’ve messed something up on our end:

DXGI_ERROR_DRIVER_INTERNAL_ERROR

I recommend reaching out to NVIDIA and seeing if they can assist with this.

In the event that you are unable to launch Darktide from Steam or the Microsoft Store, please see if any of the links below can be of help:

[PC] Stuck on ‘Preparing to Launch’?

[PC] How to Resolve Darktide Launcher Issues

[PC] “Missing Downloaded Files” Referencing CrashifyUploader.exe

[PC] Microsoft Store Error Guide

[PC] Darktide.exe - Application Error (0xc0000005)

We are aware that a small number of players encountered issues attempting to launch on Windows 11, and it was noted that having an older version of the Epic Games client running on your PC resulted in some odd interaction with the Darktide launcher that should now be resolved.

In the event that you are still unable to launch Darktide, please help us investigate 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]

Platform:
[Steam/Microsoft Store]

Player ID:
[Steam ID/Steam Profile URL/Game...

We are continuing to investigate an issue that was reported during the Pre-Order Beta concerning some players observing an ‘Out of Memory’ error.

Firstly, please ensure your 'Virtual Memory’ in Windows is set to ‘Automatically Manage Paging File Size for All Drives’ by:

1. Navigate to Control Panel > System and Security
2. Select ‘System’
3. Select ‘Advanced system settings’
4. Under the ‘Advanced’ tab, select the ‘Settings’ button underneath ‘Performance’
5. Select the ‘Advanced’ tab
6. Select the ‘Change’ button underneath ‘Virtual memory’
7. Ensure the ‘Automatically Manage Paging File Size for All Drives’ checkbox is marked
8. Restart your PC

In the event that you are still encountering this error, please help us investigate 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]

Platform:
[Steam/Microsoft Store]

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

Upload Consol...

Ray Tracing is currently unavailable for AMD and Intel GPUs due to issues with this implementation that we are currently addressing.

We are working to resolve this issue as soon as possible.

The rollout of new servers with launch should continue to mitigate the issue. Keep us posted.

The experimental branch will mirror the release branch, and the release branch will contain everything experimental once had (minus the crashing, we hope…).

So you should be able to play as normal on either branch.

Thank you!

FOLLOW-UP FROM:

Promising improvements have been made in this area but we understand some issues may remain.

We will be monitoring our crash data closely and looking at where else we need to address.

However, it’s worth keeping in mind some of these crashes may be the result of localised driver-related issues and the like.

More information in the articles linked below. Please...

Really promising improvements have been made in this area. We’re quite confident you will have a much better experience with our upcoming release patch.

I’m closing this and creating a new Topic for release which can be seen here:

FOLLOW-UP FROM:

We are aware of and looking in to the internal_error and Error Code: 2007 (same error) being reported.

It should be noted that we do not support IPv6-only networks at this time.

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. N...

I’m chasing for updates on this. In the mean time, I’ve created a new Topic for this particular error for release, which can be seen below:

I’ll be closing this and posting anything new to .

Are you using a Bluetooth-connected headset?

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

We are aware of and looking in to an issue where Darktide does not always detect or utilise the GPU correctly.

In the case that Darktide is not detecting your dedicated GPU correctly, please see:

[PC] How to Resolve Darktide Using the Incorrect GPU

If you have run through the solutions linked above, or if your GPU is not being utilised correctly despite being detected, please share your experience in the Performance Feedback category.

We kindly ask that you complete the questions that appear automatically upon creating a new Topic. With this information, we can investigate your issue properly.

Please be aware that whilst we will be monitoring all reports in Performance Feedback, we will not respond unless we require more information.

We are aware of and looking in to the failed_joining_lobby and Error Code: 3001 (same error) being reported.

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

We are aware of and looking in to the lost_connection and Error Code: 2003 (same error) being reported.

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

Exist...