F18 Operation Cerberus North Campaign Mission 2 and 4 Crash

[Jonnylap1]

Hi, I experienced a crash while playing mission 2 and 4 of this campaign.

Can you please tell me if I have done something wrong?

I don't have any mods running.

Thanks so much for your help.

 

Jonathan

 

 

dcs.log dcs.log.old debrief.log

Edited August 25, 2023 by Jonnylap1
incorrect title

[Flappie]

I don't see any crash in your logs. Please attach the latest zip file from the Logs folder.

[Jonnylap1]

I just realized I made a mistake with the Campaign title.  I was actually playing Operation Cerberus North.

As for the zip file, I'm not seeing any in my logs folder for some reason.

I'll also attach the crash and dmp if that helps.

dcs.20230220-223000.crash dcs.20230220-223000.dmp dcs.log dcs.log.old debrief.log

[Flappie]

Then you should edit your first post title to show the proper campaign name.

I don't know what I see in your .crash file, and none of your log files contain the bigger picture (they are not from the same game session).

Here's the content of the .crash file:

# -------------- 20230220-223000 --------------
DCS/2.8.2.35759 (x86_64; Windows NT 10.0.19045)
D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\GraphicsVista.dll
# C0000005 ACCESS_VIOLATION at 00007FFFB9052E45 00:00000000
SymInit: Symbol-SearchPath: '.;D:\Program Files\Eagle Dynamics\DCS World OpenBeta;D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 532, UserName: 'jonla'
OS-Version: 10.0.19045 () 0x300-0x1
0x0000000000002E45 (GraphicsVista): Graphics::DXProjLight::GetLoadStep + 0x17D5
0x000000000000268E (GraphicsVista): Graphics::DXProjLight::GetLoadStep + 0x101E
0x000000000001E936 (GraphicsVista): dbg_obj::~dbg_obj + 0x76
0x0000000000177042 (Visualizer): TransformComponent::validatePositionsTree + 0x6D592
0x0000000000186162 (Visualizer): TransformComponent::validatePositionsTree + 0x7C6B2
0x00000000000142D6 (ucrtbase): _execute_onexit_table + 0x156
0x00000000000141FB (ucrtbase): _execute_onexit_table + 0x7B
0x00000000000141B4 (ucrtbase): _execute_onexit_table + 0x34
0x0000000000177E2D (Visualizer): TransformComponent::validatePositionsTree + 0x6E37D
0x0000000000177F52 (Visualizer): TransformComponent::validatePositionsTree + 0x6E4A2
0x0000000000019A1D (ntdll): RtlActivateActivationContextUnsafeFast + 0x11D
0x000000000005DCEC (ntdll): LdrShutdownProcess + 0x24C
0x000000000005DA7D (ntdll): RtlExitUserProcess + 0xAD
0x000000000001E86B (KERNEL32): FatalExit + 0xB
0x00000000000205BC (ucrtbase): exit + 0x1DC
0x000000000002045F (ucrtbase): exit + 0x7F
0x0000000000C14FD4 (DCS): SW + 0x7A9464
0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
0x00000000000526A1 (ntdll): RtlUserThreadStart + 0x21

 

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

[Jonnylap1]

Thanks mate, will do.

 

Edited August 25, 2023 by Jonnylap1

[Brettinator]

Hi Jonny. For what it's worth. I was having a very similar issue. Computer was working fine with DCS, then after the latest update and adding Inherent Resolve I began random rebooting at various times after the campaign loaded. I spent about a 1/2 day on this Sunday and seemed to get the issue corrected, at least so far it seems good. It wasn't DCS. I wasn't getting a crash file in my logs, the system would just reboot at random times after loading, sometimes after the engine start, sometimes right away. I suspect there's a bit of processor work required when you first load the campaign. Anyways, I began looking at my system diagnostics and ran a few programs to cleanup my system. I used Fortect and still got the reboot. It wasn't until I ran the scannow cmd program that it found some file errors. After letting scannow fix those files, it did a reboot once more upon loading dcs and the campaign and somehow after that it was gone. No more reboot. No idea if that will help you. I do appreciate how frustrating this is, caused me to nearly give up entirely but got a wild hair to focus on this on Sunday and found myself flying again by Sunday night, even with my VR headset so all good. Maybe that will help you. By the way, I was about to put in my ticket to DCS and noticed there wasn't a crash log so that was what gave me the idea to dig a little deeper into my machine. Apparently a lot of things can cause this. What let me to scannow was running the event viewer and reviewing the event IDs on google. I found several events and just kept working through them until one led me to the scannow recommendation and that seemed to do the trick. I'm not super technical but thought maybe my experience would help. 

Edited September 5, 2023 by Brettinator