• 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.
Launcher logs will not help us diagnose a game crash, I'm afraid. Once the game runs the launcher is unloaded.

In Windows Vulkan support in this game is only intended as a diagnostic measure, so we should try and diagnose your problem. That said, if it is really DX11 at fault that can only really be a Windows or video driver issue!
I don't get crashes in other games though. Before all these launcher shenanigans happened, I got random crashes in this game for almost half a year...
 
Now it also crashed in Vulkan... :D This game is just completely broken for me.
It may or may not be the game per se.

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
 
It crashed again. I could not find an exceptions.log file, but here are the others you requested. The system log is empty and cannot be uploaded as well. Thanks again.
 

Attachments

  • DxDiag.txt
    109,4 KB · Views: 0
  • pdx_settings.txt
    5,6 KB · Views: 0
  • error.log
    3,6 MB · Views: 0
"setting_framerate_cap"={
version=0
value="off"
}
Did you set that cap to 60? What fps are you seeing in the game before it crashes?
 
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.


THEN 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

Thank you SO MUCH!

I just ran into this issue last night and followed your walkthru for fixes. Game finally launches!
 
I had the same problem, but when launching Imperator: Rome. I made it working when I went into properties of imperator.exe and disabled, launching it as administrator. Likewise, I think it would work the same with ck3.exe, Hope it helps!
This fixed mine, thank you! Great tip. Not sure how that button EVER got clicked.
 
In my case, the following helped:

According to the log files, the game always wanted to access the file “c:\Windows\USB Vibration\7906\EZFRD64.dll”.
After I deleted this file, the game started again without any problems.

I have no idea what the file is for, but at the moment no other program has reported needing this file.
 
In my case, the following helped:

According to the log files, the game always wanted to access the file “c:\Windows\USB Vibration\7906\EZFRD64.dll”.
After I deleted this file, the game started again without any problems.

I have no idea what the file is for, but at the moment no other program has reported needing this file.
We've seen that issue with our games going back some years! It is a driver for some sort of joystick, and often has a really old driver like 2008 or something. Just unplugging the device should get past it, but check with the device vendor for an updated one.

That issue is unrelated to the others discussed in this thread.