Edit: I have edited this post to make it short and sweet....1. I had severe FSX instability, with CTD's when trying to use the menu bar, and when flying in general. Also, crashes when trying to end FSX.2. Through much testing, I found the culprit...Your FPS Limiter file (fsx.exe.limiter) that is created when you use the G.U.I. bat file creator of FPS Limiter, can become corrupted over time. When you use that to fire up FSX, it will show up as CTD's and other anomalies.To fix this, just delete that file in the folder it was created, and then once again using the G.U.I., merely create another file to fire up FSX with. That fixed all my CTD issues, and returned FSX to stability.Now..was that short and sweet? LOL!I hope this helps another....

Interesting find and thanks for sharing. Having installed a new Vcard after running it with all the popular tweaks old and new I decided to start completely from scratch with a new goal of keeping it as simple as possible and seeing how that compares.BTW what drivers did you end up staying with for best IQ?

The menu crash is caused by uiautomationcore.dll. Its fixable if you use a vista 32(at least I think its vista32) version of that file instead

I really am having a hard time understanding posts blaming things with causing problems that doesn't cause problems on my rig?? Maybe it,s not FPS Limiter but your computer?? Just asking...Lou

Good find, Mitch: I use this all the time, (thanks to BoJo), but I gave up on the ENB bloom mod for the same reason - and EZCA causes a hesitation for me every 4 - 5 seconds, so it's gone as well! I just want to fly!

Interesting find and thanks for sharing. Having installed a new Vcard after running it with all the popular tweaks old and new I decided to start completely from scratch with a new goal of keeping it as simple as possible and seeing how that compares.BTW what drivers did you end up staying with for best IQ?

I'm staying at present with the 260.99's 'cause I really like the way it renders water textures, etc.About the crashes...it took me about two hours to find out what was causing the crashes, that I never had before. I NEVER would have suspected that file. I deleted it, made a replacement...and all crashes and slow menu, or crash-from-menu problems disappeared. When I start to have those issues again, I'll merely assume the file corrupted for whatever reason and make another one.

Good find, Mitch: I use this all the time, (thanks to BoJo), but I gave up on the ENB bloom mod for the same reason - and EZCA causes a hesitation for me every 4 - 5 seconds, so it's gone as well! I just want to fly!

Hi Paul,I love the ENBbloom and have used FPS Limiter both together without any problems. For whatever reason, if you start to get CTD's and such, merely make another FPS Limiter 'start FSX' file and have at it. Cured all the CTD's for me.

The menu crash is caused by uiautomationcore.dll. Its fixable if you use a vista 32(at least I think its vista32) version of that file instead

This was somthing else, The corruption also slowed down menus coming up after a click request, or totally droped you out of FSX. I don know what you mean about the other, though.By creating a new FPS Limter.exe file, all of the symptoms went out the window!

I really am having a hard time understanding posts blaming things with causing problems that doesn't cause problems on my rig?? Maybe it,s not FPS Limiter but your computer?? Just asking...Lou

LOLOLOLOLOL! You're lucky so far. But when you become UNLUCKY---with time, remember my find, and if you use FPS Limiter all the time, this will cure the headaches.I never had any CTD issues before, but as I and you know, files can and do become corrupt for many reasons. This will certainly help you.I use ENBloom and FPS Limiter without issues in normal use. Replacing the old fsx.exe.limiter file with a new one from the GUI, solved all CTD's and slow or CTD-menu items. .Mitch