Crashes consistently on mission 2 at end of mission

[ghighcove]

So I keep having it consistently crash to desktop at the end of the second mission, right as the ILS endpoint comes up. Happened twice. Can't continue as is. What files would help? I saved the log file and also the log zip, it references this error in the crash log:

# C0000005 ACCESS_VIOLATION at 2E6DD867 00:00000000

Edited April 15, 2020 by ghighcove

[Hammer1-1]

Post a track file and your DCS log/crash log or whatever it generated. I just finished this campaign last week and had no issues with it whatsoever.

[ghighcove]

I don't have the track file, I do have this crash log and the dcs.log file. If there is a track file saved, I can provide that, but otherwise, it's gone. I do have the TacView, also attached here.

 

I'm reluctant to re-fly the mission a third time and waste another 20 minutes of my life to get a track, but will do if it's absolutely necessary. I'm hoping what I provided here is enough. Note that in between plays, I turned down all the graphics due to the excessive frame drops with the latest DCS version release, the same issues everyone else is having. The game is smoother, but this mission still broke in the same exact place.

dcs.log-20200415-013234 - Copy crash after f-15 aggressors m2.zip

other files.zip

[Hammer1-1]

Theres an issue where the F-18 is trying to launch off of the Stennis...you're flying in Nevada, right? I dont recall hornets taking off from any carrier in Nevada, but thats possibly whats causing your crash. Also looks like an F-16 is having issues too. Do you have any mods installed by any chance?

[Sabre-TLA]

Thanks for helping Hammer1-1.

 

BIGNEWY has a forum post with some good tips to try if your game is crashing.

 

You can read it here.

[ghighcove]

Ok, good news and bad news.

 

Bad news first. It crashed again, in the exact same place as the other two times. So that was another 20 minutes of my day doing the same boring mission again, with no fix, and the exact same crash I had described. The file I sent earlier, was it any help at all? I kind of get the feeling no one looked at it.

 

The fix you sent -- much appreciated. It did seem to markedly improve my performance and probably was addressing an issue that was hurting other aspects of my DCS play, so that is good. But the campaign is still broken as-is for me. It breaks right when the final ILS waypoint flicks on, reliably. Nothing else I play on DCS, campaign, mission, etc., breaks like this. Something is wrong.

 

Here's the latest crash file, attached. Also Tac AI. I would appreciate someone looking at it, assuming it is worth your time to address so that I can get what I paid for, a working campaign. Until I can play past this mission, my negative review on Steam stands, the one where I say it doesn't work. Maybe a lot of those reviews don't hold a lot of weight because a lot of those people didn't own the DLC, but I own all of the relevant DLC and whole lot more. I buy DLC often, and most of the time it works. This isn't working. I would like this escalated to the next step, and that I not be asked to do another playthrough until someone has looked at the files I made an effort to attach here. Thank you.

 

@Hammer11 -- I appreciate your help, but you know I'm posting this in the F-15C Aggressors campaign, right? Not sure why you are mentioning an F-18, did I accidentally send a file from another mission? I did do a F-18 mission right after my crash (rather, tried it, Track IR was not working after that). I'm wondering now if you had recently completed the F-18 Aggressors or Red Flag campaign instead and thought I was posting about that. I'm posting specifically about Mission 2, F-15 Aggressors BFM campaign.

latest files.zip

[Sabre-TLA]

Yes we do look at the logs.

 

Did you do all the recommended actions listed in BIGNEWY's post? Sorry but it's not clear from your reply if you did the DCS Repair, updated video card drivers, renamed your DCS Saved Games folder, removed MODs, etc.

 

Also have you tried to uninstall and reinstall the campaign files?

 

If you try landing without using the ILS does it still crash?

 

Both logs look similar and here is the snippet before it crashes so it might have something to do with the metashaders:

2020-04-15 17:03:41.108 ERROR   EDTERRAINGRAPHICS41: metashaders/terrain/5.0/surface5.0.fx|metashaders/transformmodifiers/transform_simple.meta.hlsl|CLIPMAP_NORMAL_MAP=;CLIPMAP_SHADOW_MAP=;COLORCLIPMAP_ALPHA_IS_AO=;COLOR_CLIPMAP=;DIRECTX11=true;LAKE_COLORCLIPMAP=;NODEFINITIONS=;NOISE_OP=PhotoshopOverlay;PBR_TEXTURES=;SPLATMAP=;SURFACE5=;TAD_CLIPMAP=;USE_DCS_DEFERRED=1;USE_TERRAIN_PALETTE=|: no subgeometry current
2020-04-15 17:04:07.577 WARNING LOG: 100 duplicate message(s) skipped.
2020-04-15 17:04:07.577 INFO    EDTERRAINGRAPHICS41: forestDistanceFactor has been changed to 0.500000. Update lod buffers.
2020-04-15 17:04:07.577 INFO    EDTERRAINGRAPHICS41: InstanceManager2::updateObjectDeclBuffer()
2020-04-15 17:04:07.577 INFO    EDTERRAINGRAPHICS41: InstanceManager2::updateObjectLodDeclBuffer()
2020-04-15 17:04:12.355 INFO    EDCORE: try to write dump information
2020-04-15 17:04:12.356 INFO    EDCORE: # -------------- 20200415-170412 --------------
2020-04-15 17:04:12.357 INFO    EDCORE: DCS/2.5.6.45915 (x86_64; Windows NT 10.0.18362)
2020-04-15 17:04:12.359 INFO    EDCORE: E:\Games\steamapps\common\DCSWorld\bin\DCS.exe
2020-04-15 17:04:12.360 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 20A4D867 00:00000000
2020-04-15 17:04:12.365 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;E:\Games\steamapps\common\DCSWorld;E:\Games\steamapps\common\DCSWorld\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'ghigh'
2020-04-15 17:04:12.367 INFO    EDCORE: OS-Version: 10.0.18362 () 0x300-0x1
2020-04-15 17:04:13.856 INFO    EDCORE: 0x000000000067D867 (DCS): woLA::loadNewInputLayout + 0x2A5767
2020-04-15 17:04:13.856 INFO    EDCORE: 0x0000000000676398 (DCS): woLA::loadNewInputLayout + 0x29E298
2020-04-15 17:04:13.856 INFO    EDCORE: 0x0000000000674DBD (DCS): woLA::loadNewInputLayout + 0x29CCBD
2020-04-15 17:04:13.857 INFO    EDCORE: 0x00000000006734C8 (DCS): woLA::loadNewInputLayout + 0x29B3C8
2020-04-15 17:04:13.857 INFO    EDCORE: 0x0000000000466249 (DCS): woLA::loadNewInputLayout + 0x8E149
2020-04-15 17:04:13.857 INFO    EDCORE: 0x00000000004272F4 (DCS): woLA::loadNewInputLayout + 0x4F1F4
2020-04-15 17:04:13.857 INFO    EDCORE: 0x0000000000003A64 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x4C4
2020-04-15 17:04:13.857 INFO    EDCORE: 0x0000000000003EED (World): wSimCalendar::DoActionsUntil + 0x1FD
2020-04-15 17:04:13.858 INFO    EDCORE: 0x00000000006DBC3F (DCS): woLA::loadNewInputLayout + 0x303B3F
2020-04-15 17:04:13.858 INFO    EDCORE: 0x00000000006ECEC3 (DCS): dDispatcher::InitDatabase + 0xDFF3
2020-04-15 17:04:13.858 INFO    EDCORE: 0x00000000006C3364 (DCS): woLA::loadNewInputLayout + 0x2EB264
2020-04-15 17:04:13.858 INFO    EDCORE: 0x00000000006C3729 (DCS): woLA::loadNewInputLayout + 0x2EB629
2020-04-15 17:04:13.858 INFO    EDCORE: 0x0000000001696BD3 (DCS): AmdPowerXpressRequestHighPerformance + 0xB19BCF
2020-04-15 17:04:13.859 INFO    EDCORE: 0x00000000008A01FE (DCS): uiAsyncNet::onGameStop + 0x67CCE
2020-04-15 17:04:13.859 INFO    EDCORE: 0x0000000000017BD4 (KERNEL32): BaseThreadInitThunk + 0x14
2020-04-15 17:04:13.859 INFO    EDCORE: 0x000000000006CED1 (ntdll): RtlUserThreadStart + 0x21
2020-04-15 17:04:20.794 INFO    EDCORE: Minidump created.

 

How are the temps on your system? I've seen access violation crashes from overheated systems.

 

Sorry more questions than answers at this point. We will retest to see if we can reproduce it.

[Sabre-TLA]

Another thing we noticed in the dxdiag output:

 

RadeonSettings.exe - not sure why this is being reported as it appears you have an Intel system and GTX card. Did you have an AMD card installed at some point?

 

This is a software component of the Catalyst Control Center by Advanced Micro Devices.

The Catalyst Control Center is an overclocking and optimization utility for ATI Radeon graphics cards.

 

Not sayings it's the root cause but it seems out of the ordinary and reporting as an error in the dxdiag report.

 

---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 1503147946455305397, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: RadeonSettings.exe
P2: 10.1.1.1682
P3: 593efe33
P4: StackHash_ac46
P5: 0.0.0.0
P6: 00000000
P7: PCH_E7_FROM_ntdll+0x000000000009CC14
P8: c0000005
P9: 0000000000000008
P10: 


+++ WER1 +++:
Fault bucket 1218307148305802016, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: RadeonSettings.exe
P2: 10.1.1.1682
P3: 593efe33
P4: StackHash_ac46
P5: 0.0.0.0
P6: 00000000
P7: PCH_5B_FROM_ntdll+0x000000000009CC14
P8: c0000005
P9: 0000000000000008
P10: 


+++ WER2 +++:
Fault bucket 1705433060719858585, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: DCS.exe
P2: 2.5.6.45915
P3: 5e8205ed
P4: DCS.exe
P5: 2.5.6.45915
P6: 5e8205ed
P7: c0000005
P8: 000000000067d867
P9: 
P10: 

[ghighcove]

I'll address the Radeon part first -- I think that's the card native to the motherboard, but not connected to anything. I did notice the Radeon utilities on recently (my main cardis NVIDIA), so that's a good note for me to look out for.

 

Regarding the other checks besides the page file, it's a lot to get through. I'll see what I can do, but that's sounding like a couple of hours worth of work, installing, uninstalling, etc. Seems like a lot of hoops to jump through.

 

If I wanted to just address the metashaders issue and see if that fixed it, what would I check?

 

I have to say the crash itself is very definite in terms of something loading about Nellis or near Nellis from that angle. Could I be missing a vehicle model or something like that?

[Sabre-TLA]

Hold off on doing any major updates to your system at this point.

 

We retested the mission tonight and got some similar crashes as soon as we put the ILS on after departing Nellis. Same video card drivers as what you reported so it might be driver related.

 

There is a 2.5.6 update coming out tomorrow I believe so we will retest it against that and see if it still happens. There is also a new driver update for the GTX cards so we will test against both.

 

This isn't something we can manipulate directly within the mission so it may be a bug in the game engine but we have to replicate it so we can give the ED DEVs the details.

 

For now you should be able to complete the mission provided you don't turn on the ILS when airborne. :(

[ghighcove]

Thanks, I appreciate the update, and as you said, I'm also due to update my NVIDIA drivers along with the DCS update coming out Thanks for the effort on this.

[Maltschik]

Hi ghighcove + Sabre-TLA,

 

I have the same problem with the crash. It must be a bug which happens ONLY within this campaign: While on the ground I can switch between NAV and ILS, but once airborne switching to ILS makes the complete game crashing.

 

Note: in all other user-missions and campaigns switching to ILS works fine. I am currently at Mission 3 and I help myself by neither switching to ILS manually nor flying over the last waypoint for automatically switch to ILS. Then I can finish all the missions.

 

But this isn’t the way it should be :-( so hopefully you / ED can fix this strange bug.

[N22YF]

In 2.5.6.49798, I had what sounds like the same problem—not in this specific mission, but I repeatably ran into it in certain (but not all) other F-15C (and also A-10A) missions—but it thankfully appears to have been resolved in the current version, 2.5.6.52437. Was it resolved for y'all too?

[Maltschik]

No, at least in my case it is still a specific bug within this campaign (but honestly I don’t care anymore - I’ve finished it and sadly it was boring as hell).

[Snake122]

Just reporting I'm getting this same crash still on stable 2.5.6.55960 as I cross over APEX.