I know it is a long shot even if we have similar hardware but check out my post here that helped me go from constantly crashing multiple times per match to crashing every 5 matches or so.
I manually capped the framerate in the Nvidia control panel rather than letting the game do it (which worked fine but then would uncap itself without changing the settings)
Checked āLowering Threadsā and āDisabling DLSSā but after reading some comments here, experimented a bit: Capped FPS to 60, switched to borderless window and crashes almost gone (1 crash in 3 missions).
Set thread count back to default - looks like it does not have any effect.
My suggestion (in my case ) is that the more FPS you have - the more chances of crash. As setting worker threads to 1 āhelpedā by lowering FSP to ~40. And turning DLSS on giving me more FPS.
update to my update, game back to crashing again all the time after the last patch. Donāt know why! Have retried everything again. At least itās not nearly as often as before, just once every game or two.
Update: Finally playing. Donāt know how. But 30fps cap and Workers at 1 with all extra DLSS-related stuff off seems to be working alright for me. Can get about two or three levels in without crashing.
We kindly ask that you complete the questions below. With this information, we can investigate your issue properly.
Issue Description:
Among other crash encounters, Today 11/23/2022 I have been black screen crashing after loading into a game. No error message, my PC hangs and crashes. In one occurence it made my Audio Driver hang too and disconnect my headphones and I had to reassign my audio in my PC settings. Crash Report (If Applicable):
GUID: 99b2a32b-ef51-493f-89f3-3b059a833945
Log File:
Info Type:
Error Displayed (If Applicable):
N/A Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]
1.Launch Game
2.Go to Mourning Star
3.Queue for Quickplay Hazard Level 2
4. Load Map
5. Spawn in mission in progress with horde on screen
6. Start swinging and killing mobs
7. PC Hangs
8. Black Screen Crash
Mission Name (If Applicable):
Ammunition resupply mission for this one. It happens on all missions.
Platform:
[Steam/Microsoft Store]
Steam Player ID:
[Steam ID/Steam Profile URL/GamerTag]
Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]
11/23/2022 3:00PM [PST] Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)
Often to Constant Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Its a crash, no screenshot available. Logs.zip (57.2 KB)
Upload Console Log:
Press the Windows key + R
Enter %appdata% within the search input and select āOKā
Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
Upload here
Upload darktide_launcher.log:
Press the Windows key + R
Enter %appdata% within the search input and select āOKā
Navigate to AppData\Roaming\Fatshark\Darktide
Locate the darktide_launcher.log in this directory
Can you enable āGPU Schedulingā. I think this requires a computer reboot after you enable it.
We are adding UI to the Advanced Graphics Settings page to control enabling the new GPU scheduler. The settings page can be reached through Settings ā System ā Display ā Graphics Settings . If both your GPU and driver support the new GPU scheduler, the UI below will appear.
Issue Description:
Upon browsing the Penance menu, as you move tabs and open preview of equipment performance starts to go down hard, if you leave the menu open my computer crashes as my GPU (specifically) cannot handle it.
Steps to Reproduce:
Open Penance menu;
Start browsing previewing equipment;
Change class tabs (or donāt), and after opening tons of tabs just leave it be, you will it take more resources with time
Computer crashes
Mission Name (If Applicable):
Platform:
Steam
Player ID:
[Steam ID/Steam Profile URL/GamerTag]
Approx. Time of Issue & Timezone:
11/21/2022, 12:55:00PM GMT-3 (but tons of crashes like this in the weekend)
We kindly ask that you complete the questions below. With this information, we can add it to our database for investigation.
Almost any game, map, charactor
When you get the āWhooshā sound when you are about to be melee hit, and you dodge, my game crashes. It happens so frequently in this new update it is almost unplayable.
Mission Name (If Applicable):
Platform:
[Steam]
Player ID:
[Steam ID/Steam Profile URL/GamerTag]
Approx. Time of Issue & Timezone:
after new update 1.07 I think? It is a constant issue
Reproduction Rate:
Every 2/3 games or so.
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Upload Console Log:
Press the Windows key + R
Enter %appdata% within the search input and select āOKā
Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
Upload here
Upload darktide_launcher.log:
Press the Windows key + R
Enter %appdata% within the search input and select āOKā
I said it before here, but almost none of the comments here mentions it:
I had many, many chrashes, but for me the trick was going into FULLSCREEN BORDERLESS and updating my CHIPSET DRIVERS. (Link for AMD ChipsetDownload Auto Detect)
Now I can go with DLSS, RTX, Max Worker Threads, it doesnt matter. Since then I got random crashes roughly 1 in 6 hours.
Iāll load in to a mission but usually before I am able to move, I hear a brief buzzing sound like part of the audio is glitching, everything will freeze (if it wasnāt still frozen) and Iāll crash to desktop. Once I was able to take a couple of steps before the buzz & crash.
Steps to Reproduce:
It seems to happen regardless of which class or mission I play. Use Quickplay to join a mission, sit through the loading screen, and the issue happens the moment you exit the loading screen and first see the level.
Platform:
Steam
Player ID:
76561197972431515
Approx. Time of Issue & Timezone:
Night of 11/21, Afternoon of 11/22 [EST]