Help anyone,Hresult Fatal Error with with no identified "dll" I've read all the great reports and responses concerning Fatal errors in flight that cause the W7-64 to freeze. But accasionally every few hours I get the following Hresult Error:The program fsx.exe version 10.0.61472.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: fc8 Start Time: 01cbf65549e9d2a3 Termination Time: 160 Application Path: C:\FSX\fsx.exe Report Id: 297889a4-624a-11e0-8383-002683143ddcAS YOU CAN SEE, IT IDENTIFIES NO SPECIFIC MODULE or "dll" file to fix. ????The full error print out from the Event Viewer is as follows:fsx.exe 10.0.61472.0 fc8 01cbf65549e9d2a3 160 C:\FSX\fsx.exe 297889a4-624a-11e0-8383-002683143ddc 55006E006B006E006F0077006E0000000000 Log Name: ApplicationSource: Application HangDate: 4/8/2011 8:39:22 PMEvent ID: 1002Task Category: (101)Level: ErrorKeywords: ClassicUser: N/AComputer: Walt-FS-PCDescription:The program fsx.exe version 10.0.61472.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: fc8 Start Time: 01cbf65549e9d2a3 Termination Time: 160 Application Path: C:\FSX\fsx.exe Report Id: 297889a4-624a-11e0-8383-002683143ddcI have a Win7-64 i5-650, 4GB, Nvida GTS450, ASUS P8P67-Pro, w/FSX SP2,FSGenesis US,UTX-US,, REX2,UT2,ANY HELP WOULD BE APPRECIATEDTHANKS,

Is FSX the only app where windows is freezing ?Making a SWAG ... I would look at windows drivers ... any yellow exclamation icons in device manager?Study up on using verifier.exe to determine if your drivers are up to standards.Are there any other symptoms before the freezes? Like pc getting more unresponisive ?All just guesses ... troubleshooting requires analysis based on information from observation.It could even be malware or a virus... but who knows... I have no real information to go on.

Try dropping the Vista uiautomationcore.dll into your main FSX folder. Do not delete the one you now have in one of your C:\Windows folders.http://forum.avsim.net/topic/273341-heres-the-apparent-fix-to-fsx-crashing-win-7-x64/page__p__1793447__hl__vista+uiautomationcore__fromsearch__1#entry1793447If you installed FSX in C:\Program Files(x86) then you should uninstall it and install in a separate folder like C:\Games or whatever name you choose for the new folder.

1. Try the UIAutomationCore.dll fix if your crash is when you right-click with the mouse (after 20 or so clicks). The UIAutomationCore.dll v. 6.0.6001.18000 file must be placed in your FSX directory.2. You might be running out of memory. Try increasing the RAM FSX can access beyond 2,048 MBy:

Widows Start MenuRunbcdedit /set IncreaseUserVa 3072OKReboot

to tell Windows to allocate up to 3 GBy RAM for FSX to use. Note: 3,072 is the maximum: If you have problems try reducing 3072 by 64 at a time (other values not allowed).3. A faulty Add-On DLL (memory leakage or outright bug): "Try uninstalling all your add-ons until you no longer get the crash." A hopless strategy, especially with random CTDs that are hard to replicate. (Hopefully MS Flight will be better at identifying fulty modules.)Cheers,- jahman.