• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

takanomi

Recruit
Feb 27, 2025
3
1
I have this message that comes when I launch the game.
It's been a few month since I play and never had any problem, it happened suddenly today.

Do you know how can I fix it ?

When I launch the game, when it begins to load, it crashes and gives me the message :

An error has occured and the application quit unexpectedly. A crash report has been
generated which could help us to fix the issue in a future release.
 
Of course that very general message does not tell us what caused the crash.

Any mods involved?

If not, 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.
IF dxdiag.txt fails to attach here, rename it to dxdiag.log , or zip it up.

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.txt
 
I don't use any mod, and I have steam. I tried to launch the exe file directly but the same problem.
I also did the first part of your message but nothing changed.

Here you have the files you asked for.
I have nothing in the exception.log, I have a folder with this name but nothing in it.
The error and system logs are empty. And dxdiag doesn't want to be added here I don't know why

Thanks a lot for your help
 

Attachments

  • pdx_settings.txt
    5,4 KB · Views: 0
IF dxdiag.txt fails to attach here, rename it to dxdiag.log , or zip it up.

The most common cause of this since the recent 1.14.3 patch is Avast or Norton's antivirus (at least!) blocking the updated ck3.exe . Regardless of what AV app you use, make sure ck3.exe is in all its exceptions lists.