5 months ago - AndrewT - Direct link

Game Version​

1.9.2.1
Can I ask why you are not on the current game version, which is 1.11.2? Because if this is a bug in 1.9.2.1 it has probably already been fixed in a later version.  
5 months ago - AndrewT - Direct link
Any mods in use?

Is this crash repeatable from a particular save or saves? Or more random?  
5 months ago - AndrewT - Direct link
Well, the error log often has cosmetic errors in it, they may or may not actually be the trigger for your crash.

I ran your 'last_save.ck3 hands-off for 5 game years with no crashes, despite there being many errors like this in my log
[13:27:30][jomini_script_system.cpp:276]: Script system error!
Error: Event target link 'compare_value' returned an unset scope
Script location: file: events/dlc/bp2/bp2_yearly_1_events.txt line: 6535
So the cause is elsewhere, it seems.

"setting_framerate_cap"={
version=0
value="off"
}
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.


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 , exceptions.log  
5 months ago - AndrewT - Direct link
JayJJoker said: Hey so i didnt find 'cap refresh rate' so I assume you are talking about cap FPS?
When in the launcher Game Settings menu you disable Vsync, you get a Refresh Rate option (which does indeed set a line in the pdx_settings.txt file called setting_framerate_cap). Please set that to 60.

Assuming that doesn't help, you probably have the bios/CPU issue described here:
forum.paradoxplaza.com

Victoria 3 | 12th/13th Generation Intel Processors

Hello all! An update, 12th and 13th Generation Intel Processors are related to a Crash to Desktop (CTD) happening frequently, this is related to architecture changes by Intel and specifically E-cores. We are working with Intel to address these... forum.paradoxplaza.com forum.paradoxplaza.com
Please try that out!