search

nanopool / nanominer

Nanominer is a versatile tool for mining cryptocurrencies on GPUs and CPUs.
https://nanominer.org
639 stars 347 forks source link

Delay overclock until after DAG is generated #187

Open zylopr opened 3 years ago

zylopr commented 3 years ago

Hello.

I run my RTX 3070s with +1,400 MHz memory overclocks which works fine if the overclocking is applied after the DAG is generated, but if the overclock is applied before the DAG is generated, it ends up with a lot of rejected shares. The same thing happens every few days when there's a new DAG epoch resulting in me having to redo the overclocking settings every few days.

Is it possible for the next version of Nanominer to disable the overclocking whilst the DAG is being generated when the program is first launched? (And also with new DAG epochs?)

Thank you.

Raptor2213 commented 3 years ago

I'm having the same issue as well. If I'm overclocked when the DAG is generated, I'll get some rejected shares due to a "provisioned pow solution is invalid" error message. If I set everything to default, generate the DAG, and then overclock, it works fine.

edwardivpn commented 3 years ago

I experience the same issues as OP has described - I also hope this could gain some attention from devs to be addressed in the next release.

Right now I am using the following workaround with my 5x3070s rig, running on Windows 10. It involves creating two simple tasks within Windows Task Manager.

The first task starts Nanominer immediately when the user is logged into the system. The second one starts the MSI Afterburner app with my overclocking profiles (by adding the ' -profile1' argument) with the same condition but added 30 seconds delay. This allows Nanominer to load DAG files into GPUs running on default clocks, and a few seconds later, MSI Afterburner starts and applies my overclocking profile to all cards. The auto start on boot in the MSI Afterburner app has to be disabled.

I still have to watch for the time until the next DAG epoch and reboot my rig, otherwise, rejected shares start appearing, very likely due to the new DAG file being loaded while the GPUs are overclocked.

I saw in the docs that there is an option to configure Nanominer to use the 'reboot.bat' file when the hashrate drops below a set threshold, but unfortunately, it can't be used for this particular case as the hashrate remains unchanged when rejected shares occur.

With that in mind, if devs could add a custom option to trigger a system reboot or the Nanominer app restart after X number of shares being rejected, that would allow resolving an issue that occurs with the new DAG epoch as well using the workaround above.