Driver crash after closing the Darktide

Warhammer 40,000: Darktide Technical Support
1

I have been having an issue after updating my driver to AMD 22.11.1 from 22.10.1. I am only able to roll back to 22.5.1, but come across the same issue now with that driver as well.

If I close Darktide by using the menu to quit, if it crashes to desktop, or if I alt-F4, or end task from the control panel. I will have anywhere from 10 seconds to a minute before my screens freeze and become unresponsive. Windows is still running fine in the background as I can play sounds or Win-X, U, R to restart my computer. Once my computer restarts, windows has overwritten my driver and I have to reinstall the AMD driver. I have tried to replicate this with several other games that I own but I am not able to.

I have cleaned out the drivers in safe mode and done a clean install to no avail.
I have blocked windows update from being able overwrite the driver. (doesn’t work)
I have cleared out the driver cache.
I have clean installed Darktide.
After exiting Darktide I have even rush restarted my PC. It restarts fine, but then after 10 seconds to a minute in windows it will do the driver crash again.

I was hoping that the latest patch would help, but it has not. Any ideas or help would be greatly appreciated.

Platform:
Steam

Player ID:

Approx. Time of Issue & Timezone:
Started Saturday November 19th after update of driver. Did not have an issue playing on the 17th or 18th.

Reproduction Rate:
100%

2

Can you also upload any console log files from when you force exit the game

https://forums.fatsharkgames.com/t/how-to-provide-a-crash-report-console-log-or-darktide-launcher-log/55163/3

3

console-2022-11-22-22.07.28-73106110-099f-43e1-ac09-af2b5a2d5272.log (143.3 KB)

This is from control panel end task.

4

This is a localised issue and I’d rather be honest in that we may not be able to help with this, but I’ve raised it with our developers nonetheless.

5

It appears that this has resolved itself after the full release patch. Unfortunately I was unable to find out on my end what was the cause. There definitely was something within the beta client that was causing this though.