• 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.
Steam or MS store edition please?

If MS store, please try this trick:

If Steam, DXDIAG is a program you run from a command prompt or the Windows start menu 'run' dialog box (or 'search programs' in Windows 7 or later). 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 your Documents/Paradox/CK3/pdx_settings.txt .
From your Documents/Paradox/CK3/logs/ folder, attach system.log , error.log
 
I'm using steam version.

The files you asked are here, except error.log is totally empty so the forum doesn't allow me to attach it here.
 

Attachments

  • system.log
    627 bytes · Views: 0
  • DxDiag.txt
    136,9 KB · Views: 0
I think this is not one of our more common issues ... two quite separate unrelated crashes in ck3.exe in that dxdiag. Also seeing some other crashes in explorer.exe and problems in the Windows store .. would you say you are seeing more general issues on this machine?

I take it HOI4 and I:R, say, are working okay for you?


Just to be sure here's the clean reinstall procedure:

- move any valued save games elsewhere
- "uninstall" in Steam-CK3
- manually delete both the Steam/SteamApps/common/CK3 AND Documents/Paradox/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.
 
Other games working fine. Actually even CK3 worked last time I launched it. I also tried this reinstall procedure but it doesn't help. It seems it just took longer to crash because it needed to load cache after a reinstallation. Then it began crashing like it used to do.

Might be worth noticing might be not, but the first time when it crashing I couldn't even send out crashing report because the reporting program also glitched. After reinstallation, I can send out crashing report now (not that it'd be helpful).
 
Hmmm. Can we see a new dxdiag and error.log please?