dcs crashes

[0414 Wee Neal]

Hi I have been suffering ctd over the last couple of days, logs attached.

 

Any help // views appreciated?

 

Neal

dcs.log-20190805-203239.zip

dcs.log-20190805-201443.zip

dcs.log-20190804-172246.zip

dcs.log-20190402-203034.zip

[FlyingDeacon]

I’m experiencing the same video spikes and crashes. I’m running the 2.5 stable version. This has been the case since the last update.

 

Hopefully the next update will correct this.

[0414 Wee Neal]

I was on beta, changed to stable, still crashes! fingers crossed for Wed update?

[BIGNEWY]

Hi

 

it looks like a display driver crash, have you tried a fresh install of your display driver?

 

2019-08-05 20:32:38.393 WARNING LOG: 108 duplicate message(s) skipped.
2019-08-05 20:32:38.393 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2019-08-05 20:32:38.393 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:370
2019-08-05 20:32:38.393 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2019-08-05 20:32:38.393 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:370
2019-08-05 20:32:38.400 INFO    EDCORE: try to write dump information
2019-08-05 20:32:38.404 INFO    EDCORE: # -------------- 20190805-203239 --------------
2019-08-05 20:32:38.406 INFO    EDCORE: DCS/2.5.5.34108 (x86_64; Windows NT 10.0.18362)
2019-08-05 20:32:38.407 INFO    EDCORE: C:\WINDOWS\SYSTEM32\d3d11.dll

[0414 Wee Neal]

Hi

 

I have just rolled back my driver by one version and flown a mission and all good (apart from getting shot down of course!). I will try the same mission that I kept getting ctd on, which is mission 1 of the Blue Nosed Bastards campaign. Fingers crossed it is a Nvidia driver issue, there have been so many updates from Windows, Oculus, Nvidia, DCS etc it not easy to pin them down.

 

Regards

 

Neal

[BIGNEWY]

Good to hear you have made some progress, hope it resolves your crash :)

[flyco]

DCS Crashes on Touchdown

 

I am getting recurrent crashes on touchdown - the system freezes for a couple of seconds and then announces a crash. I have attached a copy of the crash log from the most recent.

 

It only appears to happen on Multiplayer missions, exceeding an hour, and always exactly at touchdown. Fellow players report my aircraft leaping into the air, and freezing at this point.

 

I am also experiencing regular incidents of aircraft going through the runway, although I sense that this is not the same problem - indeed it happens every time I try to start a P-51, and very often with other prop aircraft. In addition, in this latter case the aircraft continues to fly and I can re-emerge from the runway and repeat this procedure repeatedly. I suspect this to be a 'red herring', but felt I should include it for completeness.

 

To the best of my recollection, the crash on touchdown has always happened after a protracted flight in the A-10C. However, that may be because this is the only aircraft I fly for over an hour and a half.

 

From examination of the log, I suspect the crash coincides with the Access Violation message which appears in the log, and which is reproduced below with a few surrounding lines.

 

2019-08-06 21:01:03.416 INFO DX11BACKEND: Unloaded 33 mb of textures.

2019-08-06 21:01:55.940 INFO EDCORE: try to write dump information

2019-08-06 21:01:55.944 INFO EDCORE: # -------------- 20190806-210156 --------------

2019-08-06 21:01:55.947 INFO EDCORE: DCS/2.5.5.34108 (x86_64; Windows NT 10.0.17763)

2019-08-06 21:01:55.951 INFO EDCORE: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Weather.dll

2019-08-06 21:01:55.955 INFO EDCORE: # C0000005 ACCESS_VIOLATION at A70C1164 00:00000000

2019-08-06 21:01:55.961 INFO EDCORE: 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*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Alan'

2019-08-06 21:01:55.965 INFO EDCORE: OS-Version: 10.0.17763 () 0x300-0x1

 

I use Helios, with the main electronic displays exported - however, I have done this for some years now without any problems. I understand that I should perhaps try a similar sortie without Helios, but am so reliant on it that I am reluctant to expose myself (and my fellow fliers), to the considerable inconvenience.

 

Does anyone have any suggestions? I will confess that since it always appears to occur on long MP missions, and only at landing, I could continue with it and just make sure that I am the last to land - the main problem then would be that I would never get an uncorrupted TacView record.

[FlyingDeacon]

Could someone tell me if they see what is causing my crash issue from the logs attached? Thank you.

dcs.log-20190809-210752.zip

dcs.log-20190811-235505.zip

dcs.log-20190812-052703.zip

[BIGNEWY]

Could someone tell me if they see what is causing my crash issue from the logs attached? Thank you.

 

# -------------- 20190812-052703 --------------

DCS/2.5.5.33184 (x86_64; Windows NT 10.0.18362)

C:\WINDOWS\SYSTEM32\d3d11.dll

# C0000005 ACCESS_VIOLATION at 7D51F4F0 00:00000000

SymInit: Symbol-SearchPath: '.', symOptions: 534, UserName: '13375'

OS-Version: 10.0.18362 () 0x300-0x1

0x000000000011F4F0 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0xD430

0x00000000000058B5 (dx11backend): RenderAPI::DX11Renderer::getBufferManager + 0xC85

0x0000000000072FCD (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x6688D

0x00000000000BC85F (edterrainGraphics41): createInstancerRenderable + 0x2D14F

0x00000000000BBC59 (edterrainGraphics41): createInstancerRenderable + 0x2C549

0x00000000000298C3 (edCore): ed::thread::hardware_concurrency + 0x8E3

0x0000000000020687 (edCore): ed::make_main_thread_tasks + 0x17

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

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

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

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

0x0000000000017BD4 (KERNEL32): BaseThreadInitThunk + 0x14

0x000000000006CE71 (ntdll): RtlUserThreadStart + 0x21

 

looks also like display driver crashing.

 

Have you tried a windows update and a gpu driver update?

[FlyingDeacon]

I did the windows update and still have the same results. I’ll try the gpu update.

[0414 Wee Neal]

I have found my ctd only seems to happen on the Blue nosed Bastards campaign. I will try again after doing a windows update.

[FlyingDeacon]

It appears I'm done with DCS for a while. I've completely reformatted my computer, reinstalled the basics with DCS and I still get the same VR spikes and game crashes. I give up.

[BIGNEWY]

Do you overclock your GPU by any chance?

 

I have seen overclocks create more problems than they solved with DCS.

 

If you have not already contact support directly

 

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

[FlyingDeacon]

Do you overclock your GPU by any chance?

 

I have seen overclocks create more problems than they solved with DCS.

 

If you have not already contact support directly

 

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

No I do not overclock the GPU. The issue began at the last 2.5 stable version update. Just an FYI - I'm not upset, this particular computer is dedicated to DCS only. I'm hopeful that a future update will correct the issue somehow.

 

Is there a way to download and install a previous version of 2.5 stable version? If not, I'll just be patient for a future update.

[BIGNEWY]

You could use this guide to revert to a previous version

https://forums.eagle.ru/showthread.php?t=114030

 

My concern in your case it seems to be limited to your install as others are not reporting the same, Just some that were having an FPS issue with that campaign.

 

Have you done a cleanup and repair?

[FlyingDeacon]

You could use this guide to revert to a previous version

https://forums.eagle.ru/showthread.php?t=114030

 

My concern in your case it seems to be limited to your install as others are not reporting the same, Just some that were having an FPS issue with that campaign.

 

Have you done a cleanup and repair?

Yes I did a clean install. I'm not running any particular campaign. My issue occurs simply flying the P-51 over Tblisi with no other modules or maps installed.

 

I've never tried the cleanup but I thought a reformat of my PC and clean install of windows 10 would take care of that.

Edited August 16, 2019 by FlyingDeacon

[0414 Wee Neal]

Interesting that my ctd are happening in the p51 as well, albeit different mission?

[FlyingDeacon]

I'm now thinking that my issue is the video card and has nothing to do with DCS. I'm running the GeForce RTX 2070 and I'm seeing that there are a lot of issue with that card.

 

Can someone take a look at these two recent logs files from today. Thank you.

dcs.log-20190817-210855.zip

dcs.log-20190817-211455.zip

[BIGNEWY]

2019-08-17 21:08:54.236 ERROR DX11BACKEND: failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED

2019-08-17 21:08:54.236 ERROR DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG

2019-08-17 21:08:54.329 INFO EDCORE: try to write dump information

2019-08-17 21:08:54.339 INFO EDCORE: # -------------- 20190817-210855 --------------

2019-08-17 21:08:54.368 INFO EDCORE: DCS/2.5.4.30386 (x86_64; Windows NT 10.0.18362)

2019-08-17 21:08:54.398 INFO EDCORE: C:\WINDOWS\SYSTEM32\d3d11.dll

2019-08-17 21:08:54.418 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 1B85F4F0 00:00000000

 

It does look like a driver failure, my advice would be to use DDU cleaner, wipe the driver and install the latest game ready driver.

 

It may help.

 

Also do you overclock your GPU? I seen some overclocks create issues with DCS.

[fagulha]

I don´t know if it going to help you, but, i want to give a try because i spent last 2 weeks (plus) looking for the reason of that kind of errors (Access violation etc):

 

In my case i think it was the Steam/SteamVR trying to open the compositor and although i choose "Run as administrator" using mouse right-click, Properties, and compatibility, Steam didn´t assume that. So, everytime i want to fly DCS, or other game/simulator, i do it manually, right click on the Steam shortcut and choose "Run as administrator" (and do the same with the DCS shortcut). Since yesterday i didn´t have any crashes and im going to continue testing. I just found this because in other (space) simulator it was crashing everytime after 2 minutes/10 minutes of playing, and then Steam gave me the error "-203" (instead of DCS which give me a log with Access Violation error Backend etc). I search a lot about it and for my understanding was the culprit of my problem. Steam try to access some dll and doesn´t have permission. Those two things are related as far i investigated and experiencied it. Give it a try and give feedback please.

 

My specs:

 

I7 4790K 4.4ghz

32GB DDR3 Ram

Zotac GTX 1080Ti 11GB gddr

Valve Index (upgraded from OG Vive since last week).

SSD´s and

AIO.

Edited September 25, 2019 by fagulha

[0414 Wee Neal]

Thanks, I will try and report back!

[Havremonster]

I have a lot of crashes tonight. Yesterday the game was fine...

Can it be my stick? It feels weard when I use the Huey.

dcs.rar

[fagulha]

It does look like a driver failure, my advice would be to use DDU cleaner, wipe the driver and install the latest game ready driver.

 

It may help.

 

Also do you overclock your GPU? I seen some overclocks create issues with DCS.

 

 

BIGNEWY,

 

Since last 2 weeks (and it happened to me in the past but then go away) i have constant crashes with those type of errors (ACCESS VIOLATION), and as far i know it´s Steam privileges related. I investigated about error -203 (Steam) and has to do with with access denied to files by Steam. Yesterday i started Steam "Run as administrator" manually (right mouse button and select "run as administrator" instead as i did before, because for unknown reason even if i set in Compatibility options for Steam start always as "Run as administrator" it wont work), and i have no crash since. Today i made a 2 hour flight with my squadron and 2 days ago was impossible. So, please, if you want some answers for helping more people take a look about this fix. Probably its a code error that Steam must fix and not EA.

 

 

Thank you for your help and commitment, keep up.

 

F.

[BIGNEWY]

Hi fagulha

 

thanks for sharing that with us.

 

I am sure it will help some

[fagulha]

Hi fagulha

 

thanks for sharing that with us.

 

I am sure it will help some

 

You´re welcome. I really hope it helps others, it was a mastermind to find the cause of the errors.

 

Best regards, and thank you once again.

 

Fagulha.