Since V 5.1.5.1 P3D always Crash

[Chamsin91]

Hi

Yesterday im going to V 5.1.5.1 since the Update, my P3D V4.4 Crashs always 10-15min after Take Off....

 

Protokollname: Application
Quelle:        Application Error
Datum:         05.04.2019 21:09:25
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      DESKTOP-SV9459L
Beschreibung:
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.4.16.27077, Zeitstempel: 0x5bfdbb35
Name des fehlerhaften Moduls: FSUIPC5.dll, Version: 5.1.5.1, Zeitstempel: 0x5c920d17
Ausnahmecode: 0xc000041d
Fehleroffset: 0x00000000000df637
ID des fehlerhaften Prozesses: 0x26a4
Startzeit der fehlerhaften Anwendung: 0x01d4ebdc4780b221
Pfad der fehlerhaften Anwendung: D:\P3D V4\Prepar3D.exe
Pfad des fehlerhaften Moduls: D:\P3D V4\Modules\FSUIPC5.dll
Berichtskennung: 0ad669b0-89f9-4bea-b040-056fe9673ea5
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Ereignis-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="2019-04-05T19:09:25.126682900Z" />
    <EventRecordID>79963</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-SV9459L</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.4.16.27077</Data>
    <Data>5bfdbb35</Data>
    <Data>FSUIPC5.dll</Data>
    <Data>5.1.5.1</Data>
    <Data>5c920d17</Data>
    <Data>c000041d</Data>
    <Data>00000000000df637</Data>
    <Data>26a4</Data>
    <Data>01d4ebdc4780b221</Data>
    <Data>D:\P3D V4\Prepar3D.exe</Data>
    <Data>D:\P3D V4\Modules\FSUIPC5.dll</Data>
    <Data>0ad669b0-89f9-4bea-b040-056fe9673ea5</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

Cheers Thomas

[Pete Dowson]

3 hours ago, Chamsin91 said:

Yesterday im going to V 5.1.5.1 since the Update, my P3D V4.4 Crashs always 10-15min after Take Off....

What was your previous version of FSUIPC5? Is is registered?

The error is 

ERROR_SERVICE_REQUEST_TIMEOUT "The service did not respond to the start or control request in a timely fashion."

but of course FSUIPC is not the "service", so something in Windows is timing out.

We need much more information in any case. The location withing FSUIPC would be known, but not without the Log, for instance.

This could be due to a corrupt WX file.  Try moving all of them out of your Prepar3D Documents folder. Or it could actually be a scenery problem. Is it always in the same area of the world, over the same scenery?

And what add-ons are you using? A list of those would be useful, especially any that use FSUIPC. Also please show us these files:

Your DLL.XML and EXE.XML files, both froom your ProgrmData folder and from your User AppData\Roaming folder for P3D4.

Also we always need your FSUIPC5.INI and FSUIPC5.LOG files, from the P3D4 Modules folder.

You can attach to a message here, but please ZIP them first.

Pete

 

[Chamsin91]

Hey Pete

 

My previous version of FSUIPC was 5.15, and yes its registered.

I have this problem after the uptade to 5.151 on Thursday. No its not always the same area, sometimes in Europe, next Crash in US...

I use Active Sky P3D V4, i get always this Message to: Cannot control ambient weather parameters 

 

 

FSUIPC5.zip

APP DATA ROAMING Files.zip

ProgrammData Files.zip

[Pete Dowson]

3 hours ago, Chamsin91 said:

My previous version of FSUIPC was 5.15

Hmm. The changes since then a pretty minor.

Have you tested after removing all your .wx files as suggested?

3 hours ago, Chamsin91 said:

I use Active Sky P3D V4, i get always this Message to: Cannot control ambient weather parameters 

That's nothing to do with FSUIPC, but if Active Sky's module is being loaded then FSUIPC will connect to it and if the module is corrupted or the wrong version for this build of P3D4, then it could cause FSUIPC to crash.

The message from Active Sky does mean that its module can't interface to that version of P3d4, so in turn it implies either a bad ASP4 DLL or the wrong version. Could you make sure your Active Sky is up to date?  If not update it, if so, perhaps try re-installing. The DLL module it uses is changed for each build of P3D4 because it hooks into the P3D4 code.

The fact that FSUIPC 5.15 didn't crash doesn't mean it was okay with this. Even small changes in code and the subsequent re-compile can move data areas around and so change the events which occur on corruption.

You can check that it is to do with weather by stopping FSUIPC doing any weather activity. Temporarily, to check this, add

NoWeatherAtAll=Yes

to the [General] section of FSUIPC5.INI.

YOUR FILES

The FSUIPC5.zip just includes

FSUIPC5.DLL -- i.e.the module supplied by use and installed for you. why you sent us back our own module i don't know
FSUIPC5.LOG -- as requested, and the most important

but not the FSUIPC5.INI file requested.

I assume this is the log after the crash? so the place it got to is as far as it logged anything before the crash?  There's nothing obvious showing up.

I'll check the crash location.

Pete

 

 

[Pete Dowson]

Unfortunately the crash location doesn't appear to correspond to any particular part of FSUIPC5.

But there is one other thing to try, as well as those suggested above. Let FSUIPC5 act with the weather data as normal (i.e. remove the "NoWeatherAtAll" line if you added it, but change your AppData copy of DLL.XML as shown in red below:

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>FSUIPC 5</Name>
    <Disabled>False</Disabled>
    <Path>D:\P3D V4\Modules\FSUIPC5.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>as_connect</Name>
    <Disabled>True</Disabled>
    <Path>as_srv\as_connect_64.dll</Path>
  </Launch.Addon>
</SimBase.Document>

This will stop the Active Sky module loading altogether, so at least show one way or the other whether it is the FSUIPC calls into it which crash/

Pete

 

[UniformAlpha2014]

Hi Pete,

I was also updating to version 5.151 and get that crash. I noticed that the sim (P3Dv4.5) lags very hard. 

I tested that on several scenarios all around the world with different aircrafts. Always the same result. 

Here is my FSUIPC.ini file: 

FSUIPC5.ini

[John Dowson]

Hi Colin,

your log file after the crash, together with the ini.  would have been useful!

Have you tried the other solutions in this post before posting? i.e. removing wx files, and also disabling weather? If not, please do so.

Was the change only from FSUIPC 5.150 to 5.151, or is this also with P3D updated from 4.4 to 4.5? What add-ons are you using? Were any of these updated?

So, please try solutions mentioned and report results, and if you are still having problems, post your ini and log files together. Also, if its a CTD, then the windows event log information would also be useful.

Thanks,

John

P.S. what do you mean by 'lags very hard'?

[UniformAlpha2014]

21 minutes ago, John Dowson said:

Hi Colin,

your log file after the crash, together with the ini.  would have been useful!

Have you tried the other solutions in this post before posting? i.e. removing wx files, and also disabling weather? If not, please do so.

Was the change only from FSUIPC 5.150 to 5.151, or is this also with P3D updated from 4.4 to 4.5? What add-ons are you using? Were any of these updated?

So, please try solutions mentioned and report results, and if you are still having problems, post your ini and log files together. Also, if its a CTD, then the windows event log information would also be useful.

Thanks,

John

P.S. what do you mean by 'lags very hard'?

Hey,

so I was updating from FSUIPC version 5.11 to 5.151. The upgrade from P3dv4.4 to 4.5 haven't caused any problems.

I was trying to delete the previous wx file and edited the FSUIPC.ini file as mentioned above with no different result. 

Addons are quite a lot: ActiveSky, ASCA, ENVTEX, ENVSHADE, ORBX (base,vector,openlc,germany north + south,netherlands), PMDG737, 747, 777, FsLabs A3xx, and lots of payware airports.

On my last crash, windows 10 says: 

Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.5.11.29713, Zeitstempel: 0x5ca56c53
Name des fehlerhaften Moduls: FSUIPC5.dll, Version: 5.1.5.1, Zeitstempel: 0x5c920d17
Ausnahmecode: 0xc000041d
Fehleroffset: 0x00000000000df637
ID des fehlerhaften Prozesses: 0x34a8
Startzeit der fehlerhaften Anwendung: 0x01d4fb9c5d29e473
Pfad der fehlerhaften Anwendung: D:\P3Dv4\Prepar3D.exe
Pfad des fehlerhaften Moduls: D:\P3Dv4\Modules\FSUIPC5.dll
Berichtskennung: 73fd8d21-5662-4482-98a8-af31b951a807
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

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="2019-04-25T20:25:36.289729100Z" />

  <EventRecordID>3421</EventRecordID>

  <Channel>Application</Channel>

  <Computer>xPredator</Computer>

  <Security />

  </System>

- <EventData>

  <Data>Prepar3D.exe</Data>

  <Data>4.5.11.29713</Data>

  <Data>5ca56c53</Data>

  <Data>FSUIPC5.dll</Data>

  <Data>5.1.5.1</Data>

  <Data>5c920d17</Data>

  <Data>c000041d</Data>

  <Data>00000000000df637</Data>

  <Data>34a8</Data>

  <Data>01d4fb9c5d29e473</Data>

  <Data>D:\P3Dv4\Prepar3D.exe</Data>

  <Data>D:\P3Dv4\Modules\FSUIPC5.dll</Data>

  <Data>73fd8d21-5662-4482-98a8-af31b951a807</Data>

  <Data />

  <Data />

  </EventData>

  </Event>

 

And btw the sim crashed without a "Prepar3D has stopped working" message, but rather crashed without any message. 

"huge lags" are milliseconds, maybe seconds with 0-1 fps 

(the .ini file is the same as above)

 

Patrick

 

FSUIPC5.log

[John Dowson]

Did you try disabling Active Sky (as_connect) by editing the dll.xml, as explained in Pete's last post above?

[UniformAlpha2014]

8 hours ago, John Dowson said:

Did you try disabling Active Sky (as_connect) by editing the dll.xml, as explained in Pete's last post above?

Yeah I just tried it one more time. But I noticed something.

Before every crash there is a "DistributedCOM" Error. It says it cannot start a file called "coredpussvr.exe" somewhere in the Windows/System32 folder. Right afterwards P3D crashes.

Eventlog:

-

System

- Provider       [ Name] Microsoft-Windows-DistributedCOM       [ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}       [ EventSourceName] DCOM

- EventID 10000       [ Qualifiers] 0

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8080000000000000

- TimeCreated       [ SystemTime] 2019-04-26T14:54:34.143684500Z

EventRecordID 3021

Correlation

- Execution       [ ProcessID] 964       [ ThreadID] 14448

Channel System

Computer xPredator

- Security       [ UserID] S-1-5-21-1236235040-2779368353-1591499981-1001

-

EventData

param1

C:\Windows\System32\coredpussvr.exe -Embedding

param2

0

param3

{417976B7-917D-4F1E-8F14-C18FCCB0B3A8}

 

Edit: Maybe you can provide me the previous 5.1.5.0 version of FSUIPC. That should be more stable than the new one. 

 

Patrick

Edited April 26, 2019 by UniformAlpha2014

[John Dowson]

Hi Patrick,

thats interesting...a new feature in 5.151 does use the PDK distributed com interface, so if thats not working it could cause a problem. This seems more to be an issue with your windows installation though. I'll investigate further, and I'll build (and post) a 5.15 version for you (later today) to test. However, 5.15 also uses the PDK, but maybe not distributed COM (I'll check).

Cheers,

John

[John Dowson]

Here's 5.15: FSUIPC5.txt

Rename to 'FSUIPC5.dll' once downloaded.

John

[John Dowson]

I've looked into the Distributed COM events and think this is a bit of a red herring...

Anyway, here's another version to try - 5.151a. In this version, I've simplified the interfaces to the PDK used by FSUIPC (now using only one frame event rather than 2).

Can those with this problem please give this a try and report back: FSUIPC5.txt

(Again, its a dll file renamed to *.txt to prevent virus-checking problems - please download, rename and install).

Thanks,

John

 

[UniformAlpha2014]

Hey John,

I was testing the fsuipc v5.15 for a few days now. I was wondering why all my switches on my x55 hotas aren't working. I checked the log files but there was nothing strange. fsuipc send the command to the sim. But nothing happend on the aircraft (FsLabs A320). 

I was wondering how. I downgraded my sim to P3Dv4.4 again a few days ago (because of performance), but the switches still don't work properly. 

Now my addition question is: When I upgrade fsuipc to another version, what do I have to reinstall?

 

Edit: Yes I take a look on that 5.151a

[John Dowson]

Quote

 But nothing happend on the aircraft (FsLabs A320).

Thats very strange. Did you try a different aircraft? Are you sure FSUIPC is running (can you see it in the 'Add-ons' menu?)

Quote

When I upgrade fsuipc to another version, what do I have to reinstall?

If you already have FSUIPC installed, you can just replaced the FSUIPC5.dll file. The files attached in the posts above are dll files, just download them, rename to 'FSUIPC5.dll' and copy (replace) to your sims 'Module' folder (which is'D:\P3Dv4\Modules\'). If you've re-installed the sim, you may first need to re-install by running the (latest) installer first.

[UniformAlpha2014]

14 minutes ago, John Dowson said:

Thats very strange. Did you try a different aircraft? Are you sure FSUIPC is running (can you see it in the 'Add-ons' menu?)

Yes I tried with the default F-22 and PMDGs 777. I noticed that the commands with key memos are working fine. See in the picture below. The left side is working, but the right side not. 

14 minutes ago, John Dowson said:

If you already have FSUIPC installed, you can just replaced the FSUIPC5.dll file. The files attached in the posts above are dll files, just download them, rename to 'FSUIPC5.dll' and copy (replace) to your sims 'Module' folder (which is'D:\P3Dv4\Modules\'). If you've re-installed the sim, you may first need to re-install by running the (latest) installer first.

I just reinstalled the academic client for v4.4. No complete reinstallation. 

 

[John Dowson]

By 'not working', do you mean that you cannot see your button presses, or your previous assignments are lost? If the latter, then maybe your joystick ids have changed (and you are not using the joy letters facility). That would also affect your axis though!  If its the former, then check your log file to see if your devices are recognised.

[UniformAlpha2014]

So I checked the new 5.151a version. The distributed COM Error is done. But fsuipc still crashes:

 

-

System

- Provider       [ Name] Application Error

- EventID 1000       [ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated       [ SystemTime] 2019-05-02T13:10:14.662405900Z

EventRecordID 4559

Channel Application

Computer xPredator

Security

-

EventData

Prepar3D.exe

4.4.16.27077

5bfdbb35

FSUIPC5.dll

5.1.5.1

5cc9b3ed

c0000005

00000000000e1088

23b0

01d500e56184c209

D:\P3Dv4\Prepar3D.exe

D:\P3Dv4\Modules\FSUIPC5.dll

681a8ce7-d9f1-4119-a5ae-bdcc7f2ad735

Errorcode: 1000

[John Dowson]

When did it crash? Can you post the log file please.

[UniformAlpha2014]

That should be the one. 

which logging should I turn on in fsuipc?

FSUIPC5_prev.log

[John Dowson]

So its crashing when loading/on start-up. When you re-installed 4.4 did you re-install the correct version of your add-ons?

Try again without ActiveSky, and also with NoWeatherAtAll=Yes.

You should also start with a default aircraft really as well - especially it seems if you use the FSLabs A320 (see this thread: https://www.avsim.com/forums/topic/526406-must-i-start-p3d-with-a-default-aircraft/).

John

[UniformAlpha2014]

Hello

here is a quick update on this:
I found out that the AIM OCI traffic program makes FSUIPC crash. When I deactivate it in the Addon.cfg there is no crash at all. 

So, do you know about a instability between AIM and FSUIPC, and maybe how to fix it?

[John Dowson]

There is a know problem with AI when using AIM OCI which is currently being investigated - see 

This only seems to happen with lots of AI traffic, so for the time being try and reduce your traffic sliders to < 50%.