• 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:
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/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/logs/ folder, attach here system.log , error.log , exceptions.log
 
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:
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/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/logs/ folder, attach here system.log , error.log , exceptions.log
It didn't help.

I send the entire logs folder because there are a lot of files like "error.1.log, error.2.log, etc" and I do not really sure which one is needed.
 

Attachments

  • DxDiag.txt
    104,6 KB · Views: 0
  • logs.zip
    571,5 KB · Views: 0
  • pdx_settings.json
    1,7 KB · Views: 0
I don't see the refresh rate cap set there, did you do that? What fps are you seeing? We're trying to restrict it to 60.
 
Is the game now at 60 fps or lower? If so, has that helped the problem at all?
 
That is unexpected - crashes after a certain period of play are usually overheating, which ought not to happen at 60hz.

Please report the temperatures of your CPU and video (GPU)
1/ before starting the game up and
2/ after say 10 minutes' play.
If your PC's vendor has given you no way of reading temperatures, install
SPEEDFAN http://www.almico.com/sfdownload.php
 
That is unexpected - crashes after a certain period of play are usually overheating, which ought not to happen at 60hz.

Please report the temperatures of your CPU and video (GPU)
1/ before starting the game up and
2/ after say 10 minutes' play.
If your PC's vendor has given you no way of reading temperatures, install
SPEEDFAN http://www.almico.com/sfdownload.php
It's definitely not a temperature issue because the game doesn't crash during AFK for several hours, but crashes happen every~20-40 minutes when I start playing.
Also, my maximum GPU temperature is 66℃ (36℃ in regular system use) and the CPU temperature is 60℃ (42℃ in regular system use).
 
I'm pretty much out of ideas why this is happening on this machine then. That dxdiag does show a very heavy use of the paging file, even though I assume this game is not running at that time. Try making it 64gb
 
Overheating OR not enough voltage, try changing svb in bios to give cpu more wiggle room on voltage, worked for me on similar problem
How do I do this?
I lowered the max FPS in Vic 3 to 30 (from 60) and I'm still crashing within a minute of starting a game. I'm running Windows 11 on bootcamp.