You're not alone, the game is crashing quite frequently for some since the latest launcher update a week or so ago. On the official Paradox tech forums there are recent numerous crash report threads https://forum.paradoxplaza.com/forum/forums/crusader-kings-iii-tech-support.1078/ as well as here on steam https://steamcommunity.com/app/1158310/discussions/1/

In the meantime we just have to wait until they push an update out. The crashing isn't affecting everyone, so they're not in a rush.

Try the Dark Ages Mod, it seems to be stable for me.

Originally posted by *s*t*a*r*s*:

You're not alone, the game is crashing quite frequently for some since the latest launcher update a week or so ago. On the official Paradox tech forums there are recent numerous crash report threads https://forum.paradoxplaza.com/forum/forums/crusader-kings-iii-tech-support.1078/ as well as here on steam https://steamcommunity.com/app/1158310/discussions/1/

In the meantime we just have to wait until they push an update out. The crashing isn't affecting everyone, so they're not in a rush.

I've played the game without mods and its functioned just fine. A little bit of lag when I zoom in or out, when the map has to load, but other than that, no problem. Vanilla is running perfectly. Its only when playing with the AGOT mod that I encounter problems.

Originally posted by Seva:

Try the Dark Ages Mod, it seems to be stable for me.

Thank you for the suggestion, but I'm really only interested in playing Game of Thrones mods.

After the update with dragons came out, I decided to try the AGOT+ submod on the regular AGOT. Before that, AGOT worked as it should. After I installed AGOT+, after about 10 minutes of the session, the game started to crash. At first, I thought it was because of AGOT+ and deleted it. The game still crashed. Now it doesn't even load into the game, and at the moment of loading, the game just crashes. Vanilla works, but AGOT, even without submods, stopped working completely. Did you solved this problem? Or should we wait for fixes?

Originally posted by 𝐝𝐮𝐝𝐞:

After the update with dragons came out, I decided to try the AGOT+ submod on the regular AGOT. Before that, AGOT worked as it should. After I installed AGOT+, after about 10 minutes of the session, the game started to crash. At first, I thought it was because of AGOT+ and deleted it. The game still crashed. Now it doesn't even load into the game, and at the moment of loading, the game just crashes. Vanilla works, but AGOT, even without submods, stopped working completely. Did you solved this problem? Or should we wait for fixes?

I haven't been able to solve the problem. I suppose it could be a launcher problem, as everyone claims, but my husband (who is much more tech savvy than me) is convinced its a mod issue. I haven't even tried playing the game since I posted this, but I was gonna try today. I can let you know if anything has changed.

Originally posted by YaminaKakarot:

Originally posted by 𝐝𝐮𝐝𝐞:

After the update with dragons came out, I decided to try the AGOT+ submod on the regular AGOT. Before that, AGOT worked as it should. After I installed AGOT+, after about 10 minutes of the session, the game started to crash. At first, I thought it was because of AGOT+ and deleted it. The game still crashed. Now it doesn't even load into the game, and at the moment of loading, the game just crashes. Vanilla works, but AGOT, even without submods, stopped working completely. Did you solved this problem? Or should we wait for fixes?

I haven't been able to solve the problem. I suppose it could be a launcher problem, as everyone claims, but my husband (who is much more tech savvy than me) is convinced its a mod issue. I haven't even tried playing the game since I posted this, but I was gonna try today. I can let you know if anything has changed.

Okay, I just tried to play base AGOT, and its the same problem. Despite my launcher having to update again. So I'm gonna wait a few more days and try again.

Originally posted by YaminaKakarot:

Originally posted by YaminaKakarot:

I haven't been able to solve the problem. I suppose it could be a launcher problem, as everyone claims, but my husband (who is much more tech savvy than me) is convinced its a mod issue. I haven't even tried playing the game since I posted this, but I was gonna try today. I can let you know if anything has changed.

Okay, I just tried to play base AGOT, and its the same problem. Despite my launcher having to update again. So I'm gonna wait a few more days and try again.

My launcher updated, tried to play today, agot without any submods crashed after 3 in-game years, with agot+ even less (about 5 minutes and crashes). Well, I will try to do something, if I can fix it, I will definitely write.

Originally posted by 𝐝𝐮𝐝𝐞:

Originally posted by YaminaKakarot:

Okay, I just tried to play base AGOT, and its the same problem. Despite my launcher having to update again. So I'm gonna wait a few more days and try again.

My launcher updated, tried to play today, agot without any submods crashed after 3 in-game years, with agot+ even less (about 5 minutes and crashes). Well, I will try to do something, if I can fix it, I will definitely write.

Thanks. When I play tested AGOT alone, I didn't even make it 5 minutes. As soon as I clicked on my character's profile, it crashed. But please do keep me updated.

Originally posted by YaminaKakarot:

Originally posted by 𝐝𝐮𝐝𝐞:

My launcher updated, tried to play today, agot without any submods crashed after 3 in-game years, with agot+ even less (about 5 minutes and crashes). Well, I will try to do something, if I can fix it, I will definitely write.

Thanks. When I play tested AGOT alone, I didn't even make it 5 minutes. As soon as I clicked on my character's profile, it crashed. But please do keep me updated.

So, after reinstalling DirectX, Visual C and other drivers, the game seems to work. I checked at the logs and crashreports, another problem was the lack of RAM (I only have 8 GB). And after all the problems fixed above, mod works fine, but AGOT+ still crashes after a year of playing. I also asked people, they say that AGOT+ is a very unstable submod, so it doesn’t work for many people either, this is a problem with AGOT+ itself. If this manipulations does not help, try deleting the old playset with mods in the Paradox launcher, creating a new one and loading new mods into it. Here's what the developers write: "Sometimes it's necessary to create a new playset and add the mods that you know will work from there. The launcher will typically cache the submods you're using in a playset(to help with loading speed primarily) and this can produce some weird issues sometimes when trying to disable mods. It's also important to note that any time you make major changes to a playset or reinstall mods it's usually best practice to make a new playset to avoid any potential issues. Sometimes you will need to take a slower approach to making a new playset. After making the new playset, depending on how many submods you’re aiming for, you can add a few of them at a time and test for stability. If it works fine, you can then add one or two more(being mindful of load order) and test for stability again. If it still works, you can continue this process until you find the mod(s) that are causing issues. This is also a good method for testing the best load order. The fewer mods you have at a time the easier it is to test and find incompatibilities."

Originally posted by 𝐝𝐮𝐝𝐞:

Originally posted by YaminaKakarot:

Thanks. When I play tested AGOT alone, I didn't even make it 5 minutes. As soon as I clicked on my character's profile, it crashed. But please do keep me updated.

So, after reinstalling DirectX, Visual C and other drivers, the game seems to work. I checked at the logs and crashreports, another problem was the lack of RAM (I only have 8 GB). And after all the problems fixed above, mod works fine, but AGOT+ still crashes after a year of playing. I also asked people, they say that AGOT+ is a very unstable submod, so it doesn’t work for many people either, this is a problem with AGOT+ itself. If this manipulations does not help, try deleting the old playset with mods in the Paradox launcher, creating a new one and loading new mods into it. Here's what the developers write: "Sometimes it's necessary to create a new playset and add the mods that you know will work from there. The launcher will typically cache the submods you're using in a playset(to help with loading speed primarily) and this can produce some weird issues sometimes when trying to disable mods. It's also important to note that any time you make major changes to a playset or reinstall mods it's usually best practice to make a new playset to avoid any potential issues. Sometimes you will need to take a slower approach to making a new playset. After making the new playset, depending on how many submods you’re aiming for, you can add a few of them at a time and test for stability. If it works fine, you can then add one or two more(being mindful of load order) and test for stability again. If it still works, you can continue this process until you find the mod(s) that are causing issues. This is also a good method for testing the best load order. The fewer mods you have at a time the easier it is to test and find incompatibilities."

That is a little helpful. But I did make a new playset with only AGOT in it, and I'm still getting crashes within the first 5 to 10 minutes. Usually when I click on a character profile, but ALWAYS when I click on a dragon profile. I have 16GB RAM, so that shouldn't be the problem at all. Idk what else to do.

Originally posted by YaminaKakarot:

Originally posted by 𝐝𝐮𝐝𝐞:

So, after reinstalling DirectX, Visual C and other drivers, the game seems to work. I checked at the logs and crashreports, another problem was the lack of RAM (I only have 8 GB). And after all the problems fixed above, mod works fine, but AGOT+ still crashes after a year of playing. I also asked people, they say that AGOT+ is a very unstable submod, so it doesn’t work for many people either, this is a problem with AGOT+ itself. If this manipulations does not help, try deleting the old playset with mods in the Paradox launcher, creating a new one and loading new mods into it. Here's what the developers write: "Sometimes it's necessary to create a new playset and add the mods that you know will work from there. The launcher will typically cache the submods you're using in a playset(to help with loading speed primarily) and this can produce some weird issues sometimes when trying to disable mods. It's also important to note that any time you make major changes to a playset or reinstall mods it's usually best practice to make a new playset to avoid any potential issues. Sometimes you will need to take a slower approach to making a new playset. After making the new playset, depending on how many submods you’re aiming for, you can add a few of them at a time and test for stability. If it works fine, you can then add one or two more(being mindful of load order) and test for stability again. If it still works, you can continue this process until you find the mod(s) that are causing issues. This is also a good method for testing the best load order. The fewer mods you have at a time the easier it is to test and find incompatibilities."

That is a little helpful. But I did make a new playset with only AGOT in it, and I'm still getting crashes within the first 5 to 10 minutes. Usually when I click on a character profile, but ALWAYS when I click on a dragon profile. I have 16GB RAM, so that shouldn't be the problem at all. Idk what else to do.

Besides that, I also had a crash when I zoomed in on the map or clicked on the war/event window. In general, my order of actions:
1. Before that, I reinstalled Windows
2. Downloaded the latest current versions of Microsoft .NET Framework, DirectX 11/12, Microsoft Visual C++ 2015-2022
3. Redownloaded the game, mods, created a new playset and entered the game.
And yet I strongly recommend checking for current driver versions. If this does not help, you will need to look at what the crash log says, it is located in the Paradox Launcher folder in the Documents.