PLEASE READ THIS CAREFULLY AND FOLLOW ANY INSTRUCTIONS ENCOUNTERED. Yes, that means doing the stuff that is suggested. If it says "all", it does not mean "whatever you feel might be relevant", but "all".
Many who ask for help give us very little information about what is happening at the time, and it makes the process of helping out ineffective. We will from now on just refer people to this post if we get too little information from you. If you were given a link to this thread (or referred to my sig), this means you. Try to answer each question, and add any other information you think would be useful.
Also please create your own thread with your report, do not reply to an existing one. This is to avoid confusion about which problem the answers are addressing, and most of all to avoid that the original poster's problem is drowned and forgotten.
If your problem is nontrivial, such as a bug that we have never seen before or have investigated with no success earlier, you can expect it to take quite some time before we can fix it, even weeks or months. You should start a new campaign in the meantime, not wait for the solution.
CRITICAL INFO:
POST YOUR SAVEGAME. Here's how.
REALLY IMPORTANT INFO:
- Did you remember to post your savegame?. Here's how.
- Which version are you playing? If you do not use 1.1 yet, please upgrade and start a new campaign.
- On the same topic, do you have any unofficial mods installed?
- Have you applied all the permanent fixes for 1.1 in this sticky? If not, do that right now, even if they don't seem relevant. Even if you don't even currently have a problem and wandered here by accident. These fixes will make no damage to any part of the game. Pay attention to the installation instructions for each, and your problem may be solved. If you have got them already, check that there are no updates since you last did.
- Have you tried all the temporary fixes in the sticky mentioned earlier? If not, do that right now, even if they don't seem relevant.
- It didn't work? Please post a report.
- It worked? Great, your campaign is resurrected! Please post a report nevertheless, as we need it to find better, permanent fixes and to make the next version as stable as possible.
- Does it still crash if you do not enable the background script?
- Have you tried it 3 times or more, with consistent crashes?
- Did you remember to say which version you are playing?
IMPORTANT INFO:
Some of this can be hard to find out, but if you use the toggle_fow console command you'll be able to see it better. You can use console commands by tapping the key right below Esc on your keyboard.
- Did you remember to post your savegame?. Here's how.
- Have you diligently started the background script every time you loaded the game? Occasionally not having it activated will probably not make any difference, if you're lucky, but running most of the game without it is likely to make stuff inconsistent (this means crashes).
- What is happening when the crash occurs? Are you attacking someone, were you attacked, were you conducting diplomacy, was the AI doing its turn (if so, which faction?) etc.
- Where does stuff happen when the crash occurs? This makes us able to focus more on the area in question instead of looking around the map.
- What year is it?
- Are any cities about to rebel? There are apparently all sorts of bad stuff that can happen with this. We've eliminated most, but a few rare cases seem to remain. In particular, but not only, have you evacuated any city to let it rebel? If so, try to move one unit in there so that it can be ousted upon rebellion.
- If it's a crash upon clicking end turn/during AI turn: Does it still crash if you cancel all your construction and recruitment orders?
HELPFUL INFO:
This is somewhat complicated, and usually will not be necessary, so feel free to skip it. If the first couple of suggestions we make don't work out, at some point we'll probably ask you to get a Filemon/ProcMon log and/or installation validation for diagnosis. Refer to the linked posts for how to do that.
Bookmarks