Page 1 of 1
[0.13.17]crash at game start
Posted: Sun Aug 21, 2016 4:41 pm
by matjojo
Game crashed at start, no mods enabled.
What I did:
- start the game, play for a bit
- put laptop in sleep mode without stopping the game
- open laptop stop the game
- start game directly again, game gives can not start already running message
- wait a minute
- start game, get error (unexpected error)
sorry, forgot specs:
CPU: i3-4005U
GPU: Intel HD 4600
OS: Windows 10
Re: [0.13.17]crash at game start
Posted: Sun Aug 21, 2016 6:23 pm
by TruePikachu
Code: Select all
2550.852 Error CrashHandler.cpp:135: Exception Code: c0000005, Address: 00007FF7305BBC6E
ModuleBase: 00007FF72FD60000, ImageSize: 01106000, RelativeAddress: 0085bc6e
2550.853 Error CrashHandler.cpp:145: Exception Context:
rax=0000000000000000, rbx=000001fc61606a90, rcx=000001fc63771a40,
rdx=0000000000000000, rsi=0000000000000018, rdi=0000005b0e8fbfb8,
rip=00007ff7305bbc6e, rsp=0000005b0ecff8c0, rbp=0000005b0ecff9c0,
r8=0000005b0ecff718, r9=00007ffae87d1190, r10=0000000000000000,
r11=0000000000000246, r12=0000000000000000, r13=000001fc63828e60,
r14=0000000000000000, r15=000001fc61606b40
Factorio crashed. Generating symbolized stacktrace, please wait ...
c:\cygwin64\tmp\factorio-3jumdq\libraries\stackwalker\stackwalker.cpp (906): StackWalker::ShowCallstack
c:\cygwin64\tmp\factorio-3jumdq\src\util\logger.cpp (328): Logger::writeStacktrace
c:\cygwin64\tmp\factorio-3jumdq\src\util\logger.cpp (382): Logger::logStacktrace
c:\cygwin64\tmp\factorio-3jumdq\src\util\crashhandler.cpp (105): CrashHandler::writeStackTrace
c:\cygwin64\tmp\factorio-3jumdq\src\util\crashhandler.cpp (155): CrashHandler::SehHandler
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB0A857E1E)
00007FFB0A857E1E (KERNELBASE): (filename not available): UnhandledExceptionFilter
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB0DFED998)
00007FFB0DFED998 (ntdll): (filename not available): memset
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB0DFD5B26)
00007FFB0DFD5B26 (ntdll): (filename not available): _C_specific_handler
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB0DFE9AFD)
00007FFB0DFE9AFD (ntdll): (filename not available): _chkstk
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB0DF74FE9)
00007FFB0DF74FE9 (ntdll): (filename not available): RtlImageNtHeaderEx
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB0DFE8C0A)
00007FFB0DFE8C0A (ntdll): (filename not available): KiUserExceptionDispatcher
c:\cygwin64\tmp\factorio-3jumdq\libraries\allegro\src\win\d3d_disp.cpp (1613): d3d_display_thread_proc
c:\cygwin64\tmp\factorio-3jumdq\libraries\allegro\src\threads.c (95): detached_thread_func_trampoline
c:\cygwin64\tmp\factorio-3jumdq\libraries\allegro\src\win\wxthread.c (38): thread_proc_trampoline
d:\th\minkernel\crts\ucrt\src\appcrt\startup\thread.cpp (115): thread_start<unsigned int (__cdecl*)(void * __ptr64)>
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB0C458102)
00007FFB0C458102 (KERNEL32): (filename not available): BaseThreadInitThunk
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB0DF9C5B4)
00007FFB0DF9C5B4 (ntdll): (filename not available): RtlUserThreadStart
This crash is from over 40 minutes after the game has been started.
Re: [0.13.17]crash at game start
Posted: Sun Aug 21, 2016 6:50 pm
by Loewchen
Re: [0.13.17]crash at game start
Posted: Mon Aug 22, 2016 5:37 pm
by matjojo
nonononononononono, The instance of the game running when going into sleep mode is no the one that crashed, it crashed when starting a new instance I opened just in case
Re: [0.13.17]crash at game start
Posted: Mon Aug 22, 2016 5:45 pm
by Loewchen
matjojo wrote:
nonononononononono, The instance of the game running when going into sleep mode is no the one that crashed, it crashed when starting a new instance I opened just in case
I see.
Re: [0.13.17]crash at game start
Posted: Tue Aug 23, 2016 11:58 am
by posila
The log looks like it is from Factorio that you closed after opening the laptop. Crash happens over 40 minutes after the game was started.
So it seems to me the unexpected error happened before Factorio initialized logging.