LINCS warning followed by an Early WU End message is an indication that progress of a Work Unit was terminated due to Simulation Instability. Following log entries show this message:
[01:20:01] Completed 132000 out of 200000 steps (66) [01:20:05] + Writing 'sec_per_frame = 1050.500000' to config [01:20:05] + Working ...Timered checkpoint triggered. [01:43:59] Quit 101 - Fatal error: [01:43:59] Step 133288, time 266.576 (ps) LINCS WARNING
[01:43:59] relative constraint deviation after LINCS: [01:43:59] max 0.000464 (between atoms 70341 and 70343) rms 0.000007 [01:43:59] [01:43:59] Simulation instability has been encountered. The run has entered a [01:43:59] state from which no further progress can be made. [01:43:59] If you often see other project units terminating early like this [01:43:59] too, you may wish to check the stability of your computer (issues [01:43:59] such as high temperature, overclocking, etc.). [01:43:59] Going to send back what have done. [01:43:59] logfile size: 76172 [01:43:59] - Writing 76858 bytes of core data to disk... [01:43:59] ... Done. [01:43:59] [01:43:59] Folding@home Core Shutdown: EARLY_UNIT_END [01:44:04] CoreStatus = 72 (114) [01:44:04] Sending work to server
[01:44:04] + Attempting to send results [01:44:04] - Reading file work/wuresults_02.dat from core [01:44:04] (Read 76858 bytes from disk) [01:44:09] - Uploaded at ~15 kB/s [01:44:09] - Averaged speed for that direction ~36 kB/s [01:44:09] + Results successfully sent [01:44:09] Thank you for your contribution to Folding@Home.
In this case a WU ended early, however partial results were sent to Stanford for partial credit.
This happens due to bad work units as Larry the weatherman explains this thread: /forum/remark,11699582~mode=flat