FSX has detected a problem with third-party software program (add-on) FSUIPC4

[arod291]

Hello Mr. Dowson,

I receive this error (FSX has detected a problem with third-party software program) upon initializing FSX.  I have a paid copy of FSUIPC and currently using version 4.966c on a Windows 10 Home 64 Bit.  I've been using FSUIPC for quite a long time without any issues. The last time everything worked without any issues was Sunday May 16th, 2021.  I made a change in the FSX.cfg that day and that is, I added the line DisablePreload=1 under [Main].  The reason I did this was because FSX had been taking pretty long to load and so I did some research and came upon this fix.  I also removed some airplanes I really did not use (which potentially could've caused issues with some add-ons so I brought them back).  I then shut down FSX and restarted FSX.  Everything worked well even though the latency on FSX to load did not change a bit. At the end of my flying I shut down FSX as well as the PC and went my way.  

The next day I booted up my PC and immediately noticed Windows Update was running.  It ran for about an hour. Once it finished the update, FSX started booting up.  I currently have FSX set to start automatically as soon as PC is booted up.  In the middle of FSX booting up, the power went out just momentarily (it flickered). I then booted up the PC once again. FSX began to load and I noticed it took longer than usual before it prompted me with this message:

What I have done so far.... I reverted back everything I had done on Sunday.  Brought back the airplanes into the Airplanes folder and removed that line in the FSX.cfg file. I was still getting the same error message after reverting those changes.  I then did some troubleshooting after I found some of your recommendations on other posts.  I emptied the dll.xml from all modules being loaded and left only the lines for the FSUIPC module but FSX crashed with the same error msg.  I then added all the other modules to the dll.xml, saved it and ran FSX once again, but once again I got the error msg. The FSUIPC4.log file is pretty long but I believe it's not logging anything since Sunday May 16th.  I am adding the first few lines and if you determine that you need to see the entire log, I will add it in here. Below you'll also see the Windows Event log with the error being thrown.  Please let me know if you need me to include the add-ons list or FSUIPC.ini file or anything else.  Thank you so much sir.

Partial Log File
********* FSUIPC4, Version 4.966c (17th April 2017) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0)
fsx.exe version = 10.0.61637.0
Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"
Running inside FSX on Windows 10
Module base=6E850000
User Name="XXX XXXX" --removed for privacy
User Addr="xxxxxxx@gmail.com"
FSUIPC4 Key is provided
WideFS7 Key is provided
       16 System time = 16/05/2021 17:46:54
       47 FLT UNC path = "\\PCXXXX\Flight Simulator X Files\"
       63 ------ Module Version Check ------
       63        acontain.dll: 10.0.61637.0
       63             api.dll: 10.0.61637.0
       63        controls.dll: 10.0.61637.0
       63      fs-traffic.dll: 10.0.61637.0
       63             G3D.dll: 10.0.61637.0
       63        language.dll: 10.0.61637.0
       63            sim1.dll: 10.0.61637.0
       63        visualfx.dll: 10.0.61637.0
       63         weather.dll: 10.0.61637.0
       63          window.dll: 10.0.61637.0
       63 ----------------------------------
      156 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      219 FS UNC path = "\\PCXXXX\Microsoft Flight Simulator X\"
     1047 ---------------------- Joystick Device Scan -----------------------

Windows Event - Application Error
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: ai_player.dll, version: 10.0.61637.0, time stamp: 0x46fadb57
Exception code: 0xc0000005
Fault offset: 0x00037399
Faulting process id: 0x2220
Faulting application start time: 0x01d74dbf68fba05e
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll
Report Id: 530b3afc-f7de-43d3-af7d-af801b37ddde
Faulting package full name: 
Faulting package-relative application ID: 

[Pete Dowson]

8 hours ago, arod291 said:

but once again I got the error msg. The FSUIPC4.log file is pretty long but I believe it's not logging anything since Sunday May 16th.  I am adding the first few lines and if you determine that you need to see the entire log, I will add it in here.

If no new log is being produced it just means Windows determined that the last time FSX crashed, it thought FSUIPC was the culprit.  FSUIPC isn't actually crashing this time, otherwise a new log would be produced. Did you try saying "Yes" instead of "No"?

8 hours ago, arod291 said:

Below you'll also see the Windows Event log with the error being thrown. 

What happens when FSX crashes for any reason, FSUIPC still has threads running which try to tidy up. It means that it is seen as the reason or the crash when it is not. In the case you display here, the culprit shown in the Event log is:

8 hours ago, arod291 said:

Faulting module name: ai_player.dll

which is the part of FSX handling AI Traffic. This suggests there may be a corrupt traffic file, or more likely a corrupt AI aircraft texture.

If FSUIPC crashes, the log so far is important, and needs to be shown to the end -- the last thing it did would be a prime clue as to the cause, so truncating it as you have done tells us little. If the file is large (which it shouldn't be if you've not enabled extra logging options) then you can ZIP it up and attach it.

8 hours ago, arod291 said:

In the middle of FSX booting up, the power went out just momentarily (it flickered). I then booted up the PC once again. FSX began to load and I noticed it took longer than usual before it prompted me with this message:

So, your power outage is the original cause of the crash? But there was no FSUIPC log?

I think you need to assume the crash was because of that power outage, not FSUIPC, and let Windows continue loading it.

Pete

 

[arod291]

6 hours ago, Pete Dowson said:

If no new log is being produced it just means Windows determined that the last time FSX crashed, it thought FSUIPC was the culprit.  FSUIPC isn't actually crashing this time, otherwise a new log would be produced. Did you try saying "Yes" instead of "No"?

When I clicked Yes, it just closed itself up within a few seconds.  When I clicked No, I'm trying to recall exactly what it did, but I do remember it just does nothing at all. I will try to say "No" again so I can be a little more specific about it when I describe it to you.

6 hours ago, Pete Dowson said:

If FSUIPC crashes, the log so far is important, and needs to be shown to the end -- the last thing it did would be a prime clue as to the cause, so truncating it as you have done tells us little. If the file is large (which it shouldn't be if you've not enabled extra logging options) then you can ZIP it up and attach it.

Right, I fully understand. The reasons I didn't attach it was because it seemed lengthy and because it seemed as if the last time it logged anything was Sun. May 16th so I figured it served no purpose.  I am currently at work but will attach it later this afternoon.

6 hours ago, Pete Dowson said:

So, your power outage is the original cause of the crash? But there was no FSUIPC log?

I think you need to assume the crash was because of that power outage, not FSUIPC, and let Windows continue loading it.

Well, to be honest with you, I was just stating some of the possibilities of what could've happened. The Windows Update might be the culprit, or perhaps the crash left some temp files that perhaps you're aware of and are now causing issues.  Or given the fact that the AI DLL is the one with the issue, it might be related to those airplane folders I had moved, even though I did placed them back afterwards.  

 

I'm gonna check the Temp folder and delete all its contents just to make sure.  I'll also check to make sure the airplane profiles in the FSUIPC.ini are not pointing to one of those I removed and if it is then I'll remove all its reference from the ini file.  I understand I added all those airplanes folder back but still I'd like to troubleshoot that just in case.

 Thank you for the quick reply sir.

[arod291]

Hello Again Mr. Dowson,

I am not able to attach any files bigger than 1.5kb so I am adding the text here.

As I mentioned earlier re: troubleshooting ...I just cleared everything in the Temp folder just to cover my bases. I restarted and got the same error. I clicked "No" on the popup and FSX started up.  I then chose any random airports from the Freeflight and it started perfectly fine but when I clicked the Add-ons it doesn't display FSUIPC. In fact it only displayed 2 add-ons out of several I have.  I then removed all the lines referencing every airplane(profile) from the FSUIPC.ini file, being careful not to alter anything else, and then restarted FSX but the error came up again. 

PS I no longer see any event errors being thrown related to the AI dll or anything else.  However, I did noticed in the log file where it fails to load linda.exe on line 1266.  Linda.exe is not in my Modules folder for some strange reason and I have no clue how it dissapeared from there.  Could this be the issue?  I removed the line in the INI file that loads linda.exe and still got the error.

Thank you!

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

FSUIPC.log [deleted] - Deleted due to not been found valid in order solve the issue. 

[Pete Dowson]

9 hours ago, arod291 said:

I am not able to attach any files bigger than 1.5kb so I am adding the text here.

Log files are text files. They do ZIP up really small. Please do that in future.

And the reason your log is bigger that it needs to be is that you have enabled additional logging options. There's no need at all to enable button and axis logging. those are only used for limited period when looking for problems with buttons or axes!

9 hours ago, arod291 said:

I restarted and got the same error. I clicked "No" on the popup and FSX started up. 

It is NOT an error. It simply means that FSX crashed the last time and Windows thinks it might be due to FSUIPC! I already explained that.

By answering NO every time FSUIPC is never getting started, let along crashing. You need to answer YES, as I also said, and then, if FSX crshes, show me the Log up to that point AND the Windows Event Viewer details for that crash.

If you don't do these things there's no way I can help you!

Quote

 when I clicked the Add-ons it doesn't display FSUIPC. 

Of course it doesn't, as you told Windows not to allow it to be loaded!

Quote

PS I no longer see any event errors being thrown related to the AI dll or anything else. 

Unless you let the error occur you won't get any error details logged. You are just getting the warning and telling Windows to avoid loading FSUIPC. That helps no one.

10 hours ago, arod291 said:

However, I did noticed in the log file where it fails to load linda.exe on line 1266.  Linda.exe is not in my Modules folder for some strange reason and I have no clue how it dissapeared from there. 

Well you've been saying you been deleting things all over the place. FSUIPC won't be deleting anything, and in any case you aren't even allowing it to run.  Error 2 simply means "file not found".

Quote

Could this be the issue? 

No, because FSUIPC doesn't care whether you run Linda or not.

Quote

I removed the line in the INI file that loads linda.exe and still got the error.

Where do you see that? The log you are posting is from 5 days ago. You've not tried to run FSUIPC since.

The log you posted, dated the 17th, shows a perfect session with FSX and FSUIPC terminating normally. There is nothing wrong, except that you have lots of logging enabled which I don't need to see and I don't suppose you do either.

Please do read what I'm saying. If you think you have a problem with FSUIPC, let it run, then show me the details. It is isn't allowed to run it tells us nothing at all.

Pete

 

 

[arod291]

18 hours ago, Pete Dowson said:

It is NOT an error. It simply means that FSX crashed the last time and Windows thinks it might be due to FSUIPC! I already explained that.

By answering NO every time FSUIPC is never getting started, let along crashing. You need to answer YES, as I also said, and then, if FSX crshes, show me the Log up to that point AND the Windows Event Viewer details for that crash.

If you don't do these things there's no way I can help you!

That's fine I see it as an error and if you take a look at the title on the dialog, it says "error".

As I said before when I clicked "Yes" it would close FSX and the log file wasn't being touched. That's the reason I didn't include the entire log on my first post.

Anyhow, I appreciate your help trying to look into this. I was able to solve the issue by removing and re-installing FSUIPC. I did save the old INI file so I could get all my profiles and settings back into it and now FSX is back to normal.

Again, thank you for looking into this. 

[Pete Dowson]

5 hours ago, arod291 said:

As I said before when I clicked "Yes" it would close FSX and the log file wasn't being touched.

And is there then an entry in the Event Viewer explaining why?  The first thing FSUIPC does if it is loaded is create the log, so if it got as far as being loaded it would have replaced the one you have with an empty one at least.

5 hours ago, arod291 said:

I was able to solve the issue by removing and re-installing FSUIPC

That really doesn't change anything in FSUIPC -- replacing the code module withthe exact same code module. But maybe since the date on the file would change Windows cleared its error flag.

Aha! For a Windows-enforced crash like that (which wasn't clear to me before, sorry), this FAQ subforum entry by another user deals with the registry fix for it:

It didn't occur to me to refer you to this because there's been no sign of a crash actually in FSUIPC -- the only one you found was in AIPlayer.

Pete

 

[arod291]

14 hours ago, Pete Dowson said:

That really doesn't change anything in FSUIPC -- replacing the code module withthe exact same code module. But maybe since the date on the file would change Windows cleared its error flag.

Aha! For a Windows-enforced crash like that (which wasn't clear to me before, sorry), this FAQ subforum entry by another user deals with the registry fix for it:

To be honest I thought about doing a system restore but then I thought about just removing FSUIPC and installing it again since it would create less of a problem.  I really don't know what happened and you're probably right, windows cleared the error somehow.  My guess is either Windows Update did something to have FSX mistrust the DLL or perhaps when I prematurely turned off the system while FSX was booting up, something was left lingering around that caused FSX to mistrust the DLL afterwards.  I don't know for sure but thank God it's back to normal.

Thank you sir and apologies for the long log file!