Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CaptainMu

Members
  • Joined

  • Last visited

  1. Possible solution!!!I posted a while ago, that reducing my processor to just one kernel with msconfig worked for me - no freezes anymore. Though I did not like this workaround for obvious reasons. But it was a sign that multicore processors seem to be the common factor in freezes. Some other solutions where you configure FSX in the config file of FSX to use a certain core pointed to the same direction.Now I stumbled across a thread where someone figured out that his overclocking brought his FSX to freeze, and that the freezes stopped when he decreased the clock multiplier enough in his BIOS. Well, I never did overclocking, I thought first. But interesting was the theory of the author that some kind of minimal off-balance between the different cores in the processor seems to have been the origin of his FSX freezes. (BTW, he had no problem with any other game while doing overclocking)So I had a look into my BIOS (AMD Phenom II x4 955) - more exactly into the processor settings. There I found an option called ACC (Advanced Clock Calibration), which was turned OFF. I read about that feature and found out that it probably could not harm when it was turned to AUTO. (There seems to be no clear documentation about this feature by the manufacturer) I switched it to AUTO - and FSX had NO FREEZES any more since then!!!Obviously, the ACC feature does what it says: It seems to "calibrate" the processor clocks, maybe synchronizing them to work better together. (I am no expert) I read, that not every BIOS has that feature - even when running an AMD processor. But it's probably worth looking for it. Maybe other processors or motherboards have instead of this another feature to solve the problem.Good luck and I would love to get some feedback, if it works for you mates, too.
  2. Because of removing the duplicate key assignments? Wow! I'll try that, though I don't use Saitek gear. ;)
  3. I think I found a workaround!!!Via msconfig in Win 7 I limited my system to use only one processor core. I flew a test flight of 3 hours, and up to now no freeze. Before that, I never succeeded to fly so long without a freeze.
  4. Seems to be a really weird problem, when I look at the variety of circuamstances.The fix of UIAutomationCore.dll did NOT solve my inital freeze problem. I stumbled about this problem when I was looking for a solution for my freeze problem. Actually, I never noticed the UIAutomationCore.dll problem before I read about it, but then I could reproduce it by clicking several menu items. But with copying the Vista UIAutomationCore.dll, I solved that problem, at least.But back to the original freeze problem:I agree, that it seems to be connected to Win 7, maybe to the 64bit version precisely.My freeze occurs usually between 1 minute and 2 hours after loading a flight - flying in my Cessna at an altitude of 2.000 to 5.000 feet. So this problem is not alone about hight altitude flights.@deepsea631: I don't have a force feedback joystick and no G15 keyboard. I am using the K350 keyboard and the marathon mouse M705 by Logitech. So, we have only the Logitech in common.@Nexus6: I don't have saitek products. I use flight yoke and pedals by CH products. (Though, as said before, I get the freeze even without connecting them)@abulaafia: I don't use a saitek yokeBTW, when I force quit on FSX while REX is connected, I get the exception HRESULT: 0xC000020D (see the attachment). But I am not sure, if this isn't the result of the freeze at FSX. When REX is not connected, I get no HRESULT.So I sum it up:The freeze occurrs...- on different processors- with different graphics chips- on different altitudes (high and low)- with different keyboards and mouses- with different controllers (or entirely without controllers)- with and without REX or ASA- with different sound devices (though the frequency of the freezes seems to be influenced by it)- with installations on the system partition or on another partition- with FSX SP1 or SP2 (with or without Acceleration), though from the feedback in the internet it seems to me that it doesn't occurr so frequently without SP2.- while flying over dense scenery AND while flying in the nowhere- with or without internet connection And there are times when it happens really quickly, and on other days it takes a while.Seems to be a really nasty problem!!! Not really deterministical! ;)
  5. 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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.