[2022] Ck3 crashing pc

In the launcher-game settings menu set Display mode to fullScreen, Vsync off, refresh rate 60.


If those don't help:
DXDIAG is a program you run from the Windows search box on the task bar. After running it will open a window and start collecting info with a progress bar in the lower-left corner. When it completes click the 'save all information' button and save it to a file then attach that file here.

Please attach here your Documents/Paradox Interactive/CK3/pdx_settings.txt .
From your Documents/Paradox Interactive/CK3/logs/ folder, attach here system.log , error.log


Please report the temperatures of your CPU and video (GPU)
1/ before starting the game up and
2/ after say 10 minutes' play.
If your PC's vendor has given you no way of reading temperatures, install
SPEEDFAN http://www.almico.com/sfdownload.php  

From that pdx_settings.txt you don't seem to have set the refresh rate cap? Please try that.

That error.log looks pretty ugly! 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
- 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.
- start the game with no mods active and test

In particular make sure there are no files or folders left under either the Steam CK3 or Documents CK3 locations, before installing again.



Please report the temperatures of your CPU and video (GPU)
1/ before starting the game up and
2/ after say 10 minutes' play.
If your PC's vendor has given you no way of reading temperatures, install
SPEEDFAN http://www.almico.com/sfdownload.php  

Since 1.5.1 you can delete that /logs/ folder again. Do you still get these errors in taht log?  

A much better error log! But that made no difference to your crashing problem - it's still the whole PC, is that right?

Note you may need to add the new ck3.exe to your AV app's exceptions lists.

And can I get a new dxdiag.txt please.

blackbataillon said: Temps are in the picture from first reply.

I don't see them in any of your posts here?  

Can you please use a different app to see those temperatures? Speccy is one good one.

I see no crash in ck3.exe in there, nor even a LiveKernelEvent what normally happens after a forced reboot. In the Windows Event Viewer, are there any significant errors just before one of these restarts?  

70c is getting up there, but not to the point of causing problems like this - that'd normally be 80c or more. Was this taken when the game was running?

It is quite unusual for the CPU to be hotter than the GPU though.


There was nothing in the Windows Event Viewer?  

I am sorry then, you have a clear problem in your cooling system there.

Clean out all air vents it has (compressed air cans are good for this). Make sure airflow to them is not blocked by anything like walls, books or whatever.
If that doesn't drop the temps enough, you probably have a faulty fan or a heatsink/thermal paste problem. You may need professional help at that point.

Good luck!  

blackbataillon said: Yeah. just drop the problem because you have no clue. Please get me someone who has some knowledge and can maybe help me. Ty.

See my join date ? I've been doing this since before then, I do know what I'm talking about here.

You are getting temps up to 94c. They should never get over 80c regardless of what a game does. You have a problem with cooling, I promise you. You said the CPU as old; if its thermal paste has never been renewed that is very likely the cause.  

Andrew is right, your temps are the cause. If you don't trust us, trust the manufacturers own specifications:


(https://ark.intel.com/content/www/u...54690k-processor-6m-cache-up-to-3-90-ghz.html)

Your CPU is cooking hence your PC shuts down to prevent irreparable damage. If you don't want to accept this that's fine but this isn't something we can fix for you, the problem is your hardware.