I have a 12th generation Intel Processor but i'm having the same issues! Is there any news regarding a possible fix?
-
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.
That's insane and ridicolous... This new PC is barely 4 months... It's so sad and maddening when you play only a small bunch of titles but these ones get utterly screwed
Edit: insane and ridicolous referred to the Intel situation
- 1
Did you do it trough the USB drive thing? I read something about it but I admit I'm too dumb when it comes to these things. I tried dowloading the Utility program to update the BIOS "easily" within Windows but I'm afraid my motherboard doesn't support the EZ Update function unfortunately... At this point I can only hope and pray PDX and Intel find a common solution to this
Edit: Never mind! With God's help most likely, I successfully managed to update my BIOS! Now I'm reinstalling Vic3, I'm gonna let you know if it gets fixed for me too
Last edited:
- 1
Allright um... something happened, so in my first try I just got straight up a Blue Screen when the game was trying to load the map... The second try it did successfully loaded the map and I even managed to get ahead of 6 to 7 years without problems, than I paused and saved the game and when I exited my entire PC just freezed and I had to forcefully turning it off from the start button... So to some extent the symptoms even worsened lol
Should I try again? I'm afraid any newer attempts might very well utterly screw my computer without no coming back
Update: Thankfully no more freezes but the crashes are still present and quite frequent too, Now im kinda stucked in 1850s, one thing I noticed is that apparently if I ran it in observing mode the game lasts quite long, I even managed to reach the 1870s without any crash
Update n°2: Long story short, it seems the issue wasn't the Processor but rather the insane amount of Memory Vic3 is now using, with peaks around 95%... I have 16Gb of ram which for modern day games isn't the best obviously but still tolerable I guess
Well... anyways... it seems this all debacle pretty much made ours Vic3 done for... Changing a whole PC for just one game, as much as you might like it, is out of question, at least for me. Is there any hope left this could be fixed by PDX? At the very least finding a fix for the memoey-eating monster that apperently has been unleashed within the 1.7 patch
Despite being pretty much a lost cause by now, here attached all the logs and files from the crashes folder. Maybe there's some hidden clue to let me allow to play at least a few years without issues. Thank you!
Edit: I already tried to disable the fullscreen optimization, disabling the V-sync and cap the framerates to 60 but nothing has changed, crashes still heppen with the same frequency, same within the manual settings of Windows paging size
Last edited:
I have an i5, does that mean there's still hope for me?Intel 12 - 14 (last three generations) are busted, but if its i3/i5 (lower max power) type it should be mostly safe.
That is you might want consider getting different CPU
A law firm is investigating whether to launch a class action case against Intel for 13th/14th Gen CPU instability issues
And you can register your interest via an online form.www.pcgamer.com
I already tried that but it didn't work... I don't know I can retry, so initial sizes should be 32 GB while the maximum?
Tried it, nothing
Damn this is so frustrating knowing that from the release I haver had such issues!
Last edited:
Hold on! Really?! That actually sounds great! Thank you so much for your time and patience! If you find my issue isn't related to this thread you're of course allowed to move it elsewhere. Just please keep me updated!
Here attached my dxdiag
Yoru page file is unchanged:
THEN Please do a full clean re-install:
- move any valued save games elsewhere
- "uninstall" in Steam-Vic3
- manually delete both the Steam/SteamApps/common/Victoria3 AND Documents/Paradox Interactive/Victoria3 folders - In particular make sure there are no files or folders left under either the Steam Victoria3 or Documents Victoria3 locations, before installing again.
- re-install game in Steam, run a Steam Verify when done.
- add Victoria3.exe to the exceptions list of your antivirus app; ESPECIALLY if you have Windows Defender, add it to the Ransomware "Apps Allowed Through" list.
- start the game with no mods active and test with a new campaign, NOT any existing one.
Is that any better? If not, a new dxdiag plus all those other log and text files I asked for before,please.
That's about 25gb whereas we wanted t to be 32gb at least. Can we get screenshots of that dialog now, in English if possible? FY you have plenty of free space on your C: drive , you can put the whole page file there.
THEN Please do a full clean re-install:
- move any valued save games elsewhere
- "uninstall" in Steam-Vic3
- manually delete both the Steam/SteamApps/common/Victoria3 AND Documents/Paradox Interactive/Victoria3 folders - In particular make sure there are no files or folders left under either the Steam Victoria3 or Documents Victoria3 locations, before installing again.
- re-install game in Steam, run a Steam Verify when done.
- add Victoria3.exe to the exceptions list of your antivirus app; ESPECIALLY if you have Windows Defender, add it to the Ransomware "Apps Allowed Through" list.
- start the game with no mods active and test with a new campaign, NOT any existing one.
Is that any better? If not, a new dxdiag plus all those other log and text files I asked for before,please.
Unfortunately I'm still having crashes, I followed each step here presented in order. I allowed up to 92gb of paging file size
Here attached all the logs and files
Edit: Quick update, I don't know if it's related but I when I tried a second launch I got a Blue Screen with a DCP Whatchdog Violation error
I tried another launch and it went smoothly, but still encountering crashes mid game
Last edited:
Intel's crashing CPU nightmare, explained
Intel's rapidly dying CPUs mark the biggest hardware scandal since the Pentium FDIV bug. Here's what's causing it and what you should do if your CPU is exhibiting issues.
www.pcworld.com
From what I see online that BSoD is a pretty general one, might be hardware or driver.here's one case:
If there's a .DMP as described there then MS will need to look at it. It is absolutely possible this is an effect of the Intel issues that FieryHero is helping us with.
Redirecting
answers.microsoft.com
If there's a .DMP as described there then MS will need to look at it. It is absolutely possible this is an effect of the Intel issues that FieryHero is helping us with.
@FieryHero That article again only refers to 13 and 14 gen CPUs, but this user has a 12th gen - is it likely to be covered by that article?Intel's crashing CPU nightmare, explained
Intel's rapidly dying CPUs mark the biggest hardware scandal since the Pentium FDIV bug. Here's what's causing it and what you should do if your CPU is exhibiting issues.
Yep I thought the same, I doubt it's related to Vic3 itself but it could be connected to the Intel's issue. Thank again for your time!
Did you uncover some updates or newer infos about my previously attached crash logs?
There have been no updates to this game since you started reporting this issue.