What 4 of us have in common is the i7 975.I have a full CH products setup. Also, I DON'T use that limiter program.I'm doing KPAE to KLAS in the new PMDG 747-8F, so I'll see what pans out. I haven't done a long haul since a week ago and, sure enough, the problem occurred. That flight was from PHNL (the new FSDreamTeam scenery) and KLAS (an newish FSDreamTeam scenery). You know what else I've seen lately? Texture starvation. You know how you get models now showing up and other weirdness when this happens? I wonder if they're related? I've found that some settings on NickN's guide aren't as good for doing long-haul in heavy metal and I back off of those settings a bit.The advice given here to start over and add things back in one at a time is also good. Maybe one of the following isn't right:FSGenesis Mesh products (World, Canada, USA, Mexico, Alaska)Scenery Tech landlcass (all continents)Various Blueprint sceneriesVarious Aerosoft sceneriesVarious FSDreamTeam sceneriesI'm very tired of reinstalling and I've done it about 4 times since last fall. However, it may well be that there are som addons in conflict. What about addons for the rest of you?The only thing I've seen in common is our processor.I hope we find an answer soon.

I heard on an another forum, that FSDT's Addon Manager causes problems for some users. It is recommended to update it. Disabling it temporarily could be worth testing as well.

>>What 4 of us have in common is the i7 975.I've been looking around online for a few weeks now and I'm still having the same problems that you all describe with a few twists. First I don't have an i7 CPU.My problem is that FS X freezes at any altitude and at any frequency between almost immediately to over an hour or two of running it. I don't believe this is a hardware issue. I recently 'upgraded' my computer's OS from Vista Ultimate 64 to Windows 7 Ultimate 64. The problem started after the OS upgrade. I ran FS X on the Vista OS for years without problems on this same hardware. I did notice a reduction in the frequency of crashes when I updated all of the drivers for the system from the hardware vendor's sites (overwrote whatever Win 7 put in there for drivers).My hardware:Intel DP45SG MotherboardIntel 6600 Quad Core (Core 2)8GB RAMNvidia 8800 series video (768MB VRAM?)Built in sound (IDT)Intel SATA Raid running RAID 5 ( 3X500GB drives)Like I said, everything worked great before upgrading to Win 7.Keep posting, someone will come up with what's going on sooner or later.-Eric

I saw this freezing a few weeks ago, and after making a few changes I haven't seen any more of it. I suspect (but can't yet prove) that what I was seeing is the effect of a TCP/IP stack stall on SimConnect. I know that if I force a disorderly shutdown of ASA running on a remote PC, FSX will freeze for a few minutes exactly like the random freezes I was seeing before, and then recover on its own.For reference, I'm running an i7 975 on an eVGA X58 SLI (E758) motherboard with Vista64 Home Premium.First, on my eVGA X58 motherboard, there's a setting for Low Memory Gap (aka memory hole on some other mobos). I have a 2GB GTX285, and a recent BIOS update reset the value to Auto. I changed the memory gap setting from auto to 2 GB. Since I did this the random black screen crashes that started popping up after the BIOS update have pretty much stopped.The last BIOS update also added a PCIE max payload size, which defaults to 256K. I set it to 4096K. I think that having this set too low can restrict the available bandwidth to the video card on the PCIe bus and possible cause video timer resets that'll crash the drivers, and by extension FSX.I made a couple changes to the TCP/IP behavior, principally by disabling Nagle optimization (which causes the TCP/IP driver to wait for more data rather than sending a small packet right away. For real time IPC-type processes, the Nagle algorithm can really disrupt real-time data flow, such as what goes via SimConnect and/or FSUIPC. It's a registry setting:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{NIC-id}Add this DWORD value: TcpAckFrequency=1I also made a few other changes to the TCP/IP stack driver, with these commands in an elevated (admin mode) CMD window:netsh int tcp set global congestionprovider=ctcp netsh int tcp set global rss=enabled netsh int tcp set global chimney=enabledSee http://www.speedguide.net/read_articles.php?id=2574 for a discussion of what these changes do.So far, the freezes have subsided. YMMV, of course.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I am having the same problem, regardless of airplane, be it the LDS 767, PMDG 744, 748 or MD11. I have ASA and UT2 running. I have a Core i7 920, 6GB of RAM and GTS 250 1GB video card. I'm using Windows 7 Professional x64.I just applied the TCP/IP settings mentioned above and will give it a shot. Hopefully it works.I forgot to mention that I am also using registered FSUIPC. However about 15 minutes after posting this message it froze.

I am having the same problem, regardless of airplane, be it the LDS 767, PMDG 744, 748 or MD11. I have ASA and UT2 running. I have a Core i7 920, 6GB of RAM and GTS 250 1GB video card. I'm using Windows 7 Professional x64.I just applied the TCP/IP settings mentioned above and will give it a shot. Hopefully it works.I forgot to mention that I am also using registered FSUIPC. However about 15 minutes after posting this message it froze.

In your FSUIPC4.ini file, do you have a param called TrafficScanPerFrame, and if so, what's it set to?Something set mine to 100, where it should be more like 10. With UT II it caused me some trouble.No idea if that's a factor in these pauses...CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

My FSUIPC4.ini file does not have the TrafficScanPerFrame parameter.I flew from PANC to PHNL yesterday without any freezing using the PMDG 747-8F. If it continues to work I will report back. Although I haven't really changed anything.

So what has (at least I hope it has) fixed the pauses, is:- BP at 100000, TBM at 50, fiber_frame_time_fraction at 0.33, fps limit fps at 25 (no external frame limiter) and AffinityMask at 15. Those are the only radical changes I've made, and these have come slowly, with lots of reading and testing. Last night I was at 500000, TBM 40 and 70, 25fps locked, AMask at 12. I flew the A2A Spit from SEA to PDX at ~9000'/250kts, and experienced eight pauses, each about a minute long, and this time I waited for all to continue - and they did - except the last one, and in that case I gave it the three-fingered salute, waited, Alt-Tabbed it twice, waited, and a few seconds later it popped to the desktop - and then back to fullscreen, - paused mode. I also loaded the 196.21 before the tests. To fix the remaining ground flashing I just take a fast look at each wingtip (TrackIR) and then the flashing doesn't occur again. A couple of days ago I backed everything to the left, and the flashing and pausing disappeared entirely - but one can't fly like that. I hope this helps someone zero in.

Well I made the changes posted by wk6d (Bob Scott) when he first put them up and was flying freeze free for about 16 flights or just over 24 hours, that is until yesterday :( Again completely random I just leveled off @ 10,000ft. in DA's Piper Cheyenne going from YHBA-YBHM I was using FTX (all), UT2, AH and ASA, no Radar Contact. This was the first time I had a freeze with a GA aircraft but then again I don't fly much GA stuff. Sure enough right after it happened I got back in and completed the flight using the same setup, heck I didn't even restart my CPU! I just started using Air Hauler (AH) Fantastic program btw! So I'll be flying low and slow in FTX for awhile I'm going to disable UT2 and use the FTX traffic. I'll see if this adds to my time betwen freezes, I'll report back when it happens again.

I had many of the same issues - the one thing that made the difference and solved my FSX frame rate issues: always make sure you install the current Directx from Microsoft after you've re-isntalled FSX. This will refresh even the Directx 9 modules that FSX depends on. I used dxwebsetup.exe from the Microsoft Direct X site.I had serious issues where frame rates gradually dropped to 2 or 3 fps after a period of 20 minutes- and then went up to 30 FPS when I muted the sound via "Q" or clicked on another non-FSX window. It wasn't sound card drivers - as I have two different vendor sound cards (one for general sound, the other for recording software) as the problem followed each sound card when I switched between using them as the active default.Regards,Mike.Dell XPS 720 Quad Core 6600 with 4MB Windows 7 Ultimate - 32bitNVidia 8800 GTX 768MB - Driver 196.21

I've tried almost every trick listed so far, but FSX is still locking up under Windows 7. After checking a few other sites I'd like to know if there is any hardware that we all have in common. I know we mostly have different CPU's and motherboards from reading previous posts, but what about sound and video cards?I'm running an Nvidia 8800 video card (PCI express) with the latest drivers and IDT built in audio on an Intel DP45SG motherboard - also with the latest drivers.I've read on some other sites that this problem does not happen on ATI video cards. Anyone running one with problems?I'm still believing that this is a software issue as I ran FSX on this same exact hardware for a few years before 'upgrading' to Windows 7. Before the upgrade everything ran fine, but now FSX freezing seems to be the only problem that my upgrade from Vista Ultimate 64 to Windows 7 Ultimate 64 has caused.I'm about ready to install another hard drive in my system and reinstall Vista just for FSX.Thanks,Eric

I've tried almost every trick listed so far, but FSX is still locking up under Windows 7. After checking a few other sites I'd like to know if there is any hardware that we all have in common. I know we mostly have different CPU's and motherboards from reading previous posts, but what about sound and video cards?I'm running an Nvidia 8800 video card (PCI express) with the latest drivers and IDT built in audio on an Intel DP45SG motherboard - also with the latest drivers.I've read on some other sites that this problem does not happen on ATI video cards. Anyone running one with problems?I'm still believing that this is a software issue as I ran FSX on this same exact hardware for a few years before 'upgrading' to Windows 7. Before the upgrade everything ran fine, but now FSX freezing seems to be the only problem that my upgrade from Vista Ultimate 64 to Windows 7 Ultimate 64 has caused.I'm about ready to install another hard drive in my system and reinstall Vista just for FSX.Thanks,Eric :( Tonight I installed a different sound card in my system and disabled the onboard audio on the motherboard. The new sound card is a Creative X-Fi XGamer. So far so good, no crashes or hangs, everything seem to be running fine including FSX! :( I'll post more if it continues to work!

btw - you just installed one of the two soundcards I've been using - the Soundblaster x-Fi Gamer. The other I have is a PCI-424 for MOTU hard disk recording - not used for FSX at all - but I did temporarily config FSX to use it as a test - to eliminate Soundblaster or it's drivers as being an issue.

btw - you just installed one of the two soundcards I've been using - the Soundblaster x-Fi Gamer. The other I have is a PCI-424 for MOTU hard disk recording - not used for FSX at all - but I did temporarily config FSX to use it as a test - to eliminate Soundblaster or it's drivers as being an issue.

OK, been flying for about 6 hours now, both high and fast and low and slow without any issues (over two days). Previously, since upgrading to Windows 7 I could not complete a flight over about an hour, usually having FSX freeze up in about 2-15 minutes.Some interesting observations:I have the Logitech G15 keyboard that shows CPU usage on an LCD display on the keyboard. Running with the SoundBlaster X-Fi Gamer the CPU usage is down about 50% from what I usually saw with the IDT onboard sound enabled. (now running about 30% across all 4 cores vs. about 70% with the onboard sound enabled with lots of traffic in the area both with Vista and Win 7).The graphics are much smoother, even with real world traffic enabled (via LiveTraffic).As I had noted before, this same computer had run FSX fine under Vista 64 Ultimate with the onboard IDT sound. After upgrading to Windows 7, the program would intermittently freeze (with the sound continuing as if it was in normal flight without any interaction with ATC).It seems that for my computer disabling the IDT sound chip in BIOS and installing the SoundBlaster X-Gamer has solved the problems. (fingers crossed here) I'm curious if anyone else who's having problems - are you using an IDT chipset for sound?Happy to be flying again....Eric

Hi everybody! I have got the same problem: Random freezes with FSX.I have read the whole thread, and I think that I can throw in some more infos for you guys:1) Windows 7 64 bit2) Graphics: ATI 5850 (So, this problem also occurrs on ATI graphics cards)3) Processor: AMD Phenom II X4 9553) I tried to run FSX under diagnostic mode (meaning starting up the computer only with the basic services). In particular, The sound was deactivated. I am using my onboard sound device - realtek. So I wonder, if buying another sound device would really solve the problem.4) I am using REX2, and it seems as if the weather engine leads to a faster occurrence of the freeze. Once, it happened exactly while REX was updating the weather.5) I don't think that the freezes are connected to game controllers like pedals, because I did some test flights with autopilot on while my rudders and my yoke were disconnected.6) I have fixed the problems with UIAutomationCore.dll by copying a version for Vista in my flight directory. (Crashs while using the ingame FSX menues)My system is pretty fresh and I have had the problem practically from the installation of FSX (SP1, SP2, Global Scenery, UTX Europe, GEX Europe, SceneryTech Europe) on.Are there any more feedbacks, if some of your countermeasures worked out?Chris