Factorio Forums

Not sure what went wrong here, but I'm submitting a bug report because this is the first time since I bought the game way back in early access that I've had a crash to desktop so this feels like a somewhat special occasion! Plus, the popup suggested I should, so I'm doing my civic duty.

I was holding a rail blueprint over an area, mulling over exact placement but hadn't clicked anything yet, and then I got the message that the game had crashed. The only other thing I'd done in the previous few minutes preceding the crash was I'd finished researching Cliff Explosives so I changed the recipe in a Mk2 Assembler on Vulcanus to manufacture them since I'd prepped it with the inputs necessary before I left.

I'm using no mods at all, playing vanilla for my first runthrough of Space Age (Which is amazing by the way and I'm enjoying it so much!). I had also just turned on Steam's recording feature so have the last 10 seconds before the crash as well to show exactly what I was doing (Which was not much).

I've booted the game up again since the crash and it's working fine, so thankfully it's nothing show-stopping that will prevent me from continuing.

Thanks for the report. The log file shows it crashed trying to draw sprites which has historically virtually always meant failing hardware. If you know of a way to reproduce this please let us know. Otherwise if you continue to have issues I recommend testing your hardware to see if you can identify what might be failing.

Damn, all the hardware's relatively new. If It failed to draw sprites I take it that's the graphics card on its way out. I'll look into it though, thank you for the tip, I appreciate it.

Coillscath wrote: Sun Dec 01, 2024 8:03 am If It failed to draw sprites I take it that's the graphics card on its way out.

This is a cpu operation, so likely CPU/RAM defect or instability.

Loewchen wrote: Sun Dec 01, 2024 2:25 pm

Coillscath wrote: Sun Dec 01, 2024 8:03 am If It failed to draw sprites I take it that's the graphics card on its way out.

This is a cpu operation, so likely CPU/RAM defect or instability.

Oh right, damn. Those are the two things I replaced most recently so that's frustrating. I appreciate the help narrowing it down though.