-
Notifications
You must be signed in to change notification settings - Fork 217
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
Reduced hashrate across the board #1580
Comments
Got the same Thing.... When i benchmark, after a few benches the power Limit of all gpus is set to 49% instead of 100%. Switched to.. 1.9.0.23 |
How can we fix this shit? Cause i switched back to 1.9.0.23 and it does the same. |
Still same whatever tried restarting |
Duplicate issue please read response #1583 (comment) |
@ne0rrmatrix What algorithms on AMD? AMD doesn't have any power settings from NHML. |
Fixxed for me! Thanks for the fast support! Great job! |
S74nk0 AMD works with new updated version that you posted. No issues with AMD ATM. Nvidia is working well with update too. BTW i have to start afterburner after starting nicehash as it seems to mess with custom OC from afterburner. It all works fine as long as i set afterburner after i launch nicehash though. If i start nicehash after setting OC in afterburner it goes away and i have to click profile and set it again. |
Duplicate of #1583 |
I downloaded latest stable client 1.9.15 and it had lower hashrates for both nvidia and amd cards across two machines. It appeared the OC i had on nvdia combined with ethenlargement pill loaded resulted in Nvidia 1080ti averaging 31MH's and i had on previous client been getting 49 to 51 overall. Also the other algo's had hashrates drop by more than 40 percent.
On AMD system the algo's were across the board just flat out different and lower in a very meaningful way. About a 50 to 60 percent drop in performance. Will be staying on previous client till i figure out what is going on.
I am running ethenlargment pill process manually. I am running an OC using afterburner manually. Issue is most likely user error. I switched back to older client and everything returned to normal on both AMD and Nvidia systems.
The text was updated successfully, but these errors were encountered: