Just had the same problem again (after some nonproblematic runs), with the same WU (same R/C/G). Except this time, I wasn't around to see the error when it occurred, so the ERROR 0x3 only got written to FAHLog when I came back and hit OK on the Microsoft Runtime error popup. That explains the 3-hour gap, and based on my temperature readings the core was running the entire time, which I would rather it not do if it's not doing anything productive...
Is there a way to prevent problematic WUs like this one from being reassigned to a machine it's failed on already?
Code: Select all
[18:00:09] Project: 6020 (Run 0, Clone 182, Gen 9)
[18:00:09]
[18:00:09] Assembly optimizations on if available.
[18:00:09] Entering M.D.
[18:00:15] Completed 0 out of 500000 steps (0%)
[18:09:53] - Autosending finished units... [February 12 18:09:53 UTC]
[18:09:53] Trying to send all finished work units
[18:09:53] + No unsent completed units remaining.
[18:09:53] - Autosend completed
[21:23:21] CoreStatus = 3 (3)
[21:23:21] Client-core communications error: ERROR 0x3
[21:23:21] Deleting current work unit & continuing...