Any idea of the cause of this CTD.....

[DescendDescend 25]

Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: unknown Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 00000000 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.0.6001.2.1.0.768.3 Locale ID: 2057Additional information about the problem: LCID: 2057I used to get it on my Vista 32 installation but the same is occuring on a completely new PC (except the 8800GTX) with Vista 64 and new FSX install. It has occurred with the PMDG747 and LDS 767 with UTX and My Traffic and is frequent and random. I am beginning to suspect FEX or FSUIPC so their removal is next. Any thoughts appreciated. Hardware runs for hours on Prime95. Apologies if this should be in the hardware forum but I don't suspect a hardware fault (yet).

[byork 2,259]

I'd update your video and sound drivers before you do anything major.Cheers,Bryan

[Guest firehawk44]

This is a common error for several applications, not just FSX. I recall getting the error once with FSX and never found a solution. I did a search on Google for "Problem Event Name: BEX" and found absolutely NO solutions to any of the problems discussed. It appears BEX stands for "Branch Exception" and has something to do with Data Execution Prevention or DEP. You'll find more info about DEP under System Protection>Advanced Tab>Performance Settings. I'm thinking Bryon has the right solution - uninstalling and reinstalling your video and sound card drivers and make sure you have the latest WHQL drivers installed. One or both of the cards may be illegally using memory addresses causing a conflict and crashing the application. This can be caused by bad installation of drivers or corrupt drivers. Make sure your virtual memory setting is set to "System Managed Size" too. Sorry I could not have a more positive solution.BTW, you have a nice and powerful system.Best regards,Jim

[3-2-1-Now 126]

Hi,Disable DEP and see what happens. Google for it - you have to run a command line.@Jim: If (as you say) it is DEP related, why do you go on to say "uninstall the graphics drivers"? It won't make any difference. ;)Best regards,Robin.

[Guest firehawk44]

"@Jim: If (as you say) it is DEP related, why do you go on to say "uninstall the graphics drivers"? It won't make any difference. ;)"A good and fair question Robin. I really didn't state it was DEP related; that's what I found on Google that it is related to the "BEX" event. I recommended uninstalling the graphics drivers since there could be corruption or a bad install that caused the exception. I think if you look at the reasons for DEP, it's to shut down system parts that are not working right before they create additional problems. To be sure: "Data Execution Prevention (DEP) is a security feature that can help prevent damage to your computer from viruses and other security threats. Harmful programs can try to attack Windows by attempting to run (also known as execute) code from system memory locations reserved for Windows and other authorized programs. These types of attacks can harm your programs and files." So a display driver or sound card driver not working properly could cause this problem.I tried to shut down DEP for FSX once and it would not allow me to do it. I personally would not recommend turning off DEP.Best regards,Jim