Title typo: should of course read 'update'. ------------------------------------------------------------------------The past symptoms:1. Would take a flight out of random-of-my-choice scenery locations, and after a few minutes from lift-off, FSX would crash to the desktop.2. Would try to access the Scenery Lib and would CTD.3. Would call up the menu list, and might CTD right away, or would be allowed to continue on to whatever I wanted to view/change4. Would CTD after I tried to exit the sim.Any of the above could happen by themselves, or when I just started FSX and only tried one of the above mentioned. This could happen, or not happen during a flight, at totally random. I tried MANY remedies, but after all of them failures, I decided to delete the FPS Limiter BATCH FILE that one makes to use the FPS Limiter Program, on a 'didn't-try-this-yet' hunch, and after making another one, and placing it within the ROOT folder of FSX, am happy to report that I have NOT had one CTD occurrence of the above, whether as taking one of the actions alone, or in a combination of them. FSX has been rock-solid for all aspects of use, and ends only when I instruct it to. This no CTD usage has happened ONLY after recreating another FPS Limiter BATCH File, and placing itside the FSX Root Folder. Nothing else was done after that before I started up FSX and from then, to now (about two weeks) have had no further P.I.A. CTD's!If you use the FPS Limiter program as I do, ( I also use ENBseries) to start FSX, and experience any of the above, then try out what I did on your system for the CTD solution. It certainly worked in my case, and again stated; that was the ONLY thing I did immediately before having no further CTD's of any kind. My feeling is that over time this BATCH file can become corrupted, and that introduces instability into the use of FSX. Post Edit: My system is an i7-975 overclocked to 4.010GHz, with an nVidia branded GTX285 1GB vid card, driven by nVidia 260.99. Sound card is Creative Titanium family. Memory is 4 GB's Triple Channel overclocked to 1366 MHz. After swapping out the Batch file for a newly created one, FSX is running smooth as silk.

Title typo: should of course read 'update'. ------------------------------------------------------------------------The past symptoms:1. Would take a flight out of random-of-my-choice scenery locations, and after a few minutes from lift-off, FSX would crash to the desktop.2. Would try to access the Scenery Lib and would CTD.3. Would call up the menu list, and might CTD right away, or would be allowed to continue on to whatever I wanted to view/change4. Would CTD after I tried to exit the sim.Any of the above could happen by themselves, or when I just started FSX and only tried one of the above mentioned. This could happen, or not happen during a flight, at totally random. I tried MANY remedies, but after all of them failures, I decided to delete the FPS Limiter BATCH FILE that one makes to use the FPS Limiter Program, on a 'didn't-try-this-yet' hunch, and after making another one, and placing it within the ROOT folder of FSX, am happy to report that I have NOT had one CTD occurrence of the above, whether as taking one of the actions alone, or in a combination of them. FSX has been rock-solid for all aspects of use, and ends only when I instruct it to. This no CTD usage has happened ONLY after recreating another FPS Limiter BATCH File, and placing itside the FSX Root Folder. Nothing else was done after that before I started up FSX and from then, to now (about two weeks) have had no further P.I.A. CTD's!If you use the FPS Limiter program as I do, ( I also use ENBseries) to start FSX, and experience any of the above, then try out what I did on your system for the CTD solution. It certainly worked in my case, and again stated; that was the ONLY thing I did immediately before having no further CTD's of any kind. My feeling is that over time this BATCH file can become corrupted, and that introduces instability into the use of FSX. Post Edit: My system is an i7-975 overclocked to 4.010GHz, with an nVidia branded GTX285 1GB vid card, driven by nVidia 260.99. Sound card is Creative Titanium family. Memory is 4 GB's Triple Channel overclocked to 1366 MHz. After swapping out the Batch file for a newly created one, FSX is running smooth as silk.

The EXE .bat file the limiter gui makes has to be in the main folder where that limiter gui resides. After you make the BAT file for FSX you can then make a shortcut and place the shortcut where you choose. If you were moving the BAT file (the orig) elsewhere that would explain your CTD's. Jim

The EXE .bat file the limiter gui makes has to be in the main folder where that limiter gui resides. After you make the BAT file for FSX you can then make a shortcut and place the shortcut where you choose. If you were moving the BAT file (the orig) elsewhere that would explain your CTD's. Jim

-----------------------------------------------------------------------------Oh hey, that could be, perhaps. But, I also didn't move the original out of the GUI 'Limiter' folder, but also moved a copy into the FSX Root folder. So, there was always an actual copy of the BATCH file in the folder you state. I merely made a short-cut on the desktop to fire it up. I do have a copy though of the BAT file as stated in my Root FSX directory. I'll take that out and see if anything changes; ie; crashes start to happen again. If that does happen, I'll report back that having a copy of the BATCH file on tap in the FSX Root Folder...seems to smooth things out.Mitch

MitchHow much RAM do you have? You said "Memory is 4 GB's Triple Channel" is that 3 x 4GB or just 1 x 4GB?The cpu you have needs Triple Channel DDR3 RAM in multiples of 3 in order to run in a stable manner, eg 3 x 1GB, 3 x 2 or 3 x 4 (6 x 1 or 6 x 2 6 x 4) so 4GB on its own would induce instability.Just a thought! :( RegardsPeterH

MitchHow much RAM do you have? You said "Memory is 4 GB's Triple Channel" is that 3 x 4GB or just 1 x 4GB?The cpu you have needs Triple Channel DDR3 RAM in multiples of 3 in order to run in a stable manner, eg 3 x 1GB, 3 x 2 or 3 x 4 (6 x 1 or 6 x 2 6 x 4) so 4GB on its own would induce instability.Just a thought! RegardsPeterH

I have 12 GB's of in-system RAM, in 3X4 format at Triple Channel. :) I should have perhaps been clearer. Since creating a new batch file for FS Limiter, no further problems of any kind. Thanks for your thoughts!Mitch

Mitch3 x 4GB - Perfect :( PeterH