Jul 24, 2013 Thanks For Watching! Remember to like the video if you liked the video. Additional information below. Twitter. How to fix Crusader Kings II: Charlemagne Crash and Religion Tab issue Crash might occur at startup or just by clicking the religion tab, to fix the crashes following are the steps to be considered.
- Member
Post by knuckey on Nov 5, 2017 11:04:52 GMT
If you are experiencing blank event pop ups you haven't got the correct version of the base game, please update to 3.0.1 to fix this.It also seems many people are having issues loading the mod, so I'll start this thread to get all reports in the same place so we can try and better tell what the problem is.
This is only for CTDs whilst loading the mod, if you have any gameplay related bugs/CTDs please report in the bug reports section: citadel.prophpbb.com/forum5.html
Now if you do have a CTD on load please check the following:- Make sure CK2 is patched to the correct version. (3.1)
- Check vanilla loads properly and that the checksum is KKAD. If you have the wrong checksum you need to re-install CK2. If you have trouble with this please visit CK2 tech support: forum.paradoxplaza.com/forum/forumdisplay.php?679-Crusader-Kings-II-Tech-Support
- Check the mod is installed in <your documents>Paradox InteractiveCrusader Kings IImodA Game of Thrones
- De-select/untick any other mods/submods in the launcher
Ck2 Crash Processing Flags For Sale
If this is all fine please try a reinstall of CK2 and any DLCs, then delete the mod and reinstall that.Ck2 Crash Processing Flagstaff
If you are still having issues starting up the mod it is likely your system does not have enough memory. In general we recommend at least 4GB of memory on a 64bit operating system.More info from A-D on the Paradox forum, the problem maybe due to DLCs and not having enough memory:
EK has had that problem since a few updates, the mod essentially is feature-heavy and requires alot more RAM than the 2gb that Vanilla CK2 requires, for a while EK was in terms of memory-footprint the biggest mod. 32bit OS, such as XP are limited in RAM to 3.3gb, if the mod during load requires more, it crashes because it runs out of memory. So 4gb and above is essentially recommended for big mods at this point, this includes AGOT.
For a fix, there are only partial fixes. Turn off all graphic DLC stuff, Units, Flags, Portraits and start the mod. If it runs, you can play AGOT in vanilla mode. After this you can try to load up the mod by activating more and more graphical DLC until you get the Runtime Error again, if so then the amount of the last successful load is as much as you can have active at once. The heavier the mod gets, i.e. the more features and such are added, the less likely it becomes this will work if you have a 32bit OS or not enough RAM in case of a 64bit OS.
As an example, before the Essos update, i could run AGOT with every DLC released active, now i have to turn off essentially everything except the african portraits to get it to run.
Please note, this is only applicable if you get a Runtime Error, otherwise the problem might be elsewhere.
For a fix, there are only partial fixes. Turn off all graphic DLC stuff, Units, Flags, Portraits and start the mod. If it runs, you can play AGOT in vanilla mode. After this you can try to load up the mod by activating more and more graphical DLC until you get the Runtime Error again, if so then the amount of the last successful load is as much as you can have active at once. The heavier the mod gets, i.e. the more features and such are added, the less likely it becomes this will work if you have a 32bit OS or not enough RAM in case of a 64bit OS.
As an example, before the Essos update, i could run AGOT with every DLC released active, now i have to turn off essentially everything except the african portraits to get it to run.
Please note, this is only applicable if you get a Runtime Error, otherwise the problem might be elsewhere.