Game crash during "Initializing Game" (Same goes for CK3)

[iamthevendetta]

Short summary of your issue
Victoria 3 won't get pass loading screen, specifically during "Initializing Game"

Game Version
1.4.2

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?
100%

Please explain the issue you experienced in the most condensed way possible:
I tried clean install the game by deleting all local and cloud save files, deleting launcher V2 from AppData\Roaming, deleting Victoria 3 folder from Documents\Paradox Interactive, enabling AVX (as per one of the threads here mentioned), none of them work wonders.

Please explain how to reproduce the issue:
Launch the game from both launcher and .exe

Is there anything else you think could help us identify/replicate the issue?
No

I have attached a save game:
No

Upload Attachment:
No files. Game CTD without generating any log.

Notes:
I can run EU4, HOI4 and older CK2 without problems. I'm only having problems with both Vic3 and CK3 (same stuffs, can't get pass loading screen).

 

[iamthevendetta]

[Update]
I opted in 1.5 Beta and it still crashed. However this time with crash report as attached.

 

[AndrewT]

From that .json file the game is not even getting started at all. What happens if you run Victoria3.exe and ck3.exe directly from File Explorer? Any error show?

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.

 

[iamthevendetta]

From that .json file the game is not even getting started at all. What happens if you run Victoria3.exe and ck3.exe directly from File Explorer? Any error show?

Same thing, stuck at the "Initializing Game" screen before crashing.

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.

As attached.

 

[AndrewT]

No obvious cause for this in there. A few nVidia issues but I'm not sure they are the problem here.

If you select Vulkan as the renderer instead of DirectX 11 , does that change matters?

What if you make a new Windows user on this machine and log into it with that - any different with either game?

 

[iamthevendetta]

If you select Vulkan as the renderer instead of DirectX 11 , does that change matters?

This setting was only available in CK3 launcher. Nevertheless, it went CTD without error.

What if you make a new Windows user on this machine and log into it with that - any different with either game?

No different, it's still crashing...

 

[AndrewT]

In that new Windows user, go into startup settings and disable everything you can. Reboot and try again.

If still a problem, install and run the free utility Speccy. Send its output to a text file and attach that here please.

Speccy - Free Download

Download Speccy - the System Information tool

www.ccleaner.com

 

[iamthevendetta]

Hey Andrew just a quick update, a good news that is!

I looked into Event viewer and found this Event 2004, in which I went to check the said virtual memory.

Turned out I somehow unchecked this auto setting and set to custom size limiting the memory to just under 3000 MB.

After restarting the PC, I'm now able to launch both games via the launcher as per usual and no more crashing!

Anyway thanks for the heads up, hopefully it'll be of any help to others having this issue as well.

Cheers!

 

[AndrewT]

I looked at that in dxdiag but it said:

Page File: 10426MB used, 8793MB available

How that equates to a hard-set to 3gb I cannot understand! MS, eh ...

Anyway well done. I'm think I should just recommend everyone set it to 32gb at least from now on ... !

 

[SuiciSpai]

This needs to be sticky. Although it seems that my SSD also needed firmware upgrade, this was the FIRST step I needed to do to even have logs.