Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Good Morning Pete,

Recently I added a new  motorised Throttle to my sim (complete with its own drivers) and subsequently removed it and replaced it with my original Bodnar/FSUIPC throttle. Since then I have been experiencing regular  (P3D stopped working) crashes. I can sometimes complete a short flight but not very often.

I can only assume that it was the uninstalling of the throttle software that led to the problems as P3D and Prosim 737 had been running perfectly beforehand.

Would you please have a look at the FSUIPC Log File from today in the hope that it might show something that you could guide me with.

Windows Event Viewer also produced 11 Error messages from the point of booting up the comp to the crash.

I am getting close to the point of a complete uninstall/reinstall but want to avoid that if at all possible.

Thanks,

William

********* FSUIPC4, Version 4.962 (8th February 2017) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 3.4.22.19868
Reading options from "E:\P3Dv3.1\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 10
Module base=5F3A0000
User Name="xxxxxxxxxxx"
User Addr="xxxxxxxxxxxxxxxx"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 15/02/2017 08:49:46
        0 FLT path = "C:\Users\William\Documents\Prepar3D v3 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 3.4.22.19868
        0             api.dll: 3.4.22.19868
        0        controls.dll: 3.4.22.19868
        0      fs-traffic.dll: 3.4.22.19868
        0             G3D.dll: 3.4.22.19868
        0        language.dll: 3.4.22.19868
        0            sim1.dll: 3.4.22.19868
        0        visualfx.dll: 3.4.22.19868
        0         weather.dll: 3.4.22.19868
        0          window.dll: 3.4.22.19868
        0 ----------------------------------
        0 Trying E:\P3Dv3.1\Modules\SimConnectP3D3.dll
        0 Found it: trying to connect
       16 FS path = "E:\P3Dv3.1\"
     1344 ---------------------- Joystick Device Scan -----------------------
     1344 Product= BU0836X Interface
     1344    Manufacturer= Leo Bodnar
     1344    Vendor=1DD2, Product=1001 (Version 1.33)
     1344    Serial Number= B05579
     1344 Product= Button Box Interface
     1344    Manufacturer= Leo Bodnar
     1344    Vendor=1DD2, Product=1140 (Version 1.4)
     1344    Serial Number= B30634
     1344 Product= Button Box Interface
     1344    Manufacturer= Leo Bodnar
     1344    Vendor=1DD2, Product=1140 (Version 1.4)
     1344    Serial Number= B27021
     1344 Product= BU0836X Interface
     1344    Manufacturer= Leo Bodnar
     1344    Vendor=1DD2, Product=1001 (Version 1.35)
     1344    Serial Number= B18042
     1344 Product= BU0836A Interface
     1344    Manufacturer= Leo Bodnar
     1344    Vendor=16C0, Product=05BA (Version 1.34)
     1344    Serial Number= B53222
     1344 Product= Button Box Interface
     1344    Manufacturer= Leo Bodnar
     1344    Vendor=1DD2, Product=1140 (Version 1.4)
     1344    Serial Number= B30632
     1344 Product= Saitek Pro Flight Rudder Pedals
     1344    Manufacturer= Saitek
     1344    Vendor=06A3, Product=0763 (Version 1.1)
     1344    Serial Number= 
     1344 -------------------------------------------------------------------
     1469 LogOptions=00000000 00000001
     1469 -------------------------------------------------------------------
     1469 ------ Setting the hooks and direct calls into the simulator ------
     1469 --- CONTROLS timer memory location obtained ok
     1469 --- SIM1 Frictions access gained
     1485 --- FS Controls Table located ok
     1485 --- Installed Mouse Macro hooks ok.
     1485 --- Wind smoothing fix is installed
     1485 --- SimConnect intercept for texts and menus option is off
     1485 --- All links okay (except older global weather setting method)
     1485 -------------------------------------------------------------------
     1485 SimConnect_Open succeeded: waiting to check version okay
     1485 Trying to use SimConnect Prepar3D
     1485 Opened separate AI Traffic client okay
    36578 Running in "Lockheed MartinÆ Prepar3DÆ v3", Version: 3.4.22.19868 (SimConnect: 3.4.0.0)
    36578 Initialising SimConnect data requests now
    36578 FSUIPC Menu entry added
    36594 C:\Users\William\Documents\Prepar3D v3 Files\Previous Flight.fxml
    36594 E:\P3Dv3.1\SimObjects\Airplanes\Prosim 737-800 Regular\Prosim738.air
   208516 User Aircraft ID 1 supplied, now being used
   208781 System time = 15/02/2017 08:53:14, Simulator time = 08:50:50 (08:50Z)
   208797 Aircraft="Prosim_737_800_Winglets_Prosim_Livery"
   209094 ***** HID USB device reconnected: re-initialising FSUIPC connections
   209110 ---------------------- Joystick Device Scan -----------------------
   209110 Product= BU0836X Interface
   209110    Manufacturer= Leo Bodnar
   209110    Vendor=1DD2, Product=1001 (Version 1.33)
   209110    Serial Number= B05579
   209110 Product= Button Box Interface
   209110    Manufacturer= Leo Bodnar
   209110    Vendor=1DD2, Product=1140 (Version 1.4)
   209110    Serial Number= B30634
   209110 Product= Button Box Interface
   209110    Manufacturer= Leo Bodnar
   209110    Vendor=1DD2, Product=1140 (Version 1.4)
   209110    Serial Number= B27021
   209110 Product= BU0836X Interface
   209110    Manufacturer= Leo Bodnar
   209110    Vendor=1DD2, Product=1001 (Version 1.35)
   209110    Serial Number= B18042
   209110 Product= BU0836A Interface
   209110    Manufacturer= Leo Bodnar
   209110    Vendor=16C0, Product=05BA (Version 1.34)
   209110    Serial Number= B53222
   209110 Product= Button Box Interface
   209110    Manufacturer= Leo Bodnar
   209110    Vendor=1DD2, Product=1140 (Version 1.4)
   209110    Serial Number= B30632
   209110 Product= Saitek Pro Flight Rudder Pedals
   209110    Manufacturer= Saitek
   209110    Vendor=06A3, Product=0763 (Version 1.1)
   209110    Serial Number= 
   209110 -------------------------------------------------------------------
   209172 ***** HID USB device reconnected: re-initialising FSUIPC connections
   209188 ---------------------- Joystick Device Scan -----------------------
   209188 Product= BU0836X Interface
   209188    Manufacturer= Leo Bodnar
   209188    Vendor=1DD2, Product=1001 (Version 1.33)
   209188    Serial Number= B05579
   209188 Product= Button Box Interface
   209188    Manufacturer= Leo Bodnar
   209188    Vendor=1DD2, Product=1140 (Version 1.4)
   209188    Serial Number= B30634
   209188 Product= Button Box Interface
   209188    Manufacturer= Leo Bodnar
   209188    Vendor=1DD2, Product=1140 (Version 1.4)
   209188    Serial Number= B27021
   209188 Product= BU0836X Interface
   209188    Manufacturer= Leo Bodnar
   209188    Vendor=1DD2, Product=1001 (Version 1.35)
   209188    Serial Number= B18042
   209188 Product= BU0836A Interface
   209188    Manufacturer= Leo Bodnar
   209188    Vendor=16C0, Product=05BA (Version 1.34)
   209188    Serial Number= B53222
   209188 Product= Button Box Interface
   209188    Manufacturer= Leo Bodnar
   209188    Vendor=1DD2, Product=1140 (Version 1.4)
   209188    Serial Number= B30632
   209188 Product= Saitek Pro Flight Rudder Pedals
   209188    Manufacturer= Saitek
   209188    Vendor=06A3, Product=0763 (Version 1.1)
   209188    Serial Number= 
   209188 -------------------------------------------------------------------
   419016 ***** HID USB device reconnected: re-initialising FSUIPC connections
   419078 ---------------------- Joystick Device Scan -----------------------
   419078 Product= BU0836X Interface
   419078    Manufacturer= Leo Bodnar
   419078    Vendor=1DD2, Product=1001 (Version 1.33)
   419078    Serial Number= B05579
   419078 Product= Button Box Interface
   419078    Manufacturer= Leo Bodnar
   419078    Vendor=1DD2, Product=1140 (Version 1.4)
   419078    Serial Number= B30634
   419078 Product= Button Box Interface
   419078    Manufacturer= Leo Bodnar
   419078    Vendor=1DD2, Product=1140 (Version 1.4)
   419078    Serial Number= B27021
   419078 Product= BU0836X Interface
   419078    Manufacturer= Leo Bodnar
   419078    Vendor=1DD2, Product=1001 (Version 1.35)
   419078    Serial Number= B18042
   419078 Product= BU0836A Interface
   419078    Manufacturer= Leo Bodnar
   419078    Vendor=16C0, Product=05BA (Version 1.34)
   419078    Serial Number= B53222
   419078 Product= Button Box Interface
   419078    Manufacturer= Leo Bodnar
   419078    Vendor=1DD2, Product=1140 (Version 1.4)
   419078    Serial Number= B30632
   419078 Product= Saitek Pro Flight Rudder Pedals
   419078    Manufacturer= Saitek
   419078    Vendor=06A3, Product=0763 (Version 1.1)
   419078    Serial Number= 
   419078 -------------------------------------------------------------------
   419141 ***** HID USB device reconnected: re-initialising FSUIPC connections
   419141 ---------------------- Joystick Device Scan -----------------------
   419141 Product= BU0836X Interface
   419141    Manufacturer= 
   419141    Vendor=1DD2, Product=1001 (Version 1.33)
   419141    Serial Number= B05579
   419141 Product= Button Box Interface
   419141    Manufacturer= Leo Bodnar
   419141    Vendor=1DD2, Product=1140 (Version 1.4)
   419141    Serial Number= B30634
   419141 Product= Button Box Interface
   419141    Manufacturer= Leo Bodnar
   419141    Vendor=1DD2, Product=1140 (Version 1.4)
   419141    Serial Number= B27021
   419141 Product= BU0836X Interface
   419141    Manufacturer= Leo Bodnar
   419141    Vendor=1DD2, Product=1001 (Version 1.35)
   419141    Serial Number= B18042
   419141 Product= BU0836A Interface
   419141    Manufacturer= Leo Bodnar
   419141    Vendor=16C0, Product=05BA (Version 1.34)
   419141    Serial Number= B53222
   419141 Product= Button Box Interface
   419141    Manufacturer= Leo Bodnar
   419141    Vendor=1DD2, Product=1140 (Version 1.4)
   419141    Serial Number= B30632
   419141 Product= Saitek Pro Flight Rudder Pedals
   419156    Manufacturer= Saitek
   419156    Vendor=06A3, Product=0763 (Version 1.1)
   419156    Serial Number= 
   419156 -------------------------------------------------------------------
   423281 Starting everything now ...
   423360 ASN active function link set
   423360 Ready for ASN WX radar
   424453 Advanced Weather Interface Enabled
   433938 Sim stopped: average frame rate for last 31 secs = 26.8 fps
   433938    Max AI traffic was 0 aircraft

 

 

Posted
27 minutes ago, 13Aces said:

Recently I added a new  motorised Throttle to my sim (complete with its own drivers) and subsequently removed it and replaced it with my original Bodnar/FSUIPC throttle. Since then I have been experiencing regular  (P3D stopped working) crashes. I can sometimes complete a short flight but not very often.

Did you fully uninstall the previous device? Otherwise registry entries will still say that the old one is still there, and trying to read non-existent devices is likely to give problems. Go t the Control Panel - System and uninstall from there as well as uninstalling any programs associated with it.

I see that one of your devices is constantly re-connecting. This:

209094 ***** HID USB device reconnected: re-initialising FSUIPC connections

occurs many times, each time immediatley after the other, during start up. That's not good. FSUIPC isn't polling for new devices, it simply asks Windows to notify it if any are freshly connected.

However, this in itself should not make P3D crash, though it may hang it.

Unfortunately, though you say you found the Windows crash details you show none at all, so there's nothing to point out which P3D or System component actually crashed.

Pete

 

Posted

Indeed Pete it is so frustrating. Next attempt at loading P3D worked perfectly. Now on a flight.

I did use the uninstall from Program and Features

Below a selection of the reported errors from the crash earlier this morning.

 

Faulting application name: microsoftedgecp.exe, version: 11.0.14393.82, time stamp: 0x57a55786
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000604
Fault offset: 0x0000000000000000
Faulting process id: 0x1c88
Faulting application start time: 0x01d2876b4ce72c27
Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe
Faulting module path: unknown
Report Id: 94d2d01a-b550-4f22-a9a8-df30a18868c3
Faulting package full name: Microsoft.MicrosoftEdge_38.14393.0.0_neutral__8wekyb3d8bbwe
Faulting package-relative application ID: MicrosoftEdge


Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x58256ca0
Exception code: 0xc0000005
Fault offset: 0x00048e64
Faulting process id: 0x1ec8
Faulting application start time: 0x01d2876872e694c3
Faulting application path: E:\P3Dv3.1\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 9868b082-f67a-4ade-a1c2-026412998e1f
Faulting package full name: 
Faulting package-relative application ID: 

Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 77E98E64

The C:\WINDOWS\SYSTEM32\ntdll.dll error above is one that I regularly see after P3D crashes. Plus another about Kernal power.

Posted
1 hour ago, 13Aces said:

The C:\WINDOWS\SYSTEM32\ntdll.dll error above is one that I regularly see after P3D crashes. Plus another about Kernal power.

I think you need to report this to L-M. Have you already checked through the crash reports already there.

L-M will probably ask you to test with no add-ons at all first, then add things back bit by bit. I think you should do that in any case, before reporting on that Forum probably.

The first Windows crash above is in something called "MicrosoftEdge". I don't think that's anything to do with P3D, is it? Maybe it's another indication of something else wrong in your system.

Pete

 

Posted

I never like threads that the OP doesn't conclude-- so after several more starts and several crashes mixed with completed successful flights I decided to go the full reinstall route using the "Reset this PC" option in Win 10. I selected the "full clean" option to ensure that nothing was left behind.

For anyone reading this thread--my system has an SSD and a HDD-- it took approximately 6.5 hours to complete the  reset process. Now I should have a clean Win 10 installation to start the  reinstall process.

Thanks again for helping Pete

William

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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.