Sparky7 Posted January 24, 2018 Report Posted January 24, 2018 I am new to this forum having recently purchased a full licenced version of FSUIPC4 version 4.972. I am currently running FSX SE with a CH throttle quadrant and a Black Widow XE joystick. My hardware platform is a DELL XPS 8920 64 bit machine running windows 10. Hopefully the fault description, and the supporting info supplied, conform to Pete Dowson’s helpful guide on problem reporting so here goes… Any thoughts or suggestions would be most helpful J Problem description: FSUIPC4 installed in trial mode and worked fine in FSX-SE, I re-installed having purchased a licence key, the install was successful and again FSX-SE worked correctly and displayed the options menu and the fully tabbed interface. So far so good… then at some point FSX SE crashed (probably following a period when the machine was in sleep mode) but before I had set up any control axis, buttons, etc. The next time I ran FSX-SE it complained that it didn’t like the FSUIPC4.dll and gave me the option to run the FSX with and without the FSUIPC software. Running without allows FSX SE to run normally, running with it now causes FSX SE to hang and then close. Problem data logs: The associated windows application report shows an app crash. See attached file. Also seen is a windows application report citing a SidebySide error. See attached file. I have not been able to find the FSUIPC.log or FSUIPC4.log I suspect these have not been created since I never got as far programming up the CH throttle etc. The DLL.xml is attached The Install FSUIPC4.log file is attached dll.xml FSUIPC4 Install.log Windows app crash report.txt Windows SidebySide error report.txt
Pete Dowson Posted January 24, 2018 Report Posted January 24, 2018 15 minutes ago, Sparky7 said: The next time I ran FSX-SE it complained that it didn’t like the FSUIPC4.dll and gave me the option to run the FSX with and without the FSUIPC software. Running without allows FSX SE to run normally, running with it now causes FSX SE to hang and then close. This is a well known problem which is a combination of Windows marking the DLL as unwanted, and SimConnect, par of FSX, ignoring the error Windows returns when it tries to load the DLL. SimConnect actually assumes the DLL is loaded and jumps to where its entry point should be -- result, crash. When a program crashes, as your FSX-SE did, then Windows marks the last DLL left stuck running memory as "bad" which stops it loading next time. Re-run the FSUIPC4 Installer. The installer clears the Registry flag which tells the system not to load it. Pete
Sparky7 Posted January 24, 2018 Author Report Posted January 24, 2018 Hi Pete, Many thanks for the prompt reply and solution!. I re-installed as suggested and approved the dlls inclusion at start up... FSX ran ok. Subsequent re-starts have not shown a recurrence of the error message. Paul
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now