[RESOLVED]Constant crash to desktop

[Dave317]

I've been playing the viggen campaign and keep crashing at the same point. Not sure if any other modules are affected but I'll give them a try. It's an unmodified version that I've repaired. Is this the log that is needed?

 

 

 

# -------------- 20191223-121821 --------------

DCS/2.5.5.41371 (x86_64; Windows NT 6.1.7601)

F:\Program Files\Eagle Dynamics\DCS World\bin\edterrain4.dll

# C0000005 ACCESS_VIOLATION at C9F1BCAB 00:00000000

SymInit: Symbol-SearchPath: '.;F:\Program Files\Eagle Dynamics\DCS World;F:\Program Files\Eagle Dynamics\DCS World\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'David'

OS-Version: 6.1.7601 (Service Pack 1) 0x100-0x1

0x000000000021BCAB (edterrain4): (function-name not available) + 0x0

0x000000000021B26C (edterrain4): (function-name not available) + 0x0

0x000000000021228A (edterrain4): (function-name not available) + 0x0

0x000000000021C175 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x0000000000211F43 (edterrain4): (function-name not available) + 0x0

0x000000000001D49D (edterrain4): (function-name not available) + 0x0

0x00000000000066BB (Terrain): createGlobalLand + 0x27B

0x00000000000C70F6 (WorldGeneral): getInterceptionParams + 0x6F6

0x00000000000C7958 (WorldGeneral): buildPointsSector + 0xA8

0x00000000000C8079 (WorldGeneral): getGroundProximityFactor + 0xF9

0x00000000002F221D (DCS): (function-name not available) + 0x0

0x00000000002FB8DE (DCS): (function-name not available) + 0x0

0x00000000002B30AF (DCS): (function-name not available) + 0x0

0x0000000000002D11 (World): (function-name not available) + 0x0

0x00000000000031DF (World): (function-name not available) + 0x0

0x0000000000574132 (DCS): (function-name not available) + 0x0

0x0000000000585688 (DCS): (function-name not available) + 0x0

0x0000000000556994 (DCS): (function-name not available) + 0x0

0x00000000001C8FBF (DCS): (function-name not available) + 0x0

0x000000000073B946 (DCS): (function-name not available) + 0x0

0x000000000001556D (kernel32): BaseThreadInitThunk + 0xD

0x000000000005372D (ntdll): RtlUserThreadStart + 0x1D

[Dave317]

Does it with the F14 too. Just said 'DCS has stopped working' and crashed to desktop. No crashlog created this time.

[Dave317]

And another :(

 

 

 

 

# -------------- 20191223-135502 --------------

DCS/2.5.5.41371 (x86_64; Windows NT 6.1.7601)

F:\Program Files\Eagle Dynamics\DCS World\bin\edterrain4.dll

# C0000005 ACCESS_VIOLATION at B131BCB1 00:00000000

SymInit: Symbol-SearchPath: '.;F:\Program Files\Eagle Dynamics\DCS World;F:\Program Files\Eagle Dynamics\DCS World\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'David'

OS-Version: 6.1.7601 (Service Pack 1) 0x100-0x1

0x000000000021BCB1 (edterrain4): (function-name not available) + 0x0

0x000000000021B1E9 (edterrain4): (function-name not available) + 0x0

0x000000000021228A (edterrain4): (function-name not available) + 0x0

0x000000000021C175 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x000000000021C1A1 (edterrain4): (function-name not available) + 0x0

0x0000000000211F43 (edterrain4): (function-name not available) + 0x0

0x000000000001D49D (edterrain4): (function-name not available) + 0x0

0x00000000000066BB (Terrain): createGlobalLand + 0x27B

0x0000000000015A00 (Weather): gOvercast::DrawPtcls + 0x4540

0x00000000000150BF (Weather): gOvercast::DrawPtcls + 0x3BFF

0x00000000000154D8 (Weather): gOvercast::DrawPtcls + 0x4018

0x00000000000845B3 (Visualizer): smCamera_Implement::SetProjBounds + 0xBDD3

0x00000000005741A4 (DCS): (function-name not available) + 0x0

0x0000000000585688 (DCS): (function-name not available) + 0x0

0x0000000000556994 (DCS): (function-name not available) + 0x0

0x00000000001C8FBF (DCS): (function-name not available) + 0x0

0x000000000073B946 (DCS): (function-name not available) + 0x0

0x000000000001556D (kernel32): BaseThreadInitThunk + 0xD

0x000000000005372D (ntdll): RtlUserThreadStart + 0x1D

[BIGNEWY]

Hi

 

please attach the whole dcs log, it will give us some more clues hopefully.

 

Ensure windows and display driver are up to date, and run a cleanup and repair.

 

If you have a track replay in the zip that is created when you crash please attach it and I will try and reproduce.

 

thanks

[Dave317]

Is this what you need? It's a clean install with no mods.

dcs.log-20191223-135502.zip

[BIGNEWY]

Thanks, I will take a look

 

edit:

 

I had a look at the track, but was unable to reproduce the crash.

 

Try a fresh DCS folder in your saved games location, if you rename it you can keep it as a backup.

 

then restart DCS login and test again

 

thanks

Edited December 23, 2019 by BIGNEWY

[Dave317]

That didn't work. Still crashing and the drivers are all up to date.

dcs.log-20191223-154112.zip

Edited December 23, 2019 by Dave317

[BIGNEWY]

I have tried to reproduce but again not been able to.

 

Long shot what antivirus are you using? excluding dcs from realtime scan can help sometimes with strange crashes.

 

Is your windows 7 up to date also?

 

thanks

[BIGNEWY]

another long shot, are you using reshade?

[Dave317]

Windows is up to date and I'm not using reshade.

[Dave317]

I'm going to try a complete fresh install. Only difference i can see is my Saved games folder was called 'DCS' and now it is named 'DCS.openbeta.'

Not sure if this has changed recently or even if if would cause an issue.

 

 

I'll see how I get on and report back if I'm still having problems.

[JIMJAM]

I would rather DCS not run at all than to make a change which appears to solve the issue and then out of the blue usually when you are really having fun and BAM.... CTD.

My folders are also a mess. The only good news is I learned to save your input/aircrafts/ folder that has ALL your hard work setting up your controls. I have a dozen modules so from scratch you are looking at a long time.

[Dave317]

I've tried a complete fresh install which seemed to work. I tried a few Viggen and Gazelle missions which worked without a problem. F14, FA18 and AV8B always crash though.

dcs.log-20200103-192448.zip

[BIGNEWY]

Hi Dave317

 

Is windows 7 up to date? ( and just to check are you aware windows will stop supporting it at the end of the month )

 

noticed this in your log, not sure about this

2020-01-03 19:22:17.149 ERROR DX11BACKEND: getVideoMemoryUsage doesn't work.

 

Try the windows update, and ensure the display driver is up to date.

 

also it maybe worth renaming your dcs folder in saved games ( keep it as a backup for now )

 

G:\Saved games\DCS.openbeta\ to G:\Saved games\DCS.openbetabackup

 

restart DCS login and redo settings.

 

test and see if it helps.

 

let us know how you get on.

[Dave317]

Windows should be up to date. It automatically updates and yes I'm aware it it not being supported anymore. I'll upgrade to Windows 10 when I get round to it.

I've removed my saved games folder and let dcs rebuild it but it's still the same.

[BIGNEWY]

If you have not already I would suggest contacting support directly

 

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

 

They maybe able to assist further.

 

I hope you track this issue down.

 

thanks

[Dave317]

Thanks for all of your help.

[BIGNEWY]

Thanks for all of your help.

 

No problem, and let me know if you find the solution.

[Dave317]

Don't want to say too much but it might be solved. I tried reinstalling after formatting the Ssd but random files said they were corrupt. I've now installed it on a brand new Ssd and I've not had a problem since. Looks like my Ssd may have been bad.

[BIGNEWY]

Don't want to say too much but it might be solved. I tried reinstalling after formatting the Ssd but random files said they were corrupt. I've now installed it on a brand new Ssd and I've not had a problem since. Looks like my Ssd may have been bad.

 

Great to hear!

 

Thanks for letting us know.