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

Mining got stuck after error - yay! found 2 shares at once #312

Open
Magadan84 opened this issue Dec 6, 2024 · 5 comments
Open

Mining got stuck after error - yay! found 2 shares at once #312

Magadan84 opened this issue Dec 6, 2024 · 5 comments

Comments

@Magadan84
Copy link

I faced a few times an issue when mining got stuck but at the same time, power consumption and hash rate were shown as normal mining. But only by analyzing a pool statistic it gets understandable that no mining there for a while. Only restarting helps to continue real mining.
The following message is in the miner log when no mining on the pool.

GPU #0: yay! found 2 shares at once
-- 1:wildrig-multi -- time-stamp -- Dec/06/24 8:15:04 --
-- 1:wildrig-multi -- time-stamp -- Dec/06/24 8:25:22 --
[08:25:22] GPU #1: yay! found 2 shares at once

More details are attached.

wildrig-multi version - 0.41.4
HiveOS - 0.6-227@241127
Radeon RX 6800 XT x2
Pool - eu.evrpool.com:1111
Overclock - Pwr Eff CClk MClk | 157W 0.183 1600 1054
wildrig issue log.txt
wildrig issue

@andru-kun
Copy link
Owner

gpu just crashes, use higher voltage for core/memory for stability. Unfortunately can't help with exact numbers

@Magadan84
Copy link
Author

when it crashes it should restart ideally. An alternative option is to show real hashrate = 0, and power consumption needs to be minimal/idle, doesn't it? I have never seen such a wrong representation of crashes and statistics.

@andru-kun
Copy link
Owner

it should, but I have no idea why it continue to show hashrate while reasults are incorrect(all that "yay! found 2 shares" without real shares found and sent to pool)

@Magadan84
Copy link
Author

it should, but I have no idea why it continue to show hashrate while reasults are incorrect(all that "yay! found 2 shares" without real shares found and sent to pool)

Don't rush to answer and draw conclusions, I believe that you can solve this issue or enhance integration with hiveos someday.
Just a kind piece of advice, fee motivates developers to improve the quality, and active issues, especially critical ones, leading to loss of money, motivate users to change a toolset. Good luck.

@andru-kun
Copy link
Owner

Don't rush to answer and draw conclusions, I believe that you can solve this issue or enhance integration with hiveos someday.
Just a kind piece of advice, fee motivates developers to improve the quality, and active issues, especially critical ones, leading to loss of money, motivate users to change a toolset. Good luck.

Nah, it doesn't motivate, I develop my miner mostly "just for fun", and lately no more fun investigate AMD problems or something :) Anyway, thanks for the report, some day will check that closely. So far better to use different miner in your case.

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