Hi,

 

So after trying to make my second flight in FSX I was about to land after a 3hr flight and I click on the on the menu bar and all the sudden I get FSX not responding and restart FSX. Second flight, second timeit happens......Why?!?!? please help!!! Maybe I do too much in the background? Thanks!

Most likely a memory or lack of sufficient resources issue. Long flights can cause your system to heat up a bit. Maybe not overheat it but put more stress on resources. Moving around in Windows during a flight puts even more resources on FSX and your system. Things like going Windowed to Full Screen and back and forth can take up resources. Without a look at your event viewer log, it will be hard to pinpoint the cause. The event log usually shows the faulting module and that could indicate an addon quit working properly and caused the crash. If you are not familiar with the Event Viewer for your system, I recommend clicking on the Start Button and click on Help and Support. In Help and Support, just type Event Viewer in the search bar. It will take you to the Event Viewer plus provide you information on how to use it to diagnose a crash or problem with your computer. I have many more suggestions that I have recommended in other posts here that you might try. There are a lot of fellow flight simmers who have suffered the infamous Menu bar crash.

 

Best regards,

Jim

Would this help?

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

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

Exception code: 0xc0000005

Fault offset: 0x00000042

Faulting process id: 0xb98

Faulting application start time: 0x01cd676a15366599

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report Id: 03dc51fb-d37c-11e1-b6c5-86c91a7a1422

 

Log Name: Application

Source: Application Error

Date: 7/21/2012 5:35:40 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Clement-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

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

Exception code: 0xc0000005

Fault offset: 0x00000042

Faulting process id: 0xb98

Faulting application start time: 0x01cd676a15366599

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report Id: 03dc51fb-d37c-11e1-b6c5-86c91a7a1422

Event Xml:

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

<System>

<Provider Name="Application Error" />

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

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2012-07-21T21:35:40.000000000Z" />

<EventRecordID>1308</EventRecordID>

<Channel>Application</Channel>

<Computer>Clement-PC</Computer>

<Security />

</System>

<EventData>

<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>c0000005</Data>

<Data>00000042</Data>

<Data>b98</Data>

<Data>01cd676a15366599</Data>

<Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>

<Data>unknown</Data>

<Data>03dc51fb-d37c-11e1-b6c5-86c91a7a1422</Data>

</EventData>

</Event>

Unfortunately, it did not reference a faulting module but the Memory_Access_Violation Exception Code 0xc0000005 showed up. That doesn't really mean much either but it's an indicator to me it's a memory resource issue. What were you flying when the errors occurred? Did the crash occur at the same location? What other addons were running at the time of the crash? FSInn? FS Co-Pilot? Ezdok? Were you flying in a commercial scenery area like FTX/Orbx? You can try lowering your settings in FSX. For instance, turn off all AI and run the flight again. If no crash, then it's probably one of those settings that's set too high. Autogen is another frame hog and you can disable that too or lower it if you have it maxed out. Like you said, you probably have too much stuff running in the background. I know the FPS on my system begin to lag a lot when I'm flying a commercial addon like PMDG, in real world heavy weather with AS2012, and flying over commercial addon scenery. You also need to consider your display driver settings as some can really bring your system down if set too high, like AA/AF. Normally FSX likes those settings in the display driver to be "Application Controlled" but this is not the recommendation of any of the experts who have successfully tweaked FSX to its limits. Still, what works for some may not work for you. Read the recommendations made by Srjan Word Not Allowed in his excellent software/hardware guide for fsx. It's pinned in the Hardware Forum. NickN also has some excellent recommendations in his guide on Setting up FSX and Tuning It - http://www.simforums.com/forums/topic29041.html.

 

If you are overclocked, make sure you look at your BIOS memory frequency/timing and voltages and make sure they are correct and not too high or too low. You can find the proper memory timings and settings in the CPU-Z freeware under the SPD tab. CPU voltages too low or too high have also caused these types of crashes.

 

Hope this helps.

 

Best regards,

Jim

Adding to Jim's tips, did you already check the problem with the uiautomationcore.dll?

 

Read some older thread here. http://forum.avsim.n...hing-win-7-x64/ Don't get distracted by the mixed up layout of that thread, making it a bit hard to read. I think it's worth trying since those menu crashes sound very much like that problem.

 

One just has to place that file in the FSX folder. If it doesn't help, just delete it. No harm done.