Page 1 of 1

[14.21] Uknown CTD on startup

Posted: Tue Jan 10, 2017 2:40 am
by Yehn

Code: Select all

   0.000 2017-01-09 19:37:34; Factorio 0.14.21 (build 25327, win64, alpha)
   0.000 Operating system: Windows 7 Service Pack 1
   0.000 Program arguments: "C:\Users\Kio\Downloads\Factorio_0.14.3\bin\x64\factorio.exe" "--mod-directory" "modsnight" 
   0.000 Read data path: C:/Users/Kio/Downloads/Factorio_0.14.3/data
   0.000 Write data path: C:/Users/Kio/Downloads/Factorio_0.14.3
   0.000 Binaries path: C:/Users/Kio/Downloads/Factorio_0.14.3/bin
   0.013 System info: [CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz, 8 cores, RAM: 16326MB]
   0.014 Display options: [FullScreen: 1] [VSync: 0] [UIScale: 100%] [MultiSampling: OFF] [Screen: 255]
   0.015 Available display adapters: 2
   0.015  [0]: \\.\DISPLAY1 - NVIDIA GeForce GTX 980 {0x05, [0,0], 2560x1440, 32bit, 59Hz}
   0.015  [1]: \\.\DISPLAY2 - NVIDIA GeForce GTX 980 {0x01, [2560,0], 1920x1080, 32bit, 60Hz}
   0.015 Create display on adapter 0. Size 1280x720 at position [630, 342].
   0.474 Error CrashHandler.cpp:139: Exception Code: c0000005, Address: 0x000000013fe957a0
ModuleBase: 0x000000013f5b0000, ImageSize: 011e6000, RelativeAddress: 008e57a0
   0.474 Error CrashHandler.cpp:149: Exception Context:
rax=0000000000000000, rbx=0000000000000000, rcx=0000000000000000,
rdx=000000000000007f, rsi=0000000000000001, rdi=0000000000000000,
rip=000000013fe957a0, rsp=000000000305f0e0, rbp=000000000305f1e0,
 r8=000000000000007f,  r9=0000000000000000, r10=0000000000590cf0,
r11=0000000000000000, r12=0000000000000001, r13=0000000000590cf0,
r14=0000000000000000, r15=0000000000000000
   0.474 Crashed in C:\Users\Kio\Downloads\Factorio_0.14.3\bin\x64\factorio.exe (0x000000013f5b0000 - 0x0000000140796000)
Factorio crashed. Generating symbolized stacktrace, please wait ...
c:\cygwin64\tmp\factorio-bf8mp7\libraries\stackwalker\stackwalker.cpp (906): StackWalker::ShowCallstack
c:\cygwin64\tmp\factorio-bf8mp7\src\util\logger.cpp (337): Logger::writeStacktrace
c:\cygwin64\tmp\factorio-bf8mp7\src\util\logger.cpp (391): Logger::logStacktrace
c:\cygwin64\tmp\factorio-bf8mp7\src\util\crashhandler.cpp (105): CrashHandler::writeStackTrace
c:\cygwin64\tmp\factorio-bf8mp7\src\util\crashhandler.cpp (175): CrashHandler::SehHandler
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00000000777F9490)
00000000777F9490 (kernel32): (filename not available): UnhandledExceptionFilter
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0000000077A668CF)
0000000077A668CF (ntdll): (filename not available): RtlNewInstanceSecurityObject
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00000000779D1193)
00000000779D1193 (ntdll): (filename not available): KiUserApcDispatcher
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00000000779A9D0D)
00000000779A9D0D (ntdll): (filename not available): RtlDecodePointer
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00000000779991AF)
00000000779991AF (ntdll): (filename not available): RtlUnwindEx
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00000000779D1278)
00000000779D1278 (ntdll): (filename not available): KiUserExceptionDispatcher
c:\cygwin64\tmp\factorio-bf8mp7\libraries\allegro\src\win\wwindow.c (455): window_callback
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 000000007789C3C1)
000000007789C3C1 (USER32): (filename not available): GetSystemMetrics
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 000000007789A01B)
000000007789A01B (USER32): (filename not available): IsDialogMessageW
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 000000007789A061)
000000007789A061 (USER32): (filename not available): IsDialogMessageW
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00000000779D1225)
00000000779D1225 (ntdll): (filename not available): KiUserCallbackDispatcher
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 000000007789BB2A)
000000007789BB2A (USER32): (filename not available): PeekMessageW
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 000000007789BAF9)
000000007789BAF9 (USER32): (filename not available): PeekMessageW
c:\cygwin64\tmp\factorio-bf8mp7\libraries\allegro\src\win\d3d_disp.cpp (1544): d3d_display_thread_proc
c:\cygwin64\tmp\factorio-bf8mp7\libraries\allegro\src\threads.c (95): detached_thread_func_trampoline
c:\cygwin64\tmp\factorio-bf8mp7\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: 000000007777652D)
000000007777652D (kernel32): (filename not available): BaseThreadInitThunk
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00000000779AC521)
00000000779AC521 (ntdll): (filename not available): RtlUserThreadStart
   3.073 Error Util.cpp:77: Unexpected error occurred. If you're running the latest version of the game you can help us solve the problem by posting the contents of the log file on the Factorio forums.
Please also include the save file(s), any mods you may be using, and any steps you know of to reproduce the crash.
   3.077 Initialised Direct3D:[0] NVIDIA GeForce GTX 980; driver: nvd3dumx.dll 10.18.13.6519
   3.078     Video memory size (dedicated video/dedicated system/shared system/available): 4008/0/7907/3710 MB
   3.094 DSound: Starting _dsound_update thread
   3.094 DSound: Enter _dsound_update; tid=14480
I had been starting up and closing down factorio a lot while working on a mod. Interestingly, I hadn't made any changes for this startup.

Worked perfectly fine before and after.

Re: [14.21] Uknown CTD on startup

Posted: Tue Jan 10, 2017 3:14 pm
by Loewchen
Try solution 2 from here: viewtopic.php?f=7&t=9300

Re: [14.21] Uknown CTD on startup

Posted: Tue Jan 10, 2017 3:49 pm
by posila
Thank you for the report.
As I understand it, it happend once in many many starts of the game ... I looked at the line on which it crashed, but didn't see anything out of ordinary.
I think it might have been cosmic ray :)

Re: [14.21] Uknown CTD on startup

Posted: Tue Jan 10, 2017 4:13 pm
by daniel34
posila wrote:I think it might have been cosmic ray :)
https://en.wikipedia.org/wiki/Cosmic_ra ... lectronics
Studies by IBM in the 1990s suggest that computers typically experience about one cosmic-ray-induced error per 256 megabytes of RAM per month.
After reading that I'm surprised that we don't have more 1/0 cases on the forums.

Re: [14.21] Uknown CTD on startup

Posted: Tue Jan 10, 2017 4:46 pm
by posila
I think lot of people just don't report issues ... especially if they happen just once.

Re: [14.21] Uknown CTD on startup

Posted: Tue Jan 10, 2017 5:01 pm
by Yehn
posila wrote:I think lot of people just don't report issues ... especially if they happen just once.
posila wrote:Thank you for the report.
As I understand it, it happend once in many many starts of the game ... I looked at the line on which it crashed, but didn't see anything out of ordinary.
I think it might have been cosmic ray :)
Yes, that's right. Still working again without any issues right now. Thought I would report just in case...

Re: [14.21] Uknown CTD on startup

Posted: Tue Jan 10, 2017 8:43 pm
by Xeanoa
daniel34 wrote:
posila wrote:I think it might have been cosmic ray :)
https://en.wikipedia.org/wiki/Cosmic_ra ... lectronics
Studies by IBM in the 1990s suggest that computers typically experience about one cosmic-ray-induced error per 256 megabytes of RAM per month.
After reading that I'm surprised that we don't have more 1/0 cases on the forums.

99% of those errors will just be a colour being one bit off, appear as a typo in text, change the size of a stack, or affect other things where errors are non-critical. The change for the data to actually be critical is very low.

Re: [14.21] Uknown CTD on startup

Posted: Tue Jan 10, 2017 9:06 pm
by Rseding91
Xeanoa wrote:99% of those errors will just be a colour being one bit off, appear as a typo in text, change the size of a stack, or affect other things where errors are non-critical. The change for the data to actually be critical is very low.
Could be yes but with Factorio virtually every bit needs to stay intact else we measure it as a desync because it causes the binary save to be different :)