Do you happen to have an ASUS motherboard?Still crashing with my i9 13900 kf +rtx 4070 + 32gb ram
-
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.
Then try this: Go into your BIOS, under AI Tweaker, and change "SVID Behavior" from "auto" to "Intel's fail safe". That is what fixed it for me.
If you want more details, read this thread: https://community.intel.com/t5/Proc...es-Windows-11-with-apps-games-and/m-p/1528667
Last edited:
- 1
can confirm by turning in it to intels fail safe works, its not great fix atleast for me, as it seems like my computer is slowly dying when using it freezes up a second then goes on.
Same here. I’m pretty sure it means the CPU is not good and this just buys it some life. I want to replace it but Intel’s tool will say it’s fine.
I may also be a ASUS BIOS issue. I want to see if I can downgrade it. Regardless now your game shouldn’t crash all the time.
This is the only game that I have ever had issues with so far.
So I assume this is more of a Victoria/CK issue honestly.
So I assume this is more of a Victoria/CK issue honestly.
It most likely is, if the cpu is faulty it will effect multiple games and not just vic or ck, and ck issues only happened after a recent patch.
So I built a new PC with a i9-14000K on a Gigabyte Z790. I've disabled ecore on the BIOS as the main setting, but it still CTD when I go to 5x speed. Is this something that is being looked into??
- 1
That may or may not be related to the issue discussed in this thread - which after all is supposed to be fixed in the 1.5 patches.
I suggest you treat this as a new issue, and make a new thread. here with full system info, as you see me ask for in almost every thread. Thanks!
so settning on proccesor lasso to 0-24 cpu affinity makes the game not crash, so that fix for the e cores is only half correct .
Hello, I have a post on this topic under bug reports. That's why this one helped me a bit. Unfortunately, I have to reject the statement that the problems have been fixed with patch 1.5 as completely false. The problems still existed afterwards. However, the problem has only existed since a patch was released in March/May 23. In the beginning, it was completely playable.
Switching off the e-cores doesn't help at all, the only solution that has worked for me so far is to restrict the core allocation to the performance cores via the task manager after starting the game.
This should also be possible for the devs with a short code that reads out the CPU and uses it to determine the core assignment (like core 0-7 in my case). If this source of error is eliminated, you can safely concentrate more on the other causes of error.
Switching off the e-cores doesn't help at all, the only solution that has worked for me so far is to restrict the core allocation to the performance cores via the task manager after starting the game.
This should also be possible for the devs with a short code that reads out the CPU and uses it to determine the core assignment (like core 0-7 in my case). If this source of error is eliminated, you can safely concentrate more on the other causes of error.
- 2
So. I have done even more digging. I no longer believe the problem is the game, at least it's not just the game. At least for me, on a i9-13900k, the issue is a combination of the AVX commands being called by the game which is pushing these CPUs harder in ways that they have not before, modern motherboards from Asus (and possibly MSI and others) helpfully optimizing the CPU for you by undervolting it (sometimes drastically), and the system being overly optimistic about how well the CPU being able to perform at high clocks with multiple cores at these settings.
I now have a stable setup for Victoria 3 and my i9-13900k which allows me to play for literally hours without a crash while also not being hot as hell. I am as shocked you are.
First, the motherboard: I noticed that my Asus motherboard (Z790-P Wifi) had SVID Behavior set to Auto by default. This setting runs the CPU over 0.2 volts lower than when setting it to Intel fail safe default. It was a diference between 1.64v for the Intel default and 1.38v or so for Auto. This is a pretty strong undervolt! I ended up using Worse Case Scenario settings which put the CPU at 1.47v. I really wanted to make this work as otherwise, left at these dafaults, the CPU would both thermal and power throttle when running something similar like the Intel XTU benchmark, eating 300-305W. With the Worse Case Scenario setting running around 1.47v, my CPU tends to run around 240-250W in the same benchmark.
Second, the CPU settings: I used Intel XTU for this part, as it allowed me to tune to my CPU. What became apparent after multiple stress tests is the CPU cannot handle this undervolted setting while running all the core at full bore. The default settings assumed that it could handle 5.5Ghz on all 8 P Cores and 4.3Ghz on all 16 E Cores at the same time for a period of over a minute. Well, it cannot. Esepcially true when AVX workloads are added the mix. I attached a screenshot of the tweaks I did in XTU for my processor. In short, I created as curve to lower the clock speed as more cores were enabled, and I did this for both the P and E cores. This has allowed me to run longer (5+ minute) stress tests for both regular and AVX workloads and prevent thermal throttle. This is important, as the AVX workload runs the CPU harder, pulling more power and causing more heat... and crashes. I am also using a strong AVX offset of 10. It's probably aggressive but its stable for me and with it and the core changes I can run a 6 minute long AVX stress test with no crashes and no thermal thottling. If you have a better CPU cooler and/or you do not mind some occasional thermal throttling, you could probably more the core ratios up when multiple cores are called.
With these settings I have a CPU which still turbos when I need it to turbo, a CPU that pulls much less wattage and generates much less heat, and most importantly for this forum allowed me to play Victoria 1.5.10 without crashing every 5-10 minutes.
You would need to play around in XTU to see what is stable for your CPU. Unless your CPU has absolutely won the silicon lottery, I am betting it is almost impossible to overclock these CPUs and also have stable game.
I now have a stable setup for Victoria 3 and my i9-13900k which allows me to play for literally hours without a crash while also not being hot as hell. I am as shocked you are.
First, the motherboard: I noticed that my Asus motherboard (Z790-P Wifi) had SVID Behavior set to Auto by default. This setting runs the CPU over 0.2 volts lower than when setting it to Intel fail safe default. It was a diference between 1.64v for the Intel default and 1.38v or so for Auto. This is a pretty strong undervolt! I ended up using Worse Case Scenario settings which put the CPU at 1.47v. I really wanted to make this work as otherwise, left at these dafaults, the CPU would both thermal and power throttle when running something similar like the Intel XTU benchmark, eating 300-305W. With the Worse Case Scenario setting running around 1.47v, my CPU tends to run around 240-250W in the same benchmark.
Second, the CPU settings: I used Intel XTU for this part, as it allowed me to tune to my CPU. What became apparent after multiple stress tests is the CPU cannot handle this undervolted setting while running all the core at full bore. The default settings assumed that it could handle 5.5Ghz on all 8 P Cores and 4.3Ghz on all 16 E Cores at the same time for a period of over a minute. Well, it cannot. Esepcially true when AVX workloads are added the mix. I attached a screenshot of the tweaks I did in XTU for my processor. In short, I created as curve to lower the clock speed as more cores were enabled, and I did this for both the P and E cores. This has allowed me to run longer (5+ minute) stress tests for both regular and AVX workloads and prevent thermal throttle. This is important, as the AVX workload runs the CPU harder, pulling more power and causing more heat... and crashes. I am also using a strong AVX offset of 10. It's probably aggressive but its stable for me and with it and the core changes I can run a 6 minute long AVX stress test with no crashes and no thermal thottling. If you have a better CPU cooler and/or you do not mind some occasional thermal throttling, you could probably more the core ratios up when multiple cores are called.
With these settings I have a CPU which still turbos when I need it to turbo, a CPU that pulls much less wattage and generates much less heat, and most importantly for this forum allowed me to play Victoria 1.5.10 without crashing every 5-10 minutes.
You would need to play around in XTU to see what is stable for your CPU. Unless your CPU has absolutely won the silicon lottery, I am betting it is almost impossible to overclock these CPUs and also have stable game.
Attachments
- 11
- 1
This fixed my constant crashes as well. Thank you so much for the effort you put into figuring out what was happening. In my case, I followed the first step but in the second only changed the AVX offset and was able to play with zero crashes for a few hours.
- 1
I have a i7-13900k and can not figure out a way to play since 1.5 dropped before that I had over 500 hours in but now I cant even get to the main menu, if anyone could shoot me some tip that would be great.
- 1
- 1
I have a hot tip for you. Read this entire thread, look at the multiple possible solutions, try them and see which one or ones work for you. If none of them work, open a bug report.
Well, maybe a new thread here first - it may be a setup issue rather than a game bug.
could somebody dumb down the solution for me? i enjoy Vic 3 but am far from educated in computers, or are there multiple solutions? all i know is that when i set the affinity to 0-10 CPU's it helped decrease my crashing, but did not solve my issue
- 2