Crashing every 1-2 missions with various Engine Errors

Issue Type (Required):

Crash - During Play

Issue Description (Required):

I’ve done everything I’ve found to troubleshoot this, including: updating drivers, rolling back drivers, uninstalling drivers with DDU then reinstalling the latest drivers, updating BIOS firmware, disabling Steam overlay, setting worker threads to 1, capping framerate, disabling DLSS, running multiple passes of Memtest86 with no errors, disabling mods, etc. At this point I don’t know what else to do but post here. Either I get an access violation error or some sort of index error.

[PC] Do You Use Mods? (Optional):

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Often (<75%)

Platform (Required):

Steam (PC)

[PC] Crash Report (Optional):

GUID: 0b9fab52-efb8-44c7-bc25-6bf8f0699162
Log File:
Info Type:

[Engine Error]: Access violation (0xc0000005) in build 8460a65096d130f831350b3f7b2a7a08e16c62dc
accessing address FFFFFFFE00000004 from 00007FF6392FE81A

[PC] Upload Console Log & darktide_launcher.log (Optional):

console-2024-10-26-19.22.01-0b9fab52-efb8-44c7-bc25-6bf8f0699162.log (685 KB)

I don’t know if this is helpful at all but here’s the latest crash

GUID: 193ad8f0-26cb-42b8-9fc8-cad03e83d471
Log File:
Info Type:

[Engine Error]: invalid handle

Assertion failed render_resource::extract_type(handle) != 0 at D:\a\d\rel_engine_darktide\release\rel_2024_08_20_Patch1.5.0x\runtime\d3d12_render_device\d3d12_resource_manager.h:116 in function stingray::D3D12ResourceContext::ObjectLUT::operator []


console-2024-10-27-14.12.24-193ad8f0-26cb-42b8-9fc8-cad03e83d471.log (505.6 KB)

Sorry to hear this @glorygirl

I’ve queried these crashes with our engine developers and they informed me of the following -

  • You are crashing in raytracing code, but the reason is unclear. Disabling this may help
  • There appears to be some ambiguous memory-related issue. They recommend running a diagnostic/RAM checker as your RAM may have a fault:
  1. Press the Windows key + R
  2. Enter mdsched.exe and select ‘OK’
  3. When ready, select the ‘Restart now and check for problems’ option
  4. Allow the scan to complete

Thank you for the response. I disabled raytracing and it definitely seems to be more stable. I did run two passes through Memtest and got 0 errors last time so I’ll try running it again overnight to see if it finds anything.

1 Like

Windows Memory Diagnostic reported no errors, at least.

1 Like

Glad to hear that stability is better with raytracing off, and that’s good to hear that no memory errors flagged up :slight_smile: