Jim Young

Good luck! I think most products are now compatible. Best regards,

According to the AVSIM CTD Guide (link in my signature): G2D.dll - The g2d.dll is indicated as the faulting module in the crash report. This module handles plain text messages, like the frame rate counter and those other plain text messages you see periodically while running FSX and the plain text words in the FSX Menu, like the words Options, View, etc. There may be something corrupted in your dll.xml which loads menu items. It has been fixed by rebuilding the FSX.cfg (deleting or renaming the FSX.cfg and then restarting FSX). Some others have fixed this problem by uninstalling/reinstalling the video card drivers or going back to a previous version. Best regards,

We appreciate your kind comments and glad to hear the information in the guide provided a solution. We have a newer version in draft right now and I hope to release it before the end of the month. Best regards,

Yes, regarding MyTraffic, that's stated in the AVSIM CTD Guide as one of the possibilities. According to the developer, it's a scheduling program error. All of the AI have to have a flight plan to take off and land. If an AI does not have a flight plan, it cannot take off or land and the sim crashes. I thought this problem was fixed in MyTraffic6 but evidently not. You did the right thing by deactivating the military.bgl. I have not seen it yet in MyTraffic6. It was common in MyTrafficX5.4c. Best regards,

Must be something major wrong with P3Dv3.2. Glad you are able to fix your problem by restarting your computer. When something is not installed properly in P3D, all kinds of problems exist. Sometimes something as simple as starting P3D with administrative privileges will fix a problem. It could be a bad driver too. At least P3Dv3.2 works properly. It's just the addons that are not working properly or that's how I read your statement (obliged to restart the computer if I make a modification on P3D). Not sure what you mean by modification. Installing an addon or modifying the P3D.cfg? Many addons are not compatible with P3D and you have to manually install in hopes it will work as the developer has not issued a new installer for that product. If you move your dll.xml to a temporary folder and restart P3D, this will usually fix most problems. It's just that you have to find out what module in that P3D.dll is bad and causing the problem if you do not have anymore errors. Good luck! Best regards,

I got mine last June and really like it. I have the Dell UltraSharp U3415W 34-Inch Curved LED-Lit Monitor I purchased for $880. I would not pay much more than that if I were you! Best regards,

I hope to have a new version of the CTD Guide up on AVSIM soon. The new version will have more "how to images" which many like as they don't like to read everything I say. Best regards,

I'm glad you were able to find the cause of your crashes. It's always great to hear someone has their sim back up and running. In the P3D forum, there's a pinned topic on how to install v3.2 and all of the versions install much the same way. If you are reinstalling P3Dv2.5, I would install it into a non-default directory which would be something like D:\P3Dv2.5. You can name if D:\P3D too. Some show the version so they know right away what version they have installed. P3Dv2.5 is relatively old now. I think Lockheed is going to follow the installations like Microsoft did when they were in options. Microsoft released FS2000, then 2002, then 2004, then 2006. Each version was a new product and you had to purchase each one. Lockheed started out with V1, then V2 (did a bunch of updates), then to the latest, V3. Probably, in two years, they'll update to V4. If you can afford to buy V3.2, you should as it is getting some great comments from many. I say this as you have to be very careful down with an earlier version. PMDG for instance has products that work for just a certain version or you have to watch and make sure it states it is compatible with v2.5 thru v3.2). If it states just v3.2 it may not be compatible and you will have to down load an earlier version. Same goes with many of the other addons. The P3D forum has a pinned topic that tells you how to install EZDOK into P3D. Very well done. I recommend you check Elaine's tutorial. She did a great job. I do not own OPUS so cannot advise on the correct procedures. I know ASN is automatic and they install their own simconnect version too to make sure it works with their product. I've heard good things about OPUS. We have an unofficial forum here for OPUS and I see they just released a beta to their product - http://www.avsim.com/forum/577-the-opusfsx-forum/ Hope this helps. Best regards,

According to the AVSIM CTD Guide: Kernelbase.dll – No known fix but some have solved this problem by updating or reinstalling their video card drivers. Scan your system for corrupt/missing files (click for how to). Disable startup programs by opening the Run command on your computer and typing msconfig in the box. When open, look at the Startup tab and disable all startups (they are all not needed for operation of your computer). Since you just updated objectflow on FTX Central, expect this is the cause of your error. Have your tried disabling objectflow in the dll.xml, save, and then run P3D to see if this fixes the problem. If so, you have a corrupted dll.xml OR the update to objectflow did not happen and the old version is still there. Best regards,

The dll.xml does not get rebuilt if you delete it or rebuild it. The o byte P3d.cfg is probably the one that is built when you have an error in P3D. If P3D does not start up to the startup screen, 99.9% chance it's the dll.xml as all of the modules in this file have to be loaded. There are several in the dll.xml you had installed for v3.1 that are not compatible with 3.2. FSDT replaced their module, the Orbx/FTX module does not work, and the ASN modules do not work. So, that will stop P3D from loading. Move your dll.xml and exe.xml to a temporary folder and restart P3D (if you still have the .xml files as you indicated you deleted them above but then they were rebuilt which is not possible. Only the P3D.cfg and scenery.cfg can be rebuilt. Best regards,

If it is freeware for FSX, ask in the FSX Forum. If it is freeware for P3D, ask in the P3D Forum, etc. Best regards,

Thanks Nick. Greatly appreciated. Best regards,

Split from a very old topic. Please do not necropost. Best regards,

This module is being updated by FTX/Orbx. Just disable it in the dll.xml by doubleclicking the file. It will open in notepad. Look for the module entry and then look for the entry as follows: <Name>ObjectFlow</Name> <Disabled>true</Disabled> Change this line from False to True The dll.xml is located in the same hidden folder as your p3d.cfg. Best regards,

Glad it worked. There's a donation button to the right of this forum.... Best regards,

You have P3D installed in the default folder (x86) which is not recommended. You must make sure you have UAC disabled and any anti-virus program as UAC could cause problems and your system may deny access to you as a User. If you ever reinstall P3D, install it in a non-default folder like D:\Prepar3d v2. Prepar3D v3.2 has been released. You might consider upgrading but, going from v2 to v3 is $199 for a Professional license or around $50 if you meet the requirements for an Academic license. If you have fsuipc installed, there's a file within the Module folder entitled fsuipc4 install and it checks the installation of P3D. Make sure there are no errors. DINPUT8.dll is part of Direct X runtime from Microsoft and a video card driver could be the issue too. Not sure how to disable the internal Intel HD Graphics as that might be in conflict with your Nvidia GTX760 video card. I suspect you can right click on the Computer Icon on your desktop and select properties and the select Device Drivers and then Display Adapters and disable the Intel HD Graphics OR goto your Control Panel > Hardware and Sound > Device Manager > Display Adapters and disable. You can also click on your Start button and type device manager and look up in the menu and click on Device Manager. Also, try to check your DirectX and make sure there are no errors. Click on the Start button and type dxdiag and then enter and then look through the tabs to see if there are any errors. Best regards,

See the following image for fixing your problem: Hope this helps. Best regards,

Go to the FS DreamTeam website and download and install the Standalone Addon Manager. It has been updated for P3Dv3.2. Best regards,

Thanks for the info. Here is a possible solution to the dinput8.dll error http://www.avsim.com/topic/465564-p3d-v25-ctd-dinput8dll/. I suggested unplugging the USB cable and plugging it back into another USB port. It worked. That was for a Saitek controller. Most fixes are hit and miss. I hope this suggestion works for you too. The event viewer report only shows that your computer was shutdown improperly. Nothing serious as that happens occasionally. I sometimes inadvertently turn off my computer without realizing it was it was on. There was no other reason for the event. I would not worry about it unless it continues to shutdown improperly without any action on your part. I would also download and run a driver update program. I use Driver Booster, a freeware program that scans your computer for outdated drivers and then downloads and installs the drivers. The program has a lot of nags to try to get you to purchase it but it still does everything without buying - http://www.iobit.com/en/driver-booster.php Best regards,

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,