Hi All

 

So i'm about to give up on fsx I cant take the crashes anymore and have read everywhere to try get answer maybe someone can help. My fsx just exits to desktop after a flight when I try go to windowed mode to upload my PIREP in kAcars heres what I do/have tried:

 

1) Enbseries - i have given up on because it causes too many crashes

2) I never use Alt-enter and rather click the menu as I know that's a known issue

3) I have the "correct" UIAutomationcore.dll file in my fsx root folder

4) I have unchecked the "read-only" panel.cfg and aircraft.cfg files in my PMDG models (as i have heard its an issue that gives errors on exiting fsx)

5) I have globally disabled DEP on my pc as this can cause BEX errors (since then that's sorted)

6) I have installed RivaTunerStatisticsServer and enabled "Custom Direct 3D support" as ive seen with new Nvidia cards if you try use ENB or Sweetfx there is a duplicate allocation of the directx dll files into memory and that causes the crash -  I do have sweetfx installed

7) I have disabled UAC control

8) All my add-ons and FSX itself are run as administrator

9) I do not get OOM errors or pings or anything like that so I doubt that's an issue

10) Latest FSUIPC installed (unregistered) as usually after the fsx disappearance I lose connection to the kAcars and cant submit my PIREP - so i thought it was that

 

(I am sure ive tried other things over the last few months but cant remember now lol)

 

My pc specs are:

Windows 7 64 Ultimate

Intel i5 4670K @ 4.0Ghz

Kingston 1600Mhz 16GB

Nvidia GTX 780 3GB Evga SC

Corsair GS 800w PSU

There are too many possibilities, especially with SweetFX installed. Since the uiautomationcore.dll has not stopped your crashes as it was suppose to do and you do not get Menu crashes, have you thought about moving it to a temporary folder and seeing if this fixes the problem. Many people, including me, have no problems whatsoever with the uiautomationcore.dll removed from the main FSX folder.

 

Disabling DEP is definitely not recommended as it affects the security of your computer. It is highly questionable that disabling DEP fixes StackHash crashes (it didn't for me and you are the only one so far that I have seen who says it worked for you).

 

You should post a crash report for your latest crash. You can get a link to the AppCrashView program by going to the AVSIM CTD Guide located to the right of this forum under Hot Spots. Copy and then paste the most recent crash here for analysis.

 

Best regards,

This is of course a last resort, but have you tried reinstallation of FSX? I kept having FSX is not responding issues that offered me no error code, it was impossible to figure out what was causing it. In the end, I think it was REX's fault, as whenever I tried to use their weather I had issues, regardless of whether it was turned on for that specific flight. I reinstalled, adding only the most important addons to me and now it runs great. *Knock on wood.*

Okay soooo I have moved the UIAutomationcore.dll out of the fsx folder and after 1 flight it didn't crash.. Will keep testing

 

No I haven't tried a reinstall just yet as I got many addons and having taken the plunge just yet lol (although the issue started almost the first day I installed fsx (same day I got new pc) anyways)

 

I use REX for textures but ASN for weather engine.

After installing UT2 I got those BEX errors :(

 

 

Thanks guys appreciate it. Will post if I get issues again and send appcrash log

 

Regards

Just to give you some hope... Soon after buying an expensive PC to run FSX I kept getting crashes and many were StackHash ones with no known cure. The Ebola of Flight Sim!

 

Anyway, I'm not the giving up type and I noticed that one particular crash occurred at the same point in my flight. That meant it couldn't be completely random and something had to be responsible.

 

I used a process of elimination by changing my Ai % to zero. Flying the same route didn't cause a crash so I was pretty confident the problem lay with my traffic program - MyTrafficX.

 

I wrote to the author giving the time of day the crash occurred and my location. He provided a new set of textures for an Ai aircraft and that solved my problem. I also ran a procedure with MTX to validate the textures of all MTX aircraft. That found another bad one and new textures were supplied. That fixed occasional crashes west of Denver.

 

I'm now confident I have a stable system. All my problems were down to a few bad Ai textures. I never reinstalled FSX or deleted the fsx.cfg.

 

Try flying a default aircraft on a route where you get crashes and try changing settings including Ai if necessary. Problems after installing UT2 make me suspicious. Could be the same problem I had.

 

Make one change at a time and see if it makes any difference. It will probably end up as something simple just like my problem was.