August 1, 20214 yr What? crashing: You are flying along, monitoring your flight with your cup of coffee at the ready, everything is going great... and then... you are now looking at the desktop. Your computer is running just fine, but your flight, quite rudely, is now over. You can go into the event log and see the fault report. CRASHING: You are flying along, monitoring your flight with your cup of coffee at the ready, everything is going great... and then... your computer shuts down OR your computer restarts OR you are looking at the BSOD. These are very different things. crashing: There is a problem with the code in the program you are running causing it to error and close. Your computer is fine. CRASHING: There is a problem with your computer hardware, or driver, and your computer shuts down or restarts. What does it matter? It matters because these two very different types of issues are being mixed together as the same thing as the 'crashing' issue with SU5 is being discussed. CTD is being used for both. As I understand it, CTD is describing 'crashing' not 'CRASHING'. It is causing a lot confusion and bickering. Kind of like this: Jane: "Since SU5, I've been getting CTDs whenever I fly from point A to point B. The program Just closes to the desktop". [crashing] Joe: "Yep, you have a faulty memory stick, same thing happened to me a while back". [wrong] or Bill: "I've been getting CTDs when flying over major cities. The computer just shuts down and I have to start it back up". [CRASHING] Mary: "Yep, you need to empty your community folder, same thing happened to me". [wrong] What to do? crashing: First, remove everything from your community folder to make sure it is not an addon causing an issue. If it helps, add them back one by one until you find the culprit and report it to the developer. If removing addons doesn't help, report the issue to the ASOBO and wait for them to fix it. Work around... the 'crash' may only happen in certain scenarios or with certain planes. Adjust accordingly until the fix is made. Keep an eye on the forums for any such discoveries. CRASHING: You have some troubleshooting work ahead of you. There could be any number of things wrong. The 'likely suspects' are overclocking, bad memory, bad fan, bad or inadequate power supply, faulty or out of date drivers or eating too much sugar. Not a lot of fun, but very rewarding when the culprit is discovered and you learn a lot in the process. Unfortunately, people who have computers that are CRASHING will waste a lot of troubleshooting time avoiding the reality that there is an issue with their computer. Usually that time is spent blaming the program they are running or berating people online that are trying to point out to them that they have a problem. This will go on for eternity. [NOTE: The distinction of terms 'crashing' and 'CRASHING' is not any kind of standard terminology, I just used it here in an attempt to point something out.]
Archived
This topic is now archived and is closed to further replies.