CK3 crashes

From that error log, you either have a bad installation or are using mods. If this happens with ALL mods disabled, Please do a full **clean** re-install:

- move any valued save games elsewhere
- "uninstall" in Steam-CK3
- manually delete both the Steam/SteamApps/common/CK3 AND Documents/Paradox Interactive/CK3 folders - In particular make sure there are no files or folders left under either the Steam CK3 or Documents CK3 locations, before installing again.
- re-install game in Steam, run a Steam Verify when done.
- add CK3.exe to the exceptions list of your antivirus app; ESPECIALLY if you have Windows Defender, add it to the Ransomware "Apps Allowed Through" list.

THEN expand your Windows paging file maximum size to 32gb

Optional: Increasing the paging file size on Windows computers

On computers that have 8 GB of RAM, the suggested paging file size is 16 GB. www.ibm.com AND exit every other app you can before starting the game.


THEN re-instate the changed settings as before

Right click on ck3.exe , properties, compatibility. Tick "disable fullScreen optimisations" untick every other box in that dialog, Apply and exit.
Then in the launcher Game Settings menu, select fullScreen display mode, Vsync off, cap refresh rate at 60.

Good luck!  

Krilato said: I could not find the Ransomware "Apps Allowed Through" list.

In the Windows search box type Ransomware. Enable Controlled Folder Access if disabled, then go into the Apps Allowed Through list and add those .exe files.

Couldn't find the "disable full screen optimizations" on the ck3.exe properties either.

Then you have probably right clicked on a folder or some other file - all .exe files have that option under properties-compatibility.

"setting_framerate_cap"={
version=0
value="off"
}

Did you set that cap to 60? If not please try that, thanks.  

If you turn Controlled folder Access off again now, do you still get those access errors?  

Then I guess we didn't except all those .exe files in there somehow. Never mind.

Is the situation now as it was originally here - still crashing randomly if you now start a new unmodded campaign?  

Please report the temperatures of your CPU and video (GPU)
1/ before starting the game up and
2/ after say 30 minutes' play, OR just before it crashes if it does not last that long.
If your PC's vendor has given you no way of reading temperatures, install
SPEEDFAN http://www.almico.com/sfdownload.php

And what fps are you seeing in the game now, anything over 60?  

75c is up there, but not quite at the point that problems normally start, 80c. It never ever gets up there?

And it is unusual to see CPU hotter than the GPU in our games. What are the idle temps?  

Starbird said: The game is unplayable for me now. Crashes at shorter and shorter intervals. I play on a mac. I have uninstalled using Steam. Deleted the CK3 folder and all its contents in Documents. I then re-booted before doing a fresh install. I completed a fresh install from Steam. I have all of the DLC, all enabled, and no mods. Log files from the "crashes" folder are attached.

All help much appreciated!

That will be an unrelated problem, since recent patches this game has been crashing on MacOS, unfortunately! I believe there are reports on that in Bug Reports here, please add your details to them.

aware of this but haven't been able to replicate it so they are thinking it could be down to the render options as Apple sometimes changes this around when they update their OS >
Meantime: Can you boot up the game and check the Settings menu. There should be a render option and I'd like you to change that to OpenGL instead and see if that makes a difference.  

Starbird said: Except now the game can't seem to find and re-load the Ironman game I was playing right before it crashed. Ugh.

That can't be related to the render option change. Is the save file physically still in the local or Steam Cloud locations?  

Krilato said: Is there anything more that you can think of that I can do to solve it or do I just adjust the graphics quality to low for the moment, since it is working, and we close this discussion (since people is commenting on it with questions that are not relevant to this case).

Thank you.

You'll need to wait for the devs to patch it, I'm sorry. I am actively pursuing this issue within Paradox.