• 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.
Right click on victoria3.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/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/logs/ folder, attach here system.log , error.log
From your Documents/Paradox Interactive/Victoria3/crashes/ folder, attach here the latest (only!) exceptions.txt
 
Right click on victoria3.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/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/logs/ folder, attach here system.log , error.log
From your Documents/Paradox Interactive/Victoria3/crashes/ folder, attach here the latest (only!) exceptions.txt
 

Attachments

  • pdx_settings.json
    1,9 KB · Views: 0
  • Error.zip
    4,4 KB · Views: 0
  • System.zip
    4 KB · Views: 0
  • exception.txt
    2,7 KB · Views: 0
Crashes on save are usually an antivirus app getting in the way, or running out of available memory. But with this:
[07:39:22][systemsettings.cpp:209]: RAM Total: 32605
[07:39:22][systemsettings.cpp:210]: RAM Free: 20026
[07:39:22][systemsettings.cpp:211]: Swap Total: 32757
[07:39:22][systemsettings.cpp:212]: Swap Free: 15058
that should not be the case here! As long as there is enough free space on C: to swap stuff out to disk, we could see that in the dxdiag if you attach that here please.

And make sure victoria3.exe is in all the exceptions lists in your antivirus app.
 
I did an exception in the windows defender anti virus and protection, and added inbound outbound rules in the firewall, which did not seem to work. Also when the game is about to crash the screen flickers for a bit before crashing.
 
I did an exception in the windows defender anti virus and protection, and added inbound outbound rules in the firewall, which did not seem to work.
This issue is nothing to do with firewalls, they only govern external communications not local disk activity.


If you use the default Windows Defender antivirus, its Ransomware protection will be active. Make sure victoria3.exe is in its Controlled Folder Access-Apps ALlowed Through list, AND that it is not doing realtime scans of the Documents/Paradox Interactive/Victoria3/ folders.


And I see you have the problematic Windows 11 24H2 version. While not known to cause this exact symptom, let's try this simple change just in case:
https://forum.paradoxplaza.com/foru...s-the-problem-with-computer-freezing.1774335/
Definitely worth a shot - let me know if that does help you! Note that to test it you don't actually need to use Processor Lasso, just Affinity in Task Manager (for testing purposes anyway).

Good luck!
 
The affinity change did make the crashes less frequent.

Definitely feel like this is a 24h2 version problem, because while it doesn't completely freeze like it does on dx11, it gives a similar freeze on some auto saves for a few seconds and goes back to normal, or just ctd.
 
  • 1Like
Reactions: