Hello,

So Im having this very annoying issue were if i change views to many times especially when changing views on AI aircraft i crash. Now the crash doesn't happen immediately it will happen at random times, but mainly a few mins after changing views to much. My most recent crash i hardly changed views at all but it crashed while changing, this was about 20 mins into a flight. It always crashes at least 10 or so mins into a flight. If i jump in and spam view changes for a view mins it wont crash, it will only crash 10 or some mins after i start flying.

 

Also i have tried the uiatomationcore thing and it has not helped. I've also tried looking for it in event viewer and the crashes DO NOT appear! I've also tried several programs to open the crash files that appear in my FSX folder and none of them open the crash dialogue so i cannot get any specific details which may give clues. (this happens with every crash) 

Some one please help me as it is incredibly frustrating and no one seems to have the same issue as me. I've looked everywhere and tried lost of things and nothing has worked as of yet. 

Was the AI aircraft from an add-on or the default?  AI take up more resources and you now have loaded two aircraft.  Of course, this is just guessing on my part.  I don't think I have ever heard this happening in any flight simulator.  Every time you open up another aircraft, FSX needs more and more resources.  You have the scenario with your flight and then the scenario with the AI flight.  The more powerful your system, the less likely this would happen but you did not mention anything about your system.  If you had the PMDG 777 loaded and then opened the views of other AI in the area, then that definitely would affect performance.  Again, hard to know as you did not mention any details. 

The AVSIM CTD Guide (link in my signature) provides guidance for investigating and solving these crashes/freezes.  It shows you where to go to look in the Event Viewer to find your 'event' about your crash.  It provides a link to AppCrashView which, when installed, will provide details about the crash as it interprets Windows Error Reports.  We need to see the faulting module.  That provides a clue but not necessarily the solution.  Page 10 provides some suggestions to investigate the crashes/freezes. 

 

thanks for replying Jim,

So the AI aircraft is the orbx free australia traffic, but i had the same issue when i was using WOAI, But i only have traffic set to 20%, also i have pretty powerful rig, so i very highly doubt its the resources that are an issue. Also my aircraft was just the basic 737 with a livery so nothing special.

Also as i mentioned the crashes DO NOT appear in event viewer anywhere, They simply do not appear, also I've tried appcrashview and many other applications and none load the crash, so when i do crash it leaves no trails for me to read dialogue as to what may be causing my issue.

Do you have any other ideas?

1 hour ago, mognut said:

Do you have any other ideas?

See the AVSIM CTD Guide.  There is no known solution to your issue other than WOAI has been known to cause crashes as textures are not compatible because the AI were made for FS version FS9 or earlier.

I searched everywhere for a error but the only thing i can give you is what i managed to open in the MDMP file that was put in my FSX after the crash. this is the only trace of a crash. here it is:

 

Microsoft (R) Windows Debugger Version 10.0.16299.91 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\Steam\steamapps\common\FSX\fsx_62615_crash_2018_2_6T8_29_46C0.mdmp]
Comment: 'Minidump: D:\Steam\steamapps\common\FSX\fsx.exe
'
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Version 16299 MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
16299.15.x86fre.rs3_release.170928-1534
Machine Name:
Debug session time: Tue Feb  6 19:29:46.000 2018 (UTC + 11:00)
System Uptime: not available
Process Uptime: 0 days 0:28:55.000
................................................................
................................................................
................................................................
..........................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(294c.279c): Access violation - code c0000005 (first/second chance not available)
eax=00000000 ebx=4a461008 ecx=3eba0000 edx=00eb4000 esi=000002cc edi=4a460ff8
eip=777df62c esp=00cdc43c ebp=00cdc448 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00200206
ntdll!NtGetContextThread+0xc:
777df62c c20800          ret     8
 

The faulting module is the ntdll.dll, a system dll which indicates:

• voltages on your cpu are too high or too low if you are overclocking; fix for this is to mess around with the voltages or reset your BIOS to optimized defaults
• settings in fsx-se are too high (display driver or in the fsx.cfg).  Settings too high will trigger the ntdll
• a bad driver - run a freeware program like Driver Booster to see if all of your drivers for your hardware are up-to-date

 

Hey Jim,

I Uninstalled everything and reinstalled FSX and only added my ORBX Australia scenery. I had traffic on 17% and everything else on low. I have a Intel i5 6600k, 16gb of ram and a GTX 980GTI. Everything is up to date and running smoothly on every other game with ultra settings. I treid the game again and it still crashed. I found reading through forums regarding the ntdll i could try this line of code in my fsx.cfg file:

[JOBSCHEDULER]
AffinityMask=12

I tried 12 and it still crashed so im going to try 14. If this doesnt work do you have any other suggestions?

Also my CPU isnt overclocked.

There is no magic fix for this error other than lower settings.  I wish there was a way I could say change the following parameter in the fsx.cfg but not possible.  FSX cannot run on high settings as you will get a StackHash and/or ntdll.dll error.  There is no system, not even my very powerful system (see specs in my signature), that can run FSX with max settings (well, actually, if you just run FSX without any payware add-ons, you can run FSX at max settings as I have done that and you can get very high FPS too.  I can even run the default weather program in thunderstorms with max settings with max default autogen and traffic.  When commercial add-ons are added though, things go downhill fast and I cannot enjoy FSX whatsoever unless I lower some of my settings).  FSX/FSX-SE are old software programs developed in 2006 and earlier.  FSX-SE received some minor updates but are still mostly under the licensing control of Microsoft so, any programming to make things work better is not going to happen with FSX.  P3D is based off of FSX-ESP which continued to be developed even after Microsoft laid off their programmers and is being updated.  It recently was upgraded to a 64-bit platform and you cannot use max settings with it too without getting an occasional ntdll or g3d crash.

i turned all my settings down so slow that the game looked terrible and yet it STILL crashed, what on earth is going on.

You will have to reinstall Windows and then install each of your add-ons and FSX-SE.   If you really followed my guidance in the AVSIM CTD Guide, page 10 (and you did not), you would find a solution to your problem.  That process requires removing your fsx.cfg, dll.xml, exe.xml, and scenery.cfg after you save each of them.  Run FSX-SE and your crashes should be gone.  If not, then you need to repair FSX-SE or figure out why just FSX-SE is causing a crash because it is not any of your scenery add-ons (it could be a commercial aircraft if you load an aircraft like PMDG's; if that is the case, then you need to figure out why the PMDG aircraft or whatever aircraft you loaded is causing your crash).  If FSX-SE is not crashing, then you return the scenery.cfg.  If no crash, then you return the dll.xml and exe.xml you saved.  It is really a simple process and it is required to investigate why your sim is crashing on YOUR computer.  Heck, it could be a low power supply unit or dirty fans or memory not properly seated or a corrupted user profile.  There is no way anyone can figure this out for you other than to give you guesses as to the cause because there is no one solution to your crashes.  An ntdll error could be caused by anything.  When I got my first ntdll error, I reinstalled Windows and then FSX then all of my add-ons and I had a ton of them.  That was several years ago.  Now I know I can probably solve my problem by following the guidance in the AVSIM CTD Guide. 

Well I finally Fixed it. In my starting BIOS i had a profile setting for me RAM. So i decided to set that to default and for some unknown reason, I don't crash anymore. Strange very strange. Thanks for all your suggestions Jim. It was where u said "memory not properly seated or a corrupted user profile." that lead me to fixing it so thank you.

On 2/7/2018 at 8:48 AM, Jim Young said:

fix for this is to mess around with the voltages or reset your BIOS to optimized defaults

 

20 minutes ago, mognut said:

In my starting BIOS i had a profile setting for me RAM.

Although I didn't specifically state RAM, this was one of my suggestions.  Setting the BIOS to the Optimized Defaults has almost always fixed an NTDLL error for me.  It also puts your CPU into turbo mode.  I have my BIOS set to Optimized Default and then set the OC profile to XMP so my RAM can be set at the optimal frequency. 

Really happy you got it figured out.  It is a very frustrating error.