Game crashes the entire computer with a black screen, not sure what causes it.

[Allyedge]

Hi, the title is pretty much the entire issue. This has been happening since I upgraded to a 5700X3D CPU and I could not quite identify why.

I will attach two crash folders from yesterday where this happened in case it helps in any way.

I also have 4x8 GB RAM sticks running at 3600Mhz, I thought it could perhaps be about that and tried with lower frequencies, yet with no effect.

Thanks!

 

[AndrewT]

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

 

[Allyedge]

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

Hi, there is no "exceptions.txt" file but I attached all others that you mentioned. Why would I cap the refresh rate at 60, if I have a 144hz monitor and want to play 144hz?

 

[AndrewT]

Why would I cap the refresh rate at 60, if I have a 144hz monitor and want to play 144hz?

It's just a diagnostic step. We can undo it if it does not 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.

 

[Allyedge]

It's just a diagnostic step. We can undo it if it does not 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.

I see, so far I don't think it affected anything, same issues persist.

I noticed I forgot to attach the DxDiag file, here it is.

 

[AndrewT]

I'm afraid this is almost certainly the current issue with Win11 24H2

https://forum.paradoxplaza.com/forum/threads/continuously-crashing-under-windows-11-24h2-with-exit-code-3221225620.1712339/

https://forum.paradoxplaza.com/forum/threads/bluescreens-and-freezes-after-installing-win11-24h2.1725554/

https://forum.paradoxplaza.com/forum/threads/game-crashing-after-windows-11-24h2-update.1718749/

Hopefully you can revert to 23H2! If not though, we don't really have a fix or workaround for you; just keep up to date with your Windows patches so whe MS do fix it, you'll be okay again.

Sorry for that!