I can't see anything wrong with that DLL.xml Carl. Not unless someone else can.

I have disabled the CS 737, so just disable it like I have highlighted in red. Being careful not to alter anything else.

Then see if fsx loads ok. It after midnight here, but will check your post in the morning.

 

<Launch.Addon>
<Name>Captain Sim 737 Sound</Name>
<Disabled>True</Disabled>
<Path>Captain_Sim\737\cs.sound.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>VistaMare Core</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>VistaMare\ViMaCoreX.dll</Path>
</Launch.Addon>
</SimBase.Document>

Here is just a copy of a few things I found in the applications events log that was during the times I cannot get FSX started:

 

Hope this will shed some light.

 

-

Dis regard. Need to redo since when I pasted it was scrambled.

Sorry,

Ok Carl then I guess you know what you are doing - that's good start, not sure whats going on

here is a copy of my dll.xm file

 

 

Hi Carl, i'm not sure what is the problem, but i have a couple of ideas...

 

- I see that you have Level-D installed. With Level-D, your first entry in xml.dll should be fsuipc entry and then second level-d. Also in Level-D menu in FSX, you should select option for Level-D menu to be visible only with LVD aircraft loaded. This can save you from some fsx freezes / crashes. I have edited DLL.XML for you, you can download modified DLL.XML here: https://www.dropbox.com/s/eopdkxw7xsfr76k/DLL.XML

 

 - For corrupted Logbook, i'm not sure if renaming can fix it. I never had this problem, but i know there are some tools to be used, like this: http://flyawaysimulation.com/downloads/files/1675/fsx-logbook-recovery/

or here from avsim http://library.avsim.net/esearch.php?DLID=&Name=&FileName=fsxlogrecovery11.zip&Author=&CatID=fsx

 

 - Maybe Jim can see more things in this crash log, i think that you have wrong version of uiautomationcore.dll. You can replace it with the right version, just to be sure https://www.dropbox.com/s/adxsx0mxb6wztil/UIAutomationCore.rar

 

Download appcrashview if you want, i am more familiar with this and maybe i can tell you more from that log. You can download it here http://www.nirsoft.net/utils/app_crash_view.html

 

I hope some things from my post will help you

Whatever you do, do NOT delete the dll.xml.

 

Follow the guidance provided by Zeljko above in regards to downloading and running AppCrashView and post your results here.

 

I'm moving this to the CTD Forum.

 

Best regards,

Jim

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Zeljko,

 

Thanks for all the helpful hints. I used the dll.xml file but still have the same problem. Also installed the updated uiautomationcore.dll and still no go. I have found the events log in administration and there are errors shown every time I tried to start FSX. Below is just one of the typcal errors I get. Unfortunately when I copy/paste it makes it difficult to follow in my post. Is there a good way to copy/paste from the events log similar to using the NotePad+

This is typical error found in event log. It appears to maybe have a problem with a UI.dll (??)

 

System

-Provider

[ Name] Application Error

eventID 1000

Qualifiers] 0

Level 2

 

Task 100

Keywords 0x80000000000000

TimeCreated

SystemTime] 2013-08-20T18:10:58.000000000Z

EventRecordID 99691

Channel Application

Computer Carl-PC

Security

- EventData

fsx.exe

10.0.61637.0

46fadb14

ui.dll

10.0.61637.0

46fadb59

c0000005

0003c963

ffc

01ce9dd0973abb39

C:\Flight Simulator X\fsx.exe

C:\Flight Simulator X\ui.dll

dc7a5d15-09c3-11e3-846f-4487fca83660

Hope this will show correctly to indicate what the events log is indicating. It is hard to teach an old dog new tricks but hope this help in solving my problem.

 

Your help is most appreciated.

 

Log Name: Application

Source: Application Error

Date: 8/19/2013 5:02:33 PM

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: 0x13c0

Faulting application start time: 0x01ce9d1f65c4c050

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

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

Report Id: aaa69283-0912-11e3-a989-4487fca83660

Event Xml:

just download appcrashview(see the link in my post above). Unzip, run appcrashview and find FSX last crashes by date and time. Copy and paste here, or better paste to notepad, microsoft office or something like that and attach here. Steps to attach - go to "more reply options", then "choose file" and "attach this file".

 

I can see more details in appcrashview, and especially Jim can see some other details about your system, fsx files, loaded modules at time of crash, etc.

 

BTW, what is your default flight in FSX? I saw this problem before when default flight was saved flight in FSX...

 

In FSX default flight should not be any of saved flights or with any other then default fsx aircrafts - everything else is looking for trouble.  You probably know that, but i'm trying to eliminate some posible scenarios  

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

New install is faster and the best at this stage of the game - you may have problems if you dont - repairs do not work and never will thats a given.

Zeljko,

 

 

I have tried all your good suggestions. If anything I am learning a lot more than what I knew when this all started. The bad news is the logbook app indicated my log was ok. The DLL file you sent did not change anything. I have ran the appcrashview and it did show every failure since it started in yesterday. I will try to copy and paste in the forum shortly.

 

I do not start with any of my default aircraft. Have always used a payware GA for startup for years with no problems until now. Was wondering if maybe the registry could have bee corrupted? I did replace my ui.dll file with a backup but no change.

 

Rich

Please don't use the word "reinstall". I will have a stroke if I have to think of all the tweaks, add-ons etc I would have to go through. I just hope there will be a cure other than a complete reinstall. I just can't understand by trying to install a fairly simple mod to CS 737 would cause this. As mentioned the first signal of possible problem was when after installing the mod to 737, the 737 planes just disappeared after restart from list of planes. When I went back to my default which was beech baron 55 Milviz there was a lock up. Had to use alt-ctrl-del. Restart of FSX never saw the light of day since.

The ui.dll error indicates a bad aircraft model, gauge, or texture.  Somehow you need to completely uninstall the CS aircraft and then reinstall it or try to simply reinstall it.  I think you said you had deleted the aircraft and, if you used it for your startup flight instead of the default, it is looking for the aircraft.  I would run a registry cleaner like CCleaner before trying to reinstall the CS aircraft.

 

Best regards,

Jim

HI Jim,

That makes sense since my CS was not my default but I wanted to change the default to the CS to make a short trip. Yes I did a compete uninstall using CS uninstaller and then reinstalled the CS but it still had the problem.

I think Flight 1 had a registry fixer. Not sure if it was for FSX though.

 

I have a text file using the software that Zeljko suggested. I would like to post in my reply but can't find where to put it. I thought it was always on the lower right corner. The txt file indicates everytime a UI problem.