Internet connection is great 60 Mbps down and 60 Mbps up, very solid, no outages.
I’m starting to think it is something with the miner and my setup, as for the 1st several minutes the intervals are mere milliseconds and then it elongates and laggs, almost just sits there for a few minutes then a share is found, and looking at the difficulty, etc that you had mentioned, now makes me question the setup.
You also have to take into consideration the amount of luck involved as well. There are times when I see multiple shares in rapid succession and others where I could go through 2-3 jobs without finding a single share.
I’m fairly new to mining so I could be completely wrong, but I’m pretty sure it’s functioning as it should be.
if you are mining on Flypool the reason for this is = the default difficulty was changed from 2000 to 8000,
Forgot to mention that I’m on Suprnova pool. I believe it shows the dynamic difficulty of the pool.
Guys, can we talk about Claymore’s devfee implementation? I mined for 15 minutes as a test. I got 30 shared in this time period. The devfee kicked in, and Claymore got 28 shares within about a minute. Extrapolated out, the claymore tax is 20%, which is totally absurd. I will test further but it seems the 2.5% statement is true purely in terms of time while the miner cheats and “saves” shares during regular mining to be submitted during the dev period.
From the logs:
23:16:45:275 ZEC: Share accepted (78 ms)!
23:18:11:075 ZEC: Share accepted (78 ms)!
23:19:58:882 ZEC: Share accepted (78 ms)!
23:20:20:070 ZEC: Share accepted (78 ms)!
23:21:12:373 ZEC: Share accepted (63 ms)!
23:21:39:998 ZEC: Share accepted (62 ms)!
23:21:56:376 ZEC: Share accepted (62 ms)!
23:22:03:323 ZEC: Share accepted (78 ms)!
23:22:17:778 ZEC: Share accepted (78 ms)!
23:22:28:461 ZEC: Share accepted (63 ms)!
23:23:54:283 ZEC: Share accepted (265 ms)!
23:24:08:171 ZEC: Share accepted (62 ms)!
23:24:25:483 ZEC: Share accepted (62 ms)!
23:24:32:776 ZEC: Share accepted (62 ms)!
23:27:04:271 ZEC: Share accepted (78 ms)!
23:27:10:833 ZEC: Share accepted (63 ms)!
23:27:23:118 ZEC: Share accepted (63 ms)!
23:28:45:427 ZEC: Share accepted (63 ms)!
23:28:47:718 ZEC: Share accepted (63 ms)!
23:29:34:479 ZEC: Share accepted (62 ms)!
23:29:44:888 ZEC: Share accepted (78 ms)!
23:30:06:761 ZEC: Share accepted (63 ms)!
23:30:12:345 ZEC: Share accepted (62 ms)!
23:30:32:342 ZEC: Share accepted (62 ms)!
23:30:36:595 ZEC: Share accepted (62 ms)!
23:31:09:491 ZEC: Share accepted (78 ms)!
23:31:27:900 ZEC: Share accepted (78 ms)!
23:31:36:949 ZEC: Share accepted (63 ms)!
23:31:37:765 ZEC: Share accepted (47 ms)!
23:31:39:680 ZEC: Share accepted (78 ms)!
23:31:46:163 DevFee: ZEC: Share accepted (47 ms)!
23:31:53:268 DevFee: ZEC: Share accepted (62 ms)!
23:32:08:896 DevFee: ZEC: Share accepted (63 ms)!
23:32:12:348 DevFee: ZEC: Share accepted (46 ms)!
23:32:12:571 DevFee: ZEC: Share accepted (47 ms)!
23:32:13:271 DevFee: ZEC: Share accepted (94 ms)!
23:32:15:315 DevFee: ZEC: Share accepted (62 ms)!
23:32:19:573 DevFee: ZEC: Share accepted (47 ms)!
23:32:21:151 DevFee: ZEC: Share accepted (47 ms)!
23:32:24:083 DevFee: ZEC: Share accepted (47 ms)!
23:32:25:098 DevFee: ZEC: Share accepted (47 ms)!
23:32:25:294 DevFee: ZEC: Share accepted (46 ms)!
23:32:25:802 DevFee: ZEC: Share accepted (47 ms)!
23:32:26:738 DevFee: ZEC: Share accepted (47 ms)!
23:32:26:832 DevFee: ZEC: Share accepted (62 ms)!
23:32:27:378 DevFee: ZEC: Share accepted (93 ms)!
23:32:33:509 DevFee: ZEC: Share accepted (47 ms)!
23:32:33:740 DevFee: ZEC: Share accepted (281 ms)!
23:32:36:393 DevFee: ZEC: Share accepted (62 ms)!
23:32:37:641 DevFee: ZEC: Share accepted (47 ms)!
23:32:48:188 DevFee: ZEC: Share accepted (140 ms)!
23:32:48:271 DevFee: ZEC: Share accepted (15 ms)!
23:32:48:457 DevFee: ZEC: Share accepted (31 ms)!
23:32:48:471 DevFee: ZEC: Share accepted (47 ms)!
23:32:48:481 DevFee: ZEC: Share accepted (62 ms)!
23:32:48:698 DevFee: ZEC: Share accepted (281 ms)!
23:32:51:374 DevFee: ZEC: Share accepted (47 ms)!
23:32:51:584 DevFee: ZEC: Share accepted (47 ms)!
First off, you can’t “save” shares, since they are only relevant to the block currently being worked on. If you submit shares for a previous block, they are rejected. Secondly, finding shares are subject to the variance inherent in the probabilistic PoW algorithm. You don’t find X shares every Y minutes mining with Z hash rate. Sometimes you may get 3 shares in a minute, then not find one for 10 minutes. Variance is the one absolute truth in mining. Some devfee periods will find an above average number of shares, some will be below average, just as the non-devfee periods. Ultimately, it’s what the pool registers as your effective hash rate and share rate that matters, since that’s what your payout is based on.
Does Claymore potentially switch pools too for the dev fee? I’m thinking the difficulty on the different pools could have an impact.
That’s it. The shares are lower difficulty during the devfee phase.
Hello! I’m hoping someone might be able to help me troubleshoot my rig. I’m only getting 3 of 6 GPU’s to mine anything 
So I’m running v12.4 of Claymore’s miner on Windows 10 & I’ve got 6 rx480’s.
Here’s what I’ve got in my “config” file:
-zpool eu1-zcash.flypool.org:3333 -zwal t1KcBpvyZB9ezLs8sPZ6Pd7yydTotesUWsW -zpsw z #-tt 75 #-i 8 #-powlim 50 #-a 2 #-asm 0 #-allpools 1
Here’s what I’ve got in “start” file:
ZecMiner64.exe`
Copy of the last log file here → JustPaste.it - Share Text & Images the Easy Way
Any ideas what I’m doing wrong?? Thanks!
does windows see all 6?
has it ever worked?
what version drivers?
have you run ddu in safemode? then re install proper drivers
A smooth 30 h increase. Great work mr Claymore
i’m getting 5 working. 6th rx shows up in dev manager and when it automatically installs the pc resets. msi z97 win 10 64 tried many drivers and bios configs from gen 1 to 3, clean ati reinstalls, bus speeds 64 - 32. what thetbloodclot?? advice would be appreciated thx.
does somebody know how to set cvddc and mvddc just for some but not all cards?
i have 6 cards, and i just want to set cvddc and mvddc for 2 cards , is this possible?
reason for this is i have no idea on the settings that i could use for the other 4 
Yes it is… he tells you exactly how to do it in the readme instructions
-cvddc set target GPU core voltage, multiplied by 1000. For example, “-cvddc 1050” means 1.05V. You can also specify values for every card, for example “-cvddc 900,950,1000,970”.
I came on this thread looking for a way to undervolt RX 580 on Linux. Have you managed to find a way to do so?
yes i did read the instrutions, but the thing is, i have 6 cards, i would only like to set the cvddc for gpu2 and gpu4, how to do that?
i don’t know the values of gpu0, gpu1, gpu3 and gpu5.
Two options, once use any one of the many programs that let you manually
change clocking and power to see what the default level is or try using 0
as a default base (I have no idea is 0 is default here, but it is in his
other settings)
Example –cvddc 0,0,x,0,x,0
zcrash https://forum.zcashcommunity.com/u/zcrash
June 2
yes i did read the instrutions, but the thing is, i have 6 cards, i would
only like to set the cvddc for gpu2 and gpu4, how to do that?
i don’t know the values of gpu0, gpu1, gpu3 and gpu5.
good tip , i have just tried that. however, from the moment i moved my rig to another location (garage) and dont have a monitor conneced to it anymore, it does not show certain things anymore in msi afterburner (like gpu clock/mem clock and voltage and temperature). i guess it’s because of not having a monitor connected.
i have tried also with gpu-z, and while it does show the default clock for gpu and memory, it does not show the current clock for gpu and memory. it does show the vddc in the senors tab however, i’m going to play around with it a little.
what is the best driver for a rig with a mix of r9 280, 280x and 7970s ?
Should i go with Windows 10 (which driver ?) or with Ubuntu ( which distro and which driver ? ) ?
Hello. Can i somehow get statistic in console automaticly every 5 minute?
Sometimes miner frozen and do not getting new jobs. So, if i push “s” he is restarting with msg: “Miner thread hangs, need to restart miner!”.
In logs nothing suspicious.