DCS World/A-10 crashes after updating to 1.2.4.12913

[schmiefel]

Hi,

 

after applying the lastest update (via auto-update) I get a crash after a random time - mostly Windows (W7 64bit) concerns an error like this:

Problemsignatur:

Problemereignisname: APPCRASH

Anwendungsname: dcs.exe

Anwendungsversion: 1.2.4.12913

Anwendungszeitstempel: 519f6bcd

Fehlermodulname: d3dx9_43.dll

Fehlermodulversion: 9.29.952.3111

Fehlermodulzeitstempel: 4bf70b46

Ausnahmecode: c0000005

Ausnahmeoffset: 0000000000215d8e

Betriebsystemversion: 6.1.7601.2.1.0.256.48

Gebietsschema-ID: 1031

Zusatzinformation 1: c3b4

Zusatzinformation 2: c3b4539fba14d28db0cb1fe252ca9ad6

Zusatzinformation 3: 5b46

Zusatzinformation 4: 5b46e36d8cefde71c12115f882b12e78

I recently did also an update of the current nvidia driver from last stable up to version: 320.18 (installation was done with option 'new' - I never do only update the driver)

 

The strange thing ist that these crashes only happen when I play the A-10 module; playing the P-51 module everything is running rock solid for hours.

 

I didn't test the KA-50 BS2 so far, so I can't say if the crashes occur there, too.

 

As DCS was running pretty fine before the latest updates I am a little confused where that new crashes come from.

 

But before I start rollling back everything, maybe someone else has an idea, what could cause this new issue - maybe it belongs to the newest DCS World version or the newest Nvidia driver or a combination of both or it's something complete different.

 

I attached the latest DCS crash logs (Logs.zip) and my actual dxdiag (64bit) protocole - maybe its useful for the devs.

 

Every advise is welcome :book: - and sorry for my english

 

Many greetings from Germany (near EDDM)

Michael (mike_eddm aka schmiefel)

 

Edit: the autoupdate log states subversion .167:

00000.000 INFO : === MiniLog opened UTC 2013-05-29 23:50:34

00000.007 INFO : Current version: 1.2.4.12913.167

00000.007 INFO : Arch: x86_64

00000.007 INFO : Lang: DE

00000.007 INFO : Installed modules: A-10C,WORLD,KA-50bs1,P-51D,KA-50_video_EN,SU-25T_video_EN

00000.007 INFO : LAUNCH found 1 commands

00000.008 INFO : LAUNCH started "C:\Program Files\Eagle Dynamics\DCS World\bin/Launcher.exe"

00000.008 INFO : === MiniLog closed.

 

Compared to the DCS download section it should be subversion .186 ... was there something going wrong with the autoupdate or is it a problem that I have german versions of the DCS modules?

 

Edit2: today I got the same CTD with the P-51 module - and no one has an idea whether its the latest DCS World build, the new Nvidia driver or ... something else???

 

Edit3: after getting the same CTD within MS Flight I did a rollback to Nvidia driver v. 314.22 - but no luck: again after ca. 5 minutes of flighing with DCS World A-10 I got the same CTD again with an error in DX9 DLL:

Problemsignatur:

Problemereignisname: APPCRASH

Anwendungsname: dcs.exe

Anwendungsversion: 1.2.4.12913

Anwendungszeitstempel: 519f6bcd

Fehlermodulname: d3d9.dll

Fehlermodulversion: 6.1.7601.17514

Fehlermodulzeitstempel: 4ce7c5a4

Ausnahmecode: c0000005

Ausnahmeoffset: 0000000000005f54

Betriebsystemversion: 6.1.7601.2.1.0.256.48

Gebietsschema-ID: 1031

Zusatzinformation 1: 974b

Zusatzinformation 2: 974bbc37306336002676beb29976f6fd

Zusatzinformation 3: a73b

Zusatzinformation 4: a73b91df079656f189b534e0ae27a83d

 

I will continue with my research were this new CTD behavior could come from - as I am running FSX with high demanding add-ons (FTX ORBX, REX2 OD, PMDG NGX, ...) on DX9, too, and have no issues so far ...

 

Edit4: Just wanted to sum up what I did the last days: I just uninstalled Nvidia 314.22 and did a new install of the actual on (see above), then did a re-install of DX9 (runtime from June 2010) as I could not find how to do a complete uninstall and then do a totally new installation of directx ... at last I changed my ram XMP-Profile (from2 to 1) - and now all seems to run stable again... very strange and maybe a tricky combination of several incompatibilities but I am not sure what went wrong at all.

DxDiag.txt

Logs.zip

Edited June 1, 2013 by schmiefel
additional Info - CTD in P-51 too - maybe no Driver issue - last changes