Hi, I think I nearly have had all problems you can have with FSX (and the number is very very high ;) ). First I "just" had crashes that are real CTDs. Then I figured out the type of freezes - not CTDs - this thread is about. I tried everything the last 3 Weeks. I was more trying to have a FSX running on extreme high settings stable than using the FSX what it is meant to do: FLY! What I did: Nearly all possible combinations of fsx.cfg related tweaks: buffer pools on/off/different sizes etc., disablepreload on/off, texture bandwith, fiber time fraction and so on. No cure. Then I also disabled the sound of the motherboard. No changes. Then I tried to use FSX without an external FPS Limiter. No changes. Disabled the "Application Experience Service" as mentioned in this thread. No changes. I don't know who else uses the ENB MOD, but I do and I like the style. In the end of all my tweaking fsx.cfg changes and environment changing things, I removed the ENB MOD from my FSX. And guess what: The FSX is running smooth as silk without any crashes, freezes or CTD stuff. I switched from window to fullscreen mode 10 times in a row, clicked through the menus, saved while flying, changed Time and date settings, changed plane settings. So basically everything that former ended up in CTDs. In the first 5 min I was a little bit suffering because of missing the ENB Style. But then I could barely notice the difference anymore and was happy to have FSX running as it should. The scenery is still looking faboulous on ultra high settings, so I don't see the difference to the ENB version. The only change I notice is that the Virtual Cockpit isn't so sharp as it was with the ENB Mod enabled (I changed the sharpen settings to higher values). To sum up, I definitely recommend to remove the ENB Mod for those you use it and have freezes or CTDs. Edit: I also have the Saitek X52 Pro. Yes, sometimes it is responsible for CTDs. I don't know if it is the same behavior for you, but for me it is this way: The Saitek-related CTD comes only at the beginning of loading the flight. The screen freezes at 0% and then crashes to desktop. When I simply plug out and plug in the Saitek Stick and reload the same flight, it works again. This is my workaround for the Saitek related CTDs. But maybe these crashes past when I switch back to the newest 64Bit drivers. Currently I have the original driveres from the CD installed. My specs:i7
[email protected], HT off (watercooled by Antec H20 620 at max. 75 degrees Celsius)Asrock P67 Pro38 GB Corsair Venegance DDR3 1600Asus Direct CU II 6870 1024 MB Fsx:Orbx Australia SP4, YBBN,YMML, YSCB, YBCSGEX Europe, UTX USARex Overdrive (no HD textures, just 1024)Shade for FSXPMDG 737NGX, 747-400X Best regards,Chris