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

TheNerdToo

Recruit
10 Badges
Aug 25, 2023
4
2
  • Cities: Skylines
  • Stellaris
  • Hearts of Iron IV: Cadet
  • Hearts of Iron IV: Together for Victory
  • Hearts of Iron IV: Death or Dishonor
  • Hearts of Iron IV: Expansion Pass
  • Imperator: Rome Deluxe Edition
  • Imperator: Rome
  • Crusader Kings III
  • Crusader Kings III: Royal Edition

Integrity​

I have verified my game files (on Steam)​

Yes

I have disabled all mods​

Yes

Required​

Summary​

Game Crashes to Desktop When Selecting Sandbox

Description​

Hi, ever since 1.5.8 I have been unable to play Victoria 3. When I choose Sandbox for a new game I get the loading screen and the game will crash before it loads to be played. I have tried to roll back to 1.5.7, but found that I can't play that version either any more. I have an i9-13900K so I've been using processor affinity to prevent the e cores from being used for Victoria 3. I found with previous versions the game would constantly crash unless I did this. I have tried without setting processor affinity, but haven't had any better luck. I tried contacting the support.paradoxplaza.com people, but they basically told me to uninstall and reinstall the game and telling me to use System File Checker which found no errors.

Steps to reproduce​

Start Game -> Click New Game -> Click Sandbox

Game Version​

1.5.9

OS​

Windows

Additional​

Bug Type​

Crash to Desktop

Save Game​



Attachments​

View attachment debug.logView attachment error.logView attachment game.logView attachment system.log

Player Pain​

10

 
Upvote 0
Hi! Thanks for attaching the files. We've confirmed that we already have it in our database and it's quite uncommon.

Our programmers are currently investigating it and there's a chance that the issue is on the side of Intel in which case it will be patched alongside a system update. If it turns out to be on our side, the fix will likely be deployed in a future major patch.

Apologies for the inconvenience!