November 27, 201510 yr Author 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
November 27, 201510 yr According to the AVSIM CTD Guide: Simprop.dll – Most likely a problem with the installation of Acceleration. Try uninstalling Acceleration (go to Add/Remove Programs; look for FSX and click on uninstall. It will only uninstall Acceleration. FSX will still be there). Run FSX once and see if this fixed the program. If so, reinstall Acceleration with Admin privileges. Run FSX again to make sure the problem is fixed. If problem not fixed - Remove your FSX or P3D.cfg and let the configuration rebuild. If this does not fix the problem, rename your logbook.bin in the My Documents/Flight Simulator X Files folder and try running FSX again. If that works, then you might want to download from the AVSIM Library a program called FSX Logbook Recovery 1.1 and try to repair the one you renamed. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
November 27, 201510 yr Author 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.
December 3, 201510 yr Author 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.
Create an account or sign in to comment