Thanks Umberto, also thanks to Lockheed Martin (assuming they are following this) for agreeing to become involved.
Ran FSDT Live Update (bglmanx64.dll updated to v4.5.0.3))
Same Prepar3D v4.2 Add-on configuration as before (
ALL DISABLED with exception of FSDT Addon Manager).
(1)
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes -> NO Crash
Exit (
from fully loaded Prepar3D Default Scenario) -> Yes ->
CRASHLog Name: Application
Source: Application Error
Date: 25/05/2018 13:48: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: 0x11a0
Faulting application start time: 0x01d3f4263b2b5846
Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v4\api.dll
Report Id: f0699c02-6019-11e8-a0a9-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-25T12:48:36.000000000Z" />
<EventRecordID>235144</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>11a0</Data>
<Data>01d3f4263b2b5846</Data>
<Data>D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
<Data>D:\Lockheed Martin\Prepar3D v4\api.dll</Data>
<Data>f0699c02-6019-11e8-a0a9-40e230989421</Data>
</EventData>
</Event>
------------------------------------------------------------------------
Log Name: Application
Source: Windows Error Reporting
Date: 25/05/2018 13:49:45
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Prometheus
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Prepar3D.exe
P2: 4.2.21.24048
P3: 5a7c832c
P4: api.dll
P5: 4.2.21.24048
P6: 5a7c83e1
P7: c0000005
P8: 0000000000015611
P9:
P10:
Attached files: (Also see foot of this post)
These files may be available here:
C:\Users\Cruachan\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_3eda97622fa776e55c7d333f385aa57d58aa1ec_0afb5bf4
Analysis symbol:
Rechecking for solution: 0
Report Id: f0699c02-6019-11e8-a0a9-40e230989421
Report Status: 0
Event Xml:
<Event xmlns="
http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-05-25T12:49:45.000000000Z" />
<EventRecordID>235146</EventRecordID>
<Channel>Application</Channel>
<Computer>Prometheus</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<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>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>C:\Users\Cruachan\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_3eda97622fa776e55c7d333f385aa57d58aa1ec_0afb5bf4</Data>
<Data>
</Data>
<Data>0</Data>
<Data>f0699c02-6019-11e8-a0a9-40e230989421</Data>
<Data>0</Data>
</EventData>
</Event>
SYSTEM RESTART(2)
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes ->
CRASHExit (
from fully loaded Prepar3D Default Scenario) -> Yes -> NO Crash
(3)
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes ->
CRASHExit (
from fully loaded Prepar3D Default Scenario) -> Yes ->
CRASH(4)
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes ->
CRASHExit (
from fully loaded Prepar3D Default Scenario) -> Yes -> NO Crash
(5)
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes ->
CRASHExit (
from fully loaded Prepar3D Default Scenario) -> Yes ->
CRASHRESTORED previous bglmanx.dll (v4.5.0.2 (23/05/2018 20:27))
SYSTEM RESTART(6)
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes ->
CRASHExit (
from fully loaded Prepar3D Default Scenario) -> Yes -> NO Crash
(7)
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes ->
CRASHExit (
from fully loaded Prepar3D Default Scenario) -> Yes ->
CRASH[8]
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes -> NO Crash
Exit (
from fully loaded Prepar3D Default Scenario) -> Yes ->
CRASH-----------------------------------------------------------------------
(9)
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes -> NO Crash
Exit (
from fully loaded Prepar3D Default Scenario) -> Yes -> NO Crash
-----------------------------------------------------------------------
(10)
EXIT RESULTS:Exit (
from Prepar3D Scenario screen) -> NO Crash
End Scenario -> Exit Prepar3D -> Yes -> NO Crash
Exit (
from fully loaded Prepar3D Default Scenario) -> Yes ->
CRASHDifficult for me to draw any definitive conclusions from these results other than the fact that the sim does not crash while exiting from the Prepar3D Scenario screen.
Regards,
Mike