(OLD) KNOWN ISSUE: Crashing at Random, Due to GPU-Related Errors

I thought I had fixed it with this… but can’t get past the opening combat segment without a crash.

can you post your logs and settings

I dont think the worker threads was the cause. DLSS off was enough for me

Just a note on my settings I’ve tried everything. Everything on min, everything on max. Fullscreen, borderless, windowed. DLSS and RTX have been off throughout.

Settings: (most recent)
user_settings.config (3.1 KB)

Logs: (from a series of recent crashes)

console-2022-11-18-03.31.30-013ca1d8-eafa-4afc-bc77-4fb945caac65.log (37.8 KB)
console-2022-11-18-03.28.59-6ae69d98-bccb-4fbe-a1ec-e9ec28b5869b.log (38.0 KB)
console-2022-11-18-03.27.01-f1326866-90cd-41a8-a2d9-ed4aad72b8a4.log (40.8 KB)
console-2022-11-18-03.24.51-87235d74-5cc4-463e-a24e-fc6176e632e2.log (37.6 KB)

Couldn’t finish a mission before now I’ve done two in a row, one with DLSS and one without.

Tried many fixes to no avail, but knocking worker threads down to 10 worked 100%.
Working fine now with DLSS quality, 1440p, 12700k, 3080, 64gb ddr4, 1tb 970 evo plus NVME ssd.

Sample crash from before -

GUID: d0e39b13-c375-4292-bd5a-c5d1b57d8c9e
Log File:
Info Type:


EDIT -
spoke too soon…

GUID: 316447d2-e89f-499c-a09c-4aa844c68206
Log File:
Info Type:


04:53:11.132 [AFTERMATH] Device status: GFSDK_Aftermath_Device_Status_PageFault
04:53:11.133 [AFTERMATH] Page fault information:
04:53:11.133 [AFTERMATH] Faulting GpuVA: 0x2e920000
04:53:11.133 [AFTERMATH] Resource desc:
size: 0
width: 0
height: 0
depth: 0
mip levels: 0
format: DXGI_FORMAT_UNKNOWN
Buffer Heap: false
Static Texture Heap: false
RtvDsv Texture Heap: false
Placed Resource: false
Was destroyed: false
04:53:11.512 <>HRESULT: 2289696773 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DEVICE_HUNG

At D:\a\d\rel_engine_darktide\release\rel_2022_11_15_week2and3_for_pob\runtime\d3d12_render_device\d3d12_debug.cpp:894 in function stingray::aftermath::d3d_assert
<>
<>
{00007ff6fb0f0000, 02424000, 637515ac, 09bd223f-91de-4c94-89aa-f805cd7a3f99, 00000001, D:\a\w\live_engine_darktide\release\rel_2022_11_15_week2and3_for_pob\engine\win64\release\Darktide.pdb}
{00007ff94f6f0000, 00214000, 8a328c67, 49f757e0-5c19-dd09-7957-40d5f2b050e7, 00000001, ntdll.pdb}
{00007ff94e390000, 000c2000, 2ee8abd0, cfdb74a3-8794-50d4-c3ab-dc9a45327d3f, 00000001, kernel32.pdb}

0x00007ff6fb0f0000:0x0000000000486d59 swprintf
0x00007ff6fb0f0000:0x000000000053ec5e sprintf_s
0x00007ff6fb0f0000:0x00000000005164d7 _vsnprintf
0x00007ff6fb0f0000:0x00000000000fe5de snprintf
0x00007ff6fb0f0000:0x00000000000ff148 snprintf
0x00007ff6fb0f0000:0x00000000004b684a swprintf
0x00007ff94e390000:0x000000000001244d BaseThreadInitThunk
0x00007ff94f6f0000:0x000000000005dfb8 RtlUserThreadStart
<>
<>1<</Crash version>>
<>gpu hang<</Crash type>>
<>renderer<</Thread name>>
<>win32<>
<>e4c61ff5b729f6cfb91a604e4ac57000a1aaaf0d<</Build identifier>>


EDIT 2 - A slightly different log after cranking worker threads down to 1
05:00:14.244 [Lua] INFO [PlayerUnitDataExtension] Panic started. Received state package from the future, this is likely because we haven’t run any fixed frames yet or had a major stall. Received frame (469), last frame (461).
05:00:14.271 [Lua] INFO [AdaptiveClockHandlerClient] Filtering out frame dt of 0.189500, more than 2.000000 times old max dt of 0.063865
05:00:14.279 [Lua] INFO [PlayerUnitDataExtension] Panic resolved, took 0.219 seconds.
05:00:21.790 [AFTERMATH] Device status: GFSDK_Aftermath_Device_Status_PageFault
05:00:21.791 [AFTERMATH] Page fault information:
05:00:21.791 [AFTERMATH] Faulting GpuVA: 0x3eb2b000
05:00:21.791 [AFTERMATH] Resource desc:
size: 0
width: 0
height: 0
depth: 0
mip levels: 0
format: DXGI_FORMAT_UNKNOWN
Buffer Heap: false
Static Texture Heap: false
RtvDsv Texture Heap: false
Placed Resource: false
Was destroyed: false
05:00:22.132 <>HRESULT: 2289696773 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DEVICE_HUNG

At D:\a\d\rel_engine_darktide\release\rel_2022_11_15_week2and3_for_pob\runtime\d3d12_render_device\d3d12_debug.cpp:894 in function stingray::aftermath::d3d_assert


EDIT 3
tiny bit of extra context - played a bunch of the closed beta with no issues

Intriguing! I’ll test 1 worker thread + DLSS on and see if that’s as stable as 1 worker w/no DLSS.

So far, so good: two games, no crashes, DLSS on, worker threads 1.

1 Like

Constant random crashes in-game.

GUID: 0a74d21f-1d51-41b8-a682-0dfb1f9b89a1
Log File:
Info Type:


I’m able to log in and start a cutscene or mission, but often crash out almost immediately. After troubleshooting, I believe it’s a Windows 11 issue, as all crash logs identify my OS as windows 10. As I understand, this is something it does if it runs into an incompatibility with the OS? Are there any planned fixes for Windows 11?

1 Like

this

1 Like

GUID: d5e4e33a-ffda-456f-8160-151145d31e65
Log File:
Info Type:


I’ve tried everything - Windowed, no DLSS, Threads at 1, FSR 2, no upscaling tech at all. Reinstalled the drivers aswell. NOTHING WORKED. I still keep crashing like hell, 4 missions completed after roughly 8 hours of frustration.

1 Like

Hello game started 3-5 crash = 1 game
console-2022-11-18-08.57.06-07147cc8-fb57-4c2f-8274-5df3073556d1.log (102.8 KB)

I also had these crashes during closed beta btw.
Dont know if thats the case for anyone else?

First the game crashed on the first launch, black screen and loading icons, then as soon as it launched the game crashes in the prologue after jumping down to the landing pad, probably because of the cutscene, then I downloaded the update windows and the game went a little further, you could have fought the final fight, but she stopped right after.
I will add that drivers, ram, integrity of game and windows files, everything that was given in the suggested help options, I checked and it was ok, I even turned off DLSS, but the problem remained. In addition, I recently played Vermintide 2 and with dx12 options the game also crashes only on dx 11 it works quite normally but sometimes there are screen freezes and then crashes after closing the process from the manager shows on steam that the game is still working, stops the steam button, like it is closing but steam is not responding, closing it from task manager does nothing and the steam icon disappears from the bar but the processes are still running, disabling all steam processes does nothing and when you want to restart from the icon does nothing, and after a while the manager and windows stop responding and only a hard reset helps. Both games have the same problem and the same set of shutdown consequences, as if something invasively affects the game and the system at the same time.

Mission Name: Prologue
Platform:
[Steam]
Reproduction Rate:
Constant (100%)

Unfortunately, I can’t add everything due to limiting the number of links

Supporting Evidence:
console-2022-11-17-19.35.54-0ca5ef02-3e4c-4b9e-9496-664a233e0567.log (19.3 KB)
console-2022-11-17-19.38.35-265e540b-017e-4876-a053-c8209705f892.log (14.4 KB)
console-2022-11-17-19.43.00-7dc65649-a07e-41f2-87ec-588a74278099.log (17.0 KB)

crash_dump-2022-11-17-19.35.54-0ca5ef02-3e4c-4b9e-9496-664a233e0567.dmp (624.6 KB)
crash_dump-2022-11-17-19.38.35-265e540b-017e-4876-a053-c8209705f892.dmp (615.0 KB)
crash_dump-2022-11-17-19.43.00-7dc65649-a07e-41f2-87ec-588a74278099.dmp (639.7 KB)

user_settings.config (3.0 KB)
DxDiag.txt (116.2 KB)

console-2022-11-17-19.56.25-b5be1b1d-4ccf-4590-ac0b-3fdb99dd7529.log (66.2 KB)
console-2022-11-17-20.38.33-631e0d67-c75d-4b17-9c65-270a7b973ad7.log (47.7 KB)
console-2022-11-17-21.31.05-12bc78b1-7ff2-43ef-8899-0ac901d659d4.log (54.7 KB)

EDIT: Finally, I was able to pass the prologue and probably prevent it from crashing. The funniest thing is that I am not able to verify which application was causing it, but I turned off all of them, even those from the mouse and keyboard. So if you have any applications like Dragon center, Logitech gaming software or any applications for sound cards or graphics cards then you have to close them and the game should work normally although I hope it will be fixed because I can’t imagine that my graphics card or mouse and keyboard could not have enabled dedicated applications that manage their parameters

Disabling DLSS works for me too.

console-2022-11-18-08.57.06-07147cc8-fb57-4c2f-8274-5df3073556d1.log (102.8 KB)
console-2022-11-18-10.02.36-aa1df3cf-4a83-4ff6-ba15-87061b2ab724.log (102.3 KB)
console-2022-11-18-10.12.26-2242bc53-c99b-4af5-95e2-957c1389c223.log (70.9 KB)
console-2022-11-18-10.29.42-f6f8ca20-bc06-4d36-9b7c-6eb2766bfacd.log (57.2 KB)
console-2022-11-18-10.34.48-1d5fb44e-b8d3-4d95-aee7-a897ca87b2ff.log (32.4 KB)

console-2022-11-18-11.25.07-aa587620-3d1b-47b5-bac3-6ffe0c23f5b6.log (54.6 KB)
console-2022-11-18-11.31.48-3b874063-9ea4-4acf-8d35-d2117502188c.log (89.8 KB)
console-2022-11-18-11.36.15-9cb2b033-cdfc-4add-bcfb-f13308cce1ba.log (182.9 KB)
console-2022-11-18-11.49.14-f9da00d4-fcef-4c9d-92b1-65cb30797b76.log (62.3 KB)
console-2022-11-18-11.52.01-88661bd6-43fb-4992-ba40-7fa6610079d8.log (55.8 KB)

Issue Description:
Game crashes entering the cutscene after the first training mission.

Crash Report (If Applicable):
GUID: 8e509025-da77-42ed-88d6-09e1fe72dbe0
Log File:
Info Type:


Steps to Reproduce:

  1. Enter cutscene after training mission
  2. Game crashes after a few seconds

Platform:
Steam

Player ID:
Erika Furudo

Approx. Time of Issue & Timezone:
11/17/2022 ~7:25 [Eastern Standard Time]

Reproduction Rate:
Constant (100%)

Upload Supporting Evidence:

Upload Console Log:
console-2022-11-18-00.20.51-a721e45b-2b73-43dd-b811-90705ad9cea5.log (50.8 KB)
console-2022-11-18-00.18.00-01015e82-5ef1-451f-b99c-7e85fc78d421.log (49.6 KB)
console-2022-11-18-00.29.40-8e509025-da77-42ed-88d6-09e1fe72dbe0.log (55.1 KB)

Upload user_settings.config:
user_settings.config (3.1 KB)