SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[JuanHungLo]

V1.7.0 very stable with StelliteV4.  Clocks and memory now set to "winter" mode.

https://pasteboard.co/HMQ4zHx.png


All vega rigs have AMD 18.5.1 except rig 10 which has 18.8.1 as suggested by another poster, I get no better h/s with stellitev4, maybe with heavy or v8?  I haven't tried.  RX470 rigs use Win 7 and BC drivers.  Very happy with this miner and I no longer have issues with connecting to dev's pools since changing all DNS servers to 8.8.8.8 from Open DNS servers.

[1714821136]

1714821136

[1714821136]

1714821136

[1714821136]

1714821136

[MinersRus]

V1.7.0 very stable with StelliteV4.  Clocks and memory now set to "winter" mode.

https://pasteboard.co/HMQ4zHx.png


All vega rigs have AMD 18.5.1 except rig 10 which has 18.8.1 as suggested by another poster, I get no better h/s with stellitev4, maybe with heavy or v8?  I haven't tried.  RX470 rigs use Win 7 and BC drivers.  Very happy with this miner and I no longer have issues with connecting to dev's pools since changing all DNS servers to 8.8.8.8 from Open DNS servers.

I have my router's Primary DNS set to 1.1.1.1 and Secondary DNS set to 1.0.0.1 which is said to be the fastest and most private DNS service. All of my computers on my network use the router for DNS.


I have been using this since it was first announced without issue and with no issues ever on my mining rigs.

What Is 1.1.1.1?
https://www.cloudflare.com/learning/dns/what-is-1.1.1.1

Introducing 1.1.1.1
https://1.1.1.1

[doktor83]

Very happy with this miner and I no longer have issues with connecting to dev's pools since changing all DNS servers to 8.8.8.8 from Open DNS servers.

FINALLY!

you won't believe how glad i am that you finally resolved that issue.

[GKumaran]

Bug  :  Vega 64 Litev7/Mox algo Hash drop
When : Pool disconnects and reconnects 

Tried : Different algos - LiteV7, Mox; Different pools

Eg: Extract

Code:

[2018-11-12 18:25:28] hashrate: GPU0: 4524 H/s [BUS:3]
[2018-11-12 18:25:28] hashrate: GPU1: 4532 H/s [BUS:6]
[2018-11-12 18:25:28] hashrate: GPU2: 4533 H/s [BUS:9]
[2018-11-12 18:25:28] hashrate: GPU3: 4340 H/s [BUS:13]
[2018-11-12 18:25:28] hashrate: GPU4: 4531 H/s [BUS:16]
[2018-11-12 18:25:28] hashrate: GPU5: 4526 H/s [BUS:19]
[2018-11-12 18:25:28] hashrate: Total: 26986 H/s
[2018-11-12 18:25:33] pool_ping: Sent keepalive message to pool
[2018-11-12 18:25:33] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-11-12 18:25:33] json_receive: Pool responded with KEEPALIVED
[2018-11-12 18:25:57] miner_result: Sending user result to pool
[2018-11-12 18:25:57] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"507345136185176","job_id":"573069932661019","nonce":"bf557b15","result":"7cc244775f372f86fd344b9147f32c7e2c3c252097c3c9b4498abf73a9090000","algo":"cn/mox"}}
[2018-11-12 18:25:57] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-12 18:25:57] miner_result: Pool accepted result 0x000009A9
[2018-11-12 18:26:28] pools: Job timeout detected, reconnecting to pool..
[2018-11-12 18:26:29] pool_ping: Couldn't send keepalive message to pool
[2018-11-12 18:26:35] Connection to pool lost. Reconnecting in 5 seconds.
[2018-11-12 18:26:41] json_send: {"id":1,"jsonrpc": "2.0","method":"login","params":{"login":"x.1600000","pass":"GKMiner","agent":"SRBMiner Cryptonight AMD GPU miner/1.7.0","rigid":"","algo":["cn/2","cn/1","cn-heavy/0","cn-heavy/xhv","cn-heavy/tube","cn/xtl","cn/msr","cn-lite/1","cn/xao","cn/rto","cn/b2n","cn/ita","cn/mkt","cn/mox","cn/0","cn/dark","cn/fest"],"algo-perf":{"cn/2": 1.0,"cn/1": 1.0,"cn-heavy/0": 1.0,"cn-heavy/xhv": 1.0,"cn-heavy/tube": 1.0,"cn/xtl": 1.0,"cn/msr": 1.0,"cn-lite/1": 1.0,"cn/xao": 1.0,"cn/rto": 1.0,"cn/b2n": 1.0,"cn/ita": 1.0,"cn/mkt": 1.0,"cn/mox": 1.0,"cn/0": 1.0,"cn/dark": 1.0,"cn/fest": 1.0},"algo-min-time": 600}}
[2018-11-12 18:26:41] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"711659568315371","job":{"blob":"0707c3e7a5df0562ece3b3cddd8327146e28cd4877543c8cf6b10acf61f77df8a9755c010f03b9000000007a4a7f0f500cf97dbb6ab8c4d82a7da80f9117318f42a6b8552376d22ad1467701","job_id":"669915444171056","target":"7c0a0000","id":"711659568315371"},"status":"OK"}}
[2018-11-12 18:26:41] Connected to zzzzzz:58333
[2018-11-12 18:26:41] sock_ready: User logged in
[2018-11-12 18:26:41] pool_have_job: Pool sent a new job (ID: 669915444171056) [mox]
[2018-11-12 18:26:43] miner_result: Sending user result to pool
[2018-11-12 18:26:43] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"711659568315371","job_id":"669915444171056","nonce":"0bb4aa6a","result":"486d5d4581fcc100f5fe3fa3fb22efabfba0b867d6037150f3c98c648d090000","algo":"cn/mox"}}
[2018-11-12 18:26:43] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-12 18:26:43] miner_result: Pool accepted result 0x0000098D
[2018-11-12 18:28:34] pool_ping: Sent keepalive message to pool
[2018-11-12 18:28:34] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-11-12 18:28:34] json_receive: Pool responded with KEEPALIVED
[2018-11-12 18:29:29] hashrate: GPU0: 4253 H/s [BUS:3]
[2018-11-12 18:29:29] hashrate: GPU1: 4273 H/s [BUS:6]
[2018-11-12 18:29:29] hashrate: GPU2: 4268 H/s [BUS:9]
[2018-11-12 18:29:29] hashrate: GPU3: 4110 H/s [BUS:13]
[2018-11-12 18:29:29] hashrate: GPU4: 4257 H/s [BUS:16]
[2018-11-12 18:29:29] hashrate: GPU5: 4248 H/s [BUS:19]
[2018-11-12 18:29:29] hashrate: Total: 25409 H/s

Have multiple logs showing the same.
Clocks are stable, if pool doesn't disconnect, miner is super stable

[JuanHungLo]

V1.7.0 very stable with StelliteV4.  Clocks and memory now set to "winter" mode.

https://pasteboard.co/HMQ4zHx.png


All vega rigs have AMD 18.5.1 except rig 10 which has 18.8.1 as suggested by another poster, I get no better h/s with stellitev4, maybe with heavy or v8?  I haven't tried.  RX470 rigs use Win 7 and BC drivers.  Very happy with this miner and I no longer have issues with connecting to dev's pools since changing all DNS servers to 8.8.8.8 from Open DNS servers.

nice html monitor!!!

Thanks, I just wrote some for loops and modified www.memrey.com's srb-dash-mon to suit me.  They should get the credit.

[Shivoreun]

Bro, can you tell me you settings about RX560 - v1.6.9 = 613H/s, my cards only 550H/s

Oтвeт нa твoй вoпpoc бyдeт нижe...
See answer for your question below...

Okay, so some of you said that the hashrate on Rx560 4g is lower on 1.7.0 vs 1.6.9 on heavy algos (said Haven) - HERE
I took some time and made some tests :

[overquoting skipped]

So as you can see i can't reproduce the huge -100hs drop you said. As a matter of fact, i can only produce + hash, not -  

Something really strange going on. Made a few benchmarks...
The card and driver:

Memory is micron MT51J256M3, BIOS is flashed with this strap in all above the 1750:
777000000000000022AA1C00EF615C41B0551016BA0D96060060060004061420EA8940AA030004C 01914292E692E3B16

Every miner version has compiled kernels by it's own. Every test duration is 6+ min. ODT reset and re-apply settings before each miner start.
And all of these tests is on haven algo. I think, for heavy will be the same config.

Parameters, used in config.txt:
i - intensity
w - worksize
t - threads
f - fragments
Core/mem clocks are 1200/2025

Results:
i29w16t2f1
v1.6.9 - 512
v1.7.0 - 499
i29w16t2f32
v1.6.9 - 610
v1.7.0 - 505
i29w16t2f16
v1.6.9 - 526
v1.7.0 - 502
i29w8t2f1
v1.6.9 - 539
v1.7.0 - 502
i29w8t2f16
v1.6.9 - 612
v1.7.0 - 505
i29w8t2f32
v1.6.9 - 608
v1.7.0 - 506
i29w8t2f64
v1.6.9 - 606
v1.7.0 - 513

Question 1: how to calculate starting intensity to tune the card? Somewhere I've found a formula, that best intensity = (shaders-64)/2, but all of my cards are producing compute errors on such values, so for each card I need to go down for 128-256 points, to get rid of errors...

Question2: how the intensity value is correlated with vmem size? For example, if RX560 2Gb card have max hashrate at intensity 16, is it possible for RX560 4Gb card to have bigger hashrate at bigger intensity? And how much is "tuning window" for 4Gb model, comparing to 2Gb? (assuming, that # of shaders and CU are the same on both cards)

Question3: is there a way to set intensity per-thread for each card? So, I mean, for example, 2 threads per 1 card, but 1st thread with i54, and the 2nd thread with i56? (maybe feature request for future ver?..)

P.S. Anyway, Doc, thank you for support and doing the right job!

[doktor83]

Bro, can you tell me you settings about RX560 - v1.6.9 = 613H/s, my cards only 550H/s

Oтвeт нa твoй вoпpoc бyдeт нижe...
See answer for your question below...

Okay, so some of you said that the hashrate on Rx560 4g is lower on 1.7.0 vs 1.6.9 on heavy algos (said Haven) - HERE
I took some time and made some tests :

[overquoting skipped]

So as you can see i can't reproduce the huge -100hs drop you said. As a matter of fact, i can only produce + hash, not - 

Something really strange going on. Made a few benchmarks...
The card and driver:

Memory is micron MT51J256M3, BIOS is flashed with this strap in all above the 1750:
777000000000000022AA1C00EF615C41B0551016BA0D96060060060004061420EA8940AA030004C 01914292E692E3B16

Every miner version has compiled kernels by it's own. Every test duration is 6+ min. ODT reset and re-apply settings before each miner start.
And all of these tests is on haven algo. I think, for heavy will be the same config.

Parameters, used in config.txt:
i - intensity
w - worksize
t - threads
f - fragments
Core/mem clocks are 1200/2025

Results:
i29w16t2f1
v1.6.9 - 512
v1.7.0 - 499
i29w16t2f32
v1.6.9 - 610
v1.7.0 - 505
i29w16t2f16
v1.6.9 - 526
v1.7.0 - 502
i29w8t2f1
v1.6.9 - 539
v1.7.0 - 502
i29w8t2f16
v1.6.9 - 612
v1.7.0 - 505
i29w8t2f32
v1.6.9 - 608
v1.7.0 - 506
i29w8t2f64
v1.6.9 - 606
v1.7.0 - 513

Question 1: how to calculate starting intensity to tune the card? Somewhere I've found a formula, that best intensity = (shaders-64)/2, but all of my cards are producing compute errors on such values, so for each card I need to go down for 128-256 points, to get rid of errors...

Question2: how the intensity value is correlated with vmem size? For example, if RX560 2Gb card have max hashrate at intensity 16, is it possible for RX560 4Gb card to have bigger hashrate at bigger intensity? And how much is "tuning window" for 4Gb model, comparing to 2Gb? (assuming, that # of shaders and CU are the same on both cards)

Question3: is there a way to set intensity per-thread for each card? So, I mean, for example, 2 threads per 1 card, but 1st thread with i54, and the 2nd thread with i56? (maybe feature request for future ver?..)

I will introduce a few modes for heavy algos in next version, so everyone can find the one that works for him best.

1. Optimal intensity can sometimes differ even for the same brand cards, so i don't really know how to calculate the best value. Unfortunately its a try-fail game until you find the best one. It's not always the highest intensity that gives the best results.

2. Intensity = number of global threads (in other miners that value is SRB intensity x 16). Now when you do scratchpad size * global threads you get the approx size of memory that will be used.
example for heavy : 56 * 16 * 4 = 3584mb.

3. There is, check the first page (--enableduplicategpuid (enables the usage of the same gpu id in gpu_conf multiple times))

[-manki-]

My Vega 64 gained 12H/s vs 1.6.9 on v8. Stable at 2134H/s, power consumption remained the same.

Nice hash rate, what’s your miner settings? Did you modify your mem clocks?

1488/1149@863mV, "intensity" : 123, "worksize" : 16, "threads" : 2, "fragments" : 16

[Bojcha]

The card and driver:

4. Also dont use 18.3.4

[Shivoreun]

I will introduce a few modes for heavy algos in next version, so everyone can find the one that works for him best.

1. Optimal intensity can sometimes differ even for the same brand cards, so i don't really know how to calculate the best value. Unfortunately its a try-fail game until you find the best one. It's not always the highest intensity that gives the best results.

2. Intensity = number of global threads (in other miners that value is SRB intensity x 16). Now when you do scratchpad size * global threads you get the approx size of memory that will be used.
example for heavy : 56 * 16 * 4 = 3584mb.

3. There is, check the first page (--enableduplicategpuid (enables the usage of the same gpu id in gpu_conf multiple times))

Hmm... Will try some more tests with these RX560.
3. Oh, sorry Now I see. Thanks ))

4. Also dont use 18.3.4

The 18.3.4 has a probles with Vega, but on other models there is no issues. I'am reverted back all rigs to 18.3.4, because, the newest drivers has a bug - some cards are detected as RX580, but they actually are RX570. And in my IMHO, 18.3.4 is more stable.

[tvukoman]

I'am reverted back all rigs to 18.3.4, because, the newest drivers has a bug - some cards are detected as RX580, but they actually are RX570. And in my IMHO, 18.3.4 is more stable.

Yes, in 18.6.1 my Sapphire Nitro+ RX570 4GB is detected as RX580.

But is that a problem?

[sky2018miner]

to the question what is it in 1.7.0
pitcairn r7 370 2 gb 1000/1400 - gpu / mem algorithm stelite v4
srb 1.6.9 intensity: 30, "worksize": 8, "threads": 2
driver 18.6.1 windows 10 pro --- 485h / s
There are pitching errors on pitcairn, lower intensity changes, lower frequencies of gpu, memory do not allow getting rid of errors, also tried different versions of the drivers, the result is approximately the same, the latest version without errors is 1.6.4 on it and stopped
in the new version 1.7.0 a catastrophic hash rate drop was added,
srb 1.7.0 intensity: 30, "worksize": 8, "threads": 2 --- 226h / s
tried fragment, aes --- minor changes in the results

On v8 algorithm I use two different miners
on rx460 - srb 1.6.9
on pitcairn r7 370 2 gb alternative for old gpu

[doktor83]

to the question what is it in 1.7.0
pitcairn r7 370 2 gb 1000/1400 - gpu / mem algorithm stelite v4
srb 1.6.9 intensity: 30, "worksize": 8, "threads": 2
driver 18.6.1 windows 10 pro --- 485h / s
There are pitching errors on pitcairn, lower intensity changes, lower frequencies of gpu, memory do not allow getting rid of errors, also tried different versions of the drivers, the result is approximately the same, the latest version without errors is 1.6.4 on it and stopped
in the new version 1.7.0 a catastrophic hash rate drop was added,
srb 1.7.0 intensity: 30, "worksize": 8, "threads": 2 --- 226h / s
tried fragment, aes --- minor changes in the results

On v8 algorithm I use two different miners
on rx460 - srb 1.6.9
on pitcairn r7 370 2 gb alternative for old gpu

the question is which algo was without errors on 1.6.4, and on which algo you have the catastrophic hash drop?
because you talk about stellite which is a v7 variant, then you say you use 2 miners for v8.

[bruslie]

hy @doktor83

Good Job about 1850 H/s on Tube ! thx a lot

only thing dont work anymore is hotkeys  H for hash ore S for stats ...

[livada]

hy @doktor83

Good Job about 1850 H/s on Tube ! thx a lot

only thing dont work anymore is hotkeys  H for hash ore S for stats ...

are you sure? that you were not a bit confused?
 give me SS your HR 5min and your option- 1850 in tube ?
H and S work fine in 1.7.0

[hbouma]

what to do if you get compute errors?

also getting compute errors, can't shake them, on vega FEs, 18.q3.1-oct1 driver, Heavy

Try lowering you memory clock by 10mhs, and see if that helps

I have a question about this as well. I've been getting the computing errors on a card as well on 1.6.9, but HWInfo doesn't show any GPU memory errors for the card (8GB RX 470 with 1900 Mhz memory). How are you detecting this as an overclocking hardware error when the card isn't able to? Or that the error is subtle enough to not yet be detected by hwinfo? I've already dropped the clock rate from 2000 to 1900 even though 2000 wasn't reporting any GPU errors for CN algos or etherhash either. So it seems odd that I have to keep dropping it further.

Thanks for all the work you've done on this miner!

Hal

[sky2018miner]

version 1.6.4 there are no errors on all algorithms that I tried to use v7, fast stelite, heavy, haven
in newer versions there are pitching errors on pitcairn
so i am using old 1.6.4
  for v8 I use two miners
  your 1.6.9 with rx 460, r9 285 and alternative for pitcairn r7 370 which is inconvenient for work

[tvukoman]

hy @doktor83

Good Job about 1850 H/s on Tube ! thx a lot

only thing dont work anymore is hotkeys  H for hash ore S for stats ...

are you sure? that you were not a bit confused?
 give me SS your HR 5min and your option- 1850 in tube ?
H and S work fine in 1.7.0

yes Livada, i think its possible.

On Vega Asus Strix 64 i have 1800 h/s on bittube2. If you have worksize 9 (old reccomendation for vega 64 and bittube2) try lower it to default 8. For me bump 100 h/s from 1699 to 1800 :-)



Edit: Up is just today quick test. After a while, h/s droped to 1770 but that is also great :-).
Settings: 1442/920 core, 1100/910 memory.
"id" : 2, "intensity" : 61, "worksize" : 8, "threads" : 2

[livada]

hy @doktor83

Good Job about 1850 H/s on Tube ! thx a lot

only thing dont work anymore is hotkeys  H for hash ore S for stats ...

are you sure? that you were not a bit confused?
 give me SS your HR 5min and your option- 1850 in tube ?
H and S work fine in 1.7.0

yes Livada, i think its possible.

On Vega Asus Strix 64 i have 1800 h/s on bittube2. If you have worksize 9 (old reccomendation for vega 64 and bittube2) try lower it to default 8. For me bump 100 h/s from 1699 to 1800 :-)

http://i65.tinypic.com/w1w944.jpg

Edit: Up is just today quick test. After a while, h/s droped to 1770 but that is also great :-).
Settings: 1442/920 core, 1100/910 memory.
"id" : 2, "intensity" : 61, "worksize" : 8, "threads" : 2

This is very nice HR.
MY rig not work with tube/hevay/haven and 1.6.1 driver and srbminer1.6.4 .1.6.9
but with 1.7.0 work.vega 56 nitro with hynix have 1600HR
https://image.prntscr.com/image/xy0brYM3QRKb-ko35LHTxg.jpg
and i use JCE for tube/haven/heavy (1700Hr)
https://image.prntscr.com/image/Gj5n234vTayImL_2_74Ptg.jpg

[sinephase]

I could use some advice! My hashrate for RX 570 4GB cards on windows 10 64 bit has dropped to about 300 H/s mining monero.

I was getting over 700 H/s on these 2 days ago. I woke up to windows restarted and reverted back to 17 Relive drivers that I used to have installed for mining a few months ago. Now all the cards are only mining at 300 and I get warnings that they are dropping to 0 at some points.
I reinstalled with a clean install of 18.6.1 drivers and still have the same issue. I tried again with 18.11.1 and only 1 card, same issue. I'm using 1x risers and have backed off of any clock changes to stock, same problems.
I have an EVGA 1000 watt GQ PSU and only installed Comodo security on this computer. Other than trying to reinstall windows, I'm not sure what else could be the issue. Any tips would be appreciated! Thanks!