You can use nicehash+heavy way before 1.6.4, i don't know where do you get this info from. Stale shares are not sent when using nicehash cause nicehash rejects ALL stale shares, so no point in sending them. 10-11% is much i agree.

Don't have to rebuild kernels after changing drivers, miner will work, but i would suggest you to rebuild them to be sure you are totally compatible with the drivers.

Next version (soon) will make some of you guys happy : full cmd line setup for gpu's and pool, so everything can be setup in bat (almost everything).
Yes i know you are asking for this a long time ago, but now the time has come

Also something that could improve effective hashrate, i saw some of you have 'huge' differences in miner displayed hashrate / effective hashrate, this is probably because of the way SRB handles stale shares.
More info soon

Apart from your problem with the dev fee reconnect: You shouldn't use double hash with CNv7 on an AMD FX. Bulldozer has got 2 MB L2 cache per module. That's exactly the scratchpad size of one CNv7 thread. So don't us double hash, which results in 4 MB scratchpad size, use four single hash threads and put one per module, ergo (under Windows) cores 0, 2, 4 and 6 (or 1, 3, 5 and 7). That's way faster than your config. With CNv7 you should get a hashrate of approximalely 290 H/s.

The maximum you can get with an AMD FX is, to use the circumstance that it has – beneath its 2 MB L2 cache per module – an 8 MB L3 victim cache, which is not inclusive as it is the case with all Intel CPUs. Data in the L2 cache is never in the L3 cache and vice versa. So with bulldozer, you can start 8 single hash CNv7 threads dedicated to the cores 0, 1, 2, 3, 4, 5, 6 and 7. This config will result in a lot of traffic between L2 and L3, that's why performance will not scale linear with the number of threads, but still all data is cached, no slow memory access. It will give you the max. performance, in your case around 340 H/s with FX-8320.

And what about RX580 driver version to mine heavy and V7? Thank you Doktor83 for your work

On v7 all of my cards , 470, 480, 570, 580 4gb or 8gb they all get the same speed on every launch, this is how it was in earlier versions too, only heavy had this 'have to run multiple times' to get max speed thing.
I changed almost everything in this kernel like it was in 1.6.0 for Rx cards, also nothing that has impact on intensity setting has been changed since, i don't know last 10 versions, so if 116 was a good value in 1.6.0 it should be a good value now too, i don't understand how can't you set it to 116 as before.
I also used the fragment value you wrote earlier here as a default for 580 8gb, you said you get the best results with it.

For me it's interesting that on a few xfx 580 8gb i have, even not on the same rigs, i can use the same settings on v.1.6.2 as before , and get the same hashrate as before. But i havent changed or tried out new drivers or anything on these rigs, cause they are mining rigs, the most important is that they run always stable, so i stick to a driver that is proven to be good/stable.

Win 7 or Win10, doesn't matter, blockchain drivers installed from day 1.

So i basically just upload a new version of miner when testing to the rig, copy the old config files and run the miner.
This way using absolutely everything same i can know if something is better/worse.

Is it really faster than the dedicated AMD blockchain driver 22.19.659.0 alias 17.30 beta 8?

Win7 ... 18.x drivers don't allow to enable compute mode in Win7 :/ so I use blockchain driver or 15.12 (as its best for Claymore miners on old cards)

Straps for ETH, 1150/2050 , 100w from the wall ~ 950hs on v7
56/8/2

yes it can be pushed way over 1000hs but im not looking for that, only using it for testing the miner.

it should be in a few minutes max, on my hynix 580 8gb cards i get the same hash as on 1.6.0.
Also on 470 8gb.
Don't have samsung 580 8g to try.

Hi, JCE-Miner

Thanks for that very good miner  

Testing last 0.31a version. I have, like you, Ryzen 1600, but on 3600mhz

I prefer manual config and decrease number of working core - best when 6, only new Bittube - 4.

So, my results ( not very long test )

CN7 ~ 490 h/s

CNlite ~ 1780 h/s

newBittube ~ 180 h/s

Don`t test heavy - no wallet for it.

JCE-Miner, what hash you have at CN7, light and heavy ?  

Ppl, give me pool settings and wallet to test CNheavy algo  

you should try

V1.6.3
- More speed on Vega56 cards on every algo (probably on Vega64 and VegaFE too, i don't have them to test)
- Added parameter --enableduplicategpuid (used in start.bat), that enables to use the same gpu id in gpu_conf multiple times
- Removed useless kernels 3 and 4
- Removed useless CPU opencl support

+ Vega cards should get even more speed than in previous version (try with adrenaline 18.3.4 or adrenaline 18.6.1)

+ Added parameter --enableduplicategpuid (in .bat) which basically allows you to do something like this :

"gpu_conf" :
[
   { "id" : 0, "intensity" : 120, "worksize" : 8, "threads" : 1},
   { "id" : 0, "intensity" : 120.5, "worksize" : 8, "threads" : 1},
]

So instead of using the same settings for every thread on same GPU, you can define different intensity for example for one thread.
This way maybe you can squeeze out a little more hash from your GPU.

On initialisation this is displayed as DIFFERENT GPU'S, but on hashrate display threads of same gpu are merged, so a per gpu hashrate is still displayed, not a per thread speed.

+ Removed a few useless things like kernels 3&4, and CPU OpenCL support, nobody used these but they just took me more time when implementing something new

That's were JCE is the best, the small RX on CN-v7


Hey man, Good job with the miner. experimenting with more straps (nearly reach 590 h/s with your miner, however got rejects due to unstable clock/strap). There is a big problem though, how do you suggest
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : ..., "multi_hash":464 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : ..., "multi_hash":464 },
Which OS do you use lol? this intensity is insane... 5 month ago on elpidas maximum i could get with GG (old) was 448, hynix would BSOD.
NOW, with all the bloatware from microsoft over the past months and amd drivers i can only set intensity to 25-26 (SRB, equivalent to 400-408 here) in your miner howver, the maximum i was able to get to work was:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":448 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":416 }
Do you think i have a problem with 18.3.4 driver, Windows 10 1709

Hi Guys,

Are there some estimated Hashrates for CN_Heavy?

I am interested in:
RX570, 4 GB
RX580, 8 GB

I am actuallly uses SRB Miner

Thank you

Looks like that some optimisations that work nicely for vega degrade performance on rx.
I will rework my kernel so the speed should be back to v1.6.0 speeds on rx.