Game Crash Occurring a few Seconds Before GBU-12 Impacts a Target

[Invisibull]

Aircraft used here is an F-16 in MP. Please find relevant logs attached. Thx.

null

dcs.log-20230606-193242.zip

[Flappie]

I tried the DCS track from your zip, but could not reproduce the crash.

I'm not 100% sure this is hardware related, but you should check our RAM using MemTest86 anwyay.

You're having scripts  issues:

2023-06-06 19:28:57.106 ERROR   Lua::Config (Main): Call error LuaExportAfterNextFrame:[string "D:\Desktop\Saved Games\DCS.openbeta\Scripts/TheWay.lua"]:126: attempt to index a nil value
stack traceback:
	[C]: ?
	[string "D:\Desktop\Saved Games\DCS.openbeta\Scripts/TheWay.lua"]:126: in function 'PrevLuaExportAfterNextFrame'
	[string "D:\Desktop\Saved Games\DCS.openbeta\Scripts/TacviewGameExport.lua"]:65: in function <[string "D:\Desktop\Saved Games\DCS.openbeta\Scripts/TacviewGameExport.lua"]:58>.
2023-06-06 19:28:57.125 WARNING LOG (19328): 1 duplicate message(s) skipped.

If you know how to fix these issues, give it a go. Otherwise, rename your "Saved Games/DCS.../Scripts" folder to "Scripts.bak" and see if it prevents the crashes from occuring.

Edited June 6, 2023 by Flappie

[Invisibull]

Thx for your reply. I've come to discover that the crash doesn't happen when I'm not using the MT exe. Further, even while using the MT exe it only seems to happen in that particular mission so far.  Incidentally, those script errors have been coming up for years in some cases and have never manifested in any noticeable way in the game environment; I don't think they are involved at all. 

Thx again.

[Invisibull]

I'm still getting this crash, but never when using the non-MT .exe.  I have reinstalled DCS from scratch am using no scripts or mods, and I have done tests on my memory and it is fine.  Could someone please help?

I've attached the latest DCS.log and here is the Windows Crash Report from the Event viewer:

Faulting application name: DCS.exe, version: 2.8.8.43704, time stamp: 0x64e3b9dd
Faulting module name: VCRUNTIME140.dll, version: 14.34.31938.0, time stamp: 0x023b235f
Exception code: 0xc0000005
Fault offset: 0x000000000000165e
Faulting process id: 0x4e38
Faulting application start time: 0x01d9d62a3dcb6612
Faulting application path: D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: d8dd710f-9880-4cdb-a0d4-5a185a6ec61c

 

Thx

 

dcs.log-20230824-013901.zip

[Flappie]

It seems your crash is always the same. It looks like this:

2023-08-24 01:36:38.907 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2023-08-24 01:39:00.816 INFO    EDCORE (Main): try to write dump information
2023-08-24 01:39:00.818 INFO    EDCORE (Main): # -------------- 20230824-013901 --------------
2023-08-24 01:39:00.818 INFO    EDCORE (Main): DCS/2.8.8.43704 (x86_64; MT; Windows NT 10.0.19045)
2023-08-24 01:39:00.819 INFO    EDCORE (Main): C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
2023-08-24 01:39:00.819 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffd1109165e 00:00000000
2023-08-24 01:39:00.820 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: 'D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'invis'
2023-08-24 01:39:00.821 INFO    EDCORE (Main): OS-Version: 10.0.19045 () 0x100-0x1
2023-08-24 01:39:00.821 INFO    EDCORE (Main): 0x000000000000165e (VCRUNTIME140): memcpy + 0x34E
2023-08-24 01:39:00.822 INFO    EDCORE (Main): 0x0000000000343763 (CockpitBase): cockpit::ceTMultiLine::class_name + 0x11F3
2023-08-24 01:39:00.823 INFO    EDCORE (Main): 0x00000000003450c7 (CockpitBase): cockpit::MultiThreading::annotate_viewport + 0x3D7
2023-08-24 01:39:00.824 INFO    EDCORE (Main): 0x00000000003463c9 (CockpitBase): cockpit::get_active_viewport_index + 0xE09
2023-08-24 01:39:00.824 INFO    EDCORE (Main): 0x0000000000115875 (Visualizer): smSceneManager::DestroySceneManager + 0xE6D5
2023-08-24 01:39:00.824 INFO    EDCORE (Main): 0x000000000011a9cc (Visualizer): smSceneManager::regLua + 0x2CEC
2023-08-24 01:39:00.825 INFO    EDCORE (Main): 0x0000000000877af6 (DCS): SW + 0x3E1746
2023-08-24 01:39:00.825 INFO    EDCORE (Main): 0x000000000089946a (DCS): SW + 0x4030BA
2023-08-24 01:39:00.825 INFO    EDCORE (Main): 0x0000000000857f24 (DCS): SW + 0x3C1B74
2023-08-24 01:39:00.825 INFO    EDCORE (Main): 0x0000000000858e02 (DCS): SW + 0x3C2A52
2023-08-24 01:39:00.826 INFO    EDCORE (Main): 0x000000000270adb0 (DCS): AmdPowerXpressRequestHighPerformance + 0x135CDAC
2023-08-24 01:39:00.826 INFO    EDCORE (Main): 0x0000000000c5a782 (DCS): SW + 0x7C43D2
2023-08-24 01:39:00.826 INFO    EDCORE (Main): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
2023-08-24 01:39:01.009 INFO    EDCORE (Main): Minidump created.

 

 

I'm not sure what happens. It looks like a system issue (VCRUNTIME140.dll is a Windows system library).

Please open a support ticket: log into DCS website, click "Support", then click "Create a new ticket".

[Invisibull]

Support Ticket #143755 was put in on 8/27 and so far I've been asked to check a bios setting to see if my RAM was being overclocked (it wasn't). Very disappointing to be completely ghosted by ED on this issue.

[Flappie]

Is your issue reproducible?

If it is, please attach a short DCS track with you launching two GBUs in the mission you told us about. Exit the mission when the second GBU starts falling, click "Save Track", then attach the track here. I'll see if I can reproduce the crash.

[maximov]

I am confused by this line:
2023-08-24 01:39:00.821 INFO    EDCORE (Main): 0x000000000000165e (VCRUNTIME140): memcpy + 0x34E
And we could not repeat the failure when dropping ammunition.
So far we have only a single log. Perhaps we will have more data if you will to use automatic sending of crash reports to our server:

https://www.digitalcombatsimulator.com/en/support/faq/logs/