DCS/2.5.3.24436 CRASH ERROR DX11BACKEND

[FA_Crazy-Canuck]

Ok, there have been reports of crashes due to over clocked GPU's so this is my concern more so than the artifacting. I don't seem to have any troubles with the over clock in other scenerios outside of DCS.

[Badass1982]

Mine wasn't giving ANY ARTIFACTING overclocked or not, just a black screen crash. This is a DCS engine error, I have already uploaded my crash dump through the auto thing but i can add it to this thread as I can reproduce it every time.

 

Artifacting is usually but not always due to an unstable overclock (also extremely unlikely on a factory overclocked card to be to do with the overclock as it is stable)

 

Not one of my other games (or benches crash when running my card OC'ed or not) I use a LOT of GPU and CPU benches in my daily life and none make my hardware fail.

 

Its such a cop out to say "it's your overclock".

[NineLine]

Mine wasn't giving ANY ARTIFACTING overclocked or not, just a black screen crash. This is a DCS engine error, I have already uploaded my crash dump through the auto thing but i can add it to this thread as I can reproduce it every time.

 

Artifacting is usually but not always due to an unstable overclock (also extremely unlikely on a factory overclocked card to be to do with the overclock as it is stable)

 

Not one of my other games (or benches crash when running my card OC'ed or not) I use a LOT of GPU and CPU benches in my daily life and none make my hardware fail.

 

Its such a cop out to say "it's your overclock".

 

Nobody from ED blamed your overclock, other users claimed it helped them to remove manually set overclocking, so calm down. And yes, please supply crash logs.

[Tripleinside]

my open beta seems stable now that i removed the OC Scanner overclock curve from my 2080ti, and that i reverted to the previous nvidia drivers

 

i now will reapply the overclock while keeping these drivers and see if the crashes are back, will let you know

 

PS: when crashing, i was getting a black screen like others described. while in game i was sometimes getting like a big black square furtively appearing and disappearing, FYI

Edited December 29, 2018 by Tripleinside

[FA_Crazy-Canuck]

So are you getting a crash anymore or just this artifacting?

 

Flew a multiplayer mission tonight after cleaning out the FXO and Metashader2 folders and ran a repair. Also had my stable GPU over clock running with no mods installed. Flew for one hour fifteen minutes in multiplayer and had no issues. Will report back after a few more flights.

[Badass1982]

I haven't had a chance to check it yet but I will in the next few days and I'll attach my crash dump thing too.

[FA_Crazy-Canuck]

Flew a multiplayer mission hosted by a squad mate. Flew Persian Gulf Map, crash occurred in roughly in the same place as last time and about the same amount of time. Others had no issue. Flew fine for an hour then frozen screen with an hour glass then crashes.

 

I did have the Stennis Carrier Deck paint installed made by VFW 113 as well as the platcam mod but we weren't using it. I installed these mods since I did not have an issue the other night flying. I have had no troubles using the deck paint off line.

 

Log attached.

DCSLog.zip

[FA_Crazy-Canuck]

By the way SRS produced a log at the time of the crash and it read the following:

 

Loaded Terrain - SimpleRadio Standalone!

Loaded SimpleRadio Standalone Export version:1.5.6.0

 

Not sure if this means anything but why would simple radio have to load Terrain?

[NineLine]

I do see errors related to the Stennis, not sure if they would cause a crash, you have some weird shader errors too. Are you using any sort of re-shader tools or altered textures for terrain or anything like that?

[Badass1982]

My DCS Log.

 

Just tried again , I managed to reproduce it shortly before take off. No artifacting just game froze and if I pressed escape it would stop in game sounds, pressing escape again would continue the games sounds with a stuck picture on screen of my f-15 taxiing.

 

Looks like the game has been paused but it hasnt then after a couple of seconds crashes out to the DCS splash screen. I'm including the log file.

 

I have deleted the folders suggested by the user above and launched the game again so the shader folders are rebuilt and I deleted the mods folder (and DCS savegames folder too).

 

I did in the past have RESHADE installed so I'm doing a fresh install (though this wouldn't explain why it doesn't crash when not overclocked on the smae install).

dcs.txt

Edited January 2, 2019 by Badass1982

[FA_Crazy-Canuck]

I do see errors related to the Stennis, not sure if they would cause a crash, you have some weird shader errors too. Are you using any sort of re-shader tools or altered textures for terrain or anything like that?

 

As I read through the log I noticed a reference to shaders as well. I did have reshade installed but it was turned off. I have since uninstalled reshade and ran a repair. Was too late in the evening to run additional testing. Will run a mission again and see what happens.

 

Thanks for the input.

[NineLine]

As I read through the log I noticed a reference to shaders as well. I did have reshade installed but it was turned off. I have since uninstalled reshade and ran a repair. Was too late in the evening to run additional testing. Will run a mission again and see what happens.

 

Thanks for the input.

 

Someone else mentioned reshade causing a crash, so interested to see if it helps you as well.

[Badass1982]

I tried a fresh install into a directory which is different to where the previous installation was done. No change. Ruled out re-shade causing my issue. Or Mods. Or the Shader folders as It was newly created shader folders.

 

Running the latest 2.5 BETA build.

 

Still have to try with the stable build.

[Badass1982]

My DCS Log Part 2

 

OK so after all that I reverted to the latest stable release went to start my F15-C engines and again the same crash . I have included the latest log.zip for the devs review.

dcs.log-20190103-035833.zip

[NineLine]

OK so after all that I reverted to the latest stable release went to start my F15-C engines and again the same crash . I have included the latest log.zip for the devs review.

 

I tried your track, and just starting up on my own and couldnt replicate this crash.

[Badass1982]

Do you have the same hardware. This is the only application that does this: Graphics benches don't even crash when heavily loading the card, DCS barely even loads my card.

[FA_Crazy-Canuck]

After flying a few more multiplayer flights it would appear that my crashes were caused by the GPU over heating due to the overclock. If this changes I will report back.

[Badass1982]

Mine isn't going above 65 Celcius so it's not that for me.

[Badass1982]

I've just installed my GPU water block so I'll update this thread if I find out anything new. (Under Water my GPU is 22c idle and 31c under load lol)

[Badass1982]

So I don't want to tempt fate, but I was able to just fly a DCS 2.5 open beta Bear Trap mission with my F-15 without a single black screen or crash, the only thing that has changed on my system is that my GPU is now being water cooled and thus the temps are a LOT lower. Under load (in DCS the GPU doesnt get hotter than the mid 30's C).

 

I will report back if this happens again but so far so good.

 

Oh this is WITH the card overclocked past factory settings.

[BASS702]

So I don't want to tempt fate, but I was able to just fly a DCS 2.5 open beta Bear Trap mission with my F-15 without a single black screen or crash, the only thing that has changed on my system is that my GPU is now being water cooled and thus the temps are a LOT lower. Under load (in DCS the GPU doesnt get hotter than the mid 30's C).

 

I will report back if this happens again but so far so good.

 

Oh this is WITH the card overclocked past factory settings.

 

GPU:2070s oc

same problem ,however I found my GPU power was limited at 80% or less while running this game with GPU uasge 98%,and power always drop to 20% which also take my GPU usage to 0% and make this game crashed.

[skypickle]

I've noticed the same issue with the overclock on my pascal card. Although it is stable at 2.05 ghz with temps always below 60 deg in ALL other games and even the heaven benchmark (it's watercooled), RTSS shows that it's voltage limited (even tho I've set the core voltage slider to 100% in Afterburner) Decreasing the overclock to +23% on the core clock and +10% on the memory clock eliminated crashes and the card runs at 1900 mHz.

[Scofflaw]

I'm constantly getting the same crash. I have my core and memory clocks set to +0MHz, and it still crashes. Right now it seems to crash more on specific missions, but I need to do more testing.

[SKIPPY 7-7]

getting black screen crash. Here's my post https://forums.eagle.ru/showthread.php?t=288067

[Boneski]

This was my issue just as Badass1982 stated! I did some lite over clocking to get some better VR output on my MSI RTX 2600 Ventus oc and it was a no go.

Reset to default clock.. game works fine no crash. 

 

So no over clocking for me.