Jim Young

This link has possible solutions - https://support.microsoft.com/en-us/kb/2665946

There are several probable solutions in the AVSIM CTD Guide. Since you are not overclocked you can discount that possible solution. You need to move your p3d.cfg, dll.xml, exe.xml and scenery.cfg to a temporary directory (so you can put them back if the fix does not work). The P3D and Scenery.cfg will be rebuilt back to the default settings. P3D now has the dll.xml and exe.xml in the same folder as your p3d.cfg and there may be one in the same folder where your scenery.cfg is located. So you will have to move the files in both locations. You can also try just moving your p3d.cfg and scenery.cfg and rebuild those. Try the same flight and if the crashes stop, then the cause was in the p3d.cfg or scenery.cfg. If the crashes continue, you will have to move the dll.xml's and exe.xml's or disable each entry as shown in pages 13 and 14 of the AVSIM CTD Guide. If you want to use the PMDG aircraft, then you would have to disable every entry except the one for the PMDG aircraft. Best regards,

Make sure DX10 Preview is enabled under Graphics tab. This topic might be of interest too - http://www.avsim.com/topic/480970-all-dark-when-loading-aircraft-in-fsx/

Here are the latest topic views for your perusal. During this period we had 2,186,596 topic views! All of the forums are not listed here.

Make sure d3d9.dll is removed. It is a DirectX hack and does not belong in the main FSX folder. When FSX is started, all "dll's" in the main fsx directory are loaded. When SweetFX is installed, all of the files are placed into the main fsx folder and not a separate SweetFX folder unless someone wrote an .ini file and placed it in the main FSX folder directing FSX to look into a SweetFX folder. Best regards,

I was referring to the images in post #143 above.

I have a feeling npole is snookering the community. Jim

I went back and read them Bob. This comment is a big step forward from your earlier comments. I have REX products too and really like them and think they are also excellent products for the community. As a beta tester for ProATCX, you must know there was a lot of testing of AS16 and ASCA before it was released to you. I thought the list of testers was impressive.

Finally! I was starting to worry about you Bob as your earlier comments were certainly negative. Cartoon textures and clouds? Can't remember them all. There were a lot of experienced and talented beta testers for this product and I'm sure they were not too happy when they saw your negative comments. Personally I saw a whole new product almost immediately. Today I did a flight from KLAX to KSFO (my testing ground) and I saw a dramatic improvement not only with the clouds and weather but also the frame rate. With ASN, I honestly had to shut ASN down to save some frame rates in many cases. I have my limiter set at 35 and I saw the fps counter around 30 fps throughout the flight in the PMDG 737 and over FTX/Orx North/South California. I am really excited with this product. Best regards,

There's a manual in the C:\Program Files\Scenery Config Editor folder which explains these functions. Not too many people use them.

You removed the files from the main fsx folder and you still have the issue?

The AVSIM CTD Guide (see link in my signature) provides information on what files to remove. Look at page 30 for the d3d9.dll. You have to remove all of those files. Best regards,

We have enough topics on the release of this product already. In fact way too many. Please look around. This topic is locked.

Make sure it is not disabled. I do not think it is enabled by default. Type Java in your search bar in Windows 10 and then look up in the menu for Configure Java. Best regards,

Welcome Ivar! I hope you enjoy your experiences here at AVSIM. Lots of information and lots to learn. Enjoy! Best regards,

The P3D version.

I bought it for the upgrade price of $41.92 at SimMarket. I was logged into my account and it automatically provided me the upgrade. If I did not see the upgrade price in my cart, I would have backed out and investigated. I have since installed the product and it is very different from the latest version of ASN for P3D. I am impressed so far. I went to KLAX and there was some low clouds over the area. As I went through the clouds, I could see them rushing past my aircraft window. Extremely realistic so far. The clouds looked very nice too. Awesome job and thanks to the HiFi Team and their many beta testers! For FSX I think I will keep ASN. It works well there. I am slowly moving over to P3D as I think that will be the sim of the future. Best regards,

I would not merge the files. There are some programs that install in the new location like FSDT/FlightBeam entries. That's okay as long as they are not also in the old location (where the P3D.cfg is located). I had a StackHash when messing with mine as I somehow got the ASN entries in both locations. Just make sure there are no duplicate entries. One of these days everyone will be putting the entry in the new location (where the scenery.cfg is located). Best regards,

Your crash was caused by Microsoft Visual C++2005 w/SP1. It is used to make sure FSX was installed as Microsoft intended. Probably something wrong with the install of MSV 2005. Make sure you have the X86 version (32 bit) installed. You do not need the 64 bit version. See page 33 of the AVSIM CTD Guide. Best regards,

You are reading this wrong. That's the amount used, not left over.

The PMDG 777 is working properly if you have been flying with it for over six hours. It would not be working properly if it crashed when you first loaded it. The PMDG 777 does use some VAS but not much. It's whatever else is loading. I do not know if you use photo scenery but all of the photo scenery loads during a flight whether you are flying over it or not. So that's an important consideration. I once downloaded and enabled 41 MegaSceneryEarth products and their constant loading brought my current system to its knees. My aircraft would turn black and then a black screen and then nothing. So, you must not have too much photo scenery enabled if you are able to successfully fly for 6 hours but realize, whatever photo scenery that is enabled, MSE or Orbx/FTX stuff, or freeware stuff found on the Internet, it will eventually take down your flight simulator. We have discussed this in the past but high settings affect the amount of VAS. One of our members many years ago who has a private blog recommended a LOD_Radius of 9.5. Didn't take too long before his sim crashed. Many were able to use it for many hours but eventually the sim crashed. He then admitted this setting should not be used and recommend a 7.0 setting. IMHO, that's what too high too. The computer experts tried out the various LOD_Radius settings and found the best 'max' setting and then we have people who go out of their way to defeat that max setting. I don't know if you are doing that. It's just that I want to make a point that high settings do make a difference. I doubt you will be able to really enjoy flight simulation if your P3D constantly crashes w/o explanation. I do not know how anyone can figure it out for you or help you when you state P3D just closes down, no event, no OOM or any errors. BTW, it is impossible for an event NOT to be recorded when there is a crash to desktop or even a freeze. Perhaps logging for Applications and other types of events was disabled somehow or the Administrator of your computer will not allow users to see events. The Event Viewer some times provides valuable information to help you diagnose the issue causing your crashes but it does not always provide valuable information. Sometimes the cause is "unknown" but it still is a clue in your investigation of why P3D is just closing down without any Event of crash report. I have tried to detail the procedures to investigate "the scene of the crime" in the AVSIM CTD Guide because there is really no known solution that fits everyone when say P3D crashes without explanation. I had a StackHash 2-3 years ago and could not find a solution. I bit the bullet and reinstalled Windows 7 and FSX and P3D and each addon, one by one. After I completed this task, the StackHash error stopped. That's the worse scenario. A year or so ago, I had another StackHash but I had recently overclocked my system to 4.4GHz. I moved the overclock to 4.2GHz and the crashes stopped. Sometime later I got an ntdll.dll error and I couldn't find the problem but it happened on every flight. I decided to remove my overclock and changed the settings to the Optimized Defaults. Problem solved. No more P3D or FSX crashes. I hope you can find a solution to your issue too!

You need to update your Atheros WiFi Driver: http://sysnative.com/drivers/driver.php?id=athw8x.sys As suggested in the AVSIM CTD Guide, page 15, anyone who has upgraded their computer to Windows 10 or reinstalled their OS, should update their hardware drivers. I do it regularly by using a freeware program called Driver Booster - http://www.iobit.com/en/driver-booster.php. Best regards,

See fixes for the problem above your post. If none of the suggestions fixes your problem, then you will have to reinstall Windows and then your flight simulator. BSOD's indicate a serious problem with your hardware. Not with FSX or P3D. Best regards,

Check out the following link - http://www.avsim.com/topic/466233-fsx-se-pmdg-737-ngx/ Best regards,

This is not the latest version of the fsuipc utility. The latest is 4.9.5.5 http://www.schiratti.com/dowson.html. The module is periodically updated to fix bugs so it is important you have the latest installed. You are correct in selecting 'Yes' when asked if you want to run the module. This is part of the Windows security. If you select no, the module will still run but you will be asked again and again. Best regards,