Jump to content

Keep getting CTD with A10C2


Gryzor

Recommended Posts

Hello JackFlash. It seems you're stuck with the omen described here and here:

 

@silverdevilNo such issue on my end. Here's how the log ends:

2022-11-01 05:56:15.434 INFO    EDTERRAINGRAPHICS41 (Main): 	 forestDistanceFactor = 0.500000
2022-11-01 05:56:15.434 INFO    EDTERRAINGRAPHICS41 (Main): 	 forestDetailsFactor = 1.000000
2022-11-01 05:58:21.144 INFO    EDCORE (Main): try to write dump information
2022-11-01 05:58:21.145 INFO    EDCORE (Main): # -------------- 20221101-055821 --------------
2022-11-01 05:58:21.146 INFO    EDCORE (Main): DCS/2.8.0.32066 (x86_64; Windows NT 10.0.19044)
2022-11-01 05:58:21.147 INFO    EDCORE (Main): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\edterrainGraphics41.dll
2022-11-01 05:58:21.148 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 4410972D 00:00000000
2022-11-01 05:58:21.151 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'Alast'
2022-11-01 05:58:21.152 INFO    EDCORE (Main): OS-Version: 10.0.19044 () 0x100-0x1
2022-11-01 05:58:21.505 INFO    EDCORE (Main): 0x000000000008972D (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x7536D
2022-11-01 05:58:21.505 INFO    EDCORE (Main): 0x000000000009B170 (edterrainGraphics41): createInstancerRenderable + 0x48E0
2022-11-01 05:58:21.506 INFO    EDCORE (Main): 0x00000000000F0C80 (edterrainGraphics41): edtg41::TerrainRenderable::render + 0x1020
2022-11-01 05:58:21.506 INFO    EDCORE (Main): 0x00000000000EFB4A (edterrainGraphics41): edtg41::TerrainRenderable::render + 0x8A
2022-11-01 05:58:21.506 INFO    EDCORE (Main): 0x00000000000DA2AD (edterrainGraphics41): createInstancerRenderable + 0x43A1D
2022-11-01 05:58:21.506 INFO    EDCORE (Main): 0x00000000000AD8BF (Visualizer): TerrainRenderer::render + 0x16F
2022-11-01 05:58:21.506 INFO    EDCORE (Main): 0x00000000000A6F86 (Visualizer): RenderParserImpl::isEmpty + 0xE376
2022-11-01 05:58:21.506 INFO    EDCORE (Main): 0x000000000009D12C (Visualizer): RenderParserImpl::isEmpty + 0x451C
2022-11-01 05:58:21.507 INFO    EDCORE (Main): 0x00000000000F8BFB (Visualizer): smSceneManager::regLua + 0x663B
2022-11-01 05:58:21.507 INFO    EDCORE (Main): 0x00000000000F643A (Visualizer): smSceneManager::regLua + 0x3E7A
2022-11-01 05:58:21.507 INFO    EDCORE (Main): 0x00000000000E6FC9 (Visualizer): smSceneManager::DestroySceneManager + 0x47A9
2022-11-01 05:58:21.507 INFO    EDCORE (Main): 0x000000000080CA73 (DCS): SW + 0x3CD533
2022-11-01 05:58:21.507 INFO    EDCORE (Main): 0x000000000082D349 (DCS): SW + 0x3EDE09
2022-11-01 05:58:21.507 INFO    EDCORE (Main): 0x00000000007ECA54 (DCS): SW + 0x3AD514
2022-11-01 05:58:21.508 INFO    EDCORE (Main): 0x00000000007ED924 (DCS): SW + 0x3AE3E4
2022-11-01 05:58:21.508 INFO    EDCORE (Main): 0x00000000022820EB (DCS): AmdPowerXpressRequestHighPerformance + 0xF5B0E7
2022-11-01 05:58:21.508 INFO    EDCORE (Main): 0x0000000000BDA842 (DCS): SW + 0x79B302
2022-11-01 05:58:21.508 INFO    EDCORE (Main): 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
2022-11-01 05:58:21.508 INFO    EDCORE (Main): 0x00000000000526A1 (ntdll): RtlUserThreadStart + 0x21
2022-11-01 05:58:23.065 INFO    EDCORE (Main): Minidump created.

 

That makes a lot of people having CTDs in an A-10C...


Edited by Flappie

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Hi. You're not the first one reporting this "edterrainGraphics41.dll" crash with the A-10C. I'm looking for a pattern to try and reproduce the crash.

What mission(s) are you flying when that happesn? Are you doing something special seconds before the crash? SP, MP, or both?

2022-11-07 13:58:37.301 INFO    ASYNCNET (Main): Current ping: 212.8ms
2022-11-07 13:58:52.260 INFO    EDCORE (Main): try to write dump information
2022-11-07 13:58:52.264 INFO    EDCORE (Main): # -------------- 20221107-135852 --------------
2022-11-07 13:58:52.264 INFO    EDCORE (Main): DCS/2.8.0.32235 (x86_64; Windows NT 10.0.19044)
2022-11-07 13:58:52.265 INFO    EDCORE (Main): C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\edterrainGraphics41.dll
2022-11-07 13:58:52.265 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 6D8E972D 00:00000000
2022-11-07 13:58:52.269 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: '.;C:\Program Files (x86)\Steam\steamapps\common\DCSWorld;C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'PC'
2022-11-07 13:58:52.270 INFO    EDCORE (Main): OS-Version: 10.0.19044 () 0x300-0x1
2022-11-07 13:58:53.040 INFO    EDCORE (Main): 0x000000000008972D (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x7536D
2022-11-07 13:58:53.041 INFO    EDCORE (Main): 0x000000000009B170 (edterrainGraphics41): createInstancerRenderable + 0x48E0
2022-11-07 13:58:53.041 INFO    EDCORE (Main): 0x00000000000F0C80 (edterrainGraphics41): edtg41::TerrainRenderable::render + 0x1020
2022-11-07 13:58:53.041 INFO    EDCORE (Main): 0x00000000000EFB4A (edterrainGraphics41): edtg41::TerrainRenderable::render + 0x8A
2022-11-07 13:58:53.042 INFO    EDCORE (Main): 0x00000000000DA2AD (edterrainGraphics41): createInstancerRenderable + 0x43A1D
2022-11-07 13:58:53.042 INFO    EDCORE (Main): 0x00000000000AD8BF (Visualizer): TerrainRenderer::render + 0x16F
2022-11-07 13:58:53.042 INFO    EDCORE (Main): 0x00000000000A6F86 (Visualizer): RenderParserImpl::isEmpty + 0xE376
2022-11-07 13:58:53.042 INFO    EDCORE (Main): 0x000000000009D12C (Visualizer): RenderParserImpl::isEmpty + 0x451C
2022-11-07 13:58:53.042 INFO    EDCORE (Main): 0x00000000000F8BCB (Visualizer): smSceneManager::regLua + 0x663B
2022-11-07 13:58:53.043 INFO    EDCORE (Main): 0x00000000000F640A (Visualizer): smSceneManager::regLua + 0x3E7A
2022-11-07 13:58:53.043 INFO    EDCORE (Main): 0x00000000000E6FC9 (Visualizer): smSceneManager::DestroySceneManager + 0x47A9
2022-11-07 13:58:53.043 INFO    EDCORE (Main): 0x000000000080CB53 (DCS): SW + 0x3CD653
2022-11-07 13:58:53.043 INFO    EDCORE (Main): 0x000000000082D429 (DCS): SW + 0x3EDF29
2022-11-07 13:58:53.044 INFO    EDCORE (Main): 0x00000000007ECB34 (DCS): SW + 0x3AD634
2022-11-07 13:58:53.044 INFO    EDCORE (Main): 0x00000000007EDA04 (DCS): SW + 0x3AE504
2022-11-07 13:58:53.044 INFO    EDCORE (Main): 0x00000000022791B2 (DCS): AmdPowerXpressRequestHighPerformance + 0xF521AE
2022-11-07 13:58:53.044 INFO    EDCORE (Main): 0x0000000000BDA932 (DCS): SW + 0x79B432
2022-11-07 13:58:53.044 INFO    EDCORE (Main): 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
2022-11-07 13:58:53.045 INFO    EDCORE (Main): 0x00000000000526A1 (ntdll): RtlUserThreadStart + 0x21
2022-11-07 13:58:53.616 INFO    EDCORE (Main): Minidump created.

 

Nevermind, I see you're already participating in the other thread. Let's keep chatting out there.


Edited by Flappie

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

You're having the very same crash, indeed. I want to report ths issue but we need to gather some info for devs to try and reproduce the crash in order to fix what causes this.

From what I can see, you all have one common point: you own both A-10C and A-10C II modules.

Can you confirm the issue happens only with the "old" A-10C?

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

46 minutes ago, Flappie said:

I'll report this issue but first I need to know more, @JackFlash. In which mission did that happen? During mission loading, mission start, or later? In F1 view, F2 or F10 view? Were you using radios, TGP, armament? Enemy around?

Twice in a custom MP mission, but if first occurred in the Instant Action Medium Winter mission. Crashed in middle of flight. No particular input as far as I can remember. Was looking in the TGP in F1-view. VR Reverb G2 and a 2080Ti. 
Did not use radios first time it happened. Headset goes black. Still hear the game in the background. The desktop game window still shows a freezed game image and a crash message. 

  • Thanks 1

My latest project, the Multi Function Button Box can be found at Kickstarter.

Link to comment
Share on other sites

2 hours ago, Flappie said:

Hey @Gryzor. I'm seeing a few other users with the exact same A-10C crash. How's it going with ED support?

Just to be honest, not quite good, they give me some general advices like put swapfile at 30GB (I have 60) even I reported this thread, it seems that don´t pay much attention.

Fran Clavijo
11/08/2022 13:07:58
Ok, but because the crash occours 30 minutes after start the plane, track doest reach that point (plane crash intro the ground, because track playing is bugged ... you know). Do you want the mission file?

I  find some other posts about A-10C II issues with the sames errors I have, please look the last post of this thread:

https://forum.dcs.world/topic/311685-try-this-for-28-crashing/#comment-5085000

Thanks
 
Mike
11/08/2022 15:01:49
Hello,
Please try to reduce the size of the Windows paging file to 30 GB.
If the crash occurs again please send the latest dcs.log file and we will try to reproduce the crash on our test computer.
Thanks.

--
Best regards,
Mike

Edited by Gryzor
Link to comment
Share on other sites

Thank you. I've just reported the issue even though I could not reproduce the crash so far.

I'm wondering why the DLL crashing is not the A-10's, but the terrain's.

Can you please fly not using the raster chart (image below) on your TSD, and tell us if the crashes keep happening?

rasterchart.jpg

  • Like 2

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

16 hours ago, Flappie said:

You're having the very same crash, indeed. I want to report ths issue but we need to gather some info for devs to try and reproduce the crash in order to fix what causes this.

From what I can see, you all have one common point: you own both A-10C and A-10C II modules.

Can you confirm the issue happens only with the "old" A-10C?

If my issue is the same it happens in the new A-10

My latest project, the Multi Function Button Box can be found at Kickstarter.

Link to comment
Share on other sites

I experienced 3 crash to desktop events in a row when playing multiplayer on Syria in the A10C2. It happened each time right when trying to view the TAD after selecting other pages on the left Display.

Crash was in:edterrainGraphics41.dll every time
I updated drivers

deleted that file and did a repair

Deleted FXO and MetaShaders

Tested in Singleplayer as well. same result

Steps to reproduce
Version: 2.8.0.322235
Flying over the middle of Cyprus on Syria
TAD zoomed to show Cyprus aerial map. (20NM)
Hide TAD by showing different screen using Coolie Hat Left. 
Show TAD by pressing Coolie Hat Left (DSMS->TAD)
 

tad crash.png

dcs.log-20221111-203942.zip

Link to comment
Share on other sites

I tried to reproduce this, using the track from your Zip archive as a mission, but my DCS doesn't crash when cycling the left MFCD between TAD, DSMS and MAV. I tried with TAD range 20 as well as EXP1 right over Cyprus.

Looking at your DCS.log, there's an access violation.

What I'd try to do is (always make sure DCS is not running when performing any of these):

  • Remove all mods (I think there was something about the UH-60L in the log, which probably isn't related to the crash (I've also got it installed), but you never know)
  • Check if problem persists
  • Run a slow DCS repair and have it Search for Extra Files
  • Check if problem persists
  • Rename your Saved Games\DCS.openbeta (all your config will be gone; test with the bare minimum; you can later delete the new Saved Games\DCS.openbeta and rename your original one back)
  • Check if problem persists
  • Open Avast and add an exception for the entire DCS installation folder B:\Eagle Dynamics
  • Check if problem persists

It might be a good idea to repair Windows as well, but I'm not going to write down any commands here, because doing something wrong there could possibly ruin your Windows installation, and I don't want to be the one at fault here. 😉

Good luck and let us know if any of these steps helped you!

Link to comment
Share on other sites

  • Recently Browsing   0 members

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