pbandpickleboy

At this point I solved my problem, to the best of my knowledge by deleting a line from the registry. I'm going to try a flight tonight and I will post back here afterwards.

Alright, I'm back. I tried deleting everything out of the Modules folder, replacing fsx.cg, replacing scenery.cfg, and probably something else. Just now I tried repairing FSX, which gave an issue with simport.dll. I solved this by then repairing FSX Acceleration.Just as a note, I have FSX Gold. Now I'm back to the same problem where I can't run FSX and FSUIPC. This time, both fatal crashes gave an error report with FSUIPC4.dll as the faulting module. Here's what they said: 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: I think I may try uninstalling Acceleration, repairing FSX, and reinstalling Acceleration.

Just real quick, I would assume that includes uninstalling first?

Oh wow, okay. That might be worth a shot. Thanks.

That makes sense, actually. Apparently something asked FSX to close. I don't know what, which is what I'll try to find out at AVSIM. English is my native language. I have no trouble understanding. I'm good to go now that you explained again. One last thing, and please don't take this the wrong way, but you actually never responded to my update, only the points where I argued with you. Would it be worth trying other solutions detailed in the FAQ forum besides repeatedly trying to open FSX to solve the timing issue? This may be out of your realm since it's not exactly FSUIPC related, which I understand. Thanks again, Mark

Pete, I tried sending you a message since you closed my first thread, but it didn't work so I'll post it here. I sincerely apologize for arguing with you on my post. I'm just having trouble understanding what you're saying. For example, I still don't get how FSX, FSUIPC, and SimConnect could have closed normally. The simulator crashed for some reason, which I'm unaware of at this point, besides a suspicion of being in the menus. Perhaps explaining in the simplest of terms, as if I were a young child would help. Anyway, if you could take a look at my update from my most recent post before you locked the thread and respond, that would be much appreciated. To reiterate, trying repeatedly to open FSX hasn't solved the timing issue. There is still no new FSUIPC log, or a new SimConnect log. I got two Windows crash logs unrelated to FSUIPC, which you can't help with. Would it be worth trying some of the methods in the FAQ forums to solve the timing error besides repetition? Either way, I will take all the information to the FSX CTD forum at AVSIM, as you suggested. It's a shame you couldn't help, but that's not your fault. Apparently I have another issue that is not FSUIPC related, which is out of your realm. I'll report back if something else comes up in the meantime. Thanks, Mark

"Now the closing of FS may possibly not have been of your doing, but I don't know anything else which would instigate it unless you had some application sending the CLOSE message or a Ctrl-C keypress... "A crash? A crash would instigate the closing of FS. That's what happened. My best guess at this point is that while FSX was frozen, perhaps FSUIPC and SimConnect closed before the actual crash. Other than that, I don't know why the first crash was due to an issue with Fsuipc4.dll. Quite frankly, I'm not sure why it crashed at all, besides the fact that I was in the menus, but I already have UIAutomationCore.dll. That's a whole other discussion we won't get into here. "If the crash data was for the current version of FSUIPC..." Wait wait wait. I thought there was no crash in FSUIPC. I thought it closed normally. "You've not actually supplied such a log yet." I beg to differ. Why then, in several previous posts, did you talk about the log I gave? If you're saying I never gave a successful log, how then can you say about FSUIPC closing normally in the log? Would that not be successful? On the other hand, if you're saying I never gave a log with a supported version, I know. That's what I said, but you said in a previous post "As for a supported version of FSUIPC you have only shown a log of a successful run." "All the information I know of about the loading warning you are getting is in the FAQ thread I pointed you to." Hate to burst your bubble, but you never pointed me there. I pointed myself there. If I'm wrong about these things, please just explain better. I'm finding hard to understand you. It seems at times that you contradict yourself. As for an update, continuously starting up FSX and attempting to load FSUIPC anyway hasn't fixed itself yet. I suppose I'll try some of the methods in the FAQ forum to get rid of this issue. I also did update to 4.948. I did also get two Windows crash logs, but FSUIPC and SimConnect still don't appear to be opening, which I suspected because that's where the issue lies in the timing. One log was in atc.dll, and the other was in ai_player.dll. Not sure why, but that's an issue I'll take to the FSX CTD forum at AVSIM.

Then how did the Windows crash report, also at 18:56, indicate the faulting module was Fsuipc4.dll? Makes no sense to me. The log for the "successful" run was also using version 4.9.3.9, which, according to your own words, is unsupported. How then, could the log be with a supported version? I appreciate you coming out with new updates and versions so often. It shows your dedication to creating a version with few bugs. I've been downloading the versions you're giving me, for example, 4.947j, but due to whatever the real problem may be, it hasn't been loading. My issue now is that FSX is marking it as a problem, which is why I asked about the timing problem and following the steps to troubleshoot that. The Windows log, however, shows up as sim1.dll. I apologize if it is indeed an incorrect accusation, but since FSX is detecting a problem with FSUIPC upon startup, I would suspect it is involved somehow.

Yes, thank you Luke, but that was after the fact. I've been getting that ever since, which is what I will attempt to fix at another forum. The initial cash though was in Fsuipc4.dll, but with an old version

I don't see how you can say FSX closed normally after a session lasting 1 hour and 40 minutes. It crashed mid-flight due to an issue with FSUIPC, YOUR software! You read the log! Nonetheless, I will take my problem to the forum you suggested. Thanks anyway.

I just tried again and the simulator actually crashed this time when trying to open it. The log looks like another sim1.dll, but here it is: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: sim1.dll, version: 10.0.61637.0, time stamp: 0x46fadb59 Exception code: 0xc0000005 Fault offset: 0x0001abf7 Faulting process id: 0x1d7c Faulting application start time: 0x01d11593bda5f0cb 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\sim1.dll Report Id: ad392dfe-f0f8-4828-876a-d05a82a0af6b Faulting package full name: Faulting package-relative application ID: All the files you listed are in the Modules folder, but they are described as "configuration settings" and "text files." The last FSUIPC log leads back to the date of the initial crash and reads this: ********* FSUIPC4, Version 4.939e by Pete Dowson ********* Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\Fsuipc4.ini" Running inside FSX on Windows 7 Module base=56100000 User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired 1641 System time = 23/10/2015 17:17:37 1641 FLT path = "C:\Users\Mark\Documents\Flight Simulator X Files\" 1750 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1813 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" 2828 LogOptions=00000000 00000001 2828 --- CONTROLS timer memory location obtained ok 2828 --- SIM1 Frictions access gained 2828 --- FS Controls Table located ok 2828 --- Installed Mouse Macro hooks ok. 2828 --- Wind smoothing fix is fully installed 2828 --- G3D.DLL fix attempt installed ok 2844 SimConnect_Open succeeded: waiting to check version okay 2844 Trying to use SimConnect Acc/SP2 Oct07 11063 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 11063 Initialising SimConnect data requests now 11063 FSUIPC Menu entry added 11188 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT 11188 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 65344 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\DVA_B767_300\767-300ER-GE-CF6-80C2.AIR 90469 C:\Users\Mark\Downloads\PHNL-KLAX.PLN 100828 System time = 23/10/2015 17:19:17, Simulator time = 14:17:47 (00:17Z) 105844 Starting everything now ... 106953 ASN active function link set 106953 Ready for ASN WX radar 109375 Advanced Weather Interface Enabled 218563 Weather Mode now = Global 5923016 System time = 23/10/2015 18:56:19, Simulator time = 13:55:03 (22:55Z) 5923016 *** FSUIPC log file being closed Minimum frame rate was 11.0 fps, Maximum was 16.8 fps Minimum available memory recorded was 2693Mb Average frame rate for running time of 5777 secs = 16.0 fps G3D fix: Passes 11776, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 5281 Allocs, 5281 Freed ********* FSUIPC Log file closed *********** I also followed the instructions to get a SimConnect log, which reads this: 0.00000 SimConnect version 10.0.61259.0 0.02886 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.04574 Server: Scope=local, Protocol=IPv6, Address=::1, Port=51441, MaxClients=64 0.05344 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=51442, MaxClients=64 5.05304 Panels data export found and set to 20B319D8 Hopefully this isn't too much information for you. Would it help to try some of the solutions described in the one FAQ subforum post about solving the issue, or since it appears to still be sim1.dll do I need a different solution? Just one last note that this just happened from a different location than where I usually fly. Not sure if that could make a difference, but I could try again at home if you need me to.

The new file didn't solve the problem. There don't seem to be any crash reports or logs, either in the Modules folder or in Event Viewer.

The aircraft is definitely installed correctly because I've used it before with no issues. I still could not open FSX with 4.947c. I don't think it gave a crash report. FSX just detected an issue, and if I select to run it anyway, which I have to in able to use ACARS for my VA, it just closes.

Hi, I was just doing a flight in FSX when the sim crashed. I attempted to reload it, but it detected an issue with FSUIPC. If I selected to run it anyway, it would not load and would just crash again. If I didn't it worked fine, but I need this version of FSUIPC to connect to ACARS for my VA. Any help would be appreciated. Here's the log from the initial crash: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: Fsuipc4.dll_unloaded, version: 4.9.3.9, time stamp: 0x54f46d0c Exception code: 0xc0000005 Fault offset: 0x00085231 Faulting process id: 0x14fc Faulting application start time: 0x01d10dd8325f4947 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: Fsuipc4.dll Report Id: eb9ed4f0-bc4e-4d40-8451-daa469a719ce Faulting package full name: Faulting package-relative application ID: Here's a log from a crash after attemtping to reload FSX with FSUIPC: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: sim1.dll, version: 10.0.61637.0, time stamp: 0x46fadb59 Exception code: 0xc0000005 Fault offset: 0x0001abf7 Faulting process id: 0x1004 Faulting application start time: 0x01d10de65f1d471d 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\sim1.dll Report Id: d8496ca3-ffa7-40e0-9cbe-6cdb2db060fa Faulting package full name: Faulting package-relative application ID: Again, any help would be greatly appreciated so I can return to flying ASAP. Thanks, Mark