Greetings.

First CTD on descent to EPWA for 2 hrs flight at about FL200

Prepar3D.exe

4.0.28.21686

594a7255

ai_player.dll

4.0.28.21686

594a7254

c0000005

000000000004d0e9

2b4c

01d3310351dab2a3

E:\P3D\Prepar3D.exe

E:\P3D\ai_player.dll

e9938bb1-bed1-4c00-a156-0f7dc0719e49

--------------

Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: ai_player.dll, version: 4.0.28.21686, time stamp: 0x594a7254
Exception code: 0xc0000005
Fault offset: 0x000000000004d0e9
Faulting process id: 0x2b4c
Faulting application start time: 0x01d3310351dab2a3
Faulting application path: E:\P3D\Prepar3D.exe
Faulting module path: E:\P3D\ai_player.dll
Report Id: e9938bb1-bed1-4c00-a156-0f7dc0719e49
Faulting package full name: 
Faulting package-relative application ID: 

------------

I read in P3D forum that they have already see this CTD but cannot figure out what is causing it. 

Thx for looking. 

---------

ORBX, Aerosoft EPWA, PMDG NGX, AS2016/ASCA, vPilot. Aivlasoft EFB, Navigraph charts. 

Based on CTD guide it is related to AI and the module that controls AI (a commercial AI program or the default). I have UTLive. I have been using UTLive for several months and never had any CTD. Based on P3D forum the cause was identified and the fix is found but it will be available in the next v4 version. However they do not say what is the cause and referring to Microsoft related issue. 

I had same issue but have determined it is Navigraph Desktop Charts new edition... ran it twice crashed both times... looking for a solution too

On 9/19/2017 at 11:34 AM, skysurfer said:

Based on P3D forum the cause was identified and the fix is found but it will be available in the next v4 version. However they do not say what is the cause and referring to Microsoft related issue. 

They are saying that for about every issue being posted.  I have little confidence with them finding a fix.  Still, that would be great if they found a fix and it will be released in V4.1.  Making positive statements is the way to go nowadays even if you do not mean it.  I golf everyday and I occasionally have to tell the Superintendent of the course about some maintenance issues I saw (like greens have not been rolled or cut) and he'll tell me, "thought those were done already?  I told them this morning those greens need to be cut and rolled everyday before the first groups arrive.  I thought they would get there sooner.   I'll make sure they get it done tomorrow on time.  Thanks for letting me know!"  Then I say, "okay, Tony.  That's great.  Just wanted to let you know".  I go away happy and do not continue to press him to fix a problem I saw.  Being negative and telling someone it won't be done this week is the wrong answer.  Reading the P3D Forums lately, they are fixing everything as they know what the problem is and it will be in the next update.  Aren't you happy now knowing this problem will no longer be a problem next week?

Static AI, installed by an airport scenery program not yet compatible with P3DV4 could cause the problem too.