Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About Hashrate Problem #275

Open
ygtt opened this issue Apr 19, 2021 · 1 comment
Open

About Hashrate Problem #275

ygtt opened this issue Apr 19, 2021 · 1 comment

Comments

@ygtt
Copy link

ygtt commented Apr 19, 2021

Ekran Alıntısı

Hello everyone,

My hashrate chart is like in the picture. The graphic always sounds wavy. Do you think this is normal? (My computer has been inactive during these 24 hours.) ( My GPU is RTX 2060, For this GPU, I think the values are low. please give me your opinion.)

When i check logfiles, got ERROR. Do you think this error is caused by the software or the pool?
ERROR - No share accepted in 30 minutes. Something is wrong, restart miner.

Can these 2 topics be linked?

Waiting for your thoughts.

@mlamias
Copy link

mlamias commented Apr 19, 2021

The error you are getting sounds like you have overlcoked your cards too much. I would recommend reducing your core and memory clocks until you aren't getting so much rejected shares. What I suspect is happening and leading to the wavy graph is that when you first start mining your shares are getting accepted, but you are likely starting to accumulate GPU errors from too much overlocking. At some point when you have too many GPU errors, they start getting rejected. NBMiner then probably restarts and the process starts over again (accepted shares, followed by rejected shares, and then the miner restarts). One way to see if this is happening is to look at the log files are a few hours. If you have several separate log files, then that's an indicator that your miner is restarting (and each time it does this, it generates a new log file). Simply reduce your clocks.

Also, one thing you may want to try is to set all of your cards to their default settings in MSI Afterburner. Then start mining. After the DAG file is generated, slowly start to move your clocks to a stable setting.

Let us know if you fix this. Good luck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants