addon manager crash on exit p3d 4.2 **SOLVED**

[p3dx3]

For a week I have tried to find the solution to a crash on exit, prepar3d.cfg.txt is created and Windows Event Viewer says api.dll crash after I fly then exit

I removed the folder from the prepar3d addons in my docs "fsdreamteam addon manager"

p3d quits without crashing.

Updated using Live Update

putting the addon manager back in the addon folder, p3d says to activate, start a flight, quit, the api.dll crash is back

Windows 10 Professional and the latest big update installed. Current drivers for Nvidia video card.

Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c
Faulting module name: api.dll, version: 4.2.21.24048, time stamp: 0x5a7c83e1
Exception code: 0xc0000005
Fault offset: 0x0000000000015611
Faulting process id: 0x538
Faulting application start time: 0x01d3eafa98c82a0f
Faulting application path: C:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Lockheed Martin\Prepar3D v4\api.dll
Report Id: c096d707-1fff-4b68-9905-6a464aab563f
Faulting package full name:
Faulting package-relative application ID:

[virtuali]

We are aware of this, and are investigating it.

[Cruachan]

Hi,

Just to confirm that I too am experiencing the crash on exit from Prepar3D v4.2.21.24048 under Windows 7 Pro 64bit SP1.

This only happens while exiting from the fully loaded sim and not from the Prepar3D Scenario screen. Disabling the FSDreamTeam Addon Manager appears to 'resolve' the issue and P3D exits gracefully. I have only tested in the fully loaded default scenario situation.

Prior to the recent Couatl update this was never an issue and I've been using GSX Ground Services since 12/2017.

Event Viewer reports:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   Prepar3D.exe
  Application Version:   4.2.21.24048
  Application Timestamp:   5a7c832c
  Fault Module Name:   api.dll
  Fault Module Version:   4.2.21.24048
  Fault Module Timestamp:   5a7c83e1
  Exception Code:   c0000005
  Exception Offset:   0000000000015611
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:   2057
  Additional Information 1:   4df1
  Additional Information 2:   4df16727dc39edd0dd79a54706d266f6
  Additional Information 3:   e7c7
  Additional Information 4:   e7c773fff755952d612832c9c2577e0b

Regards,
Mike

[virtuali]

The problem is now fixed in the latest Live Update we released today.

[Cruachan]

The problem is not fixed in the latest Live Update we released today.

Hi Umberto,

This topic has been marked as **SOLVED** and yet you appear to be stating that the problem is not fixed? Please forgive me for feeling a little confused. Perhaps best if I simply go ahead and apply the latest update and find out for myself.

Thanks.

Regards,
Mike

[p3dx3]

The problem is not fixed in the latest Live Update we released today.

Hi Umberto,

This topic has been marked as **SOLVED** and yet you appear to be stating that the problem is not fixed? Please forgive me for feeling a little confused. Perhaps best if I simply go ahead and apply the latest update and find out for myself.

Thanks.

Regards,
Mike

he could mean it is fixed, and run the live update as administrator to update

[Cruachan]

Just checked and, sadly, the problem persists: Exit the sim via End Scenario and....

Log Name:      Application
Source:        Application Error
Date:          22/05/2018 15:47:31
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Prometheus
Description:
Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c
Faulting module name: api.dll, version: 4.2.21.24048, time stamp: 0x5a7c83e1
Exception code: 0xc0000005
Fault offset: 0x0000000000015614
Faulting process id: 0x276c
Faulting application start time: 0x01d3f1db4e07472c
Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v4\api.dll
Report Id: 0dc49dd0-5dcf-11e8-90ed-40e230989421
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-05-22T14:47:31.000000000Z" />
    <EventRecordID>234398</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Prometheus</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.2.21.24048</Data>
    <Data>5a7c832c</Data>
    <Data>api.dll</Data>
    <Data>4.2.21.24048</Data>
    <Data>5a7c83e1</Data>
    <Data>c0000005</Data>
    <Data>0000000000015614</Data>
    <Data>276c</Data>
    <Data>01d3f1db4e07472c</Data>
    <Data>D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>D:\Lockheed Martin\Prepar3D v4\api.dll</Data>
    <Data>0dc49dd0-5dcf-11e8-90ed-40e230989421</Data>
  </EventData>
</Event>

I'll try running the Live Update again as Administrator although, strictly speaking, that should not be necessary.

Mike

[Cruachan]

Ran the FSDT Live Update as Administrator:

Hmm, that worked....once!

The sim crashed on exit with the next 2 attempts. Each time after about 30secs which seems to be the 'normal' behaviour. Same error reported in the Event Viewer.

I performed a System Restart and tried again (Default Flight and via End Scenario) - First time successful, second crashed, third successful, fourth crashed.

The next 3 exit attempts were straightforward Exits (not involving the End Scenario option) and 2 were successful with no reported errors and the 3rd crashed:

Log Name:      Application
Source:        Application Error
Date:          22/05/2018 16:42:36
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Prometheus
Description:
Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c
Faulting module name: api.dll, version: 4.2.21.24048, time stamp: 0x5a7c83e1
Exception code: 0xc0000005
Fault offset: 0x0000000000015611
Faulting process id: 0x19f0
Faulting application start time: 0x01d3f1e2eca6a631
Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v4\api.dll
Report Id: bfcc1364-5dd6-11e8-8450-40e230989421
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-05-22T15:42:36.000000000Z" />
    <EventRecordID>234471</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Prometheus</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.2.21.24048</Data>
    <Data>5a7c832c</Data>
    <Data>api.dll</Data>
    <Data>4.2.21.24048</Data>
    <Data>5a7c83e1</Data>
    <Data>c0000005</Data>
    <Data>0000000000015611</Data>
    <Data>19f0</Data>
    <Data>01d3f1e2eca6a631</Data>
    <Data>D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>D:\Lockheed Martin\Prepar3D v4\api.dll</Data>
    <Data>bfcc1364-5dd6-11e8-8450-40e230989421</Data>
  </EventData>
</Event>

So, sorry to say that with the FSDT Addon Manager/GSX enabled sim exit behaviour still remains flaky.

Hope this has been of some help, Umberto.

Regards,
Mike

[virtuali]

I'm sorry, but I cannot reproduce this.

- I could see the API.DLL crash on exit 100% of the times with the old version

- I have 0% crashes with the current one so, it's 100% clearly reproducible.

The only file that affects this is bglmanx.dll, under the Addon Manager folder. To be sure you have the fixed version, check it's version 4.5.0.2 and its digital signature has a timestamp of May 22th 2018.

[virtuali]

This topic has been marked as **SOLVED** and yet you appear to be stating that the problem is not fixed?

The browser auto-correct changed my original sentence "it's now fixed", into "it's not fixed". Now, even the sentence is fixed...

[Cruachan]

I'm sorry, but I cannot reproduce this.

The only file that affects this is bglmanx.dll, under the Addon Manager folder. To be sure you have the fixed version, check it's version 4.5.0.2 and its digital signature has a timestamp of May 22th 2018.

Hi Umberto,

Looks like I do have the latest 'fixed' file:



Regards,
Mike

[virtuali]

Looks like I do have the latest 'fixed' file:

Then I'm sorry, but I can only repeat and confirm the crash cannot happen with that version. Are you SURE you are looking at an event which was generated after installing the latest version ?

[Cruachan]

Looks like I do have the latest 'fixed' file:

Then I'm sorry, but I can only repeat and confirm the crash cannot happen with that version. Are you SURE you are looking at an event which was generated after installing the latest version ?

Hi Umberto,

I do admire your confidence. However, there has to be a reason why my experience remains at variance with your conviction. Normally having such responses I would be suspecting something else was at play here. Unfortunately this would not explain why the FSDT Addon Manager/ Couatl / GSX was not hindering Prepar3D v4.2 from exiting gracefully prior to that update. I think at least we can agree that something changed with that update. You believe that it has been fixed and this is supported by your testing procedures. I acknowledge and, indeed, accept that to be the case.

Has the original main installer been updated? If so, then perhaps the logical next step would be for me to start again by obtaining a fresh download of the product from my account and then perform a clean reinstall.

I’ll report back later.

Thanks for your input.

Regards,
Mike

[virtuali]

I do admire your confidence. However, there has to be a reason why my experience remains at variance with your conviction. Normally having such responses I would be suspecting something else was at play here.

That's likely.

API.DLL is related to Simconnect but, interestingly enough, the bug we FIXED in our program didn't had anything to do with Simconnect. It was purely something of an internal communication between the Addon Manager and Couatl, which use their own communication channel. It's also possibly related to the new PDK.

So, it's possible the issue happens also in combination with other addons, which also use the either  Simconnect or the PDK.

Unfortunately this would not explain why the FSDT Addon Manager/ Couatl / GSX was not hindering Prepar3D v4.2 from exiting gracefully prior to that update. I think at least we can agree that something changed with that update.

In order to know what changed, we should know which exact release you had before the update.

You believe that it has been fixed and this is supported by your testing procedures. I acknowledge and, indeed, accept that to be the case.

As I've said in another post:

- When this issue has been reported, I checked it, and verified I had a crash on API.DLL on exit 100% of the times.

- After the update I don't crashes anymore.

Has the original main installer been updated? If so, then perhaps the logical next step would be for me to start again by obtaining a fresh download of the product from my account and then perform a clean reinstall.

I doubt it will make any difference, because the installer would download the same file as the updater. In fact, the installer *starts* the Live Updater, same as if you launched it manually.

A more meaningful test would be disabling all the other 3rd party modules, EXCEPT the Addon Manager, and see if there's still a crash.

[virtuali]

Mabye I found something:

Are you running P3D4 As Administrator, which is NOT how it's installed by default ? I tried it and yes, I DO have the API.DLL crash, but only by changing the Compatibility settings to run As Admin.

That explains why I couldn't replicate it before: I was running the sim as installed by default by LM. Now that I can sill replicate it, there might be a chance of really fixing it.