Crash after new patch beta

[FA_Crazy-Canuck]

Those who are experiencing crashes are you over clocking the GPU?

[diditopgun]

Those who are experiencing crashes are you over clocking the GPU?

 

No.

[j0nx]

Those who are experiencing crashes are you over clocking the GPU?

 

I’m not sure what that has to do with anything anyway since the crashes started right after the latest build.

[332nd_Merlin]

Patch update game now Crashes

 

Since latest update, my game now crashes after about 15 minutes to a half hour if I'm lucky, into a mission. No log made so I don't know what happened, just a hard freeze and drops to desktop, game over!

[332nd_Merlin]

game crash

 

Also running vanilla, no mods or anything, an this happens, notice more so to happen when I switch to view other aircraft in mission dose it much quicker.

[Bun]

P-51 blown engine causes CTD for me in 2.5.4

Start cold engine and firewall throttle and prop rpm

[Esac_mirmidon]

Strange, no CTD on my side.

 

Same mission. Starting the engine and pressing the brakes with full RPM and throttle to 40 until the engine died.

 

No crash.

[NineLine]

Same, can't reproduce.

[FA_Crazy-Canuck]

I’m not sure what that has to do with anything anyway since the crashes started right after the latest build.

 

Shortly after the last build new drivers came out for Nvidia cards. There are some who have found by turning off the over clock the crashes have subsided. We are dealing with hardware and software and any number of issues are at play. Documenting all issues goes to make for a better simulation.

[Bun]

Strange, no CTD on my side.

 

Same mission. Starting the engine and pressing the brakes with full RPM and throttle to 40 until the engine died.

 

No crash.

 

 

Thanks guys - just finished a hour long flight in the P-51 in Nevada with no problems. Before I posted the bug report I tried the same mission with the same result two other times and that along with the Huey CTD during damage made me think it might be related. Later after shutting down the computer for a meal I tried the mission again and killed the engine twice without a CTD. Once braking in place while firewalling and the other screaming down the taxiway and getting some altitude before the engine shut down. Both times the mission continued without a problem. The third time I cranked the stupid up a notch and took off firewalling and hung from the prop for ten minutes. That time the engine didn't shut down probably warmed up enough while taxiing - flew around with the nose up until grew bored with this new way of flying and decided to land. Got a CTD on final when I was thirty seconds from touchdown.

 

 

 

No mods, no overclocking except a 4.2 to 4.5 bump of the CPU, single player only...

Had the 2080Ti since 19 Dec - ran fine in 2.5.3 - updated to 2.5.4 two days ago - runs cool 50C

 

 

 

Just another data point - love the new cockpit for the P-51 by the way

 

:lol:

[JagHond]

Good morning, Gentlemen.

 

Only since the last 2.5.4 'open beta' update, I'm experiencing a weird systematical issue: after flown a mission of any kind, SP or MP doesn't matter, when attempting to exit from the sim DCS crashes.

 

I've already tried to fix it by repairing my installation several times, but without results.

I have a I9 machine equipped with Windows 10 Pro (64 bit).

 

Hope only that. if there is something wrong, will be fixed soon, even in the very next update.

 

With best regards.

[Goa]

I am also experiecing CTD witouth even a warning or nothing, DCS just crash and closes , no log is generated.

 

 

Alreadry run clean and repair, removed al logs etc etc.

 

 

It can happend after 10 minutes, 20, 1 hour , it depends, there is no advice at all, dcs.exe just close itself and I am back to deksstop.

[diditopgun]

I am also experiecing CTD witouth even a warning or nothing, DCS just crash and closes , no log is generated.

 

 

Alreadry run clean and repair, removed al logs etc etc.

 

 

It can happend after 10 minutes, 20, 1 hour , it depends, there is no advice at all, dcs.exe just close itself and I am back to deksstop.

 

Did you crash on Caucasus map ?

 

I come from a 2H flight on 104th Phoenix server, no crash. I had delete fx0 and metashader2 but can't say if it's related, or map related, or... or… or… :dunno:

[Donny]

Good morning all

 

Thought I would add my log to see if I can get some tips on getting around the crashing.

 

What I have done so far

 

I have gone through and removed all the mods I know of

I have removed all my skins that I know of

I am still running SRS

I am still running Viacom

I have run a clean

I have run a repair

I am flying in VR with Oculus

Drivers are up to date (was happening prior to and after a driver update)

I don't even know how to OC my GPU so...

 

Crash happens when logging into any MP server. The attached log was from logging into the AEF Caucus Server. Got as far as the window prior picking a slot, games freezes then crashes to the desktop.

 

Happily take any advice.

 

Cheers Donny

Logs.zip

Edited December 29, 2018 by Donny

[diditopgun]

Hi ! No new good news…

 

I edited Wags today Hornet mission on PG map to play it in MP. While switching external views during test, DCS CTD without warning message nor track file.

 

I tried a second time without any mod to be sure. DCS crash the same way.

 

I played the original mission without editing and no mod. At the end of the fight while switching external views, DCS CTD without warning message nor track file. (Log attached)

 

Symptomatic since last patch and it crash only on PG map for me, Caucasus is fine I did many flight on it (MP or SP) without problems.

 

My pagefile is on and managed by system on my both SSD.

Fx0 and metasher2 had been deleted.

Last Nvidia driver.

dcsLog.zip

[NineLine]

Just flew the mission, tried to do what you said you did and I had no issues.

 

Do you have any mods, reshader or overclocking?

 

Hi ! No new good news…

 

I edited Wags today Hornet mission on PG map to play it in MP. While switching external views during test, DCS CTD without warning message nor track file.

 

I tried a second time without any mod to be sure. DCS crash the same way.

 

I played the original mission without editing and no mod. At the end of the fight while switching external views, DCS CTD without warning message nor track file. (Log attached)

 

Symptomatic since last patch and it crash only on PG map for me, Caucasus is fine I did many flight on it (MP or SP) without problems.

 

My pagefile is on and managed by system on my both SSD.

Fx0 and metasher2 had been deleted.

Last Nvidia driver.

[diditopgun]

I update what I said, I just crash right now on Caucasus… first time. I was fast cycling external view. XD

 

No overclock, crash with or without mod, I have Reshade yes (please don't tell me it's because of it, I can't play without…)

[diditopgun]

Ok, I uninstalled Reshade to test.

 

On my Caucasus mission I did not crash this time by cycling quickly external view.

So I did test on PG mission, cycling quickly external view, and… it crash !

 

So it is not Reshade.

[diditopgun]

Hi !

 

For information, in addition to reports here and my mates, I asked other online french squadron to know if they experience too the same crash issue. And yes they do !

So it's a widespread issue.

 

Does ED is actively investigating this ? Could we have a status about it please ?

 

Thanks.

[NineLine]

Hi !

 

For information, in addition to reports here and my mates, I asked other online french squadron to know if they experience too the same crash issue. And yes they do !

So it's a widespread issue.

 

Does ED is actively investigating this ? Could we have a status about it please ?

 

Thanks.

 

We are trying to reproduce, but unable to. Did you include your crash logs from your PG map crash?

[diditopgun]

Arf… :(

 

Yes I included my dcs.log from PG crash posts #33 #35 #44 #66 of this topic.

[NineLine]

But this is supposedly a new crash after you cleaned out mods, so I would need new logs please.

[diditopgun]

I just come back from a new test procedure to reproduce the crash quickly.

 

First I cleaned my "saved game" folder except graphic options and input, and then did a repair of my DCS. No mods installed for the tests.

 

My procedure is to create a new mission in ME, don't edit anything, only go clic on fly mission.

Then I cycle the F11 view quickly to overload terrain loading and make the game CTD.

 

It crashed as intended several times without crash report message.

 

Then I saw that a Nvidia graphic driver update is available. I decided to update it, but by using the fresh full install option to have something fresh and clean about it.

 

Then I started a new series of 8 tests with the same F11 view procedure as before. That on both Persian Gulf map (PG) and Caucasus map (CC).

CR=crash report message and log+track+crash+dxdiag+dmp files

CTD=crash to desktop

 

#1 PG -> CR -> CTD -> PG1.dcs.log-20190115-174603.zip

 

#2 PG -> No CR only dcs.log -> PG.dcs.log.zip

 

#3 PG -> CR at mission loading… -> CTD -> PG2.dcs.log-20190115-175442.zip

 

#4 PG -> CR -> CTD -> PG3.dcs.log-20190115-175943.zip

 

#5 CC -> CTD -> No CR only dcs.log

 

#6 CC -> CTD -> No CR only dcs.log -> CC1.dcs.log.zip

 

#7 CC -> CTD -> No CR only dcs.log

 

#8 CC -> CTD -> No CR only dcs.log -> CC2.dcs.log.zip

 

To make PG crash it's easy, only need a quick F11 cycling because terrain loading is heavy.

To make CC crash it's harder, I have to spam very quickly F11 or F11+F10 because terrain loading is far more light than PG.

 

So I think it looks like something related with memory loading during the flight, and at some point reach a maximum for an unknown reason and make the game crash. Or something like that.

 

What is sure, is that I got only few CTD on Caucasus because the map is lighter (last weekend, 8 MP flights with a friend, only one crash). Persian Gulf map is too heavy and crash rate is high so I haven't played on it since last patch.

 

I hope it can help. If you have more test suggestions, I'm open.

PG1.dcs.log-20190115-174603.zip

PG2.dcs.log-20190115-175442.zip

PG3.dcs.log-20190115-175943.zip

PG.dcs.log.zip

CC1.dcs.log.zip

CC2.dcs.log.zip

Edited January 15, 2019 by diditopgun

[Mustang]

diditopgun I see in one of your previous posts that you mention you have system managed pagefile set, this method is prone to mishandling resources with DCS and is not recommended, please try setting a fixed custom pagefile as per the info in this thread

 

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

 

I too have 32gb of system RAM and with a 16384 -16384 pagefile on my SSD I can fly in the most heaviest of missions in any map for many hours at a time, a few nights ago I flew for close to 8 hours in one session and could have even gone on for even longer.

Edited January 15, 2019 by Mustang

[diditopgun]

Ok I will try it.

 

But I had no issue before this patch since I built up my new computer last summer. Maybe pagefile can help but something happened between 2.5.3 and 2.3.4.