Page 1 of 1

[SOLVED][2.0.8] Crash after previewing new world

Posted: Tue Oct 22, 2024 8:41 pm
by duquefbatina
After installing SA I can no longer preview the worlds I'm creating, when I press "Preview", it generates the map preview then the game crashes after 1-5 seconds (it varies for some reason, but usually it's instant)

I can play the game just fine though

I had many different worlds created before this update, and could preview all of them just fine, haven't changed anything on my side (hardware or software-wise) - I played on (and previewed) a new world Sunday before installing the DLC

Problem is pretty easy to reproduce, open the game, click single player -> new game -> next -> press the preview button -> map generates and shows the preview for .1 second -> crash

Last time it crashed a messaged appeared asking to go to the log folder (that was the first time after 10 tries).

So far I've tried:
Disabling all mods
Updating my GPU driver
Reinstalling the game

Re: [2.0.8] Crash after previewing new world

Posted: Tue Oct 22, 2024 8:43 pm
by vinzenz
This might be fixed in 2.0.9, you steam storage quota is also getting low, it might help to clear out some saves on your factorio steam cloud.

Re: [2.0.8] Crash after previewing new world

Posted: Tue Oct 22, 2024 8:49 pm
by Loewchen
From the description alone and the fact that its a 13900k I would bet on the raptor lake defect.

Re: [2.0.8] Crash after previewing new world

Posted: Wed Oct 23, 2024 12:38 am
by duquefbatina
vinzenz wrote: Tue Oct 22, 2024 8:43 pm This might be fixed in 2.0.9, you steam storage quota is also getting low, it might help to clear out some saves on your factorio steam cloud.
Ok, thanks for the update, I'll look into how to clear the steam storage and delete all (or most of) my saves!
Loewchen wrote: Tue Oct 22, 2024 8:49 pm From the description alone and the fact that its a 13900k I would bet on the raptor lake defect.
Interesting, haven't heard of that, is my CPU faulty or something? And, also, wouldn't that have happened before the DLC if that's the case?

Re: [2.0.8] Crash after previewing new world

Posted: Wed Oct 23, 2024 1:03 am
by Loewchen
duquefbatina wrote: Wed Oct 23, 2024 12:38 am Interesting, haven't heard of that, is my CPU faulty or something?
Yes. The only question is, if this is caused by that defect.
duquefbatina wrote: Wed Oct 23, 2024 12:38 am And, also, wouldn't that have happened before the DLC if that's the case?
111696 114550

Re: [2.0.8] Crash after previewing new world

Posted: Wed Oct 23, 2024 2:44 pm
by duquefbatina
Loewchen wrote: Wed Oct 23, 2024 1:03 am
duquefbatina wrote: Wed Oct 23, 2024 12:38 am Interesting, haven't heard of that, is my CPU faulty or something?
Yes. The only question is, if this is caused by that defect.
duquefbatina wrote: Wed Oct 23, 2024 12:38 am And, also, wouldn't that have happened before the DLC if that's the case?
111696 114550
I meant on my computer (since I've been playing the base game for the past 2months without that ever occurring)
But yeah, quite bizarre (this intel issue with 13th 14th gen I mean), I guess I'll wait until I need a new CPU to try again xD

Thanks for the help!

Re: [2.0.8] Crash after previewing new world

Posted: Wed Oct 23, 2024 5:16 pm
by duquefbatina
[SOLVED]
After finding out about the intel issue I came across this news that intel released a BIOS correction (September 27th) for that issue which might solve it - if the CPU isn't toasted already, since my CPU seemed fine until now, I tried updating to this last release which supposedly corrects the Vmin Shift Instability and higher voltages being requested by the processor.

Aaaand it worked, I can now preview these beautiful worlds again without crashing.


BIOS update description:
"Introduce microcode 0x12B as the final mitigation of 13/14th Gen desktop processor Vmin Shift Instability issue according to Intel official

i. 0x12B encompasses 0x125 and 0x129 microcode updates, and addresses elevated voltage requests by the processor during idle and/or light activity periods.
ii. microcode 0x129 (August 2024) addresses high voltages requested by the processor.

iii. microcode 0x125 (June 2024) addresses eTVB algorithm issue."