![]() Many malware programs and anti-virus programs have false positives and quarantine files they think are malware when the file is not a virus or malware. Also look in the History tab and then Quarantine and make sure there is nothing related to P3D or a P3D in there. Goto the Malware Exclusions tab in WinPatrol and exclude the P3D folder and any addon folder from being scanned for malware. You should disable WinPatrol from loading with P3D. I also saw that you have WinPatrol loading with P3D (loaded module #87). It can only be done by a freeware program that you can download from the Internet (search Google). FSX/P3D will not allow you to disable DEP. Disabling DEP has worked for some but it is not the recommended solution. If disabling the program in the Scenery Library works, then you should reinstall the product and use the default schedules. There are also AFCAD’s that come with MTX and some of those may contain objects. An AI schedule might be causing this crash as the schedule may be looking for a flight and it cannot be found. One known solution is disabling MyTrafficX 5.4c in your Scenery Library. There is no known solution (except one) to BEX/StackHash errors other than reinstalling Windows and FSX but some have accidently fixed their problem by lowering fsx/display driver settings, rebuilding the FSX.cfg, changing voltages/overclocking settings in the BIOS, disabling all scenery add-ons in the Scenery Library, and/or shutting down FSX only in Windowed Mode and starting up in Windowed Mode but never in Full Screen. That represents the memory address of where the fault occurred. If the StackHash is shown as the faulting module, it will have four characters next to it like StackHash_0a9e. There is no module on your computer system named StackHash so no need to look for it. StackHash – See also BEX and NTDLL.dll above. Here's what the AVSIM CTD Guide says about a StackHash: a BEX/StackHash crash is very difficult to diagnose. Hope this helps (in regards to your crashes). AVSIM is set up to use BBCodes and if you copied the HTML line, you would have to use the "Link" option in the menu above and paste your HTML link in that box and it would post it here in your post. It did for me when I first used it and I had to do a lot of trials and errors before I figured it out. I use the same website for posting my images here and it's a great site but they have so many options for you to use it gets a bit confusing. When you post, the image will show up right here and one does not have to click on your links and go to another website. A bunch of options will show up and the option you want is "Image Embed Codes" and then copy the BBCode line and paste the line in your post or topic. The next time you post a link to your images, I would recommend clicking on "Embed Codes" just below your image. Did you look at your AppCrashView Report again to see if it is still the "facilities.dll" as the faulting module? ![]() If the crash occurred while starting up P3D, the problem is in your dll.xml (which you shouldn't have if you have a "virgin" install of P3D). So, how you got the facilities.dll crash with a "virgin" install of P3D is beyond me unless you ported over your old scenery.cfg into the new installation. Look in the anti-virus quarantine section and make sure no false-positives were found for any P3D files/addons.īut your crash report indicates the cause was the facilities.dll and this faulting module has been known to show up when you have AFCAD's that are duplicate and conflicting. Make sure no anti-virus program is scanning P3D while you are using P3D. If you installed a new airport scenery, make sure you installed it properly and ran the install program as the Administrator. So, if you own Taxi2Gate KSEA, you should disable the KSEA AFCAD in the AI program. The developer recommends you disable any AFCAD that duplicates a commercial airport scenery. The AI program MyTrafficX and MyTraffic6 has hundreds of AFCADS located in the MyTrafficX/Scenery folder so that the AI aircraft can properly take off and land. If the error no longer occurs, it is one of the sceneries. You may have to disable all addon scenery by unchecking each in the Scenery Library or scenery.cfg (make sure you disable all airport sceneries). If you own MyTraffic6 or MyTrafficX, disable that program in your scenery.cfg and see if that fixes the problem. Did you recently install a new scenery? An AI program? If you just installed new airport scenery, I would disable that first and see if the error returns. In FS9 and FSX this error was usually caused by duplicate and conflicting AFCAD's.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |