FatsharkLev

FatsharkLev



18 Nov

Comment

We’ll investigate - thank you for the report!

Comment

Hi @EdwardTeaington,

Your logs show that you’re running into a Deadlock type crash, which are quite notorious.

I’ve raised this crash internally for investigation. However, for now, I can recommend running through our crash solutions here:

Read more
Comment

Hi @CR0W2K,

Based on the information within your logs, it appears that you are encountering a GPU-related crash.

We’re working with our hardware partners to identify and solve underlying issues. However, it’s possible that these crashes may be the result of a localised driver-related issue and the like.

You can find information on how to solve localised GPU crashes here:

Read more
Comment

Hi @Dr.pop25,

We’ll need a crash report or console log to take a look at this please!

Read more
Comment

Hi @Lux,

Can you please check your system date/time? Please ensure that set time automatically is enabled.

Does the issue resolve after this?

Comment

Hi @PumpkinAnoa,

We’ll need a crash report or console log to take a look please!

Read more
Comment

Thank you for the report @Marbon - we’re on it!

Comment

Thanks for the report @MightyAxeMan - this crash is under investigation.

Comment

Hi @Woolstone,

The logs show you ran into a GPU crash.

If these persist, please try solutions here:

Read more
Comment

Unfortunately not, Darktide has a DX 12 requirement.

Comment

Hi @Apofis,

Based on the information within your logs, it appears that you are encountering GPU-related crashes.

We’re working with our hardware partners to identify and solve underlying issues. However, it’s possible that these crashes may be the result of a localised driver-related issue and the like.

You can find information on how to solve localised GPU crashes here:

Read more
Comment

I’ve added this crash to our database for investigation - thank you for the report!

Comment

The crash data shows a GPU-related memory issue.

I recommend trying our GPU crash solutions here:

Read more
Comment

This isn’t implemented just yet.

Comment

@destroyitwithflames, you’re running into a consistent Deadlock crash. Unfortunately, we cannot determine the cause from the data in the logs alone.

Finding a solution may require some trial and error - I recommend running through our crash solutions here:

Read more
Comment

Hi @carloseli0280, can you please provide me with your Steam profile URL and I’ll sort this for you :slight_smile: thanks!


17 Nov

Comment

This specific crash is on our radar - we’re on it!

Thank you for the report.

Post

We are aware of and looking in to the failed_handshake_timeout errors 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. En...
Read more
Comment

We’re looking into this crash - thank you for the report!