CTD P3Dv4.5 A2A Bonanza...

[Richard Portier]

Hi,

With the A2A Bonanza, I have the following problem: P3Dv4.5 CTD with a Kernelbase error. The crash always appears at the same place (each time the number of engine revolutions reaches +- 2600 rpm, see video.
If I do not load FSUIPC, there is no more error or CTD, everything works normally.

I would like to point out that I do not use FSUIPC in any way with this aircraft (no Bonanza reference in the FSUIPC5.ini) .

Video: https://www.youtube.com/watch?v=E3KXkBnRqvo&feature=youtu.be

Windows Event:

Fault bucket 3345951355, type 373162296
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.5.11.29713
P3: 5ca56c53
P4: KERNELBASE.dll
P5: 6.1.7601.24408
P6: 5c92f34f
P7: c0020001
P8: 000000000000be0d
P9:
P10:

Attached files:
C:\Users\Portier\AppData\Local\Temp\WER435F.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Portier\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_8235a6d19fa561de21e46c9e56b64d41111c155_095a596e

Analysis symbol:
Rechecking for solution: 0
Report Id: c00fa36b-6d20-11e9-9ae4-240a640748f4
Report Status: 0

FSUIPC5.log (registered):

********* FSUIPC5, Version 5.151 (21st February 2019) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FEBFA90000
Windows 7 Ultimate 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1)
Prepar3D.exe version = 4.5.11.29713
Reading options from "E:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="Richard Portier"
User Addr="bifrancois@hotmail.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 02/05/2019 23:19:46
        0 FLT path = "C:\Users\Portier\Documents\Prepar3D v4 Files\"
        0 Using DialogMode
       15 FS path = "E:\Program Files\Lockheed Martin\Prepar3D v4\"
      125 ---------------------- Joystick Device Scan -----------------------
      125 Product= Joystick - HOTAS Warthog
      125    Manufacturer= Thustmaster
      125    Vendor=044F, Product=0402 (Version 1.0)
      125    GUIDs returned for product: VID_044F&PID_0402:
      125       GUID= {14311C80-FCF8-11E5-8001-444553540000}
      125       Details: Btns=19, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z0
      125 Product= Throttle - HOTAS Warthog
      140    Manufacturer= Thrustmaster
      140    Vendor=044F, Product=0404 (Version 1.0)
      140    GUIDs returned for product: VID_044F&PID_0404:
      140       GUID= {14311C80-FCF8-11E5-8002-444553540000}
      140       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R16383,U1023,V0,X1023,Y1023,Z16383
      140 Product= Saitek Pro Flight Rudder Pedals
      140    Manufacturer= Saitek
      140    Vendor=06A3, Product=0763 (Version 1.0)
      140    GUIDs returned for product: VID_06A3&PID_0763:
      140       GUID= {13CE9E00-595F-11E3-8001-444553540000}
      140       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      140 Product= Saitek Pro Flight Yoke
      140    Manufacturer= Saitek
      140    Vendor=06A3, Product=0BAC (Version 3.3)
      140    GUIDs returned for product: VID_06A3&PID_0BAC:
      140       GUID= {A48ECF20-595D-11E3-8001-444553540000}
      140       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      140 -------------------------------------------------------------------
      156 Device acquired for use:
      156    Joystick ID = 0 (Registry okay)
      156    0=Joystick - HOTAS Warthog
      156    0.GUID={14311C80-FCF8-11E5-8001-444553540000}
      156 Device acquired for use:
      156    Joystick ID = 3 (Registry okay)
      156    3=Throttle - HOTAS Warthog
      156    3.GUID={14311C80-FCF8-11E5-8002-444553540000}
      156 Device acquired for use:
      156    Joystick ID = 1 (Registry okay)
      156    1=Saitek Pro Flight Rudder Pedals
      156    1.GUID={13CE9E00-595F-11E3-8001-444553540000}
      156 Device acquired for use:
      156    Joystick ID = 4 (Registry okay)
      156    4=Saitek Pro Flight Yoke
      156    4.GUID={A48ECF20-595D-11E3-8001-444553540000}
      156 -------------------------------------------------------------------
      187 LogOptions=00000000 00000001
      187 -------------------------------------------------------------------
      187 ### Traffic limited by user parameter to 50 aircraft
      187 SimConnect_Open succeeded: waiting to check version okay
      187 Opened separate AI Traffic client okay
      187 ### PDKmodeHelper callback registered
    87392 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.11.29713 (SimConnect: 4.5.0.0)
    87392 Initialising SimConnect data requests now
    87392 FSUIPC Menu entry added
    87392 ... Using Prepar3D with Academic License
    87407 C:\Users\Portier\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
    87407 E:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
   113413 E:\Prepar3D v4 Add-ons\A2A\SimObjects\Airplanes\A2A_Beechcraft_35_Bonanza\bonanza.air
   113428 ### The user object is 'A2A Beechcraft V35B Bonanza N41G'
   113428 ### Mode is NORMAL
   121306 ### Mode: PAUSE on
   192099 Loading Complete ...
   192162 ### Mode is NORMAL
   193332 Aircraft loaded: running normally now ...
   193379 User Aircraft ID 2 supplied, now being used
   193847 System time = 02/05/2019 23:23:00, Simulator time = 15:21:15 (20:21Z)
   193878 Aircraft="A2A Beechcraft V35B Bonanza N41G"
   200820 -------------------- Starting everything now ----------------------
   200867 LUA.0: beginning "E:\Program Files\Lockheed Martin\Prepar3D v4\Modules\ipcReady.lua"
   200882 ASN active function link set
   200882 Ready for ActiveSky WX radar with additional data
   200976 LUA.1: [START] *********************** STARTING LINDA ***********************
   200991 LUA.1: LINDA:: [START] Loading System Configuration files
   200991 LUA.1: LINDA:: *********************************************************************
   200991 LUA.1: LINDA:: [START] WARNING - All LUA logging switched off !!!
   201007 LUA.1: LINDA:: [START] Go to Setup LINDA to switch on (if required)
   201007 LUA.1: LINDA:: *********************************************************************
   201023 LUA.1: LINDA:: [START] System Configuration files loaded
   202068 Advanced Weather Interface Enabled
   202848 LUA.0: LINDA:: Offsets watching list cleared!
   209213 Weather Mode now = Theme

Thank you and Regards,
Richard

EDIT: Why are the last lines of my post crossed out?

[Pete Dowson]

40 minutes ago, Richard Portier said:

200976 LUA.1: [START] *********************** STARTING LINDA ***********************

Please try without LINDA running (rename ipcREADY.lua). LINDA may be using a driver which has a problem with your system.

If you then don't get the crash, seek help on LINDA support.

37 minutes ago, Richard Portier said:

Why are the last lines of my post crossed out?

I don't know. They are your lines.  Maybe the LINDA log line at 202848 contained some sequence which the display options here interpreted as "strikethrough". Check the original.

Pete

 

[Richard Portier]

36 minutes ago, Pete Dowson said:

Please try without LINDA running (rename ipcREADY.lua). LINDA may be using a driver which has a problem with your system.

If you then don't get the crash, seek help on LINDA support.

I don't know. They are your lines.  Maybe the LINDA log line at 202848 contained some sequence which the display options here interpreted as "strikethrough". Check the original.

Pete

 

Thank you Pete, it seems it was Linda (fingers crossed).

Strangely enough, I had the trial without Linda running, I still had the CTD. And then I proceeded as you told me, namely rename ipcREADY.lua. It seems there is a difference between the two methods, is that normal, knowing that I do not use the Bonanza via Linda?

Richard

[Pete Dowson]

11 hours ago, Richard Portier said:

Strangely enough, I had the trial without Linda running, I still had the CTD.

Maybe your ipcReady.lua runs other things?

You should really report the LINDA problem, with your crash info, to the LINDA folks.

Pete