Jump to content
The simFlight Network Forums

FSUIPC4.dll crash mid-flight


Recommended Posts

Hey guys,

 

I have FSUIPC running because of IVAO. I didnt't buy it but it came with IVAO.

 

After an hour of flying my FSUIPC4.dll is crashing in mid-flight. I'm running Windows 10 and here's my log file:

 

Name der fehlerhaften Anwendung: fsx.exe, Version: 10.0.61637.0, Zeitstempel: 0x46fadb14
Name des fehlerhaften Moduls: FSUIPC4.dll, Version: 4.8.5.3, Zeitstempel: 0x50477966
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00037504
ID des fehlerhaften Prozesses: 0x824
Startzeit der fehlerhaften Anwendung: 0x01d114c8ac4ba455
Pfad der fehlerhaften Anwendung: D:\Microsoft Flight Simulator X\fsx.exe
Pfad des fehlerhaften Moduls: D:\Microsoft Flight Simulator X\Modules\FSUIPC4.dll
Berichtskennung: 10613511-80ca-11e5-8d78-001a7dda710b
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

 

- System
    - Provider
      [ Name] Application Error
    - EventID 1000
      [ Qualifiers] 0
      Level 2       Task 100       Keywords 0x80000000000000     - TimeCreated
      [ SystemTime] 2015-11-01T18:55:06.000000000Z
      EventRecordID 1294       Channel Application       Computer Moritz-PC       Security
- EventData
      fsx.exe       10.0.61637.0       46fadb14       FSUIPC4.dll       4.8.5.3       50477966       c0000005       00037504       824       01d114c8ac4ba455       D:\Microsoft Flight Simulator X\fsx.exe       D:\Microsoft Flight Simulator X\Modules\FSUIPC4.dll       10613511-80ca-11e5-8d78-001a7dda710b

 

 

Please help me it sucks...

 

Thank you!

 

Moritz

 

Link to comment
Share on other sites

You are using a very old version of FSUIPC (4.853) which has not been supported for a very long time. Please update. The earliest supported version for FSX is 4.947c.

 

If you still have a problem I not only need to see the Windows crash details, but also the FSUIPC4.LOG file from the Modules folder.

 

Pete

Link to comment
Share on other sites

********* FSUIPC4, Version 4.853 by Pete Dowson *********

Running inside FSX on Windows 7

Module base=0F7B0000

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

        0 System time = 04/11/2015 13:45:01

        0 FLT path = "E:\Documents\Flight Simulator X-Dateien\"

       16 Trying to connect to SimConnect Acc/SP2 Oct07 ...

       31 FS path = "D:\Microsoft Flight Simulator X\"

      281 LogOptions=00000000 00000001

      281 Wind smoothing fix is fully installed

      281 G3D.DLL fix attempt installed ok

      281 SimConnect_Open succeeded: waiting to check version okay

      281 Trying to use SimConnect Acc/SP2 Oct07

     2188 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

     2188 Initialising SimConnect data requests now

     2188 FSUIPC Menu entry added

     2203 D:\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

     2203 D:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
Link to comment
Share on other sites

********* FSUIPC4, Version 4.853 by Pete Dowson *********

 

I have to repeat myself I see:

 

You are STILL using a very old version of FSUIPC (4.853) which has not been supported for a very long time. Please update. The earliest supported version for FSX is now 4.948

 

If you still have a problem I not only need to see the Windows crash details, but also the FSUIPC4.LOG file from the Modules folder.

BUT ONLY FOR A SUPPORTED VERSION!

 

Pete

Link to comment
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
×
×
  • 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.