pbandpickleboy

Thanks for the responses Randy and Jim. Let me tell you what. I think I'm just going to make the switch to vPilot

Okay, I just uninstalled and reinstalled FSInn and FSCopilot. Nothing. Crash with an unknown module, but it occurred after authorizing FSZCopilot.dll.

Thanks, Jim. Here's what I've got. After moving dll.xml to a temporary folder, the simulator did indeed start with no issues. When it asks to authorize all the modules, it crashes after FSCopilot.dll. Disabling that module allows the simulator to start with no issues. I would think FSCopilot and FSInn would be installed properly since they worked just fine about a week ago, and long before that. I believe the ntdll.dll crashes occurred while I had FSCopilot.dll out of the Modules folder. It is currently in the Modules folder, so I'm thinking it somehow got corrupted somewhere. I will try uninstalling and reinstalling FSInn and FSCopilot.

Not exactly a CTD issue, but here goes. I came hear about a year ago with a similar issue. When I go to open FSX, an error pops up saying it detected an error with FSCopilot.dll. Selecting "yes" to run it causes the simulator to crash and close. Selecting "no" allows the simulator to run just fine, but then I cannot connect to VATSIM. The initial error report showed FSCopilot.dll to be the faulting module, but I've also gotten ntdll.dll crashes, and a bunch of unkowns. I've attempted to repair FSX, after which I got 2 simprop.dll crashes, repair Acceleration, uninstall and reinstall Acceleration while repairing FSX in between, and remove FSX.cfg (copying it to a safe location first) in order to let the simulator rebuild it. All of these have been unsuccessful. Removing FSCopilot.dll from the Modules folder solves the issue, but I need that file to connect to VATSIM. The only change I made recently was installing the Project OpenSky 777, which is around when the issues started. I'm not sure if the two could be related, but I've since uninstalled the aircraft. A few other things that could be worth noting. I run FSInn on two computers, hosting FSCopilot on my laptop (the sim computer) and running the UI on another laptop. I run Windows 10 which was upgraded from Windows 7 a long time ago before this happened. I'm thinking my next attempt is going to be uinstalling and reinstalling FSInn and FSCopilot. I am aware that uninstalling and reinstalling FSX itself is a last resort. I remember deleting a line from the registry being a big help last time, but I don't know what line it was so I won't go messing around this time without help. I will also post this on the VATSIM forums in hope to get some combined wisdom. I appreciate any help I can get. Shame on me for using the wrong "here." Maybe I should proofread before posting next time. I also just want to add that the issue I had last year was very similar. but with FSUIPC4.dll. The ntdll.dll crashes were also, I believe, solely when that aircraft was installed if that makes a difference.

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.