Jim Young

The Links System no longer exists. Impossible to maintain as members would not keep the links updated. The link in your topic is dead and I have removed it. Perhaps you have a better link? Best regards,

This is just a friendly warning to our membership that AVSIM.ru or AVSIM.su are rogue websites and AVSIM Online! or AVSIM.com or AVSIM, Inc. has no associations whatsoever with these websites. Be very careful when downloading files from AVSIM.ru or AVSIM.su. We attempted to take legal action as they would not voluntarily shutdown their website but laws between here and the respective countries are hard to enforce. This is just a warning that the sites are a scam and violate our name copyrights and users should be very careful if they visit these locations.

Split from another post. Trying to manage several types of crashes in one post is difficult. The ntdll.dll crash is common. There are many suggestions for fixing this crash in the AVSIM CTD Guide (see link in my signature). There is no known fix that works for everyone. You will have to investigate "the scene of the crime". AVSIM recommends you move your p3d.cfg, dll.xml, and exe.xml (if you have them) to a temporary folder and then restart p3d and the p3d.cfg will be rebuilt. This fixes a majority of the crashes as many employ tweaks in their p3d.cfg that are not compatible with their computer. The dll.xml and exe.xml load modules that might be incompatible with P3D so, if rebuilding the P3D.cfg did not fix the problem, then you need to see if one of the modules inside the dll.xml is corrupted or incompatible. This is explained in the CTD Guide how to modify the dll.xml and exe.xml to try to find the offending module. Lastly, if overclocked, this is a know cause of this crash if your cpu voltage is too high or too low. You can play with the cpu voltage or return your overclock back to the defaults and start all over. If you are not overclocked, this this does not apply. EDIT: Did you upgrade to P3D 3.2 yet? That might fix it too. Best regards,

I did not know the g3d.dll error was a problem in fs9. You are the first to bring it up as far as I know. Perhaps if you contact Pete, the developer of FSUIPC, he might set up a trap for FS9 too. I do not know how p3d was able to fix this problem as p3d is FSX with some updates. Best regards,

The water slider and the special effects. Best regards,

Hi Gerard, Maximum size for each file uploaded to our Library cannot be larger than 500MB's. I probably misspoke but I remember Tom allowed large files 2 or 3 years ago to be uploaded but I believe he handled the uploads personally and may have made it only a temporary section. I forget what the files were about but believe it was photosceney in France. In any case, you would have to break the files down into 400-500MB's to post them as that's the rules for now. Apologize for creating the confusion. Best regards,

Please use the PM system to post private messages. Just put your cursor over the individuals username you want to contact and select "PM this member". I have split this post from the old topic you use to correspond with Rick and then removed (hid the posts from public view).

Scan your system for corrupted files - http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm Best regards,

Here is my most recent log from the latest FSUIPC for FSX: And here it is from an earlier version (note at the bottom of the report it showed what the fix did: Best regards,

Not sure the fs9 version of the fsuipc.dll traps the g3d.dll error. You will have to look into the fsuipc log and it will tell you whether it is actively trapping the error or not (plus the number of times it trapped the error). I recall a recent post where the developer of fsuipc stated it is no longer required to trap the g3d error in P3D as Lockheed fixed the problem. In any case it is not actively showing the g3d fix being installed. If you are having g3d errors in fs9 and your fsuipc log is not showing the g3d fix being installed, then I know of no solutions other than reformatting your system, reinstalling Windows and then fs9. I strongly believe an addon is incompatible with the version of the g3d.dll installed for fs9. Best regards,

I know of no other solution. Sorry. Are you using one of those hacks called the ENB or SweetFX? Best regards,

My understanding is the fsuipc is not fully compatible. So far for me it is active in my dll.xml and loading just great but many here have stated it is not compatible and needs to be updated by Pete. It's an easy thing to check out. Best regards,

Move the dll.xml and exe.xml (if you have them) to a temporary folder and restart P3D. Most likely a module not working properly. Best regards,

You do not want to have the dotnet 3.5 from the Program and Features section turned on. Make sure "DX10 Preview" is enabled in setup for black setup screens. Best regards,

There's a possibility they are already installed. In the CTD Guide there's a link to the verification tool which you can use to see if Microsoft.net 1.1 or 2.0 is installed, etc. Required dotnets for FSX are installed with FSX. FSX needs 1.1 or 2.0 (32 bit, not 64 bit) as FSX is a 32 bit program. So make sure you downloaded the 32 bit and not the 64 bit versions. Best regards,

Glad you were able to find the cause. I'm not familiar with VATSIM whatsoever as I have never used it in all my years of simming but the model C172 comes with FSX deluxe but not with P3D. The C172 has sounds and gauges and not all of the required files are in the C172 folder. Some are in the Gauges folder in FSX. I'm surprised VATSIM would have required you to have the C172 in the P3D folder when it was never installed in P3D. I suspect you will need to go to VATSIM Forums and seek a solution there (unless you have a copy of FSX). Good luck! Best regards,

Split from a very old topic. The post from mstreibig referred to by OP can be found here - http://www.avsim.com/topic/370138-xtreme-prototypes-lear-20-autopilot-problem/?p=2413855 Best regards,

You have FSX SP2 installed. The error was caused by your computer system and the uiautomationcore.dll belonging to Windows. The uiautomationcore.dll is part of the Microsoft.net packages that are used by Microsoft to make sure you application (FSX w/SP2) works properly. You need to make sure you have Microsoft.net 2.0 and 3.5 installed (see page 7 of the AVSIM CTD Guide). You can also try installing one of the uiautomationcore.dll's on page 7 and 8 of the AVSIM CTD Guide. One of those versions are placed in your main fsx folder. See my signature for a link to the AVSIM CTD Guide (new version to be released soon!!). Best regards,

The error or issue was acknowledged by Lockheed but it does not mean they are working on a solution. Only a very small minority of P3D users are having this issue. Personally I would reformat my HDD/SDD, reinstall Windows, and then P3D. Why continue to suffer? Best regards,

Split from another topic to avoid confusion as the crash in the other topic was totally different from this crash. You did not indicate system specs such as: Windows 10; i7 4770K; GTX 780; 8GB's RAM; 34 inch monitor, etc. From the AVSIM CTD Guide (see link in my signature): AppCrashView (click to download) - when you get a CTD, a Windows Error Report (WER) is generated by Windows. This report is not very detailed and Microsoft did not make it easy for you to find or interpret the report. AppCrashView interprets the Microsoft WER reports and provides more details. If you post a CTD in the AVSIM CTD Forum, you should copy and paste the latest crash report in your topic or post. Along with this, include your system specifications (if not already included in your profile). Check the Windows 7/8 Event Viewer – The Windows Event Viewer can provide a wealth of information regarding your CTD or information about your crash that may not have been recorded in a Windows Error Report. Plus there could be other problems being reported that need to be fixed that could be causing your application crashes. You can get to your Windows Event Viewer by clicking on the Start Button and, in the Search box, type Event and then look up in the Menu and click on Event Viewer or use the guidance at the following link - Opening Windows 7 Event Viewer. Windows 8 users should follow the guidance at the following link: Opening Windows 8 Event Viewer. Once the event viewer is open, click on Custom Views and then Administrative Events (this provides all events from all Sources). The Summary of Administrative Events will show you the various types of “Events”. Critical (which should be fixed as soon as possible), Error, and sometimes Warning Events are what you should be interested in. Administrative Events will show you everything that happened to your computer each time you turned it on and while it was running from the day you installed your Windows OS. If you find an error relating to P3D in the event viewer, double-click the error and a new window will be created. This is the error report we need to see. In the lower left corner click on "copy". This will copy the error to the clipboard. Now come back here and respond and then paste the error into your new post. Without further information, as defined above, it is very difficult to determine what might have caused your crashes. Hardware like throttles, mouses, and keyboards cause your system to crash as the hardware is not compatible with your version of Windows or not installed properly. A driver update program like the one I use - Driver Booster - will search for outdated drivers and then download and install the new drivers. This fixes a lot of problems. If you installed P3D without disabling UAC or your anti-virus/malware programs, this could cause these problems too. Disable any anti-virus or malware program. This is all outlined in the pinned topic in the P3D Forum - http://www.avsim.com/topic/481623-my-link-thread/ Hope this helps. Best regards,

Some have fixed this by uninstalling the drivers, restarting your computer, and then installing the drivers recommended by Windows Update. Some of the Nvidia display drivers contain bugs and Nvidia released a new driver to fix that problem. So, if you have not yet installed the latest drivers, then you should. I am using the 362.00 driver w/o any problems. Best regards,

Caused by bad overclock where cpu voltages are too high or too low; tweaks in P3D.cfg; high settings in p3d.cfg; addons like ezdok or any other software not make totally compatible with P3Dv3.1. No fix for this crash is the same for everyone. It depends on YOUR system and your setup. If you disable or uninstall ezdok, the crashes stop? Did you install ezdok using the guidance in the pinned topic in the P3D Forum? Did you install any products using the EMT? To begin investigating, you need to bring P3D back to the default: move p3d.cfg, dll-xml, exe-xml, and scenery.cfg to temporary folder. Restart P3D and let p3d rebuild your p3d.cfg and scenery.cfg to the defaults. Crashes still occur? That removes the likelihood of a bad overclock. move dll.xml and exe.xml (if you had them) back to the folder where your p3d.cfg is located. Move the scenery.cfg back. Run p3d. Are there crashes? If so, there is a problem within the scenery.cfg or dll.xml and/or exe.xml if applicable. Hope this helps. Best regards,

I adhered to the quote. No tweaks. Just used the NI settings and set LOD_Radius to 6.5 and Texture_Max_Load to 2048 or 4096. I'm also using DX10 Preview with Steve's DX10 Fixer. Best regards,

I don't know for sure. Does the troubleshoot compatibility program look for updated drivers to your hardware and install the updated drivers? I don't have Windows 10 installed yet but anytime you update drivers for your hardware in Windows 10, that can only be good as hardware and software developers are always finding bugs and issue updated drivers to fix compatibility issues with Windows 10. Same thing happened when XP, Vista, Windows 7 and Windows 8 were first released. It took some time for developers to issue updated drivers. I believe the compatibility program takes you back to Windows 7 or 8 as Microsoft found some of your drivers were not compatible with Windows 10. I would try to update your drivers by downloading a program that does that. I use Driver Booster which is freeware but it has a lot of nags to get you to purchase it. Still it is fully functional and will download and install updated drivers if found. I use it regularly as Windows 10 doesn't look for updated hardware drivers for all of your hardware, like USB ports. Best regards,

Have you thought of uploading to our Library too? Best regards,