Still hunting around and just can't pinpoint a cause for the crash. Replace the uiautomationcore.dll, looked for errors in the event viewer, everything I can think of. I may now have to start playing with the clocks and see what I can get becuase at the moment I wouldn't even think about doing a proper flight, all the time wasted with setup, then crash.

Well I am back and now on the computer again. Looking through the details of 1000 errors I can't find anything in the System or Userdata sub-menus related to FSX. Is there somewhere else I should look?

 

Everytime you have a crash on your computer an "Event" is recorded to help Microsoft Technicians determine the cause of the crash. It also records other 'events' on your system that might have failed or inform you that something worked properly and your system is secure. There are a multitude of events. I try to fix those that show up everyday on my system that shows an error occurred or there is a warning that something went amiss. Open up Event Viewer. On the left side click on Custom Views then Administrative Events. In the middle column you will see all of the individual events recorded (I have 1,729). In the right column of the Event Viewer you will see Actions. Click down to View and click on Preview Pane. Okay, now when you click on an event, just below it you will see a preview of the error - a general view of the error with the option to look online for additional help and you will see a details tab which provides information about your crash in Friendly View or XML View. Usually you can avoid looking in the details tab as the general tab provides sufficient information to diagnose your problem. In the list of Events, go down the list to the time and date of your last FSX crash and click on it. You will then see such things as:

 

Faulting application name

Faulting module name

Exception code

Fault offset

Faulting process id

Faulting application path

Faulting module path

 

We need to see this type of information in order to help you. The uiautomationcore.dll is just one of many faulting modules and it doesn't necessarily prove this was the cause of your crash. An Exception Code of 0xc0000005 indicates you had a memory access violation and that could be narrowed down to wrong memory timings/frequencies/voltages or wrong CPU voltages. Since uiautomationcore.dll is part of the Microsoft.net framework package, it could mean you're missing a certain version of Microsoft.net as versions are not backward compatible. A developer might have developed a product using Microsoft.net V 1.1 and you have only V 4 installed. So this information is important to help you. Unfortunately there is no 'magic bullet' that will fix your problem immediately. It has to be investigated and different things checked out to find the true Source of the problem.

 

Best regards,

Jim

Thanks, finally found it! Here is the general details on the crash:

 

 

 

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

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00000000

Faulting process id: 0xd28

Faulting application start time: 0x01cd244baad001cd

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

Faulting module path: unknown

Report Id: d150fb3f-9042-11e1-b83a-1c6f65c556f5

 

thanks,

What version of FSUIPC do you have installed?

Pretty sure its 4.6 Word Not Allowed