Game Crashes entire PC on unpause

[Radrez]

Integrity​

I have verified my game files (on Steam)​

Yes

I have disabled all mods​

Yes

Required​

Summary​

Game Crashes entire PC on unpause

Description​

Game crashes my entire PC when unpausing. It can happen at any point during gameplay but most often happens on the initial unpause, especially if I make a bunch of moves (apply edicts, construction queue etc.) before unpausing. I can mitigate it slightly by unpausing for a week before making first moves but it will eventually crash regardless, its just a matter of when. PC freezes entirely and only way to fix it is to hard reboot. Once I managed to pause again fast enough that it actually recovered after some time but then it crashed again after unpausing. I don't understand what is happening.

My PC:
RTX 4090
AMD Ryzen 7800X3D
32GB RAM 6000Mhz
Installed on nvme ssd

Steps to reproduce​

Most common way to reproduce is to make as many moves as you can once started the game, apply your policies, adjust taxes, set a new law, change institutions, apply edicts and add to construction queue and then unpause, almost always crashes. Otherwise its just a crash on upause at any point during gameplay.

Game Version​

1.9.5

OS​

Windows

Additional​

Bug Type​

Other

Save Game​

Attachments​

Player Pain​

10

 

[PDX_Sosanna]

Moving to Tech Support!

 

[Radrez]

So I've tried your workaround. It didn't work but because I had a couple of CPU's spared, instead of entire system crashing only the game hangs up and crashes. Please help I can't play the game at the moment.

 

[AndrewT]

Which exact workaround do you mean, please?

AMD Ryzen 7800X3D

Please check with AMD for updated chipset drivers for this CPU, thanks.

 

[Radrez]

Which exact workaround do you mean, please?


Please check with AMD for updated chipset drivers for this CPU, thanks.

I have disabled a couple of CPU cores in the task manager after starting the game and also tried running vulkan API instead of DirectX. The only difference that made is what I outlined above, managed to reduce it from entire PC crashing to only game crashing which does make sense since I am literally reserving two cpu cores to not be touched by the game.

I am on latest bios and latest drivers.

 

[AndrewT]

I am on latest bios and latest drivers.

Specifically the AMD CPU chipset driver (not just the video driver)? Because a general driver update does not usually touch those.


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.

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
From your Documents/Paradox Interactive/Victoria3/crashes/ folder, attach here the latest (only!) exceptions.txt

 

[Radrez]

Yes its on the latest chipset driver specifically. Crashes folder is empty for me.

 

[AndrewT]

Your BIOS: 2613 appears to be over a year old - can you please check with ASUS again?

But I'm pretty sure this is the common Windows 11 24H2 issue.

A user has come up with a possible workaround
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 Lasso, just Affinity in Task Manager (for testing purposes anyway).

Good luck!

 

[Radrez]

I have tried everything and I've had enough this is insanity. I tried the updates, registry key fix, cpu affinities and vulcan api. I don't have this issue with any other game so maybe just MAYBE its time to for you to try, identify and address the issue yourselves. I saw many other people having the same problem and its crazy how easy it is for you to dismiss these and just blame it on a windows update.

 

[AndrewT]

Actually it is known and provable that Windows 11 24H2 triggers this exact problem - affected users who have been able to revert to Windows 10 or 11 23H2 report the problem is instantly fixed. It does NOT only happen on this game.

I'm not 100% clear from what you say - you have updated the bios now, is that right? If so can I get a new dxdiag.txt please, plus install and run the free utility Speccy. Send its output to a text file and attach that here please.
https://www.ccleaner.com/speccy/download