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

quartzsite

Recruit
20 Badges
Jun 26, 2025
6
2
  • Hearts of Iron IV: Expansion Pass
  • Hearts of Iron 4: Arms Against Tyranny
  • Hearts of Iron IV: No Step Back
  • Hearts of Iron IV: By Blood Alone
  • Battle for Bosporus
  • Hearts of Iron IV: La Resistance
  • Cities: Skylines - Campus
  • Hearts of Iron IV: Expansion Pass
  • Cities: Skylines Industries
  • Cities: Skylines - Parklife
  • Crusader Kings II
  • Cities: Skylines - Green Cities
  • Hearts of Iron IV: Death or Dishonor
  • Cities: Skylines - Mass Transit
  • Hearts of Iron IV: Cadet
  • Cities: Skylines - Snowfall
  • Cities: Skylines - After Dark
  • Magicka 2
  • Cities: Skylines
  • Magicka
A new issue has occurred: the game crashes without generating a crash log once a certain amount of gameplay progress has been made.


Before reinstalling the game, I manually deleted the Victoria 3 folder located in the Documents directory. After that, I performed a clean installation and launched the game without any mods.


I followed the recommended settings (60 FPS cap, V-Sync disabled, full-screen mode), and started a new game without using any save files.


However, while running the game in Observer Mode, the game crashes somewhere between the years 1840 and 1850, without any crash report being generated. (This differs from previous cases, where the crash occurred shortly after starting the game.)
 

Attachments

  • pdx_settings.json
    967 bytes · Views: 0
  • autosave.v3
    17,3 MB · Views: 0
  • error.log
    3,8 KB · Views: 0
  • system.log
    1,1 KB · Views: 0
This is the DXDIAG file. Additionally, it appears that crashes occur when the game speed is set to 5. In test scenarios (observer mode, up to the year 1850), no crashes occurred when using speed 4.
 

Attachments

  • DxDiag.txt
    132,4 KB · Views: 0
Last edited:
Processor: 13th Gen Intel(R) Core(TM) i9-13900KF
You may have the CPU/bios hardware issue discussed here:
https://forum.paradoxplaza.com/foru...ration-intel-processors.1591821/post-29305331
Your bios seems to be years old; please check with Gigabyte for an updated bios. Then please implement the “Intel Default” option in it, if present.


THEN I see you have Windows 11 24H2; this can be the cause of this problem, it is a severely broken Windows update that has caused problems across the whole gaming - indeed computer - industry.

A user has come up with another possible workaround
https://forum.paradoxplaza.com/forum/threads/24h2-w11-update-issue-found-no-more-crashes.1728373/
Some affected users have definitely seen that help them with this issue. I'd suggest you look at this step first!

And here is another workaround someone posted:
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 Lasoo, just Affinity in Task Manager (for testing purposes anyway).

And finally, in the game settings menu switch the renderer to Vulkan.

Let us know if any of those help!
 
It seems that the issue has been resolved. I have tested both in a vanilla environment and in one with multiple mods installed, and in both cases the game successfully ran in observer mode up to the 1950s at 5x speed without crashing.


I attempted four different fixes, and although I’m not sure which one was ultimately effective, here’s what I did:


1. Updated the motherboard BIOS
2. Set undervolting option to "Auto" and enabled undervolting protection
3. Checked for Windows updates
4. Changed CPU E-core setting from "Random" → "Manual (assigned to core 3)" → back to "Random"

Surprisingly, crashes still occurred after updating the BIOS and adjusting undervolting settings. However, after manually setting the E-core to a specific core and then switching it back to automatic, the issue disappeared.


I suspect that manually configuring the E-core may have reset something internally. While I'm not sure which of these steps solved the problem, the game is now running stably even under the previous crash conditions.


Thank you very much for your support.
 
  • 1Like
Reactions: