Something like 30 error-ed tasks overnight with the +100 core, -200 mem settings, all showing the same 'out of paper' / error code =-36. So I think the core clock is the culprit. I've reduced it down to +50/-100 just to reduce the error rate a little while the remainder of the tasks run to completion.
---edit: changed my mind on the +50, just seems like a waste of tasks. So reduced it to factory until this batch is finished.
... with the +100 core, -200 mem settings, ... So I think the core clock is the culprit. ...
Not sure about this conclusion now. With the core clock downclocked by -100 (from 1708 to 1608), and the memory clock boosted by +200 (from 5005 to 5205), after an hour I had 2 tasks fail and 1 task succeed with exactly the same =-36 error code being returned. I was expecting there to be different errors rather than the same one. But the PC did crash so hey, at least we know those settings aren't good in their own right, hence back to factory+modified-fan-curve again.
Something like 30 error-ed
)
Something like 30 error-ed tasks overnight with the +100 core, -200 mem settings, all showing the same 'out of paper' / error code =-36. So I think the core clock is the culprit. I've reduced it down to +50/-100 just to reduce the error rate a little while the remainder of the tasks run to completion.
---edit: changed my mind on the +50, just seems like a waste of tasks. So reduced it to factory until this batch is finished.
Mike_279 wrote:... with the
)
Not sure about this conclusion now. With the core clock downclocked by -100 (from 1708 to 1608), and the memory clock boosted by +200 (from 5005 to 5205), after an hour I had 2 tasks fail and 1 task succeed with exactly the same =-36 error code being returned. I was expecting there to be different errors rather than the same one. But the PC did crash so hey, at least we know those settings aren't good in their own right, hence back to factory+modified-fan-curve again.
https://einsteinathome.org/task/606081674