So I just got the following CTD. Cannot even remember ever having it before. Thing is, I don't run with any AI. Setting is off. Avsim CTD just mentions that it is related to AI which don't help me cause I don't use AI. Any ideas?

 

Log Name:      Application
Source:        Application Error
Date:          8/20/2018 12:56:21
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-S0ADUOJ
Description:
Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263
Faulting module name: ai_player.dll, version: 4.3.29.25520, time stamp: 0x5b2c3261
Exception code: 0xc0000005
Fault offset: 0x000000000004f179
Faulting process id: 0x15e0
Faulting application start time: 0x01d4388dd3cc492e
Faulting application path: C:\Prepar 3D\Prepar3D.exe
Faulting module path: C:\Prepar 3D\ai_player.dll
Report Id: c85d17a3-c059-4a88-a02b-99f2a478ae1b
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<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-08-20T16:56:21.517001800Z" />
    <EventRecordID>2975</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-S0ADUOJ</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.3.29.25520</Data>
    <Data>5b2c3263</Data>
    <Data>ai_player.dll</Data>
    <Data>4.3.29.25520</Data>
    <Data>5b2c3261</Data>
    <Data>c0000005</Data>
    <Data>000000000004f179</Data>
    <Data>15e0</Data>
    <Data>01d4388dd3cc492e</Data>
    <Data>C:\Prepar 3D\Prepar3D.exe</Data>
    <Data>C:\Prepar 3D\ai_player.dll</Data>
    <Data>c85d17a3-c059-4a88-a02b-99f2a478ae1b</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Doesn't FTX/Orbx have AI out of Friday Harbor?  Static AI too?

You can go through this debug process that Lockheed Martin techs came up with where I have not seen any solutions based on doing that or you can rename your dll.xml(s), scenery.cfg, and move the contents in Documents/Prepare3Dv4 Add-ons folder to a temporary folder (this is so your add-ons in the Lorby_Si Addon Organizer are removed; you can also go in the Addon Organizer and disable all of the add-ons by double-clicking until the text turns red), rename the P3D.cfg, restart P3D and see if this fixes the problem (of course it will as it is one of your add-ons that is causing the issue). I would then bring back all of the addon scenery and see if the problem reoccurs.  If so, it is a scenery.  If you have any Orbx scenery, disable that.  You also need to try to recall what you did recently or before the ai_player.dll error started showing up.  Did you just install a new scenery? 

Back some time ago, I always related the ai_player.dll error to high settings but the Internet said it was related to AI (by many so-called FSX experts) so I changed it in the CTD Guide.   In the next update of the CTD Guide, I plan on removing all of the probable causes and will post only known fixes.

It is important to note there is no known fix to the ai_player.dll.  I saw over in the P3D Forum where one of the techs sent someone to another thread about sound card issues and said that would fix it.  I'm still chuckling.  It is a frustrating error though as I have had the error on occasion and still I fix it by total luck.

Jim

How did you fix it? I know each system is different but it might you give me a few rabbit holes to look into. 

I lowered my settings but that was in FSX so I had to reduce the settings in the fsx.cfg and my NVidia Inspector.  It really was a long time ago I have seen this error and surprised others are getting this error in P3DV4.  I would start by disabling all of the addon scenery installed since recently.  Having gone through many crashes, I have spent many hours trouble-shooting the issue and think of some of the recommendations I have provided others which seemed like stupid suggestions.  I always look at what I recently did with my installation of P3D.  If I overclocked my system and the error started happening randomly, I would return the overclock to the default.  Most recently, I found these tweak utilities for GPU's (in my case, the ASUS TweakII), causes crashes with different faulting modules.  I return the settings to the default, and the crashes stop.  There are so many causes for errors depending on the system, it is mind-boggling.  I've seen a lot of fixes by making sure P3D starts up with admin privileges for ALL users.  That's the reason for the CTD guide.  It provides suggestions to investigate the cause of YOUR crash.  The probable causes and stuff are things I learned by searching the Internet and where others had fixed their problems.