FSUIPC causes Crash to desktop - 1st Time

[WarEagleX]

Running Prepar3d 4.5. PacSim KSLC. ActiveSky 7044 Beta. ORBX (all of it). Pmdg 737-900. PF3. Windows 10 (all latest patches of course)

Everything was fine and it was running for about 45 minutes of sitting stationary at the gate. Taxiied for departure at 34R. PF3 cleared for takeoff and was entering runway when got an immediate crash to desktop.  This is the first crash with this error and I've flown coast to coast - since upgrading. The only thing I've noticed since upgrading to 4.5 is that there are more pauses to load scenery than ever before and this was probably only the 2nd or 3rd crash ever in Prepar3d.

Here are the errors from Windows Event Viewer in sequence:

1. .NET Runtime at 7:07:44pm

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 00007FF859941068
Stack:

2. Application Error at 7:07:46pm

Faulting application name: Prepar3D.exe, version: 4.5.11.29713, time stamp: 0x5ca56c53
Faulting module name: FSUIPC5.dll, version: 5.1.5.1, time stamp: 0x5c920d17
Exception code: 0xc0000005
Fault offset: 0x00000000000e1068
Faulting process id: 0x605c
Faulting application start time: 0x01d4fe0f105905ae
Faulting application path: D:\Program Files\Lockheed Martin\Prepar3D v4.1\Prepar3D.exe
Faulting module path: D:\Program Files\Lockheed Martin\Prepar3D v4.1\Modules\FSUIPC5.dll
Report Id: 862639c1-8f19-4165-a59a-3c4b163e2dae
Faulting package full name: 
Faulting package-relative application ID: 

3. Application Error at 7:07:51pm

Faulting application name: Prepar3D.exe, version: 4.5.11.29713, time stamp: 0x5ca56c53
Faulting module name: FSUIPC5.dll, version: 5.1.5.1, time stamp: 0x5c920d17
Exception code: 0xc000041d
Fault offset: 0x00000000000e1068
Faulting process id: 0x605c
Faulting application start time: 0x01d4fe0f105905ae
Faulting application path: D:\Program Files\Lockheed Martin\Prepar3D v4.1\Prepar3D.exe
Faulting module path: D:\Program Files\Lockheed Martin\Prepar3D v4.1\Modules\FSUIPC5.dll
Report Id: 86cc2380-fdf1-42fb-80af-a017408776f7
Faulting package full name: 
Faulting package-relative application ID: 

Also noticed a lot of Distributed COM errors at the time.

[John Dowson]

Hi,

another user posted a similar problem with a CTD after Distributed COM errors in this post:

I am looking into this and will report back if I find anything. The above post also contains a link to version 5.150 if you want to revert back to that for the time being to see if this helps.

Regards,

John

P.S. Could you post the Distributed COM errors that you received please, may be useful...

[WarEagleX]

Hi John:

Sorry for the delay - it was Game of Thrones night and I'm totally exhausted after the Battle of Winterfell 🙂See below:

Looking at the timestamps on the Distributed COM errors I think they were coincidental and not necessarily related to the fault above.  They started before I started my FS session and ended after it crashed. BUT, I've included the first and last here for your review.

1. DistributedCOM Error at 5:03:44 PM (I don't think I was even sitting at the computer or had Prepar3d running)

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID 
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user JEDI\micha SID (S-1-5-21-1770076962-628409222-175556869-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

7 more until the final one

2. DistributedCOM Error at 7:18:55 PM

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user JEDI\micha SID (S-1-5-21-1770076962-628409222-175556869-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The logs are clear after that time.

Warm regards,

Mike T.

[John Dowson]

Hi Mike,

GoT will be tonights viewing for me!

I've looked a bit into the Distributed COM errors and I also don't think they're related to the P3D crash. Can you reproduce the crash or was it a one-off?

Do you have the FSUIPC log file produced at the time of the crash?

Cheers,

John

[WarEagleX]

Hi John:

Attached is the log from last night its timestamped at 7:07p so its inline with the event viewer data.  I'll set up the same flight this evening and I'll post the results.  I downgraded 5.150 BTW and will test that.  If that works I'll restore 5.151 and do the same flight with that.  It will take a day or two so please stand by.

I appreciate your help as usual

Cheers

Mike T.

FSUIPC5.log

[John Dowson]

Is that the full log file? The log stops even before FSUIPC open a SimConnect connection to the sim, no aircraft loaded, etc. Did the sim crash on start-up? Thought the crash was when taxiing.
Please also try different (default) aircraft, and different locations to try and narrow down the problem - it may well be an incompatible add-on or corrupt file somewhere.

John

 

[John Dowson]

Hi Mike,

here's another version to try - 5.151a. In this version, I've simplified the interfaces to the PDK used by FSUIPC.

Please give it a try and report back: FSUIPC5.txt

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

Cheers,

John

 

 

 

[WarEagleX]

Hi John - Sorry for the delay in reply I had an impromptu business trip that interrupted my flight simulation - If only i could get paid to do this full-time! :-) 

On your first question - yes, the sim crashed while I was taxiing and it had been open for about 45 minutes while i boarded, pushback, and taxied at KSLC.   So it's strange that the logs were truncated.  

I will download the version you posted above and use it on my next flight today and report back.

Thanks for your continued help and hope all is well.

Mike T.