is there any fix for this issue. I have a couple of tweaks added to fsx already like UIAutomationCore.

Log Name:      Application

Source:        Windows Error Reporting

Date:          6/7/2014 7:56:07 PM

Event ID:      1001

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      User-PC

Description:

Fault bucket 296601097, type 17

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: fsx.exe

P2: 10.0.61472.0

P3: 475e17d3

P4: unknown

P5: 0.0.0.0

P6: 00000000

P7: c0000096

P8: 0ede35a0

P9: 

P10: 

 

Attached files:

C:\Users\User\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt

C:\Users\User\AppData\Roaming\Microsoft\FSX\dxdiag.txt

C:\Users\User\AppData\Roaming\Microsoft\FSX\scenery.cfg

C:\Users\User\AppData\Roaming\Microsoft\FSX\fdr.dat

C:\Users\User\AppData\Roaming\Microsoft\FSX\dll.xml

C:\Users\User\AppData\Local\Temp\WER22D4.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\Users\User\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_6b7dcde030948f96adc1312c01addc5494c4af4_120148ca

 

Analysis symbol: 

Rechecking for solution: 0

Report Id: 443e093e-ee9f-11e3-9ce4-50e549c454c9

Report Status: 0

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Windows Error Reporting" />

    <EventID Qualifiers="0">1001</EventID>

    <Level>4</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-06-07T23:56:07.000000000Z" />

    <EventRecordID>12539</EventRecordID>

    <Channel>Application</Channel>

    <Computer>User-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>296601097</Data>

    <Data>17</Data>

    <Data>APPCRASH</Data>

    <Data>Not available</Data>

    <Data>0</Data>

    <Data>fsx.exe</Data>

    <Data>10.0.61472.0</Data>

    <Data>475e17d3</Data>

    <Data>unknown</Data>

    <Data>0.0.0.0</Data>

    <Data>00000000</Data>

    <Data>c0000096</Data>

    <Data>0ede35a0</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    <Data>

C:\Users\User\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt

C:\Users\User\AppData\Roaming\Microsoft\FSX\dxdiag.txt

C:\Users\User\AppData\Roaming\Microsoft\FSX\scenery.cfg

C:\Users\User\AppData\Roaming\Microsoft\FSX\fdr.dat

C:\Users\User\AppData\Roaming\Microsoft\FSX\dll.xml

C:\Users\User\AppData\Local\Temp\WER22D4.tmp.WERInternalMetadata.xml</Data>

    <Data>C:\Users\User\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_6b7dcde030948f96adc1312c01addc5494c4af4_120148ca</Data>

    <Data>

    </Data>

    <Data>0</Data>

    <Data>443e093e-ee9f-11e3-9ce4-50e549c454c9</Data>

    <Data>0</Data>

  </EventData>

</Event>

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.

With the very limited information you provided, it would be impossible to diagnose. You are running FSX SP2. The crash report above is what would have been sent into Microsoft had they been in existence to diagnose FSX crashes but they are no longer in existence. Therefore we (I) do not have the luxury of seeing the following files that would have been sent to them:

 

C:\Users\User\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt

C:\Users\User\AppData\Roaming\Microsoft\FSX\dxdiag.txt

C:\Users\User\AppData\Roaming\Microsoft\FSX\scenery.cfg

C:\Users\User\AppData\Roaming\Microsoft\FSX\fdr.dat

C:\Users\User\AppData\Roaming\Microsoft\FSX\dll.xml

 

This is why AVSIM strongly recommends you look at the AVSIM CTD Guide located to the right of this forum under Hot Spots. It provides a link to AppCrashView which you can download and run. You should then post the latest crash report to this topic for analysis. It provides you with many other possible solutions to your problem, like renaming or moving your fsx.cfg to another directory like C:/Temp, restarting FSX and see if that fixes the problem. Another suggestion would be to disable any addon scenery in your Scenery Library and disabling any modules in your dll.xml that might be causing this problem. It shows you how to do all of this in this guide.

 

You stated you employed the uiautomationcore.dll in your main FSX directory. That may be good and it could be bad. If you deployed the wrong version or a 64 bit version instead of a 32 bit version, that could cause even more problems. Just simply stating you added this so-called "tweak" doesn't mean anything. Most individuals are eliminating their CTD's/Freezes by removing this module from their main fsx directory. The AVSIM CTD Guide explains more about the proper versions.

 

If you do not have the Microsoft Visual's C++ 2005 w/SP1 and 2008 installed, then you will have problems. The guide shows you what versions are required to properly run FSX. These versions are installed automatically when you install FSX/SP2 except SP1 to Microsoft Visual 2005. The guide has links to the proper versions.

 

If you do not have the proper versions of Microsoft.net (dotnet) installed, FSX will not run properly. FSX requires versions 2.0 and 3.5 to run properly. Addons might require later versions. Again, the proper versions are installed when you install FSX SP2 but something could have happened where those were deleted. The AVSIM Guide provides a link to the proper versions and has a tool to verify they are installed properly.

 

Hope this helps.

 

Best regards,

Thanks I will check it out