Quote (Rikuo @ Sep 30 2016 10:18pm)
That's not how it works though.
You can run it for a few hours & then open the program & have it crash instantly.. The reason you run it for 6+ hours, Is generally if its even a little unstable it should crash within the 6+ hours.
/e Run it 16 threads, Normal priority.
Ill do that tonight and post results tomorrow. Here is last nights results. I bumped the voltage to 1.25 and still crash after an hour so I assume its actually a temperature problem not voltage.
================================================================
x264-64 Stability test
================================================================
x264 0.148.2597 e86f3a1
(libswscale 3.0.0)
(libavformat 56.21.0)
built on Aug 19 2015, gcc: 4.9.2
x264 configuration: --bit-depth=8 --chroma-format=all
libx264 configuration: --bit-depth=8 --chroma-format=all
x264 license: GPL version 2 or later
libswscale/libavformat license: LGPL version 2.1 or later
==== Configuration =============================================
Log name = x264-log_Test2.rtf
Loops = infinity
Threads = auto
Priority = high
==== Results ===================================================
Start: 19:34:23.42 Fri 09/30/2016
Loop 1: 19:34:23.43
encoded 2121 frames, 3.37 fps, 35905.40 kb/s
Loop 2: 19:44:52.33
encoded 2121 frames, 3.37 fps, 35905.40 kb/s
Loop 3: 19:55:21.95
encoded 2121 frames, 3.36 fps, 35905.40 kb/s
Loop 4: 20:05:52.62
encoded 2121 frames, 3.35 fps, 35905.40 kb/s
Loop 5: 20:16:25.61
encoded 2121 frames, 3.37 fps, 35905.40 kb/s
Loop 6: 20:26:55.59
encoded 2121 frames, 3.37 fps, 35905.40 kb/s
Loop 7: 20:37:25.47
This post was edited by Criaric on Oct 1 2016 08:37am