Page 1 of 1

[1.1.104] Crash on Launch

Posted: Wed Feb 07, 2024 5:25 am
by WiseMack
I have literally not played in two months. Today I launched the game (after several updates) and it crashed on launch.
No idea what happened.
Tried to re-launch and worked just fine.
I honestly don't understand the log file, so here is the problem part

Code: Select all

173.473 Error CrashHandler.cpp:498: Exception Code: e06d7363, Address: 0x00007ffbdb71cf19
ModuleBase: 0x00007ff7f87f0000, ImageSize: 01f0b000, RelativeAddress: e2f2cf19
 173.473 Error CrashHandler.cpp:518: Exception Context:
rax=000000c6d75b5908, rbx=00007ff7fa4c4db8, rcx=000001f900000000,
rdx=0000000100051a02, rsi=000001fab3d55570, rdi=000000c6d75b5f80,
rip=00007ffbdb71cf19, rsp=000000c6d75b5e10, rbp=000000c6d75b5f50,
 r8=00007ff7f8d212a9,  r9=00003cfe7b4ce018, r10=0002a2bd00000201,
r11=000000c6d75b56e8, r12=0000000000000000, r13=000001f9b0f83d90,
r14=000000c6d75b60f0, r15=0000000000000001
 173.473 Crashed in C:\Windows\System32\KERNELBASE.dll (0x00007ffbdb6f0000 - 0x00007ffbdb9e6000)
Factorio crashed. Generating symbolized stacktrace, please wait ...
ERROR: SymGetSymFromAddr64, GetLastError: 126 (Address: 00007FF7F9B111EC)
ERROR: SymGetLineFromAddr64, GetLastError: 126 (Address: 00007FF7F9B111EC)
ERROR: SymGetModuleInfo64, GetLastError: 1114 (Address: 00007FF7F9B111EC)
00007FF7F9B111EC ((module-name not available)): (filename not available): (function-name not available)
Stack trace logging done
For the record, a program should run fine every time, the fact there was a problem once means it can happen again.
This is the reason I am reporting something that fixed itself.

Re: [1.1.104] Crash on Launch

Posted: Wed Feb 07, 2024 8:00 am
by Rseding91
Thanks for the report. Based off this entry in the log file:
173.473 Crashed in C:\Windows\System32\KERNELBASE.dll
it crashed inside a windows DLL which we have no control over.

The only times I’ve seen that happen are failing hardware and corrupt OS files. Typically failing hardware is the most common with bad RAM and or bad RAM overclocking being the most common.