You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current CoreCycler implementation is to only ever reduce the negative CO offset, never to increase it.
However, it would be really really useful if this sort of feature was available. It would be great to be able to start an automatic test, and let CoreCycler run while I'm out at work, gradually adding a bigger and bigger negative CO offset until it is unstable. That way, far less intervention would be required.
Currently, only option is to overdo the negative CO offset and hope that it isn't unstable enough to fully crash the PC, only unstable enough to fail the test.
The text was updated successfully, but these errors were encountered:
Yes, I've thought about that as well.
It does need some careful thought so that it doesn't run into an infinite loop between two values though. Basically it needs to keep track of which setting has already caused an error before, and not go back to that if X successful iterations with less undervolt have passed.
Thanks for this. Ah course. That makes sense. Yes. It would need to log the planned CO values it was going to set, so in the event of a crash, it would know the values which caused that.
I imagine the ultimate implementation being a range of tests.
Test 1 only runs for a minute or so per core - it's a rough test to determine if a value is ridiculously unstable. It gets you in a ballpark area.
Test 2 begins from the final "stable" value from test 1, but tests now for 6 minutes per core, further homing in to the ultimate value.
Test 3 continues on, but now runs for 30 mins / 1 hour per core, to undoubtedly confirm the peak achievable offset.
Hey,
Current CoreCycler implementation is to only ever reduce the negative CO offset, never to increase it.
However, it would be really really useful if this sort of feature was available. It would be great to be able to start an automatic test, and let CoreCycler run while I'm out at work, gradually adding a bigger and bigger negative CO offset until it is unstable. That way, far less intervention would be required.
Currently, only option is to overdo the negative CO offset and hope that it isn't unstable enough to fully crash the PC, only unstable enough to fail the test.
The text was updated successfully, but these errors were encountered: