Last weekend I have installed a new SSD m2 disk, re-installed W10 1803 and P3Dv4.3. Agfter having done several test flights I added more scenery ( just by adding them into the library as those scenery are pr scenery ).  I also have added Fs Global to the library. Both of those scenery have not changed. The pc has not been overclocked ( yet ).

Just got a CTD 5 minutes before landing after a flight from Amsterdam to Athens ( LGAV ). PR Addon is RWS Greece PR. It has always worked with my former install.

 

First a .NET runtime error :   Prepar3D.exe Framework-version 4.0.30319. The proces has been terminated by an unexpected expeption.  Code c000005 , adres 00007FFB118A1A43

Then 1 second later :Prepar3d.exe / 4.3.29.25520 / 5b2c3263 / terrain.dll / 4.3.29.25520 etc

 

Latest Nvidia driver. 2x 2080Ti in SLI , like before…

All suggestions are very welcome.

 

 

 

 

 

Terrain.dll (AVSIM CTD Guide):  Usually indicates high scenery/terrain settings, especially high Autogen settings.  Rebuild P3D.cfg by renaming to p3d.cfg.off.  Most of the time, this error just happens on a whim. 

The dotnet error indicates you probably have an addon or module that is not compatible with P3DV4.  Move all of the addon xml files in the Documents/Prepar3DV4 Addons to a temp directory.  See if the error continues to occur.  If so, then it might be a module in one of your dll.xml's that is causing the error.

Hi Jim,

I have read the CTD guide. At this moment I use less addons than before and the addons that I use are also the same as before. Never had a CTD .. 

The only difference is 8x SSAA instead of 4X SSAA , cloud shadows quality max instead of medium and cloud shadows DD max instead of High.

I put those settings higher as I am using 2x 1080Ti in SLI and with the lower settings both were taxed maximum 35% and now maximum 50%. Which should be not so bad ...

However , I will try again with the lower settings to see If it makes a difference.

Edited October 17, 20187 yr by GSalden

5 hours ago, GSalden said:

However , I will try again with the lower settings to see If it makes a difference.

If you rename/save your p3d.cfg, rebuild a new one, and then run the same scenario (you can change the settings on the first graphics page but I would leave the other pages alone as you are only testing to see if this makes a difference.  If it does fix the issue, then you should know there was something amiss in the p3d.cfg.  If the error continues, then I would be looking for something incompatible.  The terrain.dll error gives a hint something regarding your scenery is amiss.  Check the Lorby_Si Addon Manager and make sure all of your configs and xmls are encoded properly (think under Tools).  I think that if you have the latest Addon Manager, just saving the scenery fixes all encoding errors.  Dotnets are used by the developers to run the application/add-ons.  It could be a wrong dotnet being called but the more likely event is something incompatible.  The dotnet called in your error report is required for most applications in P3D.

Today the same flight went without issues...

Only changed the settings I mentioned above.

I will be removing my suggestions to fix errors in the AVSIM CTD Guide in the next update as they are only based on Google searches of all FS websites and were the fixes many found.  I have seen where suggestions like this do not work for everyone as everyone has a different configuration (for instance, very few use sli configs).  It was a good idea at the time but it is best for me to just show members how to investigate a crash.  That way it will be impossible for the guide to be wrong.  😂

Like I said though and in the guide, one of the things I found on Google was the fact the terrain.dll error will occur during a flight session but, after shutting down FSX/P3D and restarting or shutting down Windows and restarting, the error will no longer happen.