Games crashes after ~30min [Win11]

[Mephidross]

Short summary of your issue
The game keeps consistently CTD after a period of perhaps 30-60mins of play. The screen freezes for a few seconds, and then CTD.
Been taking place for a longer time, but I thought it was my overclocked PC setup, tried resetting the overclock but still the CTD happens.

Game Version
1.7.6 (Kahwah) (Been taking place prior)

What OS are you playing on?
Windows 11

Do you have mods enabled?
No

Have you tried verifying your game files?
Yes

How much "pain" is this causing you?
9

Please explain the issue you experienced in the most condensed way possible
The screen freezes for a few seconds, and then CTD.

Please explain how to reproduce the issue
Just playing the game, game speed does not seem to impact it significantly.

Please find attached to separate occasions of the CTD, one with the OC Bios settings, and one with the reset settings.
Disabling V-Sync, Capping refresh rates did not seem to have an impact.

 

[AndrewT]

From that error log, this is an issue in the video/graphics area, DirectX11 in particular.


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. Thanks.

Please attach here your Documents/Paradox Interactive/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/crashes/ folder, attach here the latest (only!) exceptions.txt

 

[Mephidross]

From that error log, this is an issue in the video/graphics area, DirectX11 in particular.


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. Thanks.

Please attach here your Documents/Paradox Interactive/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/crashes/ folder, attach here the latest (only!) exceptions.txt

Thank you for getting back so soon!

Files attached,

 

[AndrewT]

Disabling V-Sync, Capping refresh rates did not seem to have an impact.

The game is in windowed mode which means Vsync is not used - it will always run at the desktop hz which is 144 here.

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, new copies of all those files please!

 

[Mephidross]

The game is in windowed mode which means Vsync is not used - it will always run at the desktop hz which is 144 here.

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, new copies of all those files please!

Hi,

Tried it as suggested, and got some ~40mins gameplay before it unfortunately happened again.

Fresh files attached,

Thank you for looking into this!

 

[AndrewT]

Now we see both LiveKernelEvent and BlueScreen entries in that dxdiag - not a good sign! The former happen when a computer is forcibly downed or rebooted; the latter always mean a Windows, driver or hardware fault.

Have you seen those happen, in particular the BlueScreen events? Were they associated with this game or something else?

Please check them in your WIndows Event Viewer; hopefully the BlueScreen events have some extra text that points to the general area of the problem at least.


AND Please report the temperatures of your CPU and video (GPU)
1/ before starting the game up and
2/ after say 20-30 minutes' play.
If your PC's vendor has given you no way of reading temperatures, install
SPEEDFAN http://www.almico.com/sfdownload.php

 

[Mephidross]

Sorry for the delay, worklife getting in the way.

So after the setting adjustments I had a one CTD while in the loading screen into the game (prior to Main Menu).
Then I indeed had an event when the entire PC froze and rebooted, it did happen during the game, but I omitted it because I was adjusting my CPU's voltages at the time and suspect it is related to that rather than this issue. (Other games, including some heavy duty games, work just fine.)

Just had a 32min game prior to CTD,

CPU Temps were between 35° - 77°, averaging at 55,5° while playing.

GPU temps between 39,7° - 64,8°, averaging at 60,04° while playing.

The setting/FPS change had some impact, because during the weekend I was able to get a few 2 - 2,5 hours sessions in.

Best regards,

 

[AndrewT]

CPU Temps were between 35° - 77°, averaging at 55,5° while playing.

GPU temps between 39,7° - 64,8°, averaging at 60,04° while playing.

Those GPU temps are okay but that CPU is getting close to 80c, where IME is where such problems start. Indeed it is unusual to see the CPU hotter than the GPU. I'd speculate this crash happens when the CPU hits 80s or so.

With Speedfan or other utilities you can force the fans to 100% constantly - see if that helps. If it does, you probably have a faulty fan or a heatsink/thermal paste problem. You may need professional help at that point.

If not though, I'm truly not sure what is doing this to you! Were you able to find the Bluescreens in the Windows Event viewer?