Crash after new patch beta

Try and delete all the files in the bin folder except the DCS_updater.exe and do a repair...

Thanks but it did not solve the problem. :-(

Best regards Grippen7

Hi all,

Found the solution to bring the sim alive again.

Removed all mods and files with the errors. (ERROR SECURITYCONTROL)

I tought that the Mbb 339 was on my C: drive instead of my H: drive.

Skyhawk was installed in this directory: (removed it.)

c:\Users\ABC\Saved Games\DCS.openbeta\

Files removed from this directory:

h:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\

After this I performed a repair and now DCS is running again.

Thank for all your help and hope others could solve there problems too.

PS:

Merry christmas and a happy new year to all DCS staff and virtual pilots!

Best regards, Grippen7

2018-12-24 01:52:10.005 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/vnao/dcs_manifest.x86_64

2018-12-24 01:52:10.031 INFO SECURITYCONTROL: Loaded (mm) mods/tech/wwii units/dcs_module.dll.crypt

2018-12-24 01:52:10.031 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/dcs-gpu/dcs_manifest.x86_64

2018-12-24 01:52:10.031 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/main/dcs_manifest.x86_64

2018-12-24 01:52:10.191 ALERT SECURITYCONTROL: Manifest 'mods/aircraft/hawk/dcs_manifest.x86_64' is from a different build.

2018-12-24 01:52:10.235 ERROR SECURITYCONTROL: Failed to parse manifest: mods/aircraft/mb-339pan/dcs_manifest.x86_64

Same here lots of crashes after last patche

:mad::mad::mad::mad::mad::cry::cry::cry:

dcs.log-20181225-235838.zip

dcs.log-20181225-210504.zip

dcs.log-20181225-210510.zip

Yeah it definitely was the last patch. Was having a long steak off no crashes then immediately after three last patch, 2 friends and I are getting them like crazy. The event viewer has been showing edcore.dll, uh1h.dll as being the major culprits

Getting crashes as well, goes straight to desktop without even creating a proper crashlog.

All drivers are up to date.

Hi !

Same here. (Last Nvidia driver)

Last week I flew a MP mission (F-18, Persian Gulf) with a friend, created after wednesday 2.5.4 update. No problem.

Today, back from holidays, I take the same mission file, edit it to make some changes to have a similiar mission (farther target location with more SAM and night time). Crash to desktop after about 30min without any crash message, crash log or track. We try again and crash again after almost the same amount of time.

I try in SP and it crash too. I had some mods so I try with no mods and do many flight test (using temporal acceleration), same result: crash. No specific action done when it crash.

Crash time is not always the same, it depend what I do. It can be after about 30min (or more) if I take off and fly at mission start. But I can stay 1h waiting on catapult then take off and it crash later.

But if I do several flights with same flight path and parameters (altitude, throttle, etc...) it will crash approximately at the same time/location.

last dcs.log and mission file attached.

From windows Event Viewer (Windows Logs/Application):

Nom du journal :Application

Source : Application Error

Date : 27/12/2018 01:37:41

ID de l’événement :1000

Catégorie de la tâche : (100)

Niveau : Erreur

Mots clés : Classique

Utilisateur : N/A

Ordinateur : DESKTOP-07JQNT2

Description :

Nom de l’application défaillante DCS.exe, version : 2.5.4.25729, horodatage : 0x5c1a9459

Nom du module défaillant : ntdll.dll, version : 10.0.17763.194, horodatage : 0xe8b54827

Code d’exception : 0xc0000374

Décalage d’erreur : 0x00000000000faf49

ID du processus défaillant : 0x2b08

Heure de début de l’application défaillante : 0x01d49d7b92d3827e

Chemin d’accès de l’application défaillante : D:\Eagle Dynamics\DCS World\bin\DCS.exe

Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\ntdll.dll

ID de rapport : 53ec8a08-cbe0-4227-8077-21fbd6c8abbc

Nom complet du package défaillant :

ID de l’application relative au package défaillant :

XML de l’événement :

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2018-12-27T00:37:41.912108500Z" />

<EventRecordID>228</EventRecordID>

<Channel>Application</Channel>

<Computer>DESKTOP-07JQNT2</Computer>

<Security />

</System>

<EventData>

<Data>DCS.exe</Data>

<Data>2.5.4.25729</Data>

<Data>5c1a9459</Data>

<Data>ntdll.dll</Data>

<Data>10.0.17763.194</Data>

<Data>e8b54827</Data>

<Data>c0000374</Data>

<Data>00000000000faf49</Data>

<Data>2b08</Data>

<Data>01d49d7b92d3827e</Data>

<Data>D:\Eagle Dynamics\DCS World\bin\DCS.exe</Data>

<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>

<Data>53ec8a08-cbe0-4227-8077-21fbd6c8abbc</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

Nom du journal :Application

Source : Windows Error Reporting

Date : 27/12/2018 01:37:43

ID de l’événement :1001

Catégorie de la tâche :Aucun

Niveau : Information

Mots clés : Classique

Utilisateur : N/A

Ordinateur : DESKTOP-07JQNT2

Description :

Détecteur d'erreurs 2293996761087507587, type 4

Nom d’événement : APPCRASH

Réponse : Non disponible

ID de CAB : 0

 

Signature du problème :

P1 : DCS.exe

P2 : 2.5.4.25729

P3 : 5c1a9459

P4 : StackHash_f6de

P5 : 10.0.17763.194

P6 : e8b54827

P7 : c0000374

P8 : PCH_96_FROM_ntdll+0x00000000000A01B4

P9 :

P10 :

 

Fichiers joints :

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER90DD.tmp.dmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9236.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9256.tmp.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9264.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9265.tmp.txt

 

Ces fichiers sont peut-être disponibles ici :

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DCS.exe_deaece4692f7367f20e351fda2c0e7cf73fdd5_fea6d887_1b1b966b

 

Symbole d’analyse :

Nouvelle recherche de la solution : 0

ID de rapport : 53ec8a08-cbe0-4227-8077-21fbd6c8abbc

Statut du rapport : 268435456

Récipient avec hachage : 9347b501a12ed66f0fd5e9e66c847c83

GUID CAB :0

XML de l’événement :

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Windows Error Reporting" />

<EventID Qualifiers="0">1001</EventID>

<Level>4</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2018-12-27T00:37:43.449791000Z" />

<EventRecordID>229</EventRecordID>

<Channel>Application</Channel>

<Computer>DESKTOP-07JQNT2</Computer>

<Security />

</System>

<EventData>

<Data>2293996761087507587</Data>

<Data>4</Data>

<Data>APPCRASH</Data>

<Data>Non disponible</Data>

<Data>0</Data>

<Data>DCS.exe</Data>

<Data>2.5.4.25729</Data>

<Data>5c1a9459</Data>

<Data>StackHash_f6de</Data>

<Data>10.0.17763.194</Data>

<Data>e8b54827</Data>

<Data>c0000374</Data>

<Data>PCH_96_FROM_ntdll+0x00000000000A01B4</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER90DD.tmp.dmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9236.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9256.tmp.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9264.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9265.tmp.txt</Data>

<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DCS.exe_deaece4692f7367f20e351fda2c0e7cf73fdd5_fea6d887_1b1b966b</Data>

<Data>

</Data>

<Data>0</Data>

<Data>53ec8a08-cbe0-4227-8077-21fbd6c8abbc</Data>

<Data>268435456</Data>

<Data>9347b501a12ed66f0fd5e9e66c847c83</Data>

<Data>0</Data>

</EventData>

</Event>

Maybe I say something stupid but it looks like a kind of "memory leak". It load/leak until a point where it crash.

Havadarya Power Plant.miz

dcslog.zip

I had some mods so I try with no mods and do many flight test (using temporal acceleration), same result: crash. No specific action done when it crash.

;) with or without mod it crash. Log I gave you is with no mod.

EDIT:

I test again this morning with no mod and no Tacview (I had a doubt about it).

I took off and did my reference flight path test, no crash (Oh ! maybe tacview related ?). I took off again in the same flight session, same reference flight path test and… It crash… so it's not tacview related.

I attached the log (always no crash mention in the log, no track etc...)

dcsLog.zip

Did you try a Clean and then a Repair?

You can use the Skatezilla tool for that.

I am getting the same errors it seems. Any fix?

my crashes are multiplayer related. can't get into server anymore

I am flying F/A-18C, and my mission is attached in my post above, #33.

i dont think, that the current crashes so many different people experience with 2.5.4 are caused by any mods, missions, modules...i think its cause is something in the core engine...just an assumption, but reading through the different crash reports, i cant find any thing they have in common, except ver. 2.5.4.

I just come back from an other test always on the same mission.

This time in MP with my friend as host (last time I was the host) to see if he crash too or only me.

After 30/40min of flight my friend crash in the same way.

I attached his dcs.log.

I will create the same mission but on Caucasus map and we will fly it tonight to see if it could be Persian Gulf map related or not.

dcsLog.zip

Been flying now for 45 mins in your mission, no crash, do you have a single player track with the crash? You crash file doesnt have any track included. Were you doing anything specific when it crashed?

There is no track unfortunately, the game just disappear and send back to desktop.

I do nothing specific when it crash.

That's right.

During this MP flight it crashed just after we finished bombing (coincidence I think) but all other time MP or SP We/I were only cruising.

One I (or my friend) am hosting. But I don't think it's MP related because it crash in SP too.

I just come back from the "same" mission re-created on Caucasus map in MP with my friend. 01h05 of flight, no crash.

Thanks you ! :thumbup: