Page 1 of 1
[2.0.42] Crash on map preview (14900K)
Posted: Mon Mar 24, 2025 3:16 pm
by dzejvidz
Version 2.0.42
Hello i have this problem maybe for 3-4 days
I launch the game i want to start a new World i tweak the resources then click preview and it instantly crashes it happens every time with and without mods.I donĀ“t know what to do can someone please help
Re: [2.0.42] Crash on map preview (14900K)
Posted: Mon Mar 24, 2025 3:19 pm
by Loewchen
This would be typical for the raptor lake defect, but you uploaded the wrong log.
Re: [2.0.42] Crash on map preview (14900K)
Posted: Mon Mar 24, 2025 3:21 pm
by dzejvidz
Which one should it be (the log)
Re: [2.0.42] Crash on map preview (14900K)
Posted: Mon Mar 24, 2025 3:22 pm
by boskid
Well, this specific log file does not cover any details related to any specific crashes. While looking at this log i noticed you have 14900k CPU. Since generating preview usually requires high amount of computations this causes high cpu load, and 13th/14th gen intel cpus are quite likely to kill themselves if you are using old bios (before microcode 0x129 if i remember correctly since it was also affecting me). I suspect the issue in your case is just CPU dying and you will need to RMA the cpu, but without any additional details i cannot tell you anything for certain.
Re: [2.0.42] Crash on map preview (14900K)
Posted: Mon Mar 24, 2025 3:31 pm
by dzejvidz
So if I understand correctly. are you saying that I have a bad processor? Or I apologize, I'm not very good at this and I don't understand it that much. You also said that it's a bad log? which one should I pin then?
Re: [2.0.42] Crash on map preview (14900K)
Posted: Mon Mar 24, 2025 3:43 pm
by Loewchen
If you had this processor running for longer than a few months without the latest bios it likely destroyed itself already. Either way, update the bios now and RMA the CPU if the issue persists.
Re: [2.0.42] Crash on map preview (14900K)
Posted: Mon Mar 24, 2025 5:05 pm
by dzejvidz
So update.
I updated BIOS and everything to seem to run good so BIOS probably was the issue.