June 7, 201411 yr Hi, I am a long time user of MSFS and have bought a new Dell inspiron 15r with Windows 8 on it and have installed FSX on it. After finding out it keeps on crashing, I brought down the settings on everything except Graphics and Aircraft Quality but that didn't work. I tried uninstalling all freeware aircraft I had on FSX and sticking with all my payware planes but that didn't work. I installed the two Service Packs for FSX AND Tried updating to Windows 8.1 but even that didn't work. I love FSX but now it's becoming really frustrating :angry: as it crashes whenever I save, load, start, end or accidentally crash into terrain. I have tried converting fsx.cfg into Fsx.orig but that made my computer really slow for 2 minutes. I have adequate RAM, Hard Drive Space and Video Card but it just doesn't work! How can I solve this? Thanks. ======================================= Computer Specs: Dell Inspiron 15R with Intel i7 Core with 2GHz and an AMD Radeon Graphics Card with 8GB RAM and 1TB Hard Drive Space (793GB Remaining).
June 7, 201411 yr Windows 8.1 is a whole new OS that brought in much more security so that users would not be attacked by those ruthless individuals who like to spread malware and viruses. Most 8.1 users have gotten FSX to work very well on their system. I think the solution to a successful installation is turning off some of these security features and to install FSX to a non-default directory like C:\FSX. Here is a link to a great guide to help you install FSX - http://support.precisionmanuals.com/kb/a87/how-to-uninstall-and-reinstall-fsx. You state you have installed the two service packs which means to me you do not have Acceleration and have FSX/SP2 installed. That's okay. I'm just verifying as you will have all sorts of problems if you were to install FSX, the two service packs and then Acceleration. They are not compatible. You do not have to convert your fsx.cfg to fsx.orig. It was just a suggestion in the AVSIM CTD Guide (and other places). Most move their FSX.cfg to another directory, like C:\Temp, restart FSX and the config will rebuild. Sometimes individuals fail to rename or move the wrong file as the directory where FSX.cfg is located will just show 'fsx' and you have to look at the file type to determine whether you have the configuration or the text version. Whenever there is an FSX crash, FSX makes a FSX.txt file (this was done so the file could be sent to Microsoft in case you wanted them to analyze your crash). So, if you renamed or moved that text file, nothing happen. The FSX.cfg continued to function as before. Also, when installing FSX and addons, you must disable User Access Controls and any anti-virus program (as recommended in the uninstall/reinstall guide I linked to above). If these were enabled during your installation of FSX, files may not have been installed completely and registry entries might not have been made as these security programs are worried the application you are installing (FSX) is a virus or malware and won't let the installation program make required registry entries. Of course, there are many addons that have security built in too to discourage pirating and, if not properly installed, will simply not work (thinking you might be a pirate). You did not provide any information as to what caused the crash (the faulting module) so I assume you did not see our AVSIM CTD Guide located to the right of this forum under Hot Spots. Page 1 and 2 provide details on how to download and run AppCrashView which provides critical information about your crash(es). The guide also provides guidance for looking at your Event Viewer in Windows 8 to see if there are any errors there that might give us a clue as to what caused your crash. After that, AVSIM provides guidance on how you can investigate what I call the 'crime scene'. It is very difficult for outsiders like us to diagnose your issues as we do not have your computer in front of us. Renaming or moving your FSX.cfg is just one way to possibly fix a crash. Another method would be to disable every addon scenery in your Scenery Library and see if this fixes the problem. If not, then you need to disable your modules in the dll.xml. This pretty much brings your installation of FSX completely back to the original without any addons installed. If you have aircraft addons, then you can disable them by simply moving the aircraft folders to another directory like C:\Temp. If this fixes your problems, then you need to start adding those addons 2-3 at a time until the problem reoccurs. This way you can narrow it down to what caused your crash(es). Near the end of the guide, you will find possible or probable causes for certain crashes, some by just looking at the faulting module. I hope this helps. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
Create an account or sign in to comment