Windows 10: FSX Crashes in Mid-Flight

Hello everyone...
My FSX is crashing in mid-flight (after takeoff, cruize, landing) while being online on the IVAO's network. Everything is running smooth when randomly FSX freezes and the blue circle mouse icon is appers and then crashes to deskpot (CTD). I think i have tried everything. I tried to uninstall the fsx with a lot of add-ons (120 gb), didn't work. I tried to install the uiautomationcore.dll, didn't work. Tried to run in windowed mode, didn't work. Tried to run in fullscreen mode , didn't work...


Specs:
I5 3470

4gb DDR4

Intel HD 2500



I was searching in the crash history and i found the module what causes the crash.



Leírás

A hibát okozó alkalmazás elérési útja: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe



Probléma-aláírás

Problémaesemény neve: APPCRASH

Alkalmazásnév: fsx.exe

Alkalmazásverzió: 10.0.61637.0

Alkalmazás időbélyegzője: 46fadb14

Hiba - modul neve: FSUIPC4.dll

Hiba - modul verziója: 4.8.5.3

Hiba - modul időbélyegzője: 50477966

Kivételkód: c0000005

Kivétel - eltolás: 00037504

Operációs rendszer verziója: 10.0.17134.2.0.0.768.101

Területibeállítás-azonosító: 1038



További adatok a problémáról

Gyűjtőazonosító: 164707c8ab91185ac769719d8af045fe (-465685170)



Sorr, it is hungarian, but the module what causes the crash in the FSUIPC4.dll.

So, what can i do now?

:)

 

FSX Fatal error mid flight

Hi I have FSX and just installed it on my new computer. I have used FSX before so I'm no new to it but I keep running into this problem of Fatal error messages popping up mid flight and crashing the game. I use Windows 10 and have a 64 bit processor and
a GTX 960 graphics card and a lot of RAM so in technical terms I should be clear but is there anything I can do to fix this? It is really discouraging to get 4 hours into a transatlantic flight and it crash on me.I've messed around with the graphic settings
a bit but nothing seems to be working. Any ideas?

 

FSX Fatal error mid flight

I also use FSX and can identify with your problem. Firstly, what is your error message? Secondly, your card is great but what are your specs on your CPU, Ram, monitor, etc. The processor is much more critical to FSX than the graphics card. As you know
a program crash at any point in the game can be caused by a myriad of factors. All it takes is one conflict to crash FSX, whether a crash to desktop, a freeze, BSOD, black screen with/without sound, etc. So, it won't be easy to isolate the problem, even
in a few steps.

So, check the error message, preferably in your Event Viewer, at time of crash. It could give an indication as to how to go about dealing with it. However, in the meantime, just to help you along your flight path without having to restart the whole flight,
periodically save the flight, say every 20-30 minutes. So, if there's a crash, you can just reload from that point and continue on. Not a solution by any means, but it will keep you going until you can identify where the problem is. The problem could
be simple, such as lowering your settings, especially, autogen, scenery details, LOD radius, traffic, clouds, and even maybe removing any addon scenery and aircraft. You mention that you were flying transatlantic when this happened. Did you have the sim
rate set to over 8X?

Let us know - others with suggestions may chime in.

 

FSX Fatal error mid flight

Maybe you've haven't had the opportunity to fly and therefore get the error message (which will be useful in noting which is the faulting module), in any case, your specs are more than adequate to run FSX at least at the default aircraft/scenery level and
higher. And as you mentioned, that you have used FSX on your previous computer without any problems. I assume that your TV monitor hasn't been a cause for errors in the past.

Aside from the FSX program, I would run chkdsk for any errors, clean up the drive and defragment.

In FSX (for testing purposes): remove any added on scenery or aircraft (except installed Afcad scenery files or airline skins).

In your FSX Settings: reduce all your settings under each of the five tabs to default. Then adjust the following in each tab:

Graphics: Target Frame Rate (30); Filtering & Global Texture Resolution (your choice); only tick Adv. Animations.

Aircraft: Untick Aircraft casts shadows on itself.

Scenery: LOD (your choice); Mesh complexity (80-100); Mesh Resolution (38 m); Texture Resolution (1 m); Water Effects (High 1.x or low 2.x); Scenery Complexity (as low as you can go for now); Autogen
Density (Normal or Sparse for now); Special Effects (your choice).

Weather: Cloud Draw Distance (Low); Cloud Detail (Detailed Clouds, Medium to High)

Traffic: Airline traffic (<40%); GA traffic (<10%); Airport Vehicle Density (Medium to High); Road Vehicles (10 -20%).

Then go to your FSX Configuration File (fsx.cfg) located here:

Your Drive:\Users\yourName\AppData\Roaming\Microsoft\FSX

(you will find two fsx.cfg files: one .cfg and the other .cfg.txt). Delete the .cfg file: FSX will rebuild a new one when you start FSX. However, you will lose any specially mapped controls, etc., so you may want to note all that down).

Start FSX to rebuild a new cfg file and shut FSX down again. Go back into your fsx.cfg file in the above location and do the following:

Make sure that your Display Device has only one entry, unless you are using Directx 10, then you will have two entries.

Under Graphics, add the line "HIGHMEMFIX=1" (without quotes). Aces team forgot to include this entry.

Under Display, WideViewAspect=True (since you're using a TV).

There are other tweaks, but generally they cause more problems than they are worth.

Also, your Nvidia card can be configured, either through their Control Panel or via Nvidia Inspector (can be downloaded for more settings), but not for now.

So that's it for setting up FSX to give you a flight at minimal to average settings. If you still get a mid-flight crash, then there must be another conflict with your hardware, which will take a lot more time to isolate. There are also guides published
for setting up FSX and dealing with CTDs, etc., but we'll see how you go with the above for now.