Jump to content
Sign in to follow this  
RaptyrOne

FSX crashes AFTER it is closed

Recommended Posts

Hey all,I'm picking up an odd but frustrating problem. FSX is fine and appears to close fine when I exit. There is no CTD while flying. However when I check the performance reliability in Windows, it shows the the app crashed at the time I closed/exited the sim. No error message ever comes up though. It is always the same timestamp and fault module. The following info is provided:Problem signatureProblem Event Name: APPCRASHApplication Name: fsx.exeApplication Version: 10.0.61637.0Application Timestamp: 46fadb14Fault Module Name: ai_player.dllFault Module Version: 10.0.61637.0Fault Module Timestamp: 46fadb57Exception Code: c0000005Exception Offset: 00037489OS Version: 6.1.7600.2.0.0.256.48Locale ID: 7177Additional Information 1: 0a9eAdditional Information 2: 0a9e372d3b4ad19135b953a78882e789Additional Information 3: 0a9eAdditional Information 4: 0a9e372d3b4ad19135b953a78882e789The only thing I can think has changed and caused this is my installing FS Labs Concorde X (incl.SP2). Is it possible that this has caused the problem to arise?My system specs are: Win 7 64bit, 6GB RAM, Core i7 920, GTX295 on Asusm M/B P6TAny ideas appreciated before I try uninstall Concorde X...


GregH

System Spec: Core i7 6700K @ 4,7GHz; GTX980Ti, 32GB DDR4 3200; WD Black NVMe; Samsung EVO850 SSD; CH Products Yoke, Pedals & Quad; Airbus Side Stick, TrackIR; 1440p

Share this post


Link to post
Share on other sites
Hey all,I'm picking up an odd but frustrating problem. FSX is fine and appears to close fine when I exit. There is no CTD while flying. However when I check the performance reliability in Windows, it shows the the app crashed at the time I closed/exited the sim. No error message ever comes up though. It is always the same timestamp and fault module. The following info is provided:Problem signatureProblem Event Name:    APPCRASHApplication Name:    fsx.exeApplication Version:    10.0.61637.0Application Timestamp:    46fadb14Fault Module Name:    ai_player.dllFault Module Version:    10.0.61637.0Fault Module Timestamp:    46fadb57Exception Code:    c0000005Exception Offset:    00037489OS Version:    6.1.7600.2.0.0.256.48Locale ID:    7177Additional Information 1:    0a9eAdditional Information 2:    0a9e372d3b4ad19135b953a78882e789Additional Information 3:    0a9eAdditional Information 4:    0a9e372d3b4ad19135b953a78882e789The only thing I can think has changed and caused this is my installing FS Labs Concorde X (incl.SP2). Is it possible that this has caused the problem to arise?My system specs are: Win 7 64bit, 6GB RAM, Core i7 920, GTX295 on Asusm M/B P6TAny ideas appreciated before I try uninstall Concorde X...
I get the crash after it closes as well ....

Share this post


Link to post
Share on other sites

The only thing I can think of that has changed recently was to install a legally downloaded Concorde X. So I have uninstalled this and also deleted the Civa folder (inertial navigation guages for the Concorde) that it appeared to install in the FSX root folder (and not uninstall). I also noticed that alongside my fsx.cfg was a pre_concorde fsx.cfg. This must have been created by the Concorde X installer, so I renamed this as the active fsx.cfg.Touch wood, the problem has not appeared again. So perhaps the Concorde X has some "issues".The logical explanation would be that when FSX is closed by the user, another "plug in" to FSX, be it an add on aircraft, scenery, AI, weather etc is not shutting down quickly enough resulting in such a "crash". Just my theory.


GregH

System Spec: Core i7 6700K @ 4,7GHz; GTX980Ti, 32GB DDR4 3200; WD Black NVMe; Samsung EVO850 SSD; CH Products Yoke, Pedals & Quad; Airbus Side Stick, TrackIR; 1440p

Share this post


Link to post
Share on other sites
Hey all,I'm picking up an odd but frustrating problem. FSX is fine and appears to close fine when I exit. There is no CTD while flying. However when I check the performance reliability in Windows, it shows the the app crashed at the time I closed/exited the sim. No error message ever comes up though. It is always the same timestamp and fault module. The following info is provided:Problem signatureProblem Event Name: APPCRASHApplication Name: fsx.exeApplication Version: 10.0.61637.0Application Timestamp: 46fadb14Fault Module Name: ai_player.dllFault Module Version: 10.0.61637.0Fault Module Timestamp: 46fadb57Exception Code: c0000005Exception Offset: 00037489OS Version: 6.1.7600.2.0.0.256.48Locale ID: 7177Additional Information 1: 0a9eAdditional Information 2: 0a9e372d3b4ad19135b953a78882e789Additional Information 3: 0a9eAdditional Information 4: 0a9e372d3b4ad19135b953a78882e789The only thing I can think has changed and caused this is my installing FS Labs Concorde X (incl.SP2). Is it possible that this has caused the problem to arise?My system specs are: Win 7 64bit, 6GB RAM, Core i7 920, GTX295 on Asusm M/B P6TAny ideas appreciated before I try uninstall Concorde X...
Do you use fsinn?

 

as.jpg

Seinfeld Quote of the Month:

"Course, it would have to be someone who hasn't heard the story before. Someone who is unencumbered by any emotional attachment. Someone whose heart is so dark, it cannot be swayed by pity, compassion, or human emotion of any kind"

Share this post


Link to post
Share on other sites

No, not using FSInn - the only add-on's I have are Traffic X and a few aircraft add-on's - PMDG 744X & J41, Aerosoft Twin Otter. Also a few of Aerosofts sceneries - Maldives, Lukla, Lord Howe, Tahiti and many add-on sceneries for South Africa and it's airports.This is offline flying (although my PC is connected to the internet all the time when the PC is on).


GregH

System Spec: Core i7 6700K @ 4,7GHz; GTX980Ti, 32GB DDR4 3200; WD Black NVMe; Samsung EVO850 SSD; CH Products Yoke, Pedals & Quad; Airbus Side Stick, TrackIR; 1440p

Share this post


Link to post
Share on other sites

Ok, I was having the same issue but it related to fsinn/fscopilot, it was annoying to say the least.


 

as.jpg

Seinfeld Quote of the Month:

"Course, it would have to be someone who hasn't heard the story before. Someone who is unencumbered by any emotional attachment. Someone whose heart is so dark, it cannot be swayed by pity, compassion, or human emotion of any kind"

Share this post


Link to post
Share on other sites
Guest firehawk44
Hey all,I'm picking up an odd but frustrating problem. FSX is fine and appears to close fine when I exit. There is no CTD while flying. However when I check the performance reliability in Windows, it shows the the app crashed at the time I closed/exited the sim. No error message ever comes up though. It is always the same timestamp and fault module. The following info is provided:Problem signatureProblem Event Name: APPCRASHApplication Name: fsx.exeApplication Version: 10.0.61637.0Application Timestamp: 46fadb14Fault Module Name: ai_player.dllFault Module Version: 10.0.61637.0Fault Module Timestamp: 46fadb57Exception Code: c0000005Exception Offset: 00037489OS Version: 6.1.7600.2.0.0.256.48Locale ID: 7177Additional Information 1: 0a9eAdditional Information 2: 0a9e372d3b4ad19135b953a78882e789Additional Information 3: 0a9eAdditional Information 4: 0a9e372d3b4ad19135b953a78882e789The only thing I can think has changed and caused this is my installing FS Labs Concorde X (incl.SP2). Is it possible that this has caused the problem to arise?My system specs are: Win 7 64bit, 6GB RAM, Core i7 920, GTX295 on Asusm M/B P6TAny ideas appreciated before I try uninstall Concorde X...
The same error you are getting shows up in my Event Viewer from time-to-time. It does not cause a crash but the event viewer states it did. I am able to exit FSX w/o problems but I did see several references to this .dll when checking out some of the errors in my Event Viewer. If you have the FTX PNW scenery installed, they have identified the ADE_FTX_PNW_KSEA_Seattle-Tacoma_Intl.bgl as the file triggering the ai-player.dll crashes when exiting FSX for some. They explain this in the read_me that came with the PNW patch 002. They are trying to determine the actual cause. That's all I know. I'm not too concerned about it as it hasn't affected my enjoyment of the PNW scenery or FSX. Hope this helps.Best regards,Jim

Share this post


Link to post
Share on other sites
The same error you are getting shows up in my Event Viewer from time-to-time.  It does not cause a crash but the event viewer states it did.  I am able to exit FSX w/o problems but I did see several references to this .dll when checking out some of the errors in my Event Viewer.  If you have the FTX PNW scenery installed, they have identified the ADE_FTX_PNW_KSEA_Seattle-Tacoma_Intl.bgl as the file triggering the ai-player.dll crashes when exiting FSX for some.  They explain this in the read_me that came with the PNW patch 002.  They are trying to determine the actual cause.  That's all I know.  I'm not too concerned about it as it hasn't affected my enjoyment of the PNW scenery or FSX.  Hope this helps.Best regards,Jim
now that I think about it .. i do believe this problem started for me after I installed FTX PNW

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    53%
    $13,405.00 of $25,000.00 Donate Now
×
×
  • Create New...