pbandpickleboy

Okay, as far as I can tell, I fixed my problem. I think deleting a line from the registry was the fix, but I'm not entirely sure. After I reinstalled Acceleration, which was my final step, the FSUIPC error reappeared on startup, but when I hit "yes" FSX still opened. It looks like I might have to reinstall my addon aircraft, again I'm not entirely sure. I also had to change my settings. Is there any way to know what they were before my issues began? The final step will be a flight. I'll post back here if anything happens then.

I fixed the problem by repairing Acceleration, which I didn't do after repairing FSX. Now I'm back to the same issue on FSX startup with FSUIPC. This time, though, when I select to run it, FSX gets a fatal error and crashes instead of just closing. Here's on of the error reports: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: FSUIPC4.dll, version: 4.9.4.8, time stamp: 0x56378f44 Exception code: 0xc0000005 Fault offset: 0x0001e2f7 Faulting process id: 0x1c94 Faulting application start time: 0x01d128c7bd55554a 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\Modules\FSUIPC4.dll Report Id: 2991c38a-94bb-11e5-82cc-008cfaab31b3 Faulting package full name: Faulting package-relative application ID: Back to a crash in FSUIPC4.dll. I was going to try uninstalling Acceleration, repairing FSX, and reinstalling Acceleration. Any suggestions? I'm also waiting to get an answer from Pete at the FSUIPC forums.

Okay, so I didn't get a chance to try a flight without FSUIPC. However, as somebody in a Facebook group suggested, I inserted the disc and chose to repair. After it was finished, I tried running FSX. I am no longer having the issue with FSUIPC, but a fatal error occurs. When I get the crash report, it says this: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: simprop.dll, version: 10.0.61637.0, time stamp: 0x46fadb59 Exception code: 0xc0000005 Fault offset: 0x00006da7 Faulting process id: 0x2cc0 Faulting application start time: 0x01d128be2fccb85e 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\simprop.dll Report Id: a937b999-94b1-11e5-82cb-008cfaab31b3 Faulting package full name: Faulting package-relative application ID: Any ideas on how to fix this? Thanks, Mark

Okay. I'll look into trying a flight this weekend without FSUIPC. I'll let you know how it goes.

I honestly haven't tried without it. I need it to run DVA ACARS, which I would prefer, but if I have to live without, I guess I could.

I'm guessing at this point a full uninstall and reinstall are in store? That's probably just what I'll end up doing next.

That was the only file so I skipped it, I reinstalled FSUIPC. It seemed like it might work this time as it didn't find any traces of previous versions. However, as you can probably assume, I got the same error while starting FSX.

I turned UAC back on and got the same error. Are you talking about C:\Program Files alone, or C:\Program Files (x86) as well?

Nope. Should it be?

I tried deleting/moving the FSUIPC Install log from the Modules folder and got an error this time. Here's a link to a picture of it. http://i68.tinypic.com/96gw02.png Thanks Luke for the suggestion. I never even thought of that. As soon as I can move or delete that final file, I will try deleting the entries from both dll.xml and fsx.cfg.

Should I talk to them about the FSUIPC error upon FSX startup? I'm not worried about FSCopilot and FSInn since they don't seem to be causing any issues, nor have they in the past. There is one last thing I will try a little later when I get home. There's a chance I deleted the FSUIPC entries in the copy of dll.xml you suggested I make, not the actual dll.xml. I want to try deleting both entries again and deleting everything FSUIPC-related from the Modules folder. Then I'll reinstall FSUIPC again and see if anything changes. Could you just clarify what you meant by moving any lines below the last line up first? Perhaps that's where the issue is.

I made the fix and the problem still came up. I think I need FSCopilot on my laptop since I run FSInn on another, but correct me if I'm wrong.

I did reinstall FSUIPC. This is what my entire dll.xml looks like. <?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>Object Placement Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\Fsuipc4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSCopilot</Name> <Disabled>False</Disabled> <Path>Modules\FSCopilot.dll</Path> </Launch.Addon> </SimBase.Document> Ugh, I was hoping I wouldn't have to uninstall and reinstall, but if that's what enables me to fly again with FSUIPC, then so be it. Hopefully the code works again. Just out of curiosity, what could have caused the corrupted installation? As I probably said before, everything worked fine for over a year at least. It was just after the CTD that I had these problems. I'm just wondering what could have corrupted the installation. Thanks so much for your help thus far. I appreciate you examining everything and attempting to give solutions instead of just claiming that your software has nothing to do with it, as Pete did. Thank you so much.

The one I moved was the one in the hidden folder, which seemed to rebuild itself. When I moved the one in the main FSX folder, I couldn't open FSX. It's safe to say I put it back immediately. I uninstalled my one addon scenery. When I tried to load FSX, it said there was an error with scenery.cfg because Area 121 could not be found. Now there is no Area 121 in either scenery.cfg. I'm not sure if it removed it or it wasn't there in the first place. I may have uninstalled the scenery while the scenery.cfg in the main FSX folder was missing, if that could be a problem as well. I deleted everything from the Modules folder except FSCopilot.dll and FSSound.dll, which I believe are not FSUIPC-related. There were two entries in dll.xml that seemed to apply to FSUIPC. I deleted both and moved up the following lines so there were no gaps. I downloaded and installed FSUIPC v. 4.948. The new install log looked fine, but it did say that there was already an entry in dll.xml. There are two once again, which appear to be the same as the two I deleted. The first one looks like this: <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\Fsuipc4.dll</Path> </Launch.Addon> This is the second one: <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> There is an entry in between if that makes a difference. I tried to open FSX. This is when I got the error about Area 121 in the scenery.cfg. I still got the same error about FSUIPC after that. Where do we go now?

I deleted the text file. I then moved fsx.cfg and scenery.cfg from AppData\Roaming etc. to a temporary folder. I thought we might have made progress, but still no dice. Maybe I need to move the scenery.cfg in the main FSX folder? I can also try deleting the addon scenery and addon aircraft. This is a link to a picture of the error I've been getting, since you kind of asked about it. http://i68.tinypic.com/qz22k1.png

Thank you jmdriskell. I found both fsx.cfg and fsx.cfg.txt. Is the text file of any significance?

The path to FSX is C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X. I set it to run as administrator for all users. I also run it in compatibility mode for Windows 7, which I also set for all users. I moved uiautomationcore.dll to a temporary folder. I'm a bit nervous about doing so, but I disabled UAC via the Control Panel. I should have a new version of FSUIPC. I don't recall tweaking FSX.cfg, but I can post it if you'd like to verify. Later when I have more free time I can try moving fsx.cfg and scenery.cfg to a temporary folder and opening FSX. I do have one addon scenery and a bunch of addon aircraft, but none have caused issues before. We shall see. Thanks for such a long post and all your suggestions. I really appreciate it. I looked ahead but haven't tried anything yet since only a few minutes have passed :smile: Should fsx.cfg be in the main FSX folder? I don't see it there.

Hi all. This is my first post here and I'm looking for your wisdom. A few weeks ago my FSX crashed in the middle of a flight. The Windows crash report said the faulting module was Fsuipc4.dll. Pete Dowson, the creator of FSUIPC, said the FSUIPC log indicated that it was closing normally in a sequence that involved SimConnect and FSX closing normally. Ever since, I have been unable to open FSX and FSUIPC. You see, I could open it by declining to run FSUIPC, but I need it to run ACARS for my VA. When I try to open FSX, I get an error that says FSX has detected an issue with FSUIPC. When I attempt to load FSUIPC anyway, FSX closes and sometimes crashes. The first time and several times since, the Windows crash reports have said sim1.dll. The thing is, the past two times, I got one error in atc.dll and one in ai_player.dll. I'm not entirely sure what's going on. Pete said that the loading issue is a timing issue with SimConnect. A SimConnect log indicated that nothing was being loaded by SimConnect. He could not explain the crashes. He recommended reinstalling FSX, which I'd like to avoid, but I will try it if that's the best/only option. I would appreciate any help since this has caused me to be unable to fly for my VA, which is what I always do anyway. If it helps, I am running Windows 10 64-bit. Thanks, Mark