unstable hashrate. from 5 and up video RX 570

[aimsml]

hello. I have a mining rigs on 4, 5, 7, 8 video cards RX 570 4 gb at 540 khash per video . MB z370, i3-8100, 8gb ram. on the 4, 5 RX 570, the hashrate is stable 2.1 mh and up. 7 and 8 rx570 ( hashrate drops to 3-3. 5 mh and down to 2.7 mh ). the video manufacturer is one. the acceleration is the same. I ran it on different pools, the result is the same. resets the hashrate to 2-3 m hash. What could be the problem? 570 - 5 rx570 575 - 7 rx570 580 - 8 rx570

a lot of rejected shares

[steveocrypto]

I'm also noticing sporadic shares being submitted way below the assigned diff. Not sure how it's happening. Here's an example of the logs with timestamps on a 743 MH/s pool, 704 miners at the time (pool diff min = 0.1).

[pupreti]

I have observed this behavior as well. I have two mining rigs one with just a single GPU and other with three GPUs. My small rig is fine and I see 100% acceptance rate but my bigger rig has a lot of rejected shares and is currently sitting at 69.16% acceptance rate.

I have restarted miner, removed overclock, rolled back Nvidia driver to the last version but nothing seems to work. While it starts our fine but after the fourth or fifth vardiff adjustment it starts dropping shares.

[CryptoGraphics]

Hello. Did you try to "split" a rig between different pools? e.g. device 0,1,2 -> hashalot device 3,4,5 -> suprnova device 7,8 -> etc

[aimsml]

Hello. Stable result for the hashalot. look at 1 screen - start,

2 screen - work

[CryptoGraphics]

What is your "Stratum difficulty" when share gets rejected? (accepted counter doesn't increase). Small tip: You can use a --log-file command which enables a file logger.

[aimsml]

What is your "Stratum difficulty" when share gets rejected? (accepted counter doesn't increase).

No information on why shares were rejected. vardif 2 up 4 according to information from the pool

[2021-03-04 07:20:40] INFO accepted: 31/31 (100.00%), total hashrate: 4200.53 kH/s [2021-03-04 07:20:40] INFO cl_device(2): hashrate: 528.46 kH/s [2021-03-04 07:20:41] INFO cl_device(4): hashrate: 529.53 kH/s [2021-03-04 07:20:41] INFO cl_device(0): hashrate: 528.42 kH/s [2021-03-04 07:20:41] INFO cl_device(3): hashrate: 528.47 kH/s [2021-03-04 07:20:42] INFO cl_device(7): hashrate: 528.49 kH/s [2021-03-04 07:20:42] INFO cl_device(5): hashrate: 490.69 kH/s [2021-03-04 07:20:42] INFO cl_device(1): hashrate: 529.48 kH/s [2021-03-04 07:20:43] INFO cl_device(6): hashrate: 529.53 kH/s [2021-03-04 07:20:44] INFO cl_device(2): hashrate: 529.48 kH/s [2021-03-04 07:20:45] INFO cl_device(4): hashrate: 529.47 kH/s [2021-03-04 07:20:45] INFO cl_device(0): hashrate: 529.44 kH/s [2021-03-04 07:20:45] INFO cl_device(3): hashrate: 529.46 kH/s [2021-03-04 07:20:46] INFO cl_device(7): hashrate: 529.52 kH/s [2021-03-04 07:20:46] INFO cl_device(5): hashrate: 490.56 kH/s [2021-03-04 07:20:46] INFO cl_device(1): hashrate: 529.54 kH/s [2021-03-04 07:20:47] INFO cl_device(6): hashrate: 529.51 kH/s [2021-03-04 07:20:48] INFO cl_device(2): hashrate: 529.47 kH/s [2021-03-04 07:20:49] INFO cl_device(4): hashrate: 529.48 kH/s [2021-03-04 07:20:49] INFO cl_device(0): hashrate: 529.41 kH/s [2021-03-04 07:20:49] INFO cl_device(3): hashrate: 529.48 kH/s [2021-03-04 07:20:50] INFO cl_device(7): hashrate: 529.50 kH/s [2021-03-04 07:20:50] INFO cl_device(5): hashrate: 498.79 kH/s [2021-03-04 07:20:50] INFO cl_device(1): hashrate: 529.55 kH/s [2021-03-04 07:20:51] INFO cl_device(6): hashrate: 529.52 kH/s [2021-03-04 07:20:52] INFO cl_device(2): hashrate: 529.47 kH/s [2021-03-04 07:20:53] INFO cl_device(4): hashrate: 529.48 kH/s [2021-03-04 07:20:53] INFO cl_device(0): hashrate: 529.41 kH/s [2021-03-04 07:20:53] INFO cl_device(3): hashrate: 529.52 kH/s [2021-03-04 07:20:54] INFO cl_device(7): hashrate: 529.49 kH/s [2021-03-04 07:20:54] INFO cl_device(5): hashrate: 499.46 kH/s [2021-03-04 07:20:54] INFO cl_device(1): hashrate: 529.48 kH/s [2021-03-04 07:20:55] INFO cl_device(6): hashrate: 529.52 kH/s [2021-03-04 07:20:56] INFO cl_device(2): hashrate: 529.44 kH/s [2021-03-04 07:20:57] INFO cl_device(4): hashrate: 529.50 kH/s [2021-03-04 07:20:57] INFO cl_device(0): hashrate: 529.43 kH/s [2021-03-04 07:20:57] INFO cl_device(3): hashrate: 529.48 kH/s [2021-03-04 07:20:58] INFO cl_device(7): hashrate: 529.51 kH/s [2021-03-04 07:20:58] INFO cl_device(5): hashrate: 499.76 kH/s [2021-03-04 07:20:58] INFO cl_device(1): hashrate: 529.47 kH/s [2021-03-04 07:20:59] INFO cl_device(6): hashrate: 529.46 kH/s [2021-03-04 07:21:00] INFO cl_device(2): hashrate: 529.47 kH/s [2021-03-04 07:21:01] INFO cl_device(4): hashrate: 529.47 kH/s [2021-03-04 07:21:01] INFO cl_device(0): hashrate: 529.47 kH/s [2021-03-04 07:21:01] INFO cl_device(3): hashrate: 529.45 kH/s [2021-03-04 07:21:02] INFO cl_device(7): hashrate: 529.55 kH/s [2021-03-04 07:21:02] INFO cl_device(5): hashrate: 499.45 kH/s [2021-03-04 07:21:02] INFO cl_device(1): hashrate: 529.50 kH/s [2021-03-04 07:21:03] INFO cl_device(6): hashrate: 529.48 kH/s [2021-03-04 07:21:04] INFO cl_device(2): hashrate: 529.50 kH/s [2021-03-04 07:21:05] INFO cl_device(4): hashrate: 529.45 kH/s [2021-03-04 07:21:05] INFO cl_device(0): hashrate: 529.48 kH/s [2021-03-04 07:21:05] INFO cl_device(3): hashrate: 529.46 kH/s [2021-03-04 07:21:06] INFO cl_device(7): hashrate: 529.56 kH/s [2021-03-04 07:21:06] INFO cl_device(5): hashrate: 499.56 kH/s [2021-03-04 07:21:06] INFO cl_device(1): hashrate: 529.51 kH/s [2021-03-04 07:21:07] INFO cl_device(6): hashrate: 529.51 kH/s [2021-03-04 07:21:08] INFO cl_device(2): hashrate: 529.46 kH/s [2021-03-04 07:21:09] INFO cl_device(4): hashrate: 529.51 kH/s [2021-03-04 07:21:09] INFO cl_device(0): hashrate: 529.47 kH/s [2021-03-04 07:21:09] INFO cl_device(3): hashrate: 529.49 kH/s [2021-03-04 07:21:10] INFO cl_device(7): hashrate: 529.52 kH/s [2021-03-04 07:21:10] INFO cl_device(5): hashrate: 499.44 kH/s [2021-03-04 07:21:10] INFO cl_device(1): hashrate: 529.53 kH/s [2021-03-04 07:21:11] INFO cl_device(6): hashrate: 529.52 kH/s [2021-03-04 07:21:12] INFO accepted: 31/32 (96.88%), total hashrate: 4205.94 kH/s [2021-03-04 07:21:12] INFO cl_device(2): hashrate: 529.48 kH/s [2021-03-04 07:21:13] INFO cl_device(4): hashrate: 529.49 kH/s [2021-03-04 07:21:13] INFO cl_device(0): hashrate: 529.46 kH/s [2021-03-04 07:21:13] INFO cl_device(3): hashrate: 529.46 kH/s [2021-03-04 07:21:14] INFO cl_device(7): hashrate: 529.50 kH/s [2021-03-04 07:21:14] INFO accepted: 32/33 (96.97%), total hashrate: 4205.88 kH/s

according to information from the pool vardiff 4 down 2. No information on why shares were rejected.

[2021-03-04 07:25:41] INFO accepted: 49/50 (98.00%), total hashrate: 4203.43 kH/s [2021-03-04 07:25:41] INFO cl_device(5): hashrate: 495.51 kH/s [2021-03-04 07:25:41] INFO cl_device(4): hashrate: 529.59 kH/s [2021-03-04 07:25:41] INFO cl_device(2): hashrate: 529.52 kH/s [2021-03-04 07:25:42] INFO cl_device(0): hashrate: 529.49 kH/s [2021-03-04 07:25:43] INFO cl_device(3): hashrate: 529.50 kH/s [2021-03-04 07:25:43] INFO cl_device(7): hashrate: 529.60 kH/s [2021-03-04 07:25:43] INFO cl_device(1): hashrate: 529.49 kH/s [2021-03-04 07:25:44] INFO cl_device(6): hashrate: 529.52 kH/s [2021-03-04 07:25:45] INFO cl_device(4): hashrate: 529.53 kH/s [2021-03-04 07:25:45] INFO cl_device(2): hashrate: 529.49 kH/s [2021-03-04 07:25:46] INFO cl_device(5): hashrate: 499.25 kH/s [2021-03-04 07:25:46] INFO cl_device(0): hashrate: 529.46 kH/s [2021-03-04 07:25:47] INFO cl_device(3): hashrate: 529.47 kH/s [2021-03-04 07:25:47] INFO cl_device(7): hashrate: 529.56 kH/s [2021-03-04 07:25:47] INFO accepted: 49/51 (96.08%), total hashrate: 4205.77 kH/s [2021-03-04 07:25:47] INFO cl_device(1): hashrate: 529.51 kH/s [2021-03-04 07:25:48] INFO cl_device(6): hashrate: 529.54 kH/s [2021-03-04 07:25:49] INFO cl_device(4): hashrate: 529.56 kH/s [2021-03-04 07:25:49] INFO cl_device(2): hashrate: 529.49 kH/s [2021-03-04 07:25:50] INFO cl_device(5): hashrate: 499.53 kH/s [2021-03-04 07:25:50] INFO cl_device(0): hashrate: 529.44 kH/s [2021-03-04 07:25:51] INFO cl_device(3): hashrate: 529.48 kH/s [2021-03-04 07:25:51] INFO cl_device(7): hashrate: 529.59 kH/s [2021-03-04 07:25:51] INFO cl_device(1): hashrate: 529.51 kH/s [2021-03-04 07:25:52] INFO cl_device(6): hashrate: 529.54 kH/s [2021-03-04 07:25:53] INFO cl_device(4): hashrate: 529.60 kH/s [2021-03-04 07:25:53] INFO cl_device(2): hashrate: 529.53 kH/s [2021-03-04 07:25:54] INFO cl_device(5): hashrate: 498.24 kH/s [2021-03-04 07:25:54] INFO cl_device(0): hashrate: 529.44 kH/s [2021-03-04 07:25:55] INFO cl_device(3): hashrate: 529.47 kH/s [2021-03-04 07:25:55] INFO cl_device(7): hashrate: 529.61 kH/s [2021-03-04 07:25:55] INFO cl_device(1): hashrate: 529.53 kH/s [2021-03-04 07:25:56] INFO cl_device(6): hashrate: 529.51 kH/s [2021-03-04 07:25:57] INFO cl_device(4): hashrate: 529.60 kH/s [2021-03-04 07:25:57] INFO cl_device(2): hashrate: 529.53 kH/s [2021-03-04 07:25:58] INFO cl_device(5): hashrate: 499.21 kH/s [2021-03-04 07:25:58] INFO cl_device(0): hashrate: 529.43 kH/s [2021-03-04 07:25:59] INFO cl_device(3): hashrate: 529.47 kH/s [2021-03-04 07:25:59] INFO cl_device(7): hashrate: 529.59 kH/s [2021-03-04 07:25:59] INFO accepted: 50/52 (96.15%), total hashrate: 4205.87 kH/s [2021-03-04 07:25:59] INFO cl_device(1): hashrate: 528.49 kH/s

vardiff 2 according to information from the pool No information on why shares were rejected.

[2021-03-04 07:40:52] INFO accepted: 103/106 (97.17%), total hashrate: 4212.28 kH/s [2021-03-04 07:40:52] INFO cl_device(0): hashrate: 529.63 kH/s [2021-03-04 07:40:53] INFO cl_device(3): hashrate: 529.49 kH/s [2021-03-04 07:40:53] INFO cl_device(7): hashrate: 529.49 kH/s [2021-03-04 07:40:53] INFO cl_device(1): hashrate: 529.62 kH/s [2021-03-04 07:40:53] INFO cl_device(6): hashrate: 529.55 kH/s [2021-03-04 07:40:54] INFO cl_device(4): hashrate: 529.45 kH/s [2021-03-04 07:40:54] INFO cl_device(5): hashrate: 512.64 kH/s [2021-03-04 07:40:55] INFO cl_device(2): hashrate: 529.57 kH/s [2021-03-04 07:40:56] INFO cl_device(0): hashrate: 529.61 kH/s [2021-03-04 07:40:56] INFO Verthash block: 1519459 [2021-03-04 07:40:56] INFO accepted: 103/107 (96.26%), total hashrate: 4219.41 kH/s [2021-03-04 07:40:57] INFO cl_device(3): hashrate: 529.49 kH/s [2021-03-04 07:40:57] INFO cl_device(7): hashrate: 529.53 kH/s [2021-03-04 07:40:57] INFO cl_device(1): hashrate: 529.61 kH/s [2021-03-04 07:40:57] INFO cl_device(6): hashrate: 529.51 kH/s [2021-03-04 07:40:58] INFO cl_device(4): hashrate: 529.41 kH/s [2021-03-04 07:40:58] INFO cl_device(5): hashrate: 507.12 kH/s [2021-03-04 07:40:59] INFO cl_device(2): hashrate: 529.54 kH/s [2021-03-04 07:41:00] INFO cl_device(0): hashrate: 529.60 kH/s [2021-03-04 07:41:01] INFO cl_device(3): hashrate: 529.50 kH/s

[kanehbosm]

these "low difficulty share" rejects do not start occurring until some time has passed, ~100+ shares. if they start they begin to accelerate in frequency. i suspect a single device in the app list, rather than all of them. once the errors start that device will still produce valie shares. i currently have three stable rigs which have produced 20,000 @ 100%. the fourth one continues to eventually start tossing "low difficulty" so i restart it. two of my rigs were behaving this way, but now only one. i suspect that if relaunched things could change.

i suspect this problem may be related to issue #32 intermittent hang.

after more investigation, upon launch, the vert.exe uses ~2000mb when launched as it loads in the vert.dat. it stays at this level then very slowly lowers (not sure if it will go all the way. because i've been restarting it as the rejects start.) the stable rigs are running at ~22mb. i noticed i could force the exe to release the memory early by opening up a bunch of browser tabs.

i tested this again, but to force the exe to release its memory i launched, one at a time, two more instances of verthashminerexe. when all three were mining i safely exited (control-c) the first two instances of the exe. the remaining app is running normally and i'm confident it will remain stable currently at 475/475 shares.

the reason i tested the "ram release" is because while i was monitoring for "rejected shares" one occurred seemingly at the same time as a small chunk of ram was released. coincidence or not, those are the steps i took and the reason.

@CryptoGraphics you asked about difficulty, i do not have a specific number but ~2.3. i'm not suspicious that difficulty is related to the issue. the console text does not tell you "rejected low difficulty share" unless you have --verbose. request: a bit of color coding in the output? i hope to figure it out myself. thank you. hope this information helps.

*i was using miningpoolhub. i'm using rx 470s

[aimsml]

Hello. Log fille, option --verbose

2021-03-05 05-02-22.txt

[2021-03-05 08:12:00] DEBUG cl_device(6):Potential result count = 1 [2021-03-05 08:12:00] ERROR cl_device(6):Submit work(nonce: 9871985) [2021-03-05 08:12:00] DEBUG stratum.submit [2021-03-05 08:12:00] INFO cl_device(3): hashrate: 529.50 kH/s [2021-03-05 08:12:00] INFO cl_device(1): hashrate: 529.57 kH/s [2021-03-05 08:12:00] INFO accepted: 61/61 (100.00%), total hashrate: 4204.79 kH/s [2021-03-05 08:12:00] INFO cl_device(2): hashrate: 529.72 kH/s [2021-03-05 08:12:01] DEBUG job_id='1b1' extranonce2=00000000 ntime=6041bd9f [2021-03-05 08:12:01] INFO cl_device(4): hashrate: 529.53 kH/s [2021-03-05 08:12:01] DEBUG job_id='1b1' extranonce2=01000000 ntime=6041bd9f [2021-03-05 08:12:01] DEBUG job_id='1b1' extranonce2=02000000 ntime=6041bd9f [2021-03-05 08:12:01] DEBUG job_id='1b1' extranonce2=03000000 ntime=6041bd9f [2021-03-05 08:12:01] DEBUG job_id='1b1' extranonce2=04000000 ntime=6041bd9f [2021-03-05 08:12:01] DEBUG job_id='1b1' extranonce2=05000000 ntime=6041bd9f [2021-03-05 08:12:02] DEBUG cl_device(6):Potential result count = 1 [2021-03-05 08:12:02] ERROR cl_device(6):Submit work(nonce: 10955956) [2021-03-05 08:12:02] DEBUG stratum.submit [2021-03-05 08:12:02] DEBUG job_id='1b1' extranonce2=06000000 ntime=6041bd9f [2021-03-05 08:12:02] INFO cl_device(6): hashrate: 529.46 kH/s [2021-03-05 08:12:02] DEBUG job_id='1b1' extranonce2=07000000 ntime=6041bd9f [2021-03-05 08:12:02] INFO accepted: 61/62 (98.39%), total hashrate: 4204.73 kH/s [2021-03-05 08:12:02] DEBUG reject reason: Invalid job id [2021-03-05 08:12:02] INFO cl_device(5): hashrate: 488.48 kH/s [2021-03-05 08:12:03] INFO cl_device(0): hashrate: 529.71 kH/s [2021-03-05 08:12:03] INFO cl_device(7): hashrate: 529.53 kH/s [2021-03-05 08:12:04] INFO cl_device(3): hashrate: 529.50 kH/s [2021-03-05 08:12:04] INFO cl_device(1): hashrate: 529.54 kH/s [2021-03-05 08:12:04] INFO cl_device(2): hashrate: 529.71 kH/s [2021-03-05 08:12:05] INFO cl_device(4): hashrate: 529.51 kH/s [2021-03-05 08:12:06] INFO cl_device(6): hashrate: 527.37 kH/s [2021-03-05 08:12:06] INFO cl_device(5): hashrate: 490.61 kH/s [2021-03-05 08:12:07] INFO cl_device(0): hashrate: 529.75 kH/s [2021-03-05 08:12:07] INFO cl_device(7): hashrate: 529.57 kH/s [2021-03-05 08:12:08] INFO cl_device(3): hashrate: 529.50 kH/s [2021-03-05 08:12:08] INFO cl_device(1): hashrate: 529.53 kH/s [2021-03-05 08:12:08] INFO cl_device(2): hashrate: 529.67 kH/s [2021-03-05 08:12:09] INFO cl_device(4): hashrate: 529.48 kH/s [2021-03-05 08:12:10] INFO cl_device(6): hashrate: 527.46 kH/s [2021-03-05 08:12:11] DEBUG cl_device(6):Potential result count = 1 [2021-03-05 08:12:11] ERROR cl_device(6):Submit work(nonce: 4600523) [2021-03-05 08:12:11] DEBUG stratum.submit [2021-03-05 08:12:11] INFO cl_device(5): hashrate: 498.55 kH/s [2021-03-05 08:12:11] INFO accepted: 62/63 (98.41%), total hashrate: 4203.49 kH/s

[aimsml]

Thanks everyone. doktor83 help me, does not have all these problems, only 1.5 percent of the donation. ??