I have FSX SP2, Windows 7 x64, 4Gb Ram and a 3.8K dual core Intel.1. FSX crashes if I start fiddling about with views and settings in mid-flight. Error :-Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0xbe33a641Faulting process id: 0x10c0Faulting application start time: 0x01cb57eb7af0bec0Faulting application path: G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: unknownReport Id: 58a5d700-c3e9-11df-9090-001fbc07f0c42. Easier probably. If I enter the map and move the plane or change settings when I get back to the plane the throttle is stuck. very annoying but the answer may be obvious to someone!Thanks

I have FSX SP2, Windows 7 x64, 4Gb Ram and a 3.8K dual core Intel.1. FSX crashes if I start fiddling about with views and settings in mid-flight. Error :-Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0xbe33a641Faulting process id: 0x10c0Faulting application start time: 0x01cb57eb7af0bec0Faulting application path: G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: unknownReport Id: 58a5d700-c3e9-11df-9090-001fbc07f0c42. Easier probably. If I enter the map and move the plane or change settings when I get back to the plane the throttle is stuck. very annoying but the answer may be obvious to someone!Thanks

Exception code indicates you had a memory access violation and you might check out the following link over in the CTD forum where I provided possible solutions to this frequent problem: http://forum.avsim.net/topic/296107-ctd-help/ It looks like you're putting too many resources on your system and you need to lower your sliders down a little.Best regards,Jim

Exception code indicates you had a memory access violation and you might check out the following link over in the CTD forum where I provided possible solutions to this frequent problem: http://forum.avsim.n...96107-ctd-help/ It looks like you're putting too many resources on your system and you need to lower your sliders down a little.Best regards,Jim

Thanks Jim. I have the picture and will check around. Seemed to happen when I was using 2 monitors (big desktop) with instructions on one. No 2 above is a reliable error and it is not always the throttle. Any ideas on that one?davidPS your link to the windows XP site is dead by the way.

Thanks Jim. I have the picture and will check around. Seemed to happen when I was using 2 monitors (big desktop) with instructions on one. No 2 above is a reliable error and it is not always the throttle. Any ideas on that one?davidPS your link to the windows XP site is dead by the way.

Actually the link is not dead. It has a full stop at the end which fazes the browser.

Just a suggestion IMHO.But see if you can as you are running Win7 64-bit:(a)move your FSX folder to the root directory in your hard drive,i.e C:\FSX or whatever you want to call it.(b)then look here for posts about moving the UIAutomation.dll file from the System32 folder to the FSX Modules folder.Hopefully,that will stop your CTDs when using the Views.It did mine.

Thanks Jim. I have the picture and will check around. Seemed to happen when I was using 2 monitors (big desktop) with instructions on one. No 2 above is a reliable error and it is not always the throttle. Any ideas on that one?davidPS your link to the windows XP site is dead by the way.

The error you had with the throttle getting "stuck" again indicates a memory issue. Perhaps you have an installation issue where a .dll or file is "calling" for an action and it's not finding the file so it's using a lot of memory looking for it. VC10man has some good recommendations but I'm against you moving the uiautomationcore.dll to your fsx modules folder. The .dll is part of the dotnet framework and should be left in the system32 folder. How it would work in the fsx modules folder is way beyond me. Some have placed it in their main fsx folder too and it somehow solved their problem. In any case, I do not think that is your problem but of course you can try his suggestion. I still say something is eating up your memory for some reason: the sliders being too high, an overclocking, or a bad install of your video card (less likely). Sorry I can't help you more.Best regards,Jim

The error you had with the throttle getting "stuck" again indicates a memory issue. Perhaps you have an installation issue where a .dll or file is "calling" for an action and it's not finding the file so it's using a lot of memory looking for it. VC10man has some good recommendations but I'm against you moving the uiautomationcore.dll to your fsx modules folder. The .dll is part of the dotnet framework and should be left in the system32 folder. How it would work in the fsx modules folder is way beyond me. Some have placed it in their main fsx folder too and it somehow solved their problem. In any case, I do not think that is your problem but of course you can try his suggestion. I still say something is eating up your memory for some reason: the sliders being too high, an overclocking, or a bad install of your video card (less likely). Sorry I can't help you more.Best regards,Jim

I am now running non-windowed full screen mode and have had no problems so far.

I am now running non-windowed full screen mode and have had no problems so far.

Also put HIGHMEMFIX=1 into the config file but not sure whether this has an effect.