Jim Young

This is a known bug. Only way to stop it is to use the task manager. In the future go to Windowed mode by clicking on Alt - Enter. Do not ever use Alt-Tab. Okay, you didn't do that? Hit Alt-Tab? This means your flight simulator is not in focus. Check your Mouse settings to make sure it detects games. If that is enabled, then disable and check. I have never heard of an application open on the desktop where the Mouse pointers do not show up on the game that is open. You could have something scheduled running in the background. Maybe your anti-virus program or anti-malware program is scanning your system at a scheduled time. Maybe something is being downloaded for Windows Update or your anti-virus/anti-malware programs. You should check out the processes in task manager and see if anything that shouldn't be running is running. I know you can have a freeze during a flight over the water (water uses a lot of resources for waves, etc.). Make sure the water setting is not set to max. Freezes also occur when resources get low on your computer system (not the FSX-SE application). So, you could be showing 4GB's of VAS for FSX-SE and it could still crash if there's something running in the background taking up resources for your whole computer system. If you are running a browser in the background, that can sometimes be a killer depending on what's running and how many tabs are open. Another major resource killer is a wrong config of your virtual memory. I recommend "System Managed Size" but many think they have tons and tons of memory and try to set up their own and they mostly fail because FSX and most of the add-ons are resource hungry and they eat up any fixed settings fast. Click on your Windows search button and type in virtual memory, look up in the menu and click on how to change virtual memory settings or something like that. The strangest part of your problem is the fact the cursor is showing on the desktop but not in the application. That is certainly strange. This means that FSX-SE is not being seen for some reason by Windows. So, there you go! AI Smooth and RC are causing the freezes. I hope you are also looking in the right place in the Event Viewer as described in the AVSIM CTD Guide. Another possibility for the freezes/OOM's is tweaks. Tweaks do not work if not properly employed and most systems are not tweaked correctly. The Bufferpools tweak brings down a lot of systems as well as the AffinityMask tweak. If you have them, just comment them out in your fsx.cfg and try the flights again. Lastly, the add-ons you are running are know resource hogs. Lots of eye-candy. When on long flights and landing at a resource intensive area such as UK2000, the demand on resources is massive. I have the same situation here when flying from FSDT Chicago to FlightBeam's Wash Dulles. If I am flying a resource intense aircraft like PMDG's 777 and using ASN and then maybe turning on photoscenery for the area around Wash DC, I pretty much always have anomalies like freezes or an OOM or the sim slows to a slide show. I do not know of any solution other than to turn off the weather and disable the photoscenery. Otherwise I have to have my fingers crossed on landing that I can land and be able to taxi to a gate. In my case I'm going to see if I can disable some of the massive eye-candy in FlightBeam's KIAD or move up to a Haswell E system with a Nvidia 1080 video card. The AVSIM CTD Guide has many more suggestions on fixing problems like yours. Look at the back section on fixing freezes during flights. If you bring your FSX-SE back to the default by moving your fsx.cfg, dll.xml, exe.xml, and scenery.cfg to a temporary folder. This will mostly bring fsx back to the default. Run the flights again (if there are entries in the dll.xml for the Concorde or the Airbus or the Wilco E-Jet or the aircraft you want to use, you should then just disable everything else in the dll.xml instead of moving it so you can use the aircraft). Run the flight again and see if this fixes the problem. If so, it is one of the many add-ons loaded in the dll.xml or exe.xml or the scenery.cfg. Hope you find a solution!

My suggestions are based mostly on what I have seen around the Internet when individuals have unexplained BSOD's or crashes. I would just make sure the USB port is up-to-date. There are many USB hubs out there if you need one. Most computers have more than one USB port though and you can simply move a device from one to the other to see if this fixes the problem. Best regards,

A Stackhash has no known fix that works for everyone. You have to investigate. The AVSIM CTD Guide provides fixes that others found throughout the whole flight sim community. Greg posted one of those possible fixes above. I recently had a StackHash and found I had duplicate or a missing entry for ASN in the dll.xml/exe.xml. Caused by me as I was trying to merge all of my entries in the dll.xml located in the same folder as the P3D.cfg to the location in the folder where the scenery.cfg is located. Best regards,

I split your post from the other topic as it is difficult to figure out who's who and systems and things done to try to fix it. The OP of that topic had a module that was unknown. Your faulting module is known. I suspect you have checked out the AVSIM CTD Guide (link in my signature) and looked at the probable fixes for an ntdll.dll error. One other possibility that has fixed the ntdll.dll error for many is to rename the MyTrafficmil.bgl as this causes crashes for some (so far it has not for me). Just rename it to MyTrafficmil.bgl.off or .orig. If you do not own MyTraffic Professional 6a, then disregard. If you do own MyTraffic Pro, I would disable MyTraffic in the scenery.cfg. You will not have AI but you want to see if the crashes continue without it loading. If the crashes continue, then it is something else. The ntdll.dll is a system file and does not belong to the P3D or FSX installations. The exception code 0xc0000374 indicates a "heap corruption". It is a common crash and it usually involves high settings or a bad overclock. If your cpu voltages are off just one point, a crash will occur with the ntdll.dll shown as the faulting module. Hope this helps. Best regards,

Hi Jose, As is recommended on AVSIM frequently and in the AVSIM CTD Guide, it is best to turn off UAC and any malware/anti-virus program when installing new software (this includes Microsoft Essentials). I personally have exempted my malware program from scanning the directory where I have my flight sims installed. If you do not know the Source of a program that you downloaded from the Internet, then you should definitely have your anti-virus or malware program enabled but we all know that Lockheed's P3D is from a trusted site. The same goes when you download a software addon from FlightOne or Aerosoft. They are not going to allow any viruses or malware with their software and it is all perfectly safe. Best regards,

That's great news Phil. At 71, I've had several friends who have gone through cancer treatments and operations and have recovered fully and I know you can do it too. I was actually thinking of you earlier today as I had not seen any further updates for some time so I was shocked and pleased to see this topic back up and on top again. Best wishes for a complete and speedy recovery! My thoughts and prayers are with you for sure! Best wishes,

Go to Scenery/World/Scenery and rename trafficAircraft.bgl to trafficAircraft.bgl.orig or .off. Best regards,

Make sure you also install with Admin Privileges and UAC is turned off. Best regards,

FSX is a program developed in 2006 and has not changed like P3D has changed. The guide is being updated but only to add some information like where the hidden folders are located and how to uninstall/reinstall. Stuff like that.

If you have the fsx version and trying to install into P3Dv3, that is a separate download and purchase. The latest version is 1.11 for FSX and P3D. I think a lot of individuals tried to install it into P3D with the EMT which is not allowed and will cause issues. If you have the 1.11 version for P3D, then it should work properly. I do know that the Flight One i-Fly aircraft have a special dll that is installed and, in my case, it was tagged by my Malware Program (MalwareBytes) as malware and placed it into quarantine. I heard this can happen Microsoft Essentials too so you might check those programs and make sure the folder and the file are exempt from scanning by your anti-virus or anti-malware programs. Best regards,

None of the scenery were updated as the dates and times they were last modified are the same. Setup.exe (which is used to install the complete package) was modified though and is larger. Thanks Elaine for the comparison screens.

You cannot attach files on AVSIM. You can only copy and then paste the file in your topic or post. You go to your crash report and highlight all of the words in the crash report you want to copy and then right click on your cursor and select "copy". You then open up a Topic or post here on AVSIM. Place your cursor in the space for your topic and right click on your cursor and select "Paste". Your crash report will be displayed. Click on the following link for more information if necessary - http://lifehacker.com/5801525/help-new-pc-users-learn-how-to-copy-cut-and-paste Best regards,

I would leave them. They are not doubles. One is for 32 bit applications (X86) and the other is for 64 bit applications (X64). Even if you remove the X64 versions, Microsoft update will probably install them again. You're missing Microsoft Visual 2005 w/SP1 though. Could cause problems if an old addon you had installed in FSX needs it. Best regards,

See my screen at the link you provided.

I agree but I had to make my comments as I was not sure whether you had used it or not. Good luck with the reinstall of the FSDT stuff.

There are many other examples like the above quotes. Trolling is not allowed here at AVSIM (please read the AVSIM Terms of Service (again)). I have banned you from this topic. Please do not do this again. I have also been placed in the moderator queue which means any future posts on AVSIM must be approved first by a Moderator.

I just finished doing a flight from KLAX to KSFO and they were all there for me!! But I have a later version of P3D - v3.3.5. I doubt you can get a refund but I do know they will be updating this aircraft to be compatible with P3Dv3. Hopefully that will not be too long for you to wait.

So it must not be installed properly OR you are not following the instructions in the Navigraph G1000 manual and the G1000 Phenom300 manual. I used the Navigraph G1000 to learn to program the G1000. If it is installed properly, you will see a SID when you select PROC then Departure (after entering an arrival and departure location in the FPL). If you do not then it simply is not installed properly. To change the SID and departure runway, you MUST use the GCU 477 Unit below the G1000. It will not work using the inner and outer keys on the G1000. The GCU 477 is easier to use anyway. You hit FPL and the FPL opens with a blinking cursor telling you to select a destination first. You hit the inner or smaller knob twice and it opens a new window with a blinking cursor first and and a non-blinking cursor ready for input. On the GCU 477 you use the keyboard to enter your destination and then hit ENT. Use your Outer Knob to move down to the blank line for departure. Hit the inner or small knob twice and then use the keyboard on the GCU 477 and enter the departure location and then hit ENT. You now have your to/from done. Hit the PROC button. Use outer/larger knob to move down to the Departure (I use the middle button on my Mouse to do this) and then hit ENT. Use your outer knob to move down to the Departure SID. Use the inner or small knob to scroll through the various SID's. Once one is selected, hit ENT and your cursor will move to the takeoff runway. Use the inner knob to scroll through the various runways and select ENT. Your cursor will move to the Transition which you can scroll through using the inner knob. Once selected, hit ENT and you will be taken to LOAD?. Hit ENT. Your departure is now complete. Do the same for the Arrival. All very simple and it works perfectly (using the GCU 477). Again, if you do not see SID's when you move to Departure in the FPL, then your Navigraph Extension is not installed properly. Apologize for the delay in responding. Hope this helps.

See what you did Martin? When you try to abuse the moderators here, it just never works out. Did you see in our Terms of Service there is no Freedom of Speech here? Did you read the term about intimidating the volunteer moderators here? If you think you are going to shame me for removing your posts, that's just simply not going to happen. Please go somewhere else. Topic locked.

Topic locked as there is no need for further discussions of a company that steals the success of other websites.

Well, let's see how long this topic stays open. I do not see the purpose of bashing companies because one person (maybe you) had issues with a piece of software. Software bashing is basically, okay, not basically, it's trolling and subsequent posts can get pretty ugly. I see no purpose for trolling or bashing any product. An issue with a piece of software is between the individual having the issue and the developer and not subject to worldwide hateful conversations. Developers try to provide the best service for their software but occasionally problems ensue with some customers who were raised to expect only perfect and the best one on one customer support that any company can provide. It does no good in the flight simulation community to bash products because of one incident (or even two or three) because one could not get the product to work correctly. Thousands of other flight simmers have gotten the same products to work perfectly. Our forums are for discussions between users to ask for help, when needed, when one cannot figure out how to use a product or to get it to work properly. The forums are not here to bash a company or an individual or a product. If you want to do that, think about leaving the community now as you will not get a whole lot of membership support for your bashing or criticism of a product or several products. If you want to get back at a developer because he/she added a little "miserable git" icon to your forum avatar showing minus points, please do not do it here at AVSIM. This topic is locked.

You might have seen my post about the two locations of the two dll.xml's and exe.xml's a few days ago in the CTD Forum. I know many other websites picked up on it too. Although I recommended they be merged, that is not necessarily the best idea as many third party developers are still using the old location and the possibility of having duplicate entries would be increased. It does not hurt to have them in both folders as long as the entries in the AppData folder do not replicate any of the entries in the new location. If you get a CTD or a freeze, this is something you should look at. I do know removal of duplicate entries have stopped the ntdll.dll and StackHash errors for many when using FSX. I merged mine and so far no problems. I do not believe there are any requirements for the order of loading modules into P3D but heard somewhere that the ASN entries should be loaded last. I personally have ASN loading last. All modules will be loaded no matter what order they are in and that's the important thing. If there was an order, I believe the P3D SDK would show this requirement so the sim doesn't crash. Best regards,

I use the AVSIM FSX Configuration Guide settings. A little high but it wipes out the jaggies and I get good fps with fps locked at 30.

It does have a lot of Congressional aides and Congressmen flying in and out of there. But mostly they are incognito except for the holes in their jeans. B) I use to park in their "private" parking lot....

A repair will not change any of the default files UNLESS you move the default files to a temporary folder. Then the new default files will be installed. But a repair only reinstalls textures, bgls, etc. I have already done the repair several times and none of my configs were touched.