Hi guys.

 

I'm really bewildered here.

 

Two days ago I had a fine running FSX (T1). I then installed Ideal FLight Demo, and played around with it for an entire day - letting it start FSX with a generated .FLT file and some times I would start FSX my self - no problems.

 

Came home this afternoon, and right away installed the Reality XP wx500 for FSX. Then I installed the most recent update for Fs2Crew JS4100 voice edition. I then Uninstalled the Ideal Flight Demo.

 

As I wanted to launch FSX (T2), it crashed, and left me with an Ezdok window open that said: "Ezdok Camera Addon: FSX Process not found. FSX_handle=0". 

 

AppCrash View reported the faulting module to be FSUI.dll

 

Ok - so I paniced and did a series of things upon reading various suggestions online (tried to run FSX in between the actions listed below):

 

1. Uninstalled and re-installed Ezdok - no effect.

2. Uninstalled Reality XP and re-installed - no effect.

3. Uninstalled JS4100 and reinstalled - no effect.

4. Ran Flight 1 registry repair tool - no effect.

5. Tried to wok with the FSXML manager from Flight1, it found no errors.

6. Ran a Malware program, which found Reality XP.dll to be infected - removed the file to the ignore list - no effect.

7. Had FSX rebuild .CFG - no effect.

8. Renamed EXE.DLL and XML.DLL - no effect.

9. Removed AutostarX

BUT then

10. Re-installed the Ideal Flight, and had IF start FSX based upon a random generated flight - and voila. FSX started. I ended the flight and loaded my normal Default flight (the FSX stock default flight). I was able to launch the JS4100 alond with a working XP wx500.

 

I haven't been able to start FSX via the FPS limiter as normal, or via the normal FSX.EXE file. Nor can I launch FSX via for example the Fs2Crew config manager - only Ideal Flight can start FSX.

 

Very, very strange.

 

From the LOG of App crash, it seems, that FSX crashed the last time I used it (T1) with Program Combability report of Ideal Flight. When it crashed next time (T2) it was due to FSUI.DLL. 

 

I've attached the Appcrash file for the latest crash this evening(T3), for the first crash this afternoon (T2) and for the crash associated with T1. Also I've attached the .FLT file that IF uses to start FSX, along with the default .FLT file. 

 

Any help is much appreciated!

 

Mas

 

Win7 x64 bit FSX SP2.

Ezdok, FSX Shader, ENB, TrackIR, TONS of scenerys, FS Global Ultimate mesh Europe, UTX, GEX, AS2012 nerworked for textures, FS Global Real World Weather networked for weather, FSinn networked, IVAP networked, TOPCAT networked, FS Flight Keeper networked, FS water config, Registered FSUIPC 4.90, WideFS registered, Invidia Inspector setup per Tabs instruction UIAutomationCore.dll, Bojotes tweaked CFG...

Renaming the exe.xml and dll.xml is not good as these files do not rebuild and are needed by FSX to run (at least the dll.xml). 

 

I have found that fsx does not work well with the external fps limiter.  I would eliminate that program and use the internal fps limiter.

 

FSX started up okay when you reinstalled the Ideal Flight so not sure what the problem you are having now.  I have seen many having problems with FSX when the change the default FSX flight.

 

In your default.flt you have 15 Panels (Panel.1, Panel.2 etc.) and my default.flt has only 8 panels.  Maybe EZdok added the other panels?

 

The uiautomationcore.dll in your main fsx folder could be doing more harm than good if you accidentally place the wrong version in the folder.  The dll only fixes fsx menu crashes.  So, repeatedly hitting the menu will cause fsx to freeze up if you do not have this dll in the main fsx folder.  However, I have never had to install this add dll and have tried several times to replicate a menu crash but cannot.  I would remove the dll to a temporary folder.  Obviously, it did not prevent a crash so it didn't work.

 

Bojotes tweaked config has caused several FSX crashes.  Maybe a wrong tweak or setting.  I would get rid of it and start with a brand new fsx.cfg.  I saw that you did have fsx rebuild a new config and it had no effect.  I still say there is something wrong with your config.

 

FSInn has caused crashes if not properly configured as required by the developer.

 

Most of your crashes did not show a faulting module (or you edited it out) and no Exception Code was shown.  This is extremely rare.

 

As I recall, fsui.dll and main.dll are part of the files required for activation of fsx. 

 

Sorry I cannot provide a fix for your problem.  You have a lot of old programs being networked on a modern computer system.  It could be anything.

 

Best regards,

Jim

Renaming the exe.dll and xml.dll is not good as these files do not rebuild and are needed by FSX to run (at least the xml.dll).

 

--- They are back, and it had no positive effect.

 

I have found that fsx does not work well with the external fps limiter. I would eliminate that program and use the internal fps limiter.

 

--- as I said tried to not use it - no efffect.

 

FSX started up okay when you reinstalled the Ideal Flight so not sure what the problem you are having now. I have seen many having problems with FSX when the change the default FSX flight.

 

--- Only by launching FSX through IF is now possible.

 

In your default.flt you have 15 Panels (Panel.1, Panel.2 etc.) and my default.flt has only 8 panels. Maybe EZdok added the other panels?

 

--- most likely.

 

The uiautomationcore.dll in your main fsx folder could be doing more harm than good if you accidentally place the wrong version in the folder. The dll only fixes fsx menu crashes. So, repeatedly hitting the menu will cause fsx to freeze up if you do not have this dll in the main fsx folder. However, I have never had to install this add dll and have tried several times to replicate a menu crash but cannot. I would remove the dll to a temporary folder. Obviously, it did not prevent a crash so it didn't work.

 

--- I did have the crash caused by menu, so I guess I need it.

 

Bojotes tweaked config has caused several FSX crashes. Maybe a wrong tweak or setting. I would get rid of it and start with a brand new fsx.cfg. I saw that you did have fsx rebuild a new config and it had no effect. I still say there is something wrong with your config.

 

--- Since FSX won´t start normally, I think so too. A clean CFG did not solve the problem.

 

FSInn has caused crashes if not properly configured as required by the developer.

 

--- It is.

 

Most of your crashes did not show a faulting module (or you edited it out) and no Exception Code was shown. This is extremely rare.

--- I did not edit anything, but maybe I coopy/pasted the wrong info from ViewApp crash?

 

As I recall, fsui.dll and main.dll are part of the files required for activation of fsx.

 

--- ?

 

Sorry I cannot provide a fix for your problem. You have a lot of old programs being networked on a modern computer system. It could be anything.

 

--- You gave it a shot - I appreciate it. I guess the inherent 1-2 year re-install is inevitable...

 

Best regards,

Jim

I just went through that this month as I upgraded from the i7 2600K to the 4770K and new Haswell MB.  It's kind of fun in that you get to see what's slowing down FSX as you install a new addon.  I had unbelievable fps with just FSX/Acceleration installed at a minimum of 150 fps to 275 or maybe 290 fps.  Now I'm back in the real world with some fsx sessions at frames in the teens and rarely above 60 fps.  I haven't overclocked yet though and, even though the fps are sometimes in the teens, the sim is very smooth.

 

Good luck on your reinstall.  Make sure you completely uninstall FSX.  The following guide might be of assistance - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

 

Best regards,

Jim

Thanks again Jim! It's a pain, but somehow I always feel good when it's done - you're always better off performance wise afterwards...

 

Mas