FSUIPC Crashing FSX:SE

[RetiredFE]

I recently updated FSUIPC to the current version and made several changes to a couple of aircraft.  Now for some reason I am getting this error message when trying to open FSX:SE.  "Flight Simulator has detected a problem with a third party software program (add-on):

Name:  FSUIPC4 dll: FS new universal IPC interface

Version: 4.974

Company: Peter Dowson

File:  Modules\FSUIPC4.dll

It's telling me to delete the program.  It also asks if I want to run this software (not recommended).   Problem is my airplanes are all tied into FSUIPC, so even if i said no, I doubt that I could fly anyway.  I am not going to delete FSUIPC.  If I try and start FSX:SE the program crashes immediately.  One other comment.  I just purchased the Carenado DA 62 yesterday.  The first time I tried to fly it after selecting it from the choices of aircraft to fly, FSX:SE crashed.  I opened it, and tried it again, everything was normal.  Today, I went to fly and this happened.  Wondering if these are related in some way??  Any help would be greatly appreciated.  Thanks

Rodger

Update:  So I decided to uninstall the Carenado DA 62 but I am still getting the same message.  So apparently the aircraft is not the problem.  So I go back and open FSX:SE, get the message and click the "No" box and not open FSUIPC.  Everything worked and as expected I have no flight controls, throttle or anything else.

 

[Pete Dowson]

36 minutes ago, RetiredFE said:

If I try and start FSX:SE the program crashes immediately.

Is no FSUIPC4.LOG being produced in the FSX-SE Modules folder? Did you look?

if there is one, we need to see it. If not, then please use Windows "Event Viewer" to obtain the details of the crash and provide those instead. We cannot help diagnose problems without information.

If the crash was not "immediate" I would say it is likely you have a corrupt weather file -- a .WX file in your Flight simulator Documents folder, or possibly the wxstationlist.bin file in the same folder as your FS-SE settings (the AppData folder). deleting both would help in that case. The reason is that FSUIPC reads weather through Simconnect and a corrupt file causes crashes and other errors.

FSUIPC 4.974 has been the current version for FSX, FSX-SE and P3D3 for a long time now.

Pete

 

 

[RetiredFE]

Pete, I got a feeling it's the WX file.  I just installed FSrealWSPro a couple of days ago.  I'll try deleting those files and if that works, I'm good.  If not I'll get the Log file to you.  Thanks for your help and quick response.  Much appreciated.

Rodger

[RetiredFE]

Pete, here is a copy of one of the crashes I had.  To be honest, not sure if this is what you need.  If not please let me know.  Thank you.

Log Name:      Application
Source:        Windows Error Reporting
Date:          8/14/2019 12:52:52 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-27VLFV2
Description:
Fault bucket 1641438089667330606, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: fsx.exe
P2: 10.0.62615.0
P3: 559f9a9a
P4: FSUIPC4.dll_unloaded
P5: 4.9.7.4
P6: 5a914fb2
P7: c000041d
P8: 000c33b0
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5B80.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E01.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E21.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E31.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E51.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_7fd5ba8e0b258cc9f3522ab80ffe9a5f318568e_a37f3a76_5d183db8-867a-4005-89cb-6e1e31711222

Analysis symbol:
Rechecking for solution: 0
Report Id: 07b3bad8-851e-4b79-96e4-f0d6442138a7
Report Status: 268435456
Hashed bucket: 8f39db2e79eec30496c78f3eef6ac22e
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-08-14T16:52:52.262175700Z" />
    <EventRecordID>2548</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-27VLFV2</Computer>
    <Security />
  </System>
  <EventData>
    <Data>1641438089667330606</Data>
    <Data>1</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>fsx.exe</Data>
    <Data>10.0.62615.0</Data>
    <Data>559f9a9a</Data>
    <Data>FSUIPC4.dll_unloaded</Data>
    <Data>4.9.7.4</Data>
    <Data>5a914fb2</Data>
    <Data>c000041d</Data>
    <Data>000c33b0</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5B80.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E01.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E21.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E31.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E51.tmp.txt</Data>
    <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_7fd5ba8e0b258cc9f3522ab80ffe9a5f318568e_a37f3a76_5d183db8-867a-4005-89cb-6e1e31711222</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>07b3bad8-851e-4b79-96e4-f0d6442138a7</Data>
    <Data>268435456</Data>
    <Data>8f39db2e79eec30496c78f3eef6ac22e</Data>
    <Data>0</Data>
  </EventData>
</Event>

[RetiredFE]

Pete, I found a log for one of the times I tried to FSX:SE to work.  This might be the one when I clicked the "No" box so that FSX:SE would not open FSUIPC. This is the only one I can find.  I also found the wstationlist.bin file and deleted it, but it did not work.

 

 

FSUIPC4.log

[Thomas Richter]

Hi,

the attached log file shows that FSUIPC normally closed after FSUIPC was running for 605 seconds (605593 milliseconds or 10 min.). You should have something more recent if FSUIPC started at all.

Thomas

Quote

********* FSUIPC4, Version 4.974 (24th February 2018) by Pete Dowson *********
Windows 10 Enterprise 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0)
fsx.exe version = 10.0.62615.0
Reading options from "D:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 10
Module base=7AC20000
User Name="Rodger Cuccio"
User Addr="rodgerc5a@yahoo.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       62 System time = 14/08/2019 12:42:40   

 605593 *** FSUIPC log file being closed
Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps
Minimum available memory recorded was 32768Mb
Maximum AI traffic for session was 0 aircraft
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

 

[RetiredFE]

I don't know how that would be possible. It's not starting.  It immediately crashes FSX:SE if I elect to run FSUIPC.  I haven't had the flight sim open for more than 3-4 minutes today as it keeps crashing before it even opens.  The only time I had it open is when I clicked "No" and told FSX:SE not to start FSUIPC.  I just confirmed that when it did open all of my flight controls etc, that are controlled by FSUIPC  were not working and shut down FSX:SE.  Frustrating

[Pete Dowson]

15 hours ago, RetiredFE said:

I don't know how that would be possible. It's not starting.  It immediately crashes FSX:SE if I elect to run FSUIPC.  I haven't had the flight sim open for more than 3-4 minutes today as it keeps crashing before it even opens.  The only time I had it open is when I clicked "No" and told FSX:SE not to start FSUIPC.  I just confirmed that when it did open all of my flight controls etc, that are controlled by FSUIPC  were not working and shut down FSX:SE.  Frustrating

Well the log, which shows a session only yesterday (the 14th) does definitely show that FSX-SE loaded with FSUIPC and did not crash. Everything terminated normally.

However, FSUIPC did not progress to the point where it was doing very much. It looks like your default flight (Carenado 690B.FLT) loaded and FSUIPC started reading the weather. How it then managed to proceed to a normal close i can't imagine, but we do know that corrupt weather files can result in corruption inside FSX-SE, and it is probably a result of that.

The crash report you showed was merely for " FSUIPC4.dll_unloaded" -- in other words FSUIPC had closed but something in FSX-SE was still trying to call a function in it.

You said you deleted the wxstationlist.bin file but nothing about the .WX files which are actually much more likely to be the culprit. It might only be the one associated with your default flight, so try either deleting or renaming Carenado 690B.wx

Pete

 

[RetiredFE]

Thanks Pete.  I found the Carenado 690B.wx file and deleted it, but I'm still getting the same Error Message.  At this point I don't know what more to do other than click the "No" button in order to start FSX:SE which then will not load FSUIPC in the "Addons" drop down menu and go back into FSX and reprogram everything.  I just do not want to uninstall FSUIPC.  I do remember getting a message at the end of one of my flights before this problem that the FSrealWXPro program did not shut down properly.  I wonder if that is the problem?

[Thomas Richter]

Hi 

to eliminate any weather problem you can add to your FSUIPC4.ini file to the [General] section

NoWeatherAtAll=Yes

There was also some registry problem in Windows 10 after programs crashed that they were added to as harmful and don't load then anymore. Have a look here

Thomas

[RetiredFE]

25 minutes ago, Thomas Richter said:

Hi 

to eliminate any weather problem you can add to your FSUIPC4.ini file to the [General] section

NoWeatherAtAll=Yes

There was also some registry problem in Windows 10 after programs crashed that they were added to as harmful and don't load then anymore. Have a look here

Thomas

Thomas, thanks for your help.  I have a couple of questions.  First, if I go into the FSUIPC4.ini file and enter the NoWeatherAtAll=Yes, I assume that I can't use the program FSrealWXPro in order to get weather.  Is that correct?  Second, I looked at the page that you gave me and in it when going into the regedit I noticed that the first line is concerning windows NT.  Here is the first line on my computer.  "Computer\HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0".  None of the entries posted in the article are in my regedit.  I'm not real good with computers so I'm not sure what to do now.  Thanks

Rodger

[Thomas Richter]

Hi,

to First: Try just to see if you get FSUIPC to load again.

to Second: You go as I did here (Win10) to the following

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

Thomas

[RetiredFE]

22 minutes ago, Thomas Richter said:

Hi,

to First: Try just to see if you get FSUIPC to load again.

to Second: You go as I did here (Win10) to the following

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

Thomas

Ok, I did as you said, and here is the file I deleted...."D:\ProgramFile...Reg_S2 $~ignorefreelibrary<FSUIPC4.dll>RUNASADMIN.  Then I went to start FSX:SE  with the same error message.  I also rebooted the computer and tried to restart FSX:SE, same error message.

Edited August 15, 2019 by RetiredFE
More information

[RetiredFE]

So I've been searching the internet all over and ran across a post named "FSUIPC 4 will not allow FSX SE to start, here in this forum.  To make a long story short, there was a conversation about a line in the FSX SE config file in the [TRUSTED] line.  This is what is supposed to be there:  " Modules\FSUIPC4.dll.baqwihiwquneutelbzwtuqrrberazbrtleiloeho=1".  So I go into my FSX SE config file only to find that, that line does not exist.  My question is, should that line exist?

I actually went ahead and installed this line, saved it, closed it, and then restarted my computer.  After reboot, I started FSX:SE with the same error results.

 

[Thomas Richter]

Hi,

what is the installation Path of FSX and did you run the FSX installer with 'As Administrator' ? Also can you show the FSUIPC install log file.

Thomas

[RetiredFE]

1 hour ago, Thomas Richter said:

Hi,

what is the installation Path of FSX and did you run the FSX installer with 'As Administrator' ? Also can you show the FSUIPC install log file.

Thomas

This PC>Loca lDisk (C:) > Users > MyName > AppData > Roaming > Microsoft > FSX

This PC > Local Disk (C:) > Users > MyName > AppData > Roaming > Microsoft > FSX-SE

TB Drive (D:)  > Program Files (x86) > Steam > Steam Apps > Common > FSX

I did run FSX installer "As Administrator"

FSUIPC4 Install.log

[Pete Dowson]

8 hours ago, RetiredFE said:

Ok, I did as you said,

Does that mean you also tried Thoms's first suggestion, the one to see if FSX-SE ean okay with "NoWeatherAtAll=Yes" set in the [General] section of the FSUIPC4.INI file?

This is important to show once and for all whether it is related to weather corruption in some way. Then we know whether to look elsewhere or not!

You should also cettainly try testing without that Weather prtogram running in any case. It may be due to something it is asking FSUIPC to do, after all!

Pete

 

[Thomas Richter]

Hi,

it's never a good idea to have FSX/ P3D installed in Programs Files folder as Windows always doesn't like programs to write to files (INI / CFG files) in that location.

I would run the latest FSUIPC4.974_Installer again as Administrator (right click on it), rename your FSUIPC4.ini file to i.e. FSUIPC4_org.ini. Delete also the FSUIPC4.log file to make sure you have only a new one existing.

Check the FSC.cfg that the flight that will be loaded is one with a default AC. Then start FSX and if it ask to run FSUIPC4.dll press OK/Yes.

Also I would check the DLL.XML and don't load other programs than FSUIPC4 to find may the problem twith other programs running.

Thomas

[RetiredFE]

1 hour ago, Thomas Richter said:

Hi,

it's never a good idea to have FSX/ P3D installed in Programs Files folder as Windows always doesn't like programs to write to files (INI / CFG files) in that location.

I would run the latest FSUIPC4.974_Installer again as Administrator (right click on it), rename your FSUIPC4.ini file to i.e. FSUIPC4_org.ini. Delete also the FSUIPC4.log file to make sure you have only a new one existing.

Check the FSC.cfg that the flight that will be loaded is one with a default AC. Then start FSX and if it ask to run FSUIPC4.dll press OK/Yes.

Also I would check the DLL.XML and don't load other programs than FSUIPC4 to find may the problem twith other programs running.

Thomas

Thomas, just want to say that this worked and thank you to all of you who have helped me with this problem.  Thanks for your patience and all of the help.   I hope I can avoid this in the future.  Been really frustrating in the last day or so trying to get this solved.  Again, thank you so much.  Greatly appreciated.

Rodger

[John G. New]

Hi all,

I have much the same problem.  This appeared after I hadn't used FSX/FSUIPC for about a month or so, and hadn't added any new add-ons in the meantime.  I get the following message:

Flight Simulator has detected a problem with a third party software (add-on):

Name:  FSUIPC4 DLL: FS new universal IPC interface

Version 4.974

Company: Peter L. Dowson

File: Modules\FSUIPC4.dll

If I try to run FSX with FSUIPC, the program immediately crashes.  The FSUIPC4.log reads:

********* FSUIPC4, Version 4.974 (24th February 2018) by Pete Dowson *********
Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
fsx.exe version = 10.0.62615.0
Running inside FSX Steam Edition on Windows 10
Module base=58B60000
User Name="John New"
User Addr="johngnew@gmail.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       16 System time = 14/04/2020 18:17:40
       16 FLT path = "C:\Users\John\Documents\Flight Simulator X Files\"
       16 ------ Module Version Check ------
       16        acontain.dll: 10.0.62615.0
       16             api.dll: 10.0.62615.0
       16        controls.dll: 10.0.62615.0
       16      fs-traffic.dll: 10.0.62615.0
       16             G3D.dll: 10.0.62615.0
       16        language.dll: 10.0.62615.0
       16            sim1.dll: 10.0.62615.0
       16        visualfx.dll: 10.0.62615.0
       31         weather.dll: 10.0.62615.0
       31          window.dll: 10.0.62615.0
       31 ----------------------------------
       47 NOTE: SimConnect Steam is supported, but it isn't installed.
       78 NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.
      109 Trying to connect to SimConnect SP1 May07 ...
      109 FS path = "D:\Program Files (x86)\Steam\steamapps\common\FSX\"
      469 ---------------------- Joystick Device Scan -----------------------
      469 Product= Saitek Pro Flight Quadrant
      469    Manufacturer= Saitek
      469    Vendor=06A3, Product=0C2D (Version 2.1)
      469    GUIDs returned for product: VID_06A3&PID_0C2D:
      469       GUID= {B8736240-B34E-11E7-8002-444553540000}
      469       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      469 Product= VKBsim Gladiator 
      469    Manufacturer= www.vkb-sim.pro www.forum.vkb-sim.pro © Alex Oz 2012-2016
      469    Vendor=231D, Product=0121 (Version 24.1)
      469    GUIDs returned for product: VID_231D&PID_0121:
      469       GUID= {B87250D0-B34E-11E7-8001-444553540000}
      469       Details: Btns=29, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U2047,V1023,X2047,Y2047,Z1023
      469 -------------------------------------------------------------------
      484 Device acquired for use:
      484    Joystick ID = 1 (Registry okay)
      484    1=Saitek Pro Flight Throttle Quadrant
      484    1.GUID={B8736240-B34E-11E7-8002-444553540000}
      484 Device acquired for use:
      484    Joystick ID = 0 (Registry okay)
      484    0=VKBsim Gladiator
      484    0.GUID={B87250D0-B34E-11E7-8001-444553540000}
      484 -------------------------------------------------------------------
      500 LogOptions=00000000 00000001
      516 -------------------------------------------------------------------
      516 ------ Setting the hooks and direct calls into the simulator ------
      516 --- CONTROLS timer memory location obtained ok
      516 --- SIM1 Frictions access gained
      516 --- FS Controls Table located ok
      516 --- Installed Mouse Macro hooks ok.
      516 --- Wind smoothing fix is fully installed
      516 --- SimConnect intercept for texts and menus option is off
      516 --- All links checked okay
      516 -------------------------------------------------------------------
      516 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!
      516 ... check whether you have a SimConnect.dll in your Modules folder. If so remove it!
      516 ... Now trying to connect to another version of SimConnect ...
      531 Trying to connect to SimConnect Original ...
      547 Now running with SimConnect Original
      547 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!
      547 ... check whether you have a SimConnect.dll in your Modules folder. If so remove it!
      547 ... Now trying to connect to another version of SimConnect ...
      547 FATAL ERROR: FSUIPC4 cannot connect to any supported version of SimConnect!
 

I'm a registered FSUIPC user and have run it for years without a problem.  I've tried the solutions posted above without any luck (and I do not have a SimConnect.dll in my Modules folder. Any ideas? (please be patient with me, I'm a bit of a computer idiot). 

[Pete Dowson]

38 minutes ago, John G. New said:

516 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!
      516 ... check whether you have a SimConnect.dll in your Modules folder. If so remove it!
      516 ... Now trying to connect to another version of SimConnect ...
      531 Trying to connect to SimConnect Original ...
      547 Now running with SimConnect Original
      547 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!
      547 ... check whether you have a SimConnect.dll in your Modules folder. If so remove it!
      547 ... Now trying to connect to another version of SimConnect ...
      547 FATAL ERROR: FSUIPC4 cannot connect to any supported version of SimConnect!

I don't know how you've done it, but you appear to have a lost or corrupted SimConnect install. You need to re-run the SimConnect installer. That will be an .msi file in the "Core Utilities" part of the FSX SDK. You must have had that somewhere if you started with FSX-SE. If you originally had FSX installed it would have installed with that.

Pete

 

[John G. New]

And that fixed it!  Not sure how it happened in the first place; must be my special genius for that sort of thing.  Anyway, thanks very much for your assistance, Pete!

Cheers

John

[begem0t]

On 4/15/2020 at 4:43 PM, Pete Dowson said:

I don't know how you've done it, but you appear to have a lost or corrupted SimConnect install. You need to re-run the SimConnect installer. That will be an .msi file in the "Core Utilities" part of the FSX SDK. You must have had that somewhere if you started with FSX-SE. If you originally had FSX installed it would have installed with that.

Pete

 

Had the same crashing problem, this fixed it. Thank you, Pete!
Funny enough the crash happened only when my bluetooth controller was connected...

[Ardriax]

On 8/14/2019 at 7:12 PM, RetiredFE said:

wont load the fsuipc even in admin mode

Install FSUIPC4.exe

4.9.7.4

5a915076

Install FSUIPC4.exe

4.9.7.4

5a915076

c0000005

00008b6d

b38

01d6e1d5491a448e

F:\Microsoft flight x\Install FSUIPC4.exe

F:\Microsoft flight x\Install FSUIPC4.exe

92bb4e5b-6a03-449e-a805-1441dd16a8d8

 

[John Dowson]

@Ardriax I don't understand what you posted, and why are you hijacking a problem that doesn't seem to be related to your issue?

Can you at least attach your installation log and you FSUIPC4.log file (if there is one), and explain what you mean by 'wont load the fsuipc even in admin mode'.
Do you mean that you cannot see FSUIPC in the add-ons menu? Does FSX (or FSX-SE - I don't even know which sim you are using!) run or does it crash?

You also seem to be using an old unsupported version of FSUIPC4. Please update to the latest version 4.975 (or 4.975a) before posting again.

John