Open derkl0 opened 3 years ago
Forgot to mention running a single 3070 with +1200 mem clock which runs great with no failures if applied after dag
I came here report the same thing. This problem is very annoying since it starts throwing huge amounts of invalids. I noticed that this occurs only on RTX 3070s (for me at least). My other cards work fine. On every epoch switch this causes problems since DAG gets regenerated. Reboot is not a problem if you apply overclocking after DAG is generated. T-rex does not have this problem though.
And I forgot to mention that RTX 3080s with mem +1300mhz (which is higher than I have on RTX 3070) doesn't suffer from this. And also I have this when mining Ethereum.
have this same issue. Would love a fix. Or at the very least an option to restart the miner on GPU error...
Hey guys just wanted to fill y'all in. Talked to the devs about it in the discord here's their response:
"Hello, we want add parameters to contol OC (core/mem) like Phoenix and reset it before DAG generation for generating valid DAG, after DAG generated miner will apply OC"
So it seems they're working on it!
Hey guys just wanted to fill y'all in. Talked to the devs about it in the discord here's their response:
"Hello, we want add parameters to contol OC (core/mem) like Phoenix and reset it before DAG generation for generating valid DAG, after DAG generated miner will apply OC"
So it seems they're working on it!
This is great news. Thank you for sharing this.
Hell yeah!
On Fri, Mar 19, 2021, 1:45 AM derkl0 @.***> wrote:
Hey guys just wanted to fill y'all in. Talked to the devs about it in the discord here's their response:
"Hello, we want add parameters to contol OC (core/mem) like Phoenix and reset it before DAG generation for generating valid DAG, after DAG generated miner will apply OC"
So it seems they're working on it!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/develsoftware/GMinerRelease/issues/157#issuecomment-801987036, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAT4RA6OFMW74LRDRACZ7BTTEIGX7ANCNFSM4Y2DWHTA .
we have published beta version with OC support: https://github.com/develsoftware/GMinerBetaRelease/releases/tag/2.48
Hello! I know that I can set my memory clocks after the DAG has been generated to avoid this, but when the DAG is regenerated later, i run into errors.
If there is a way to add a DAG generation speed modifier or a way to automatically revert memory tweaks during DAG generation that would be great.
Thank you!