Jim Young

So it doesn't work for you with those settings? I appreciate the advice you are providing but we need to know if it works or not. Personally I don't use tweaks and, if there are any tweaks that might work, the benefits are minuscule. Let your computer breathe and turn down your sliders a bit. It is not as powerful as you think. The OP's image shows cloud shadows. Turn off cloud shadows. I think that's a major performance hit. Just leave shadows on for your internal and external simobjects. You can then play with the sliders in other areas to try to get the best visuals possible. But tweaks are not going to make it. If a tweak worked, I strongly believe LM would have recommended the settings or put the settings into the default configuration as they want the best visuals possible. It would be nice though if someone could come up with one of these tweaks, turn up the sliders for the eye-candy and the images are perfectly clear. Best regards,

Well, since you have pinpointed the cause of the CTD is Radar 2.0 and or FS Panel Studio, you would get better support by posting in the appropriate forum (FS9). So I will move it there as the users of FS9 seem to have an in-depth knowledge of FS9 and the associated add-ons. Best regards,

I really do not think this is the proper forum. Trying to use SweetFX in DX10 Preview is possible - https://sfx.thelazy.net/games/preset/1089/ as some others have done it but I heard it is very difficult. AVSIM has a SweetFX forum where you might find a preset that works for you. I think there were many discussions about SweetFX in the DX10 Forum here too. It appears the cause of the API.dll crashing is SweetFX. The api.dll is used to run FSX properly. Never heard of getting a CTD when you select 'show desktop' but almost sure it is because you are using an older version of the API.dll, or have parts and pieces of the SweetFX hack installed which is making it difficult for FSX to work properly. Please do not discuss SweetFX issues in this forum. Go to our SweetFX forum. Thanks. Best regards,

I hit enter after entering the departure and it always shows as the departure. Then I enter the arrival and hit enter and it shows the departure and arrival in proper order. I then enter procedures. I do have problems entering a departure runway or SID and have to use the lower GCU 477 unit and that seems to work most of the time. But the key is to hit the Enter key after entering the departure and arrival airports. I have flown this aircraft so many times now entering a flight plan and it always works for me but it took me a couple of times before I realized I had to hit enter after entering the departure airport. I did go on YouTube to do some learning of G1000 and did not see the adverse reports. I agree there are glitches but it does work. Whenever I enter a procedure for landing, it works flawlessly and I can almost keep my hands off the controls. So, you already knew there were problems but you were trolling in hopes someone would come on and trash the product? If you knew the product didn't work as the FlightOne product, why troll? Just post that such and such does not work in the Carenado G1000 and it works perfectly in a Flight One product. No reason to troll. Plus trolling is a violation of our Terms of Service so be careful. Write exactly what is wrong with the product and go through the procedures you took so others can try to replicate or provide better advice on how to program the G1000. Best regards,

You need to submit an AppCrashView report or a report from the Event Viewer (see AVSIM CTD Guide, page 1 and 2) (see link in my signature). Hopefully it will provide more information about the crash. Also list your system specs as that might help us too. Best regards,

Not sure what you are asking. All G1000 gauges are modelled the same way for all aircraft. Do not think Flight 1 or Carenado would change the method. They all have exactly the same buttons. The Carenado G1000 is exactly like the real one too. Best regards,

Split from a very old topic.

Split from old topic in FSX Forum and place in this forum...

You are receiving a StackHash error which is impossible to fix without investigating and sometimes reinstalling Windows. It is accompanied by an ntdll.dll error most of the time. It is related to memory. This issue is currently being discussed in detail in the topic next to yours. I would recommend reading the suggestions contained in this topic - http://www.avsim.com/topic/483639-p3dv31-strange-ctds/. Yours may be easier to fix though as you have SweetFX installed or, at least you installed d3d9.dll in your main P3D directory. Known to cause problems unless properly configured. One bad entry in the .ini for SweetFX and crash. It is extremely difficult to get it to work properly all of the time without getting a CTD periodically. Best regards,

The last four digits are the memory address where the crash occurred. One time the error will be a StackHash and one time NTDLL.dll (not only in P3D but in any program ever developed such as Internet Explorer, Microsoft Word, etc., etc.). There is no way the SDK could have created or caused this problem. If you move your dll.xml over to a temporary folder the crashes will stop. Right? That indicates there is a program connected to one of those modules which is triggering your StackHash and placing a massive amount of resources on your system. You have to find out why. So, did you move your dll.xml, p3d.cfg, and scenery.cfg to a temporary folder and let the sim rebuild the p3d.cfg and scenery.cfg? Did you then reinstall vPilot and then try to get back onto VATSIM successfully? You need to determine if it is vPilot and VATSIM that are causing the problems and not one of your other addons. It's the only way I know of to investigate these crashes except to run Process Monitor and see what was loading when the CTD occurred. That's hard but not impossible as Process Monitor shows thousands of things loading in just one minute of your flight session but it usually shows the same thing loading for several seconds and then another file loading for a few seconds more during that minute. You can readily see what was loading in maybe the last 3 minutes of the flight session before the crash occurred. It could give you a hint. For instance, you stated earlier that you uninstalled your AI program and maybe you'll see that loading and you can ask yourself, "why is that loading? I uninstalled it". On page 5 of the AVSIM CTD Guide I discuss setting the Process Monitor up but I'll quote it here again: "Run Process Monitor – Another investigative tool used to pin down a situation where your application freezes, crashes, or stutters/pauses during a flight is to run a utility called Process Monitor. During your flight, this utility monitors activity such as calling textures, AI aircraft schedules, ATC, weather updates, and scenery loading. When FSX/P3D stutters or FPS drop dramatically you simply write down the time it occurred. This is important as thousands of entries are made every minute, every second. Continue doing this throughout the flight. Of course, if it freezes, you will know what was going on before the application froze. This utility will not show you a definitive cause of your issue but it will show you what add-ons were being loaded about when you received the stutter, the long pause(s), and the freeze and you can further investigate by disabling that scenery, that aircraft, or whatever might have caused the event. One member used this utility to determine that My Traffic X, version 5.4c was the cause of a BEX/StackHash/NTDLL.dll crash he was getting. It was easy to disable My Traffic X in the Scenery Library and find that FSX no longer crashed. AVSIM recommends you do not run a flight any longer than 60 minutes as the Process Monitor log becomes quite large (hopefully your application will freeze or crash by then!). For a 60 minutes flight, expect the file to be at least as large as 8GB’s or tens of millions of captured events. Make sure you delete the log or move it to another drive after you have finished your testing to free up HDD space. Another recommended tip is to make sure you use system time to mark the time of each event and do not use an external clock unless they are synchronized. Going through one minute of a process is a massive amount of data needed to be reviewed (it goes fast as thousands of entries just show a scenery being loaded). To run this utility properly, you need to capture only FSX/P3D/FS9 events. It would be nearly impossible to find a possible glitch or issue if Windows events or other system activities were being logged too. AVSIM recommends opening of the Process Monitor when you are on the active runway and preparing to takeoff to save space on your HDD: Startup FSX/P3D/FS9, as appropriate, to the Setup Screen. Open Process Monitor Click on the Filter tab and then Filter…. Click on Architecture and scroll down to Process Name Click on blank box and select FSX/P3D/FS9, as appropriate Click Ok or Apply NOTE: AVSIM recommends you click on the filter tab again and then select ‘Save filter…’ and name your Filter – FSX (or P3D/FS9). Then, in the future, you can startup Process Monitor before opening your application and watch what is loading as your application loads to the Setup Screen. You can use the utility while in Full Screen mode or Windowed Mode. In Windowed Mode you can monitor what is happening instantly but it is best to run Process Monitor in Full Screen (unless you are seeing freezes in Windowed Mode). When the flight is finished, immediately go to the Process Monitor application, click on it to bring it into focus, and hit Ctrl+E on your keyboard to capture the events (event logging will continue until you do this and make it more difficult to locate the cause of your crash). Shutdown FSX/P3D/FS9 and begin your investigating! You can also save the log for future investigations but remember the file will be as large as 8GB’s or more and using valuable disk space." Your can also try renaming the logbook.bin in the same folder as your P3D.cfg. The logbook sometimes gets corrupted but P3D will run w/o it. It shows all of your flight sessions and, in fsx, it was known to get corrupted and cause crashes. Finally, you have brought your OC back to the default so you can rule that out (with the voltages) as that is the most common cause of this error. You will definitely get rid of any StackHash error by reinstalling Windows (ugh!). That is how I fixed mine one time. You obviously have something that is affecting your installation of P3D. Maybe it's malware but something is not allowing you to run P3D properly. Yet, before you do reinstall Windows (if you decide to go that route) I hope you will try bringing your P3D back to the default and/or running Process Monitor. Best regards,

You need to send us AppCrashView report or an Event Viewer Report (page 1, AVSIM CTD Guide). Best regards,

Also, make sure you have the fix - highmemfix=1 in the Graphics section of the FSX.cfg. Many forget this parameter when first installing or deleting the config and letting it rebuild. The AVSIM FSX Configuration Guide provides many useful suggestions for setting up FSX. See link in my signature. Best regards,

I don't understand this comment. You are connnected to the Internet via wireless LAN? I guess that might make sense if you have a Laptop. So, if that's the case, and you are trying to connect to VATSIM and you lose the wireless connection for some reason, wouldn't that crash FSX? If you reinstalled your sim and all of the addons again, your crashes will likely not stop. When you move the p3d.cfg and scenery.cfg to a temporary directory, and then also move the dll.xml and exe.xml to a temporary directory, you are back to the default configuration of P3D when you first installed it (after you restart P3D and let the the configs rebuild). You can then install vPilot and try to get onto VATSIM. None of your addons that used dll.xml and exe.xml will load (FSDT, FlightBeam, FSUIPC, ASN, your recorder program, PMDG) and will not be available to use during the session but you can at least see if you can get onto VATSIM with crashing. If that works, then you can start installing GSX, FSUIPC, ASN, etc. No need to uninstall as the programs will simply overwrite your current installations, create a dll.xml and exe.xml, but your will have to reinstall or select the "repair option" if offered. Remember, P3D v3.1 does not like incompatible products that are installed using EMT. Most products can be successfully installed but there is no guarantee. When you purchased P3D, you purchased P3D and not a bunch of addons along with it. FSDT is fully compatible as well as FSUIPC (the correct version) and ASN as made their product compatible but really they are not fully compatible as there are bugs to be found by users like yourself and, when reported, the developer fixes the bug and issues an update. So, there is still no guarantee of compatibility. When the PMDG 777 and 737 were first released for P3Dv3, they were not compatible as they installed an outdated version of RAASPRO and the module had to be disabled in the dll.xml to get it to work. PMDG did release an update almost immediately though. Still there are many reports of incompatibility for some users and it is probably caused by improper installation of the addon, not P3Dv3.1. Best regards,

Good luck! The security in Windows 10 really makes installing products made from earlier OS's more difficult to install and get to work properly but, I think if you follow my suggestions you will have no problems. Best regards,

I doubt anyone has installed this product into Windows 10 as many have updated to the latest and greatest version so I think your only option would be to try the install it yourself. GEX replaces the default fsx textures with optimized textures and I would make sure you have FSX SP1 and SP2 installed OR Acceleration as those programs update textures too. I know of no programs made for FSX that will not work in Windows 10. Windows 10 does have a lot of security and you will need to disable UserAccessControls (type User Access in the Windows 10 search bar and then look up and click on "How to Change User Access Controls". When open, pull the slider all the way down to disable it). I would also disable any anti-virus and malware programs you might have installed too. When you install the program, right click on the installer and select Run as Administrator. I think GEX was one of the first programs to be released after SP1. UTX came around that time too. It was exciting times... EDIT: I just noticed I was in the FS9 area. It should work with FS9 too if the product was made for FS9. Best regards,

I found a solution but not sure it will work - http://www.avsim.com/topic/430364-rex-4-not-working-because-of-net-framework-45/ Also page 9 of their manual shows where it is installed with REX4 - http://www.realenvironmentxtreme.com/rex4td_install.pdf and is required for proper installation. Page 8 of the manual says to not install it into the Program Files (x86) area because of too much security. If you did, I would reinstall into a folder outside of the Program Files (x86) area like maybe C:\REX4. You should also make sure UserAccessControls (UAC) are disabled and any anti-virus or malware program is set to exclude the folder where you are installing the product and FSX or just disable them until the product is installed. To disable UAC, click on the Start button, type User Access in the search bar and then look up in the menu and click on How to Change User Access Control Settings. When UAC opens up, pull the slider all the way down to the bottom to disable. Best regards,

According to Allen at UTX, it should work okay with any FTX region - http://www.simforums.com/forums/question-about-utx-with-ftx_topic55060.html (might need to be registered and signed in to view). Best regards,

The dll.xml and exe.xml are not installed with P3D. They were added by an addon (usually FSDT is the first to install if as most people install FSDT airports soon after installing P3D). FSDT installs the Addon Manager which is in the menu when you open P3D up. The best thing to do his is to simply download and run the latest Standalone Addon Manager from the FSDT website. That will fix any problems with Couatl. Best regards,

It is a wrong assumption to assume you won't run out of VAS with 400-500MB's of VAS remaining. I've done it. After a long flight, say from Chicago to Dulles International (FlightBeams KIAD HD) and the weather is nasty things are going great during the descent until the final approach. Then my VAS fluctuates wildly from 900 MB's to 300 MB's to 600 MB's depending on the situation. If you have high P3D settings, high autogen, a weather program like ASN, descending into an area where there's a lot of eye-candy (like KIAD-HD), then don't expect your VAS to stay all of the time between 400 and 500 MB's. For an instant it will drop to 200 MB's but recover and go back to 500 MB's. You may not see it as you're busy looking elsewhere. I've seen this in live action and it gets to be very frustrated as I just completed a great 2 hour flight and I'm descending into a nasty weather situation and landing at a neat airport. When I see these situations, I turn off ASN and I might even turn off autogen just so I can complete the flight. But, is this the way of flight simulation? Absolutely not! Everyone wants to turn on their eye-candy (or else why did you buy it?) and you want to make some challenging situations. You are not giving us any information as to what you were doing before the OOM. Were you on a 10 hour flight with ASN enabled and flying the PMDG 777 and descending into a payware (eye-candy) airport with high autogen and high P3D/Video card settings? Was your system overclocked to the max? There are just too many variables to determine exactly what causes an OOM but we are positive it was caused by running out of VAS. But we are not certain what is needed to stop OOM's. Just reduce P3D/Video Card settings or do we also have to disable any commercial weather program, fly a default aircraft, turn off autogen and shadows? What else? But that's where you can investigate this yourself. I have accomplished many flight between Chicago and KIAD in the PMDG 777 and found that I can usually land with around 400 MB's of VAS if I turn off ASN and disable autogen. Not all of the time but "usually". Since I monitor VAS with the fsuipc.log, I have a desktop icon that leads directly to the log. I can then immediately open up the log and review it. I might make some comments or indicate what I was flying and what other addons were running (like ASN). I'll then save it as something like KORD_KIAD_PMDG777.log. But this is how we investigate as not all systems are the same or set up the same so you have to investigate YOUR situation and try to find out why you are suffering from OOM's. Hopefully, one of these days when we have almost unlimited VAS for P3D (only in a 64 bit P3D on a 64 bit OS) then we can start to crank up the settings and turn on all of the eye-candy and tell everyone about our crash involving something else as it won't be an OOM (or an OOM will be highly unlikely). I think we get about 7 or 8 tigabits (guessing tigabits as the next thing after GB's) of VAS which will be bigger than any HDD or SSD. I use the FSUIPC.log to record my VAS usage from the beginning to the end of the flight (the FSUIPC module is the one that issues warning dings that you are close to running out of memory). It shows me at the end the avg amount of VAS I had available and the highest amount and what was the lowest recorded. It will also tell me my average frame rate during the flight. So it just takes an instant for the VAS to plummet to around 200 MB's and crash your sim and that's just a blink of the eye. Good luck finding your OOM. Best regards,

This is why it is difficult for anyone to help as only you know the facts. We (Steve and I) are guessing based on past experiences. The ntdll.dll and StackHashes are system related issues and they are common with all apps, including Internet Explorer and other outside programs. So it is not just related to P3D or FSX. You mentioned you got rid of your AI program and MyTrafficX, v5.4 caused an unexplained ntdll.dll and StackHash for me 2-3 years ago. My sim was always crashing at the same location on a flight plan so I loaded Process Monitor and monitored just FSX and FSX addons. When the freeze/crash occurred, I closed down Process Monitor and then looked at the log to see what was running or loading when the incident occurred. It turned out MyTrafficX was loading AI aircraft so I disabled MyTrafficX and the freezes/crashes stopped. Further investigation by the developer indicated the AI program could not find an AI schedule for the aircraft in the area and shut FSX down. AI programs have flight schedules for AI to follow and, if a flight is missing a plan to take off and land somewhere, it crashes. This was subsequently fixed by the developer. I think if I had turned down my AI slider, it would have stopped the crashes and I run it at 30% now with MyTraffic6. I owned UT2 but never used it after buying MyTrafficX so not sure how you uninstalled UT2. Did it remove everything? This is where it gets to maybe it would be best if you reinstalled P3D or run the installer and select "Repair" when asked. A repair will bring your P3D and scenery.cfg back to the default but will not touch the dll.xml or exe.xml. It will bring the SimObjects.xml back to the default (located in your scenery.cfg folder). So you might want to back up those files if you decide to try to do a repair. Whenever you reinstall or repair a sim like P3D you should never use the old P3D.cfg but you can bring back the scenery.cfg so you won't have to reinstall all of your scenery. There are hundreds of crashes involving the ntdll.dll. A corrupted entry in the dll.xml or exe.xml can cause the ntdll.dll error. I remember once getting the ntdll.dll error and found two duplicate entries for one of the PMDG modules. I removed one and the ntdll.dll error went away. In the dll.xml at the link you provided, the as_btstrp.dll belongs to ASN and is required. It also looked properly entered. The IVAO module might belong to VATSIM? Don't know but figure that was the likely cause of his crashes. Most crashes involving the dll.xml occur when loading to the startup/setup screen as the modules are all being loaded at that time. I suspect a module in the dll.xml causes a crash when it is needed during a flight session and a program is calling for a certain version of the module and it does not see it so it crashes as the module cannot be loaded. This is why we recommend in the AVSIM CTD Guide to disable each module in the dll.xml one at a time until the culprit is found. If you have a lot of modules, that could take some time but you can disable 2 at a time and, if there is no crash, you can figure it was one of those two modules. I wish there was a magic bullet for the ntdll.dll and StackHash but there is not. You have to investigate "the scene of the crime" and hopefully you'll eventually find the cause. It is a frustrating crash as I have had it several times but, only once, did it take a few days to find the problem and that was with the MyTrafficX schedule related above. Best regards,

I would first disable EZDOK in your dll.xml (or uninstall it). That program has caused crashes for many others in the latest version of P3D. I have seen a lot of crashes with individuals going onto VATSIM too. I suspect you are using vPilot and that has caused problems if not properly set up. However, I see you have successfully used vPilot and VATSIM so I may be blowing smoke again but just saying those programs are sensitive. I don't use VATSIM but is it totally compatible with P3Dv3.1? Is UAC disabled and do you have any anti-virus program running and scanning your P3D folder during a session. You can go into the anti-virus program and disable scanning of certain drives or folders, like the P3D folder and the folders that your addons are located. There's an addon that is just not compatible with P3Dv3 and we need to figure out which one. I'm suspecting vPilot since your crashes are occurring as soon as you get onto VATSIM. Best regards,

Agree. Time to close this topic.

When I experienced the StackHash and NTDLL errors, one time it would be a StackHash error and the next day an NTDLL.dll error. But I was able to prove without question my OC caused the errors. I would get the NTDLL error, bring the OC down from 4.4 to 4.2 and the crashes would stop. I would move the OC back to 4.4 and they would occur again. Forgot to mention that as lowering the OC a notch or two may fix the problem too. On my system, I found it impossible to maintain a stable 4.4 for any length of time. I have the ASUS Z87 Deluxe MB and it has a way to OC automatically but you have to make a couple of manual settings and the Board does the rest. I am very stable at 4.2. When I had it at 4.3GHz, it went for a month or two then crashed, go for a month or two and then crash and so I just lowered it to 4.2 which I think is more than enough to run P3D and my add-ons. Best regards,

Ah! You might have been reading the AVSIM CTD Guide on StackHash crashes and NTDLL.dll errors! A bad OC is the last resort as bringing back your overclock would take some time if it turns out it wasn't the OC. However, I have fixed a lot of my ntdll.dll and StackHash errors by bringing my OC back to the Optimal Defaults. It's usually a too high or too low CPU voltage setting and you could try raising or lowering it a notch. Make sure UAC has been disabled. I see you have EZDOK in the default folder (Program Files (x86)). If UAC is enabled, Windows 8 could be denying access to P3D. EZDOK has caused a lot of problems with P3D as it was not developed for installation in P3D and individuals have been using the EMT to get it installed and are having major problems almost exactly like you are having (NTDLL/StackHash). I would disable EZDOK (EZCA) in the dll.xml and exe.xml as suggested by Steve and see if this fixes the problem. You can also move your dll.xml and exe.xml to a temporary folder, restart P3D and see if this stops the crashes. If so, there is a module in the files that is not compatible with P3D. Best regards,

That was great Steve! Covers it all! Best regards,