"SafeFSX.FLT "   is an install - you have to go load that flight in the main fsx menu

"SafeFSX.FLT "   is an install - you have to go load that flight in the main fsx menu

Hi Richard.

No it is not an install, its an FSX flight file.

 

Just did  it again. If I double click on it FSX starts with that Flight loaded. Trike at KFHR Friday Harbor.

Weird.

 

Ok Carl try this: Select that file SafeFSX.FLT and right click, choose Open With -> Choose Default Program -> Browse and navigate to your FSX folder, from there select Fsx.exe and Accept. (Works every time)

 

That dll.xml file is just for testing while you get your FSX working.

 

Cheers.

Hi Carl,

 

Speed reading through this thread indicates that you have probably done this already , but just in case:

 

What some of the posters above are trying to do is to get your CURRENT FSX install to a more-default condition by doing the following:

 

1. Resetting the startup in FSX to the Trike in the Seattle area. Forget whether you think the B55 is good or not- just get FSX back to a known simple plane at (hopefully) a known and unmodified airport. You can always change this back to something else later.

 

2. Rename FSX.CFG (so that you can get back to it later if required), and hopefully let FSX rebuild a new one.

 

3. Rename DLL.XML (like DLL.XML.bak), to get that file out of the loop.

 

4. Run FSX and get back on what happens.

 

Now- if FSX runs, first (given the above info you have provided where FSX crashed before a new FSX.CFG could be built), rename your renamed FSX.CFG back to FSX.CFG,a nd see if FSX will run. This would isolate the issue to DLL.XML

 

Having come this far, if FSX runs OK, then you have a lot of work to work through DLL.XML and find the errant entry. And many addons will not work until you do so. But at least we will know how to proceed with you.

 

Thanks, Bruce.

"FSXSafeStartup" is an executable file from flight1 just got it the other day it installs the flt file and you load in from fsx menu no doubt about that

Ramón

 

Yep, that is what I finally ended up doing but still no go. Your suggestion really should work unless something is really really gone bad. By the way this is all I get in the new fsx.cfg. So you can see it doesn't get far before it shuts down.

 

 

[GRAPHICS]

SHADER_CACHE_PRIMED_10=1693500672

[sOUND]

AmbientUIMusicVolume=-6.000000

 

"FSXSafeStartup" is an executable file from flight1 just got it the other day it installs the flt file and you load in from fsx menu no doubt about that

Yes Richard I agree, FSXSafeStartup.exe is the executable file, that installs those two files.

 

But the file we are referring to is SafeFSX.FLT, which in fact is a text file that you can open with Notepad or You can associate it to fsx.exe, so when you double click on it it wil launch FSX.

 

Cheers.

 

Ramón Yep, that is what I finally ended up doing but still no go. Your suggestion really should work unless something is really really gone bad. By the way this is all I get in the new fsx.cfg. So you can see it doesn't get far before it shuts down. [GRAPHICS] SHADER_CACHE_PRIMED_10=1693500672 [sOUND] AmbientUIMusicVolume=-6.000000

 

Darn...

 

Got to go home now, but: one way or another we will nail that sucker.

 

Cheers

Well I have gone through all the discussions we have had concerning my problem and unfortunately everything we have thrown at this has not worked. I did receive an update from windows with new framework 4.5 but still didn't solve it. I have put everything back in order with the old dll, fsx.cfg, and flight simulator files.

 

Ramón your detailed steps with the clean dll.xml started but stopped as experienced with all the other changes that were tried. Below is the latest events log, which still indicates stopping at the UI.DLL. Deleting the fsx.cfg still stops with the message I showed in the last post. I still haven't tried deleting any of the planes one by one or trying an old fsg.cfg file with DX9. Not sure if just using an old fsx.cfg might create more problems. Anyway I have had a breather and now will try once again to fix this thing before a starting a complete reinstall.

 

Thanks all,

 

Latest events log:

 

Log Name: Application

Source: Application Error

Date: 8/21/2013 11:13:25 AM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Carl-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: ui.dll, version: 10.0.61637.0, time stamp: 0x46fadb59

Exception code: 0xc0000005

Fault offset: 0x0003c963

Faulting process id: 0x1a98

Faulting application start time: 0x01ce9e80efc6f1c9

Faulting application path: C:\Flight Simulator X\fsx.exe

Faulting module path: C:\Flight Simulator X\ui.dll

Report Id: 39696971-0a74-11e3-a4c3-4487fca83660

Event Xml:

100021000x8000000000000099936ApplicationCarl-PCfsx.exe10.0.61637.046fadb14ui.dll10.0.61637.046fadb59c00000050003c9631a9801ce9e80efc6f1c9C:\Flight Simulator X\fsx.exeC:\Flight Simulator X\ui.dll39696971-0a74-11e3-a4c3-4487fca83660

 

Hello Carl

 

Ui.dll (and for that matter uiautomationcore.dll) errors are hard to track.

 

I have read of users solving it by doing only an FSX or Acceleration repair install and others by just simply reinstalling the latest version of FSUIPC.

 

Another guy Pierre-Jean just recently (August 2012) fixed it and posted his solution here at AVSIM: [FSX] [ui.Dll (?)] APPCRASH, A Fatal Error occured ... FsX done

 

 

This is a very interesting article I have tried to understand it but not sure if I can grasp all of it between the English and French However, it appears to be a similar problem. Is there a repair on FSX and Acceleration disk that can be used to try and repair fsx without losing all the add-ons? One other note is I have deleted all the files pertaining to the CS737 that I could find. It has not been reinstalled.

FSX "repair" function can be used, but you need to make a backup of all your texture replacement(if you have REX, GEX, FTXG etc)or to install them again after FSX repair, and after SP1+SP2 or acceleration. And SDK should be installed again. This way you can keep addon planes. I'm not sure that is the right solution if addon plane is the problem.

 

However, after you fix FSX or re-install(which is very unlikely to happen, of course  ), please make a backup. That is the only way to avoid this situations. Acronis true image seems to be the best solution for that.

 

Now back to troubleshooting - have you tried to repair logbook with some of that recovering tool or just renaming it? And have you tried to re-install FSUIPC? Some installers will overwritte your FSUIPC with older version and this can happen.

I'm still thinking about posible reasons, and how to save your FSX installation. Jim said that last crash report indicates bad aircraft model, gauge, or texture. We need to think about this

 

 

Is there a repair on FSX and Acceleration disk that can be used to try and repair fsx without losing all the add-ons?

 

When you insert your FSX disk, it will offer you the options of Repair or Uninstall.  How the individual who repaired his FSX/Acceleration without touching his addons (as stated in the link provided by Kabronicus) I do not know.  It will take out your scenery.cfg, your fsx.cfg, your dll.xml and exe.dll but you can copy these to a temporary directory.  Once the repair is completed you can start up FSX and see what damage has been done.  Your addon aircraft should still be there and any sceneries.  You should not return your old fsx.cfg to a repair.  I would leave that but at least you have the old one to use to enter the old values, maybe any tweaks.  You should be able to return your old scenery.cfg, dll.xml, and exe.dll.  You will have to go through the trust thingy that happens when you first start up fsx with a new config.  Before adding the dll.xml and the exe.dll, I would run fsx at least once and make sure it is up and running again with all of your addons.  Then I would replace the dll.xml and exe.dll.  If FSX does not start, then you know it was a corrupted value in one of these files.  That means you will have to reinstall the products listed in the dll.xml so that they will be properly entered into those files.  Hopefully you will not have to go through all of that. 

 

You have to understand Carl that I (and no one else) run the repair option very much.  I think I did it once a few years ago.  Here is a link on how to repair FSX that I found and it appears to be saying the same things I have stated above.

 

Hope this helps.

 

Best regards,

Jim

Jim is right on repairing - I have never seen that work, you need to re-install Carl spending to much time that could have been spent putting a solid fsx back together oh and don't load that CS file again lol

 

Jim is right on repairing - I have never seen that work, you need to re-install Carl spending to much time that could have been spent putting a solid fsx back together oh and don't load that CS file again lol

 

 

Guys welcome back to my "FSX has stopped Working" situation room.

 

Hey Rich that's OK I think I am getting closer to a re-install. WE all have spent to much time on this one.

I do agree, Jim -to date I have found very little evidence that the repair mode works especially with all the add-ons etc. Zeljko, I will rename the log file and then install FSUIPC to make sure the most recent version is installed (not Payware).

 

FSX "repair" function can be used, but you need to make a backup of all your texture replacement(if you have REX, GEX, FTXG etc)or to install them again after FSX repair, and after SP1+SP2 or acceleration. And SDK should be installed again. This way you can keep addon planes. I'm not sure that is the right solution if addon plane is the problem.

 

However, after you fix FSX or re-install(which is very unlikely to happen, of course  ), please make a backup. That is the only way to avoid this situations. Acronis true image seems to be the best solution for that.

 

Now back to troubleshooting - have you tried to repair logbook with some of that recovering tool or just renaming it? And have you tried to re-install FSUIPC? Some installers will overwritte your FSUIPC with older version and this can happen.

I'm still thinking about posible reasons, and how to save your FSX installation. Jim said that last crash report indicates bad aircraft model, gauge, or texture. We need to think about this

 

 

Zeljko, in my "Flight Simulator X Files" folder I have a logbook.lbr, logbook_; logbook bin file;

 

and a FSXlog application. Which one of these should I rename?

 

Update: Forgot I had already installed the software to try and fix the log book. That is what the FSXlog App is. Ran it again and it found no problems.

 

 

I do agree, Jim -to date I have found very little evidence that the repair mode works especially with all the add-ons etc.

 

I am truly interested as to what exactly happened as all you were doing was trying to install a gauge, a simple operation, and then you could not get into fsx.  I have never seen anything like this one before! 

 

I'm not really against using the repair function but it normally is there to return a file that accidently got deleted or removed by some addon program.  Personally I would try that first as that method should save you from reinstalling your addon aircraft.  Just save those files I recommended saving then run the repair, start up fsx and see what happens.  If it works, then you just need to return the dll.xml, and the working scenery.cfg your saved to replace the default.  You'll then have to remodify the fsx.cfg.  Heck, if that doesn't work, then a complete uninstall, running a registry cleaner like CCleaner, then reinstallation of fsx and all of your addons.

 

BTW, did you ever run a registry cleaner.  Perhaps something there got corrupted.  I think I recall you doing that after you uninstalled the CS product.

 

Best regards,

Jim

Forgot to mention, if you do uninstall/reinstall, use the following PMDG guide - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

 

Best regards,

Jim

 

Hi Carl,

 

Speed reading through this thread indicates that you have probably done this already , but just in case:

 

What some of the posters above are trying to do is to get your CURRENT FSX install to a more-default condition by doing the following:

 

1. Resetting the startup in FSX to the Trike in the Seattle area. Forget whether you think the B55 is good or not- just get FSX back to a known simple plane at (hopefully) a known and unmodified airport. You can always change this back to something else later.

 

2. Rename FSX.CFG (so that you can get back to it later if required), and hopefully let FSX rebuild a new one.

 

3. Rename DLL.XML (like DLL.XML.bak), to get that file out of the loop.

 

4. Run FSX and get back on what happens.

 

Now- if FSX runs, first (given the above info you have provided where FSX crashed before a new FSX.CFG could be built), rename your renamed FSX.CFG back to FSX.CFG,a nd see if FSX will run. This would isolate the issue to DLL.XML

 

Having come this far, if FSX runs OK, then you have a lot of work to work through DLL.XML and find the errant entry. And many addons will not work until you do so. But at least we will know how to proceed with you.

 

Thanks, Bruce.

 

 

Bruce,

Sorry I missed your post yesterday. I guess I was stressed out and just overlooked your post. Anyway I have just tried your suggestions and I am afraid to say FSX just doesn't want to get off the ground. I just can't believe it is this difficult to fix. Something is causing the execution to stop almost immediately after start up.

 

This is what I got from a clean fsx.cfg no dll.xml

 

[GRAPHICS]

SHADER_CACHE_PRIMED_10=1693500672

[sOUND]

AmbientUIMusicVolume=-6.000000