Jim Young

Make sure the C172 aircraft.cfg has the following entry: [fltsim.4] title=Cessna Skyhawk 172SP G1000 sim=Cessna172SP model=G1000 panel=G1000 sound= texture=G1000 kb_checklists=Cessna172SP_check kb_reference=Cessna172SP_ref atc_id=N700MS atc_id_color=0xffffffff ui_manufacturer="Cessna" ui_type="C172SP Skyhawk G1000" ui_variation=" Glass Cockpit" ui_typerole="Single Engine Prop" ui_createdby="Microsoft Corporation" description="A stable and trustworthy plane, most pilots have logged at least a few hours in a Cessna 172, since it's the most widely available aircraft in the rental fleet, and is used by most flight schools. Since the first prototype was completed in 1955, more than 35,000 C172s have been produced, making it the world's most popular single-engine plane. One of Cessna's first tricycle-gear airplanes, the 172 quickly became the favorite of a growing class of business pilots. Its reliability and easy handling (along with thoughtful engineering and structural updates) have ensured its continued popularity for decades." Make sure you have a folder under C172 entitled: model.g1000 and panel.G1000 and texture.G1000. Best regards,

99.9% of all BSOD's are caused by a hardware failure of some sort. Most likely cause is a corrupted or bad driver. I cannot see how any software program like P3D can cause a BSOD. The only possibility is with high settings and that will cause a BSOD with the 0124 bugcheck. A software program that places a lot of resources on the system settings like FSX/P3D will trigger a too high or too low CPU voltage setting or another setting in any overclock. It is impossible for me to overclock my system higher than 4.4GHz and I have found the stable setting at 4.2GHz. Overclocks will not allow you to push your computer to its limits. Maybe for 2 or 3 sessions with P3D but it is going to bite you eventually. There are many computer experts (of which I am not one) who have succeeded to defeat my theories on overclocking. I have run all kinds of benchmark tests to try to get my computer to BSOD with an overclock set at 4.6GHz and it refuses to crash. I load FSX (haven't tried it with P3D) and my computer crashes with a BSOD (again, a computer system problem, not a software problem). Your images are very difficult to read. Best regards,

The ntdll.dll error and the StackHash are covered extensively in the AVSIM CTD Guide (see page 36) (link to guide in my signature). There is no known one thing that causes these two errors but the guide provides some "fixes" that worked for others (we googled the Internet to look for solutions and these were what was found). I doubt the aircraft you were flying caused the crash but, like the PMDG aircraft, more resources are being used. Make sure the aircraft is compatible with P3D as that could cause the crash too. Once other possible fix that is not in the AVSIM CTD Guide is a possibility that the mytrafficmil.bgl located in MyTraffic6\Scenery may be causing the errors. When individuals disable this .bgl, the errors go away. Hope this helps. Best regards,

AA does not work well in FSX at all. A known fact. You can reduce the jaggies but not completely eliminate (although mine appear to be perfect). If the AVSIM FSX Configuration Guide did not eliminate the jaggies, then you have a tweak or something else happening that is causing an anomaly. For one thing, you cannot set all of your settings to the max and expect no jaggies. FSX evidently was not programmed properly to allow that to happen. You MUST enable AA in FSX for it to even work. So, why my AA has no jaggies and yours does is definitely a mystery. I do not use tweaks at all so this might be your issue.

If you have the ENB Series or SweetFX hack installed, this could be the cause. DX10 has issues with those hacks. DX9 does not. There is no known solution that works for everyone. Some have found that recent security updates to Windows or Windows Updates have caused the problem. They uninstall them and everything works again. If it happened when you start up FSX, there could be an incompatible module being loaded in the dll.xml. You can move the dll.xml and exe.xml to a temporary folder, restart FSX and see if this fixes the problem. If not, move the dll.xml and exe.xml back. Some have fixed this problem by moving their fsx.cfg to a temporary folder and restarting FSX. FSX.cfg will be rebuilt. You may have a tweak or other corrupted setting in the fsx.cfg. Happens frequently. Hope this helps. If not, try some of the suggestions in the AVSIM CTD Guide (see link in my signature). Best regards, Jim

I suspect you are referring to the file in our AVSIM Library - http://library.avsim.net/esearch.php?DLID=196456&CatID=fsxmisc. Just stating this so everyone will know what you are talking about (okay, I was a little confused about your subject). Best regards, Jim

The machine_check_exception BSOD indicates you have a major hardware problem - https://en.wikipedia.org/wiki/Machine-check_exception. Same goes with the clock_watchdog_time_out BSOD. See page 14 of the AVSIM CTD Guide in regards to updating your hardware drivers (link to the CTD Guide in my signature). In regards to the FSL_A32XX.dll error, see the following link for the fix - http://forums.flightsimlabs.com/index.php?/topic/7178-installation-instructions-for-v101172-fsx/. You evidently had your anti-virus program running. Best regards, Jim

Let's lock this one up. OP had another username here too (similar) so I merged them. It is strange the developer has offered to assist and the individual all of a sudden is too busy to receive support.

I think this topic has run its course and has been discussed enough. Topic closed.

I have decided to unlock this topic. Apologize for the inconvenience. Best regards, Jim

In the same folder as your FSX.cfg, there should be a "dummy" default scenery.cfg. This should never ever be edited, moved, or deleted. If you should accidentally delete your "working" scenery.cfg located in C:\Program Data\Microsoft\FSX, then FSX-SE will rebuild using the one the "dummy" default scenery.cfg. If somehow, FSX-SE was not installed properly and you have no C:\Program Data\Microsoft\FSX-SE folder, then it cannot rebuild the file. So, you need to look in C:\Program Data\Microsoft\FSX-SE folder to see if there's a scenery.cfg located there. If so, move it to a temporary folder. The one that is located in the same folder as your fsx.cfg will then be able to rebuild it. Right now it simply cannot rebuild it as the one in the C:\Program Data folder is corrupted and cannot be read. The folder holding the fsx.cfg and dummy scenery.cfg is hidden. So is the folder in C:\Program Data. See the AVSIM CTD Guide, pages 5 and 6 on how to unhide these hidden folders. A link to the AVSIM CTD Guide is in my signature. Best regards,

The AVSIM CTD Guide has information on how to fix BSOD's. BSOD's are related to hardware issues and mostly are caused due to bad or incompatible drivers for a piece of hardware. Best regards,

48 hour flash sale - http://www.justflight.com/product/flightsim-commander-9

It's how I learned to tell others. High overclocks like your 4.8GHz can sometimes become very unstable. I have my OC down to 4.2 GHz and have seen no problems for a super long time and no ntdll.dll errors. I personally do not see any performance improvements with major overclocking. Just more frustrations. Best regards,

The AVSIM CTD Guide provides possible solutions to the kernelbase.dll error (see link in my signature). Best regards,

Hi Howard, The dll.xml is not a default file with P3D. It is built when you install a product that requires/uses it such as FSDT, FlightBeam, Carenado, Orbx, FSUIPC, PMDG, etc. So, if you deleted it and P3D started up okay, it means there was an entry or module that was missing or corrupted as it shows your problem at the beginning was something in the dll.xml (as I stated early on). So, any add-on that uses the dll.xml and exe.xml will not work properly or not at all. In the folder where your P3D.cfg is located, there should be several saved dll.xml's. One might be dll.xml_Before_Addon_Manager. If you have one like that, you can rename it to dll.xml. You will have to reinstall the FSDT Addon Manager to get those entries back into the dll.xml. So, if you have a problem with an add-on running, it is most likely a module did not load properly through the dll.xml. Best regards,

If you get another ntdll.dll crash or 0124 BSOD, I can say for almost certainty, it is the overclock that somehow got corrupted. As I stated (and also in my CTD Guide), I have fixed the ntdll.dll error many times by lowering my OC or going back to the Optimal Defaults. When I get a BSOD with the bugcheck code of 0124, I immediately know what caused it. My overclock. I'm not an expert at overclocking but playing with the BIOS is my forte'. When I overclock, I search Google with a question like "how do you overclock an i7 4770K on ASUS z87" or something like that and I get JJ from ASUS giving me instructions on YouTube - https://www.youtube.com/watch?v=Z7zPu9255ZI So, if you run into problems again, I suggest you try that too. Best regards, Jim

The Thermal Status shows OK everywhere. So what's the problem? Makes no difference if a core runs hotter than others. It's still OK according to RealTemp. Benchmark programs and RealTemp programs have been found to be unreliable by me. I have ran them all when I had issues and they all passed with flying colors. Then, I run FSX and it crashes. So you have no idea how to overclock but you have the i7 4790K overclocked to 4.8GHz. (100 x 48). So, how did you get it overclocked to 4.8 because that is not a normal overclock. Any computer overclocked and especially up to 4.8 is subject to many issues. It is difficult to overclock to 4.8 unless you know exactly how to set the CPU and vcore voltages. So, since you have no experience tinkering with and overclock or the BIOS, an "expert" must have overclocked it for you. You need to go into the BIOS (usually by hitting the DEL key or F2 key several times while the system is booting up), and reset the setting to Optimized Defaults. Or you can go into the BIOS and change the 48 to a 42. I recommend the optimized defaults. Had I known you had your system overclocked to 4.8GHz earlier, I would have recommended this immediately. Overclocks are bad if not done properly. They will work for a month or two but it will eventually give you issues if not done properly. I know this for a fact as it has happened to me on many occasions and returning it to optimized defaults fixes the problem every time. Best regards,

The AVSIM CTD Guide, page 11, provides a picture and instructions on how to enable/disable modules in your dll.xml to find out which one is causing the issue(s). But the fastest way to see if it is the dll.xml is to move it to a temporary folder, restart P3D and see if P3D restarts. If it does, then there is a problem with the dll.xml and you will have to investigate to find out which module is not working properly. I have seen where the wrong version of the fsuipc.dll will cause P3D not to restart if it is not compatible with P3D. The link to the CTD Guide is in my signature. Best regards, The CTD Guide provides instructions regarding the Event Viewer and how to fix the issues. Check out the pictures and instructions! You can reinstall the academic file but it will overwrite your p3d.cfg and scenery.cfg. So you might want to back up those files. Otherwise, there should be no problems (unless you have GEP3D that replaces the default textures or Orbx Global/Vector products). Those will have to be reinstalled.

You cannot. You can go to the the topic and open up the post and then, in the upper right hand corner of the post, just to the right of the post number, left click on it and it will provide a link which you can share with others. If you don't want to share the link then you could copy the link and come go to your post and paste it in your post via the "Link" icon in the menu of your post. Hope this helps. Best regards,

If you cannot start up P3D, it is usually a corrupted add-on that uses the dll.xml to load their module. All modules in the dll.xml are loaded at startup. The sim will not start up if one of the modules is missing or corrupted. Best regards,

Ah! A new system! I like it! When one gets a new system, usually settings go much higher in the config and display driver settings (otherwise, why move up to a more powerful system?). Unfortunately, you cannot buy a new system and move 'ALL' of the sliders up. You just eat up VAS much faster with a newer system as you can render more textures faster. Fortunately a newer system with the same settings as the old system will provide better performance and quicker rendering of textures and other neat stuff but not eliminate OOM's. I have stated this in previous topics where we ran FSX on systems back in 2006/2007 that are not as powerful as today's systems and we rarely ran out of VAS because we kept our FPS slider to no higher than 30 and ran our systems with a max of 4.5 LOD Radius. Many had to reluctantly lower the 4.5 LOD to a 3.5 LOD as they really had under-powered systems!! Then someone came up with a guide (not on AVSIM) where one could raise the LOD_Radius to 9.5 and came up with some tweaks that worked for some but mostly not all. Then we had many who had OOM's and even the individual who came up with higher LOD_Radius settings said they were too high and he lowered them to only 7.5. With settings like that you are just eating up VAS faster. The max slider for LOD_Radius for P3D is 6.5 and I consider that very high for most if not all systems because your sim has to render more textures in a larger area. Couple that with payware aircraft and scenery and you'll see OOM's much faster than in FSX. Maybe I'm all wet but the way I see it. If an application can go to 64 bits and you have an unlimited amount of VAS (well, almost), then maybe it will reduce the number of OOM's no matter what the settings. But we are not there yet. Hey! I have some good news. AVSIM will be releasing a P3D configuration guide soon (very soon). Our resident expert, Rob Ainscough is almost finished. Still it won't stop the OOM's but it will give you some good guidance. Best regards,

I have never been able to fly longer than 4 hours with the PMDG 777 in P3D. I think it is impossible. The flight from FSDT Chicago to FlightBeam's Wash Dulles is close to 3 hours. When I'm coming in for a landing my VAS goes from just over 1GB to suddenly 500MB's and as I land I am hoping I don't get the dreaded OOM. Sometimes I do, sometimes I can at least taxi to a gate. I turned off cloud shadows and things are much better but I still run low on VAS. This is actually impossible. Please do not make statements like this. If you use the FSUIPC utility, you should set it up to log the amount of VAS usage during a flight. It will look something like the following: The AVSIM CTD Guide provides information on how to set up the FSUIPC to monitor the VAS and log it. VAS will go up or down depending on the activity. When you complete the flight it will show you exactly what your VAS usage was and the average FPS during the flight. Your AMD CPU is not very powerful and this may be a cause for issues with P3D. P3D uses more resources than FSX and uses DX11 whereas FSX only has the ability to use DX10 Preview. DX11 allows for more eye-candy rendering. I have found that shadows are a killer in P3D and have turned them off. I just have shadows for the aircraft and VC. That works for me. If I want to take a screenshot of my clouds and the shadows hitting the ground, I'll simply turn them on. But I do not need them during flight. Best regards,

Hate to see you go. Have you ever reported an offensive topic or post? There's a report button on the bottom of each post that you click on to report trolling or offensive comments. Our moderators cannot be everywhere all of the time and this report brings the topic to our attention. We will act appropriately. What is offensive to you may not be offensive to me or one of the other moderators but we will act. Trolling is everywhere on the Internet and people post just like to incite someone because they know they can get some people very upset. They hope you will troll too so they can report you for trolling and maybe get you suspended or receive some other punishment. My advice is not to feed the trolls. We know who most of the individuals who like to incite and troll but the offense is not enough to ban or suspend someone. In most cases we will just remove the post from view when reported (to include any responses to the troll). It's the best we can do. This includes topics started by trolls. Trolling is not allowed based on the AVSIM Terms of Service. I have no problems with suspending someone for 7 or 30 days for trolling but I would rather just remove the post or topic first. If he/she continues, I will suspend the individual for 7 or 30 days at a time until he gets the message to stop trolling in our forums. The following link is one of my favorite blogs about trolling - http://www.osnews.com/story/25540 Best regards,

You should check out the AVSIM CTD Guide (see link in my signature) for posting AppCrashView reports or posting an Event View. There are also suggestions on how to fix any crash.