Jump to content

2.5.5 CTD ntdll.dll, no log from Mission Editor


robgraham

Recommended Posts

had mission editor open had to go away from the actual gaming PC came back DCS had just closed itself.

 

Checked for a crash log nothing generated.

Check in Event viewer and I've a NTDLL.dll crash error.

 

Faulting application name: DCS.exe, version: 2.5.5.31917, time stamp: 0x5cf7db02

Faulting module name: ntdll.dll, version: 10.0.17763.475, time stamp: 0x3230aa04

Exception code: 0xc0000374

Fault offset: 0x00000000000fb049

Faulting process ID: 0x71fc

Faulting application start time: 0x01d51f203467948a

Faulting application path: J:\Eagle Dynamics\DCS World\bin\DCS.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report ID: 108487b4-8c37-416a-a533-7d5c719aee54

Faulting package full name:

Faulting package-relative application ID:

 

 

Again before I get from Nineline give us the logs, no Crash logs were generated, eg DCS didn't catch that it had an exception it just closed to desktop and the only thing in the log file was the standard items about ED CORE: having recently updated the map size when i last zoomed.

 

Stable is fine just the Open Beta doing it.

i7 13700k, 64gb DDR5, Warthog HOTAS, HP Reverb G2 VR, win 11, RTX 3070

TGW Dedicated Server Admin, Australian PVE/PVP gameplay. (taskgroupwarrior.info/2020)

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...