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.

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.

[1675701521]

1675701521

[1675701521]

1675701521

[1675701521]

1675701521

[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!

[phuongitdl]

i am more interested in your pools file, have you defined a 'cryptonight_type' for the monero ocean pool?

Code:

{
"pools" :
[
{
"pool" : "gulf.moneroocean.stream:10064",
"wallet" : "someaddress",
"password" : "MinerSRBAuto:someemail@yahoo.com"
},
{
"pool" : "gulf.moneroocean.stream:10064",
"wallet" : "someaddress",
"password" : "MinerSRBAuto:someemail@yahoo.com"
}
]
}

Let me configure config.txt
thanks

OK, so no 'cryptonight_type' set here for MO. That's good.
Maybe you could try dropping the --forcedshutdown, and let the miner release the gpu resources before restarting, let's see is that going to help.

Same issue even without the --forcedshutdown :

Code:

[2018-11-11 14:06:36] miner_result: Sending user result to pool
[2018-11-11 14:06:36] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"3e1c2dcc-ce42-4712-b638-31a9485ce557","job_id":"wq6pDg+25VtBo7gaXQa7CebyLY0a","nonce":"8f9a5855","result":"a00c81d8d7272917d59e28d93a05495df4b64261aa242e27ff2a013895260000","algo":"cn/2"}}
[2018-11-11 14:06:36] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-11 14:06:36] miner_result: Pool accepted result 0x00002695
[2018-11-11 14:06:59] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909e4b6a0df05cfe653a87512bb81ca829c8902bc3211f297bdd0ea74ebebc645a63aa77926d500000000c4c2b3b1fd2b60fec3ebd2e0f9f991eb163dddb2842121cb1dad917c190899df0a","algo":"cn/2","variant":"2","job_id":"2OiAvtwB6oSaye9aWtZV+1XvRKEw","target":"c55d0000","id":"3e1c2dcc-ce42-4712-b638-31a9485ce557"}}
[2018-11-11 14:06:59] pool_have_job: Pool sent a new job (ID: 2OiAvtwB6oSaye9aWtZV+1XvRKEw) [normalv8]
[2018-11-11 14:07:10] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909eeb6a0df05d642cbd7021a28f075cbe5efb758164cd17afbc7f7c616947f8272adcbea6289000000001e01c1da1415b9933a5eab5aeb4df30ec126c136aafae218625dca2178b5b6a004","algo":"cn/2","variant":"2","job_id":"0Qop3NIK9e9KEv2Y6evPw9t5oEMi","target":"525e0000","id":"3e1c2dcc-ce42-4712-b638-31a9485ce557"}}
[2018-11-11 14:07:46] hashrate: GPU0: 898 H/s [BUS:6]
[2018-11-11 14:07:46] hashrate: GPU1: 2071 H/s [BUS:9]
[2018-11-11 14:07:46] hashrate: GPU2: 2033 H/s [BUS:3]
[2018-11-11 14:07:46] hashrate: Total: 5002 H/s
[2018-11-11 14:08:01] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0303bfb6a0df05ca2eca4f2aa7f0f671c084d71395005494165d48195beaac7e8056898e470e6800000000b565223ce7209f0ea3df853fd1da74048ec03ef67d8e7475225c0195001bd44d02","algo":"cn-heavy/xhv","variant":"xhv","job_id":"/AMlUbG+Z2/14tLhLr+uc35Gyp0Q","target":"525e0000","id":"3e1c2dcc-ce42-4712-b638-31a9485ce557"}}
[2018-11-11 14:08:01] algo_switch: Pool requested algo switch to [haven]
[2018-11-11 14:08:06] ocl_release: Device BUS_ID6 thread0 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID6 thread1 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID9 thread2 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID9 thread3 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID3 thread4 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID3 thread5 resources released
[2018-11-11 14:08:06] Restarting miner with haven algo
[2018-11-11 14:08:07] Miner version: 1.7.0
[2018-11-11 14:08:07] Windows version: 10.0 build 16299
[2018-11-11 14:08:07] Video driver version: 24.20.11021.1000
[2018-11-11 14:08:08] AMD Platform ID: 1
[2018-11-11 14:08:08] AMD platform FOUND
[2018-11-11 14:08:08] Found 3 AMD devices
[2018-11-11 14:08:08] CPU AES-NI: TRUE
[2018-11-11 14:08:08] GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][I: 56.0][W: 8][T: 2][F: 0][A: 0][BUS: 6]
[2018-11-11 14:08:08] GPU1: Radeon RX Vega [gfx900] [8176 MB][I: 62.0][W: 8][T: 2][F: 1][A: 0][BUS: 9]
[2018-11-11 14:08:08] GPU2: Radeon RX Vega [gfx900] [8176 MB][I: 62.0][W: 8][T: 2][F: 1][A: 0][BUS: 3]
[2018-11-11 14:08:08] ADL is enabled
[2018-11-11 14:08:08] Algo switching mode enabled
[2018-11-11 14:08:08] Algo switch minimum time : 60 seconds
[2018-11-11 14:08:08] Cryptonight Haven mode enabled
[2018-11-11 14:08:08] Startup monitor disabled!!
[2018-11-11 14:08:08] Watchdog is in GPU disable mode
[2018-11-11 14:08:08] Starting init of mining threads
[2018-11-11 14:08:08] Created OCL context
[2018-11-11 14:08:08] Using kernel 1 for DeviceID 0 (Thread 0)
[2018-11-11 14:08:08] Using AES 0 for DeviceID 0 (Thread 0)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[6] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 0 (Thread 0) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[6] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 0 (Thread 1) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[9] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 1 (Thread 2) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[9] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 1 (Thread 3) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[3] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 2 (Thread 4) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 2 (Thread 5)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 2 (Thread 5)
[2018-11-11 14:08:10] Created OCL command queue for DeviceID 2 (Thread 5)
[2018-11-11 14:08:10] Created OCL input buffer for DeviceID 2 (Thread 5)
[2018-11-11 14:08:10] Created OCL output buffer for DeviceID 2 (Thread 5)
[2018-11-11 14:08:10] Loading haven kernel for DEVICE BUS_ID[3] ...
[2018-11-11 14:08:10] ctx->Program for DeviceID 2 (Thread 5) loaded

Here is another example:

Code:

[2018-11-11 21:30:57] pool_have_job: Pool sent a new job (ID: C7rG/ktMelBnqecGjwZ4B7IHWrYI) [heavy]
[2018-11-11 21:31:07] hashrate: GPU0: 862 H/s [BUS:6]
[2018-11-11 21:31:07] hashrate: GPU1: 1824 H/s [BUS:9]
[2018-11-11 21:31:07] hashrate: GPU2: 1839 H/s [BUS:3]
[2018-11-11 21:31:07] hashrate: Total: 4525 H/s
[2018-11-11 21:31:14] miner_result: Sending user result to pool
[2018-11-11 21:31:14] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"b4174d6c-8e0a-4501-88e6-3b23be0bf002","job_id":"C7rG/ktMelBnqecGjwZ4B7IHWrYI","nonce":"bd895555","result":"a1ac490f1fa789d050cac33f9f69737e8b0f98056e95062cb08fb3abe68f0000","algo":"cn-heavy/0"}}
[2018-11-11 21:31:14] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-11 21:31:14] miner_result: Pool accepted result 0x00008FE6
[2018-11-11 21:31:22] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909f486a2df052672f4b8497a74004740f17edc88cc2060eee8b8e05ae44d8628ec4ba61f255c0000000054e994d89e12ef7a2bf0163bba167f28289d312a3cb41bc06a96450822fd7e3901","algo":"cn-heavy/0","variant":"0","job_id":"GwH9wLBXtga3biaCDI5jPglYJJjf","target":"715e0000","id":"b4174d6c-8e0a-4501-88e6-3b23be0bf002"}}
[2018-11-11 21:31:22] pool_have_job: Pool sent a new job (ID: GwH9wLBXtga3biaCDI5jPglYJJjf) [heavy]
[2018-11-11 21:31:32] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"09099787a2df05a737f3dffb57b3533acf95d6f664f9adc68e93dee936750489f1542def83d93d00000000fe9dd9dbc25cbcb81754c4c4d9a96bf16b879121dcd4d6230557a17768ecbcae02","algo":"cn-heavy/0","variant":"0","job_id":"0LgUbPmJKHDKrbAbzGAf7zLUYGyP","target":"715e0000","id":"b4174d6c-8e0a-4501-88e6-3b23be0bf002"}}
[2018-11-11 21:31:32] pool_have_job: Pool sent a new job (ID: 0LgUbPmJKHDKrbAbzGAf7zLUYGyP) [heavy]
[2018-11-11 21:32:08] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0303f485a2df0503eae94e64af7b34bf11c6026c9af59511333a7e972039caaa5055cd05b3a5c200000000551b1e9077a8e4e52ced040f69bcb5f0abab07f336942460114aaabfcc229afe03","algo":"cn-heavy/xhv","variant":"xhv","job_id":"9mrvdpzan44ClfsiWDkxy2gNwsyx","target":"715e0000","id":"b4174d6c-8e0a-4501-88e6-3b23be0bf002"}}
[2018-11-11 21:32:30] algo_switch: Pool requested algo switch to [haven]
[2018-11-11 21:32:34] ocl_release: Device BUS_ID6 thread0 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID6 thread1 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID9 thread2 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID9 thread3 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID3 thread4 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID3 thread5 resources released
[2018-11-11 21:32:34] Restarting miner with haven algo
[2018-11-11 21:32:35] Miner version: 1.7.0
[2018-11-11 21:32:35] Windows version: 10.0 build 16299
[2018-11-11 21:32:35] Video driver version: 24.20.11021.1000
[2018-11-11 21:32:37] AMD Platform ID: 1
[2018-11-11 21:32:37] AMD platform FOUND
[2018-11-11 21:32:37] Found 3 AMD devices
[2018-11-11 21:32:37] CPU AES-NI: TRUE
[2018-11-11 21:32:37] GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][I: 56.0][W: 8][T: 2][F: 0][A: 0][BUS: 6]
[2018-11-11 21:32:37] GPU1: Radeon RX Vega [gfx900] [8176 MB][I: 62.0][W: 8][T: 2][F: 1][A: 0][BUS: 9]
[2018-11-11 21:32:37] GPU2: Radeon RX Vega [gfx900] [8176 MB][I: 62.0][W: 8][T: 2][F: 1][A: 0][BUS: 3]
[2018-11-11 21:32:37] ADL is enabled
[2018-11-11 21:32:37] Algo switching mode enabled
[2018-11-11 21:32:37] Algo switch minimum time : 60 seconds
[2018-11-11 21:32:37] Cryptonight Haven mode enabled
[2018-11-11 21:32:37] Startup monitor disabled!!
[2018-11-11 21:32:37] Watchdog is in GPU disable mode
[2018-11-11 21:32:37] Starting init of mining threads
[2018-11-11 21:32:37] Created OCL context
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Loading haven kernel for DEVICE BUS_ID[6] ...
[2018-11-11 21:32:37] ctx->Program for DeviceID 0 (Thread 0) loaded
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Created OCL command queue for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Created OCL input buffer for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Created OCL output buffer for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Loading haven kernel for DEVICE BUS_ID[6] ...
[2018-11-11 21:32:37] ctx->Program for DeviceID 0 (Thread 1) loaded
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Created OCL command queue for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Created OCL input buffer for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Created OCL output buffer for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Loading haven kernel for DEVICE BUS_ID[9] ...
[2018-11-11 21:32:37] ctx->Program for DeviceID 1 (Thread 2) loaded
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Created OCL command queue for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Created OCL input buffer for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Created OCL output buffer for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Loading haven kernel for DEVICE BUS_ID[9] ...
[2018-11-11 21:32:37] ctx->Program for DeviceID 1 (Thread 3) loaded
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 2 (Thread 4)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 2 (Thread 4)
[2018-11-11 21:32:38] Created OCL command queue for DeviceID 2 (Thread 4)
[2018-11-11 21:32:38] Created OCL input buffer for DeviceID 2 (Thread 4)
[2018-11-11 21:32:38] Created OCL output buffer for DeviceID 2 (Thread 4)

The miner just randomly seems to crash and the miner window gets closed. This seems to be some code exception that closes the miner.
It seems to only happen immediately after an algo switch. Would you be so kind to check the code again to see what could possibly close the miner abruptly when performing algo switch? Maybe some kind of race condition? I am also forced to use --resetmineronalgoswitch since i have some vega`s.



 

[phuongitdl]

Now testing:

8x RX580 8GB
cclock 1250, mclock 2150, cvddc 910, mvddc 910
drivers 18.3.2
miner 1.7.0

algo Haven

intensity 58
worksize 16
thread 2
fragments 8

Hashrate 1152


before on 1.6.7 with intensity 58 ...  hashrate 1120

looking stable for now

Let me configure config.txt

[charles2k]

Any experience with R9 Fury cards? What is the best setting for them? (V8 and heavy) ?

[djim123]

V1.6.9 vs V1.7.0 V8 comparison on my 7x Vega 56's


Vega #1 1891 1910 + 19 H/s
Vega #2 1871 1893 + 22 H/s
Vega #3 1884 1904 + 20 H/s
Vega #4 1852 1869 + 17 H/s
Vega #5 1844 1865 + 21 H/s
Vega #6 1855 1874 + 19 H/s
Vega #7 1840 1863 + 23 H/s
---------------------------------
Totals   13037 13178 +141 H/s or about +20 H/s for each Vega 56


Thx doc !~!

Can You share ,settings and configuration,please.

All settings for SRBMiner are the same for each Vega 56 and done in the V8 config file:

intensity: 112
worksize: 16
threads: 2

Vega 56's #1, #2 and #3 are in one system that has Radeon Adrenalin Edition 18.8.1 installed which actually produces high hash rates than the recommended Radeon Adrenalin Edition 18.5.1 installed in the system with Vega 56's #4, #5, #6 and #7.

These two systems are on a Biostar H81A motherboard and are using a single HP 1200 Watt Server Power Supply (87% Efficient) with a 17x 6-pin Breakout board. The motherboard is powered by an 180 watt Pico PSU that gets it's 12 volt input from a 6-pin connector on the breakout board. I like my systems only running on a single power supply.


System one is hashing on an  i3-4340 at 73 H/s and system two is hashing on an  i5-4570 at 195 H/s.

All power measurements are done at the wall with a Power Usage Monitor. That way the entire system is measured (motherboard, processor, memory, ssd) and the Vega 56's and it is the real power not the incomplete ones that only look at the software measurements like HWINFO which does not consider the inefficiencies of power supply and internal power conversion circuits or the rest of the system.

Realize that V8 is much more power hungry than V7 was.

I do not use soft power play tables as I have found that V7 and V8 basically run between P6 & P7 states on the core and P3 on memory. The Vega 56's are reference designs of various vendors with stock BIOS.

So my Wattman settings for six of the Vega 56's are:

Core:
Min P6 1212 MHz @ 905 mv
Max P7 1452 MHz @ 925 mv

Memory:
Min/Max P3 935 MHz @ 900 mv

Fans:
Min: 2700
Target: 4900

Temperature:
Max: 75
Target: 65

I do have one problematic Vega 56 that I have to run at:

Core:
Min P6 1212 MHz @ 960 mv
Max P7 1452 MHz @ 985 mv

Memory:
Min/Max P3 900 MHz @ 950 mv

With all that out of the way here are the final numbers:

System one 3x Vega 56's:

Vega #1 1911 H/s
Vega #2 1893 H/s
Vega #3 1904 H/s
--------------------
Total  Vega's 5708 H/s
i3-4340 adds 73 H/s
-------------------------
System Total:  5781 H/s

Total Power at the wall: 675 watts


System two 4x Vega 56's:

Vega #4 1869 H/s
Vega #5 1865 H/s
Vega #6 1874 H/s
Vega #7 1863 H/s
--------------------
Total  Vega's 7471 H/s
i5-4570 adds 195 H/s
-------------------------
System Total:  7666 H/s

Total Power at the wall: 898 watts

Thank You very much ,Sir

I forgot this setting ( I have since edited my original post)

EDIT: I forgot this setting. I needed to do this +10 as a few of the Vega 56's clocks were only in the high 1200's MHz and not the 1350+ MHz they should be and were flicking between P6 and P7 state.. It turned out those were being power limited. So be sure to do this setting also.
Power Limit +10

Thank You.