• 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.

Xenotech5

Recruit
2 Badges
Mar 17, 2025
5
1
  • Magicka
  • Crusader Kings III
Complete uninstall (deleted all documents as well), then reinstalled and verified file integrity. Still cannot get past initial loading screen to main menu before crashing to desktop. Issue hasnt occurred until I upgraded my GPU from 2080 Super to 5070Ti.
 

Attachments

  • exception.txt
    1,4 KB · Views: 0
  • meta.yml
    939 bytes · Views: 0
  • minidump.dmp
    49,1 MB · Views: 0
  • pdx_settings.txt
    322 bytes · Views: 0
  • user_crash_report.txt
    256 bytes · Views: 0
  • debug.log
    56 KB · Views: 0
The most common cause of this game failing to start since the recent 1.14.3 patch is Avast, Norton's, Sophos or AVG 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.



If that's not the case here, or doesn't help, 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.
 
Ive made an exclusion in my AV and it still seems to be not even making it past the initial load screen. Ive done as you ask and also ticked the disable fullscreen optimizations and left everything else blank. Fullscreen, no vsync, capped at 60. Still crashing after all that. Ive attached the DxDiag.txt as you requested.
 

Attachments

  • dxDiag.rar
    16,7 KB · Views: 0
Which AV do you have please? In some cases we've had to ask affected users to get help from their support to ensure ck3.exe is not blocked, and is allowed to write everywhere it wants to.

We do see one crash in the Nvidia software there, so let's try a clean re-install - I see yet another new one came out today:

- uninstall it with this tool https://developer.nvidia.com/cleanup-tool
- reboot
- install that new one https://www.nvidia.com/Download/index.aspx?lang=en-us
- reboot again
- if GeForce Experience or the Nvidia app are running after that, exit them before starting the game

Does that help?
 
Norton's is one of the ones known to cause this problem. If you believe you've added ck3.exe to its exception lists you might need help for their support on that.

You can test if that is the problem by reverting the game to a version from BEFORE 1.14.3 in the Steam betas tab for the game - does it start then?
 
Ah, so a game version from before 1.14.3 that used to work, now does not? Is that right? If so there's clearly some new local problem here!
But still add that older ck3.exe to the Norton's exceptions lists.

However I suppose our suspicions must now fall on your switch of GPUs, although that of course is routine and shouldn't be an issue in general. Igf you switch the games renderer from DirectX to Vulkan does that help at all? That is done in the launcher-game settings menu.
 
So I finally managed to get it to Launch. What I did is that I just installed it onto a different SSD drive. It now launches to main menu. My old SSD was an NVMe drive and the one I switched over to was an SATA drive. Any clue why doing this was the solution? Bad NVMe Drivers? No clue.
 
  • 1Like
Reactions: