[ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More

[keksik]

hello, im having trouble mining when integrated vga is on. i dont have these problems when using SRB. is there any parameter to use, to skip initiating integrated vga?
also tried to test gpu one by one via id parameter. and what is stable in SRB is not in this miner. despite for rx 580 i used 7+7 to avoid hangs, it hanged anyway.

Hi keksik,

What kind of troubles are you having when mining while integrated vga is on?  Is the miner failing to start?  Can you post the output of the miner when this happens?

When you say that your rx 580 hangs, do you mean that the miner is reporting 0h/s hashrate, or is your entire rig hanging/becoming unresponsive?

it reports 0h/s, however i think i found the problem, it was due to 8+8 not working for rx 580 with elpida.
7+7 = 952
8+7 = 947
7+8 = 974
8+8 = 0

so i think ill have to test urther one by one and will see.. i was mistaken when i thought it is caused by integrated gpu. let me do more test.
p.s. thans for quick reply,appreciate

[1715027357]

1715027357

[1715027357]

1715027357

[1715027357]

1715027357

[peterboy1]

these guys with rx 570/580 hashing below 1kh/s i think are doing it wrong. check your straps and oc.

all of my rx 570 hashes above atleast 1kh be it 4gb or 8gb. the only problem i have is micron, which i think is the worst in cn variants.

[kerney666]

these guys with rx 570/580 hashing below 1kh/s i think are doing it wrong. check your straps and oc.

all of my rx 570 hashes above atleast 1kh be it 4gb or 8gb. the only problem i have is micron, which i think is the worst in cn variants.

Agree, matches what we found as well. Haven't really found any card stuck below 1kh/s, except for Micron mem where we've been stuck around 860 h/s on some cards whatever we try for straps and clocks. Samsung by far the easiest, Hynix often also just a copy of lower-to-higher straps. And, I'm really not that good with straps, I should add.

[keksik]

these guys with rx 570/580 hashing below 1kh/s i think are doing it wrong. check your straps and oc.

all of my rx 570 hashes above atleast 1kh be it 4gb or 8gb. the only problem i have is micron, which i think is the worst in cn variants.

Agree, matches what we found as well. Haven't really found any card stuck below 1kh/s, except for Micron mem where we've been stuck around 860 h/s on some cards whatever we try for straps and clocks. Samsung by far the easiest, Hynix often also just a copy of lower-to-higher straps. And, I'm really not that good with straps, I should add.

guys, i used srbpolaris v3.5 with pimp my straps function, also tried pbe 1.7.1 with one click timings function.
i have the newest win 10/amd driver. in bios i changed only timings and im getting still lower than 1kh/s. mostly 900-990 between and doesnt matter if 4gb/8gb or 570/580. for example gigabyte gaming cards are hashing lower, because they have low PL. they cant handle 900mV for core, 875 is maximum and doesnt matter if samsung or hynix memory.
for example gigabyte aourus rx 570 4gb can handle 925-950 and is hashing around 980h/s.
if u cna share your straps for hynix, samsung and elpida, it will be great, so we can compare.

i dont know how u guys test and set things, i do following steps:
save bios with atiflash/gpuz tool
edit bios in pbe 1.7.1/srbpolaris v3.5 and click pump timings
save bios and load back to card
update win 10, DDU, reboot, newest amd drivers, atidag patcher, reboot, overdriveN tool
i started card by card, starting 1150/850 // 2000/850 and going up or down.
some elpidas are able to go only 1850-1925,some 2050. also said for core..cards like gaming only 875mV so maximum for them is 1175-1200 on my side.

[tvukoman]

these guys with rx 570/580 hashing below 1kh/s i think are doing it wrong. check your straps and oc.

all of my rx 570 hashes above atleast 1kh be it 4gb or 8gb. the only problem i have is micron, which i think is the worst in cn variants.

Agree, matches what we found as well. Haven't really found any card stuck below 1kh/s, except for Micron mem where we've been stuck around 860 h/s on some cards whatever we try for straps and clocks. Samsung by far the easiest, Hynix often also just a copy of lower-to-higher straps. And, I'm really not that good with straps, I should add.

Great job TeamRed!

Read every post here, testing rig for about 8 hours without crash. Now trying to fine tune.

Here is mixed rig (1 x rx570 4GB Elpida, 2 x Vega 56 referent + 1 Vega 64 Asus Strix)
Vega 56 hashing about 2000 H/s, Vega 64 2240 H/s). Vega 56 have low clock and memory 1408/1088 because on SRB is overheating and crashing on more clocks. Vega 64 is on 1520/1100.

Funny thing about RX570 is that hashrate of RX570 somehow depends of configuration on Vega cards.

When i first start miner (without --cn_config) RX570 Nitro + (Elpida) hash 920 H/s with timings 1200/1980.

Than I experiment and put on RX570 7+7 (default was 8+7) and lower clock and memory to 1225/1940 (as user Dragonmike recommended). Playing with OverdriveNtool when hashing, been able to get 942 H/s with 1200/1920 but i think that time i put Vega 56 to 15+15.

When i restarted rig, RX 570 hash just 880 H/s? Try appy OverdriveNtool with same clocks as before 1200/1920 but still 880 H/s. Than i apply 1250/1980 and still 880 H/s. mV for clock and memory 900 mV.

What am i missing and is it possible and where to delete kernel files to make automatic initialization of the cards again?

[kerney666]

these guys with rx 570/580 hashing below 1kh/s i think are doing it wrong. check your straps and oc.

all of my rx 570 hashes above atleast 1kh be it 4gb or 8gb. the only problem i have is micron, which i think is the worst in cn variants.

Agree, matches what we found as well. Haven't really found any card stuck below 1kh/s, except for Micron mem where we've been stuck around 860 h/s on some cards whatever we try for straps and clocks. Samsung by far the easiest, Hynix often also just a copy of lower-to-higher straps. And, I'm really not that good with straps, I should add.

guys, i used srbpolaris v3.5 with pimp my straps function, also tried pbe 1.7.1 with one click timings function.
i have the newest win 10/amd driver. in bios i changed only timings and im getting still lower than 1kh/s. mostly 900-990 between and doesnt matter if 4gb/8gb or 570/580. for example gigabyte gaming cards are hashing lower, because they have low PL. they cant handle 900mV for core, 875 is maximum and doesnt matter if samsung or hynix memory.
for example gigabyte aourus rx 570 4gb can handle 925-950 and is hashing around 980h/s.
if u cna share your straps for hynix, samsung and elpida, it will be great, so we can compare.

i dont know how u guys test and set things, i do following steps:
save bios with atiflash/gpuz tool
edit bios in pbe 1.7.1/srbpolaris v3.5 and click pump timings
save bios and load back to card
update win 10, DDU, reboot, newest amd drivers, atidag patcher, reboot, overdriveN tool
i started card by card, starting 1150/850 // 2000/850 and going up or down.
some elpidas are able to go only 1850-1925,some 2050. also said for core..cards like gaming only 875mV so maximum for them is 1175-1200 on my side.

Hmm could be difficult to get more unless core clk is increased then. The “big thing” with this miner, imho, is the ability to use a higher core clk without power draw increasing in an unpleasant way. We still have some swings to address, but the power draw over time is good. In a way, it’s built assuming you can at least go to 1230 cclk on a polaris, and that’s how it’s been trimmed and tested.

On the gigabyte 570 that can take a higher mV, what’s the behavior at a higher clock? On eg some 580s, we’ve seen efficiency improvements going all the way to 1300+ cclk, hashrate going +10% from 1000 to 1100 h/s with a +8% in power draw. This was a very well tuned farm testing though, I don’t have the specifics. More mentioning it as an example where higher clk is preferred to boost efficiency.

[kerney666]

these guys with rx 570/580 hashing below 1kh/s i think are doing it wrong. check your straps and oc.

all of my rx 570 hashes above atleast 1kh be it 4gb or 8gb. the only problem i have is micron, which i think is the worst in cn variants.

Agree, matches what we found as well. Haven't really found any card stuck below 1kh/s, except for Micron mem where we've been stuck around 860 h/s on some cards whatever we try for straps and clocks. Samsung by far the easiest, Hynix often also just a copy of lower-to-higher straps. And, I'm really not that good with straps, I should add.

Great job TeamRed!

Read every post here, testing rig for about 8 hours without crash. Now trying to fine tune.

Here is mixed rig (1 x rx570 4GB Elpida, 2 x Vega 56 referent + 1 Vega 64 Asus Strix)
Vega 56 hashing about 2000 H/s, Vega 64 2240 H/s). Vega 56 have low clock and memory 1408/1088 because on SRB is overheating and crashing on more clocks. Vega 64 is on 1520/1100.

Funny thing about RX570 is that hashrate of RX570 somehow depends of configuration on Vega cards.

When i first start miner (without --cn_config) RX570 Nitro + (Elpida) hash 920 H/s with timings 1200/1980.

Than I experiment and put on RX570 7+7 (default was 8+7) and lower clock and memory to 1225/1940 (as user Dragonmike recommended). Playing with OverdriveNtool when hashing, been able to get 942 H/s with 1200/1920 but i think that time i put Vega 56 to 15+15.

When i restarted rig, RX 570 hash just 880 H/s? Try appy OverdriveNtool with same clocks as before 1200/1920 but still 880 H/s. Than i apply 1250/1980 and still 880 H/s. mV for clock and memory 900 mV.

What am i missing and is it possible and where to delete kernel files to make automatic initialization of the cards again?

That sounds a little weird. I don’t know if you restarted the miner or rebooted the rig in between runs? One issue we have (which I’m a little ashamed of tbh) is our unclean shutdown. It has led to me losing perf between restarts at times. Can you reproduce your test, i.e. whenever you run the 570 only after a clean reboot you hit ~940 h/s, but 570+Vegas after a clean reboot and it’s lower for the 570?

[keksik]

these guys with rx 570/580 hashing below 1kh/s i think are doing it wrong. check your straps and oc.

all of my rx 570 hashes above atleast 1kh be it 4gb or 8gb. the only problem i have is micron, which i think is the worst in cn variants.

Agree, matches what we found as well. Haven't really found any card stuck below 1kh/s, except for Micron mem where we've been stuck around 860 h/s on some cards whatever we try for straps and clocks. Samsung by far the easiest, Hynix often also just a copy of lower-to-higher straps. And, I'm really not that good with straps, I should add.

guys, i used srbpolaris v3.5 with pimp my straps function, also tried pbe 1.7.1 with one click timings function.
i have the newest win 10/amd driver. in bios i changed only timings and im getting still lower than 1kh/s. mostly 900-990 between and doesnt matter if 4gb/8gb or 570/580. for example gigabyte gaming cards are hashing lower, because they have low PL. they cant handle 900mV for core, 875 is maximum and doesnt matter if samsung or hynix memory.
for example gigabyte aourus rx 570 4gb can handle 925-950 and is hashing around 980h/s.
if u cna share your straps for hynix, samsung and elpida, it will be great, so we can compare.

i dont know how u guys test and set things, i do following steps:
save bios with atiflash/gpuz tool
edit bios in pbe 1.7.1/srbpolaris v3.5 and click pump timings
save bios and load back to card
update win 10, DDU, reboot, newest amd drivers, atidag patcher, reboot, overdriveN tool
i started card by card, starting 1150/850 // 2000/850 and going up or down.
some elpidas are able to go only 1850-1925,some 2050. also said for core..cards like gaming only 875mV so maximum for them is 1175-1200 on my side.

Hmm could be difficult to get more unless core clk is increased then. The “big thing” with this miner, imho, is the ability to use a higher core clk without power draw increasing in an unpleasant way. We still have some swings to address, but the power draw over time is good. In a way, it’s built assuming you can at least go to 1230 cclk on a polaris, and that’s how it’s been trimmed and tested.

On the gigabyte 570 that can take a higher mV, what’s the behavior at a higher clock? On eg some 580s, we’ve seen efficiency improvements going all the way to 1300+ cclk, hashrate going +10% from 1000 to 1100 h/s with a +8% in power draw. This was a very well tuned farm testing though, I don’t have the specifics. More mentioning it as an example where higher clk is preferred to boost efficiency.

in general my rx 570 are hashing all mnore than 900-1000, im stuck with rx 580 8gb, they probably use bad timings, lets say less agressive via pbe/srb editor... so ill try use timing from 4GB version and will see how it goes. because geeting 850h/s for rx 580 8gb at 1280/2150 is nonsense


this is for example my rig with 6x gigabyte rx 580 aorus 4GB and im really satisfied:
Hynix - 1200/900mV/1975 - 975
Elpida - 1250/900mV/2000 - 980
Hynix - 1250/925mV/2000 - 1015
Hynix - 1250/925mV/2000 - 980
Hynix - 1250/925mV/2000 - 1014
Hynix - 1225/925mV/2000 - 1002

all is 5966h/s

[heavyarms1912]

Micron 8gbs can do 1k+.
Elipdas 4gb can do 1k+
Hynix 4gb AJR can do 1k+

All of these at 1250 core or lower.

[netmebtc]

6x Vega64 (2017.10.30manufactr)  Core 1408/900    mem 1045/900  powertarget -20%

16+14 or 15+15 only get 7.25kh   It seems too low .

My 6xvega56(flash to 64bios) 16+14 get 11.5k  (core:1337/900  mem：1025/900  power taget -20%)


15+15,15+15,15+15,15+15
          Team Red Miner version 0.3.6
[2018-11-05 11:21:49] Auto-detected AMD OpenCL platform 1
[2018-11-05 11:21:50] Initializing GPU 0.
[2018-11-05 11:21:54] Pool cal.cnpool.cc login succeeded.
[2018-11-05 11:21:54] Pool cal.cnpool.cc received new job. (job_id: 350770445476649)
[2018-11-05 11:21:54] Pool cal.cnpool.cc set difficulty to 150000
[2018-11-05 11:21:55] Dev pool connected and ready.
[2018-11-05 11:21:55] Initializing GPU 1.
[2018-11-05 11:21:57] Initializing GPU 2.
[2018-11-05 11:21:59] Initializing GPU 3.
[2018-11-05 11:22:03] Initializing GPU 4.
[2018-11-05 11:22:05] Initializing GPU 5.
[2018-11-05 11:22:07] Successfully initialized GPU 0: Vega with 64 CU (PCIe 19:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 2: Vega with 64 CU (PCIe 13:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 3: Vega with 64 CU (PCIe 16:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 4: Vega with 64 CU (PCIe 09:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 5: Vega with 64 CU (PCIe 06:00.0) (CN 15+15)
[2018-11-05 11:22:24] Stats GPU 0 - cnv8: 746.1 h/s, avg 1.206kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 1 - cnv8: 738.8 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 2 - cnv8: 743.5 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 3 - cnv8: 729.5 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 4 - cnv8: 735.3 h/s, avg 1.211kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 5 - cnv8: 728.2 h/s, avg 1.213kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats Total - cnv8: 4.421kh/s, avg 7.251kh/s, pool   0.0 h/s
[2018-11-05 11:22:32] Pool cal.cnpool.cc received new job. (job_id: 573976627372422)
[2018-11-05 11:22:33] Pool cal.cnpool.cc share accepted. (GPU1) (1/1/0)
[2018-11-05 11:22:36] Pool cal.cnpool.cc received new job. (job_id: 175747342969107)
[2018-11-05 11:22:47] Pool cal.cnpool.cc share accepted. (GPU2) (2/2/0)
[2018-11-05 11:22:54] Stats GPU 0 - cnv8: 1.388kh/s, avg 1.334kh/s, pool   0.0 h/s 0/0

[joseph32]

Increase your Memory. Vega 64 can easy go 2200 up to 2400+ (Liquid).

[kerney666]

6x Vega64 (2017.10.30manufactr)  Core 1408/900    mem 1045/900  powertarget -20%

16+14 or 15+15 only get 7.25kh   It seems too low .

My 6xvega56(flash to 64bios) 16+14 get 11.5k  (core:1337/900  mem：1025/900  power taget -20%)


15+15,15+15,15+15,15+15
          Team Red Miner version 0.3.6
[2018-11-05 11:21:49] Auto-detected AMD OpenCL platform 1
[2018-11-05 11:21:50] Initializing GPU 0.
[2018-11-05 11:21:54] Pool cal.cnpool.cc login succeeded.
[2018-11-05 11:21:54] Pool cal.cnpool.cc received new job. (job_id: 350770445476649)
[2018-11-05 11:21:54] Pool cal.cnpool.cc set difficulty to 150000
[2018-11-05 11:21:55] Dev pool connected and ready.
[2018-11-05 11:21:55] Initializing GPU 1.
[2018-11-05 11:21:57] Initializing GPU 2.
[2018-11-05 11:21:59] Initializing GPU 3.
[2018-11-05 11:22:03] Initializing GPU 4.
[2018-11-05 11:22:05] Initializing GPU 5.
[2018-11-05 11:22:07] Successfully initialized GPU 0: Vega with 64 CU (PCIe 19:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 2: Vega with 64 CU (PCIe 13:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 3: Vega with 64 CU (PCIe 16:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 4: Vega with 64 CU (PCIe 09:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 5: Vega with 64 CU (PCIe 06:00.0) (CN 15+15)
[2018-11-05 11:22:24] Stats GPU 0 - cnv8: 746.1 h/s, avg 1.206kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 1 - cnv8: 738.8 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 2 - cnv8: 743.5 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 3 - cnv8: 729.5 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 4 - cnv8: 735.3 h/s, avg 1.211kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 5 - cnv8: 728.2 h/s, avg 1.213kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats Total - cnv8: 4.421kh/s, avg 7.251kh/s, pool   0.0 h/s
[2018-11-05 11:22:32] Pool cal.cnpool.cc received new job. (job_id: 573976627372422)
[2018-11-05 11:22:33] Pool cal.cnpool.cc share accepted. (GPU1) (1/1/0)
[2018-11-05 11:22:36] Pool cal.cnpool.cc received new job. (job_id: 175747342969107)
[2018-11-05 11:22:47] Pool cal.cnpool.cc share accepted. (GPU2) (2/2/0)
[2018-11-05 11:22:54] Stats GPU 0 - cnv8: 1.388kh/s, avg 1.334kh/s, pool   0.0 h/s 0/0

This is way too low. The 6 x Vega56 flashed look better. The Vega 64 rig should be at 12+ kh/s even at your rather low clocks. A few questions:

1) What OS and driver is this?
2) Have you been mining CNv8 with some other miner on the same rig?
3) A mistake of ours was to not include the "standard" environment vars you should have configured in our example .bat file. If not, can you add these to your .bat file or make sure they are set in your shell?


set GPU_MAX_HEAP_SIZE=100
set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_USE_SYNC_OBJECTS=1

[lebuawu2]

6x Vega64 (2017.10.30manufactr)  Core 1408/900    mem 1045/900  powertarget -20%

16+14 or 15+15 only get 7.25kh   It seems too low .

My 6xvega56(flash to 64bios) 16+14 get 11.5k  (core:1337/900  mem：1025/900  power taget -20%)


15+15,15+15,15+15,15+15
          Team Red Miner version 0.3.6
[2018-11-05 11:21:49] Auto-detected AMD OpenCL platform 1
[2018-11-05 11:21:50] Initializing GPU 0.
[2018-11-05 11:21:54] Pool cal.cnpool.cc login succeeded.
[2018-11-05 11:21:54] Pool cal.cnpool.cc received new job. (job_id: 350770445476649)
[2018-11-05 11:21:54] Pool cal.cnpool.cc set difficulty to 150000
[2018-11-05 11:21:55] Dev pool connected and ready.
[2018-11-05 11:21:55] Initializing GPU 1.
[2018-11-05 11:21:57] Initializing GPU 2.
[2018-11-05 11:21:59] Initializing GPU 3.
[2018-11-05 11:22:03] Initializing GPU 4.
[2018-11-05 11:22:05] Initializing GPU 5.
[2018-11-05 11:22:07] Successfully initialized GPU 0: Vega with 64 CU (PCIe 19:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 2: Vega with 64 CU (PCIe 13:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 3: Vega with 64 CU (PCIe 16:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 4: Vega with 64 CU (PCIe 09:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 5: Vega with 64 CU (PCIe 06:00.0) (CN 15+15)
[2018-11-05 11:22:24] Stats GPU 0 - cnv8: 746.1 h/s, avg 1.206kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 1 - cnv8: 738.8 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 2 - cnv8: 743.5 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 3 - cnv8: 729.5 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 4 - cnv8: 735.3 h/s, avg 1.211kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 5 - cnv8: 728.2 h/s, avg 1.213kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats Total - cnv8: 4.421kh/s, avg 7.251kh/s, pool   0.0 h/s
[2018-11-05 11:22:32] Pool cal.cnpool.cc received new job. (job_id: 573976627372422)
[2018-11-05 11:22:33] Pool cal.cnpool.cc share accepted. (GPU1) (1/1/0)
[2018-11-05 11:22:36] Pool cal.cnpool.cc received new job. (job_id: 175747342969107)
[2018-11-05 11:22:47] Pool cal.cnpool.cc share accepted. (GPU2) (2/2/0)
[2018-11-05 11:22:54] Stats GPU 0 - cnv8: 1.388kh/s, avg 1.334kh/s, pool   0.0 h/s 0/0

maybe you use blockchain beta driver and forgot to disabled and enabled GPU?

[lebuawu2]

also I am having this error

Code:

[2018-11-04 16:17:05] Pool xmr-eu1.nanopool.org failed to parse server rpc: {"id":4,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}

anything I can do about it?

Just so I understand, is the miner still mining ok with this error message, or it doesn't work at all? As long as its for shares only, we will lose track of a few shares, and our poolside hashrate in the miner will be a little lower, but everything is otherwise working ok.

I got that error also when mining to nanopool, after that it will reconnect to pool again. so I guess effective pool hash rate will go down because every time got that error it will reconnect to pool again.

[netmebtc]

Rig
===================================
CPU: Intel(R) Celeron(R) CPU G3930 @ 2.90GHz   core:   2 
RAM: 4G DDR3
Virtual mem: 50 GB
OS:  Windows 10 professional   1709 16299.15
6xVega64
http://gpuz.techpowerup.com/18/11/05/evz.png
vega driver 18.5.1
========================================

set this PP_PhmSoftPowerPlayTable reg for each vega
========================
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001]
"PP_PhmSoftPowerPlayTable"=hex:B6,02,08,01,00,5C,00,E1,06,00,00,EE,2B,00,00,1B,\
  00,48,00,00,00,80,A9,03,00,F0,49,02,00,8E,00,08,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,02,01,5C,00,4F,02,46,02,94,00,9E,01,BE,00,28,01,7A,00,8C,00,\
  BC,01,00,00,00,00,72,02,00,00,90,00,A8,02,6D,01,43,01,97,01,F0,49,02,00,71,\
  02,02,02,00,00,00,00,00,00,08,00,00,00,00,00,00,00,05,00,07,00,03,00,05,00,\
  00,00,00,00,00,00,01,08,84,03,84,03,84,03,84,03,84,03,84,03,84,03,84,03,01,\
  01,84,03,01,01,84,03,00,08,60,EA,00,00,00,40,19,01,00,01,80,38,01,00,02,DC,\
  4A,01,00,03,90,5F,01,00,04,00,77,01,00,05,90,91,01,00,06,6C,B0,01,00,07,01,\
  08,D0,4C,01,00,00,00,80,00,00,00,00,00,00,1C,83,01,00,01,00,00,00,00,00,00,\
  00,00,70,A7,01,00,02,00,00,00,00,00,00,00,00,88,BC,01,00,03,00,00,00,00,00,\
  00,00,00,38,C1,01,00,04,00,00,00,00,00,00,00,00,88,D5,01,00,05,00,00,00,00,\
  01,00,00,00,70,D9,01,00,06,00,00,00,00,01,00,00,00,00,26,02,00,07,00,00,00,\
  00,01,00,00,00,00,05,60,EA,00,00,00,40,19,01,00,00,80,38,01,00,00,DC,4A,01,\
  00,00,90,5F,01,00,00,00,08,28,6E,00,00,00,2C,C9,00,00,01,F8,0B,01,00,02,80,\
  38,01,00,03,90,5F,01,00,04,F4,91,01,00,05,D0,B0,01,00,06,C0,D4,01,00,07,00,\
  08,6C,39,00,00,00,24,5E,00,00,01,FC,85,00,00,02,AC,BC,00,00,03,34,D0,00,00,\
  04,68,6E,01,00,05,08,97,01,00,06,EC,A3,01,00,07,00,01,68,3C,01,00,00,01,04,\
  3C,41,00,00,00,00,00,50,C3,00,00,00,00,00,80,38,01,00,02,00,00,B0,AD,01,00,\
  04,00,00,01,08,00,98,85,00,00,40,B5,00,00,60,EA,00,00,50,C3,00,00,01,80,BB,\
  00,00,60,EA,00,00,94,0B,01,00,50,C3,00,00,02,00,E1,00,00,94,0B,01,00,40,19,\
  01,00,50,C3,00,00,03,78,FF,00,00,40,19,01,00,88,26,01,00,50,C3,00,00,04,40,\
  19,01,00,80,38,01,00,80,38,01,00,50,C3,00,00,05,80,38,01,00,DC,4A,01,00,DC,\
  4A,01,00,50,C3,00,00,06,00,77,01,00,00,77,01,00,90,5F,01,00,50,C3,00,00,07,\
  90,91,01,00,90,91,01,00,00,77,01,00,50,C3,00,00,01,18,00,00,00,00,00,00,00,\
  0B,E4,12,60,09,60,09,4B,00,0A,00,54,03,90,01,90,01,90,01,90,01,90,01,90,01,\
  90,01,00,00,00,00,00,02,04,31,07,DC,00,DC,00,DC,00,90,01,00,00,59,00,69,00,\
  4A,00,4A,00,5F,00,73,00,73,00,64,00,40,00,90,92,97,60,96,00,90,55,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,02,D4,30,00,00,02,10,60,EA,00,\
  00,02,10
========================

OverdriveNtool set for each Vega64
==============================
GPU_P0=852;900
GPU_P1=991;900
GPU_P2=1084;900
GPU_P3=1138;900
GPU_P4=1150;900
GPU_P5=1202;900
GPU_P6=1212;900
GPU_P7=1408;900
Mem_P0=167;900
Mem_P1=500;900
Mem_P2=800;900
Mem_P3=1080;900
Fan_Min=2388
Fan_Max=4900
Fan_Target=65
Fan_Acoustic=2400
Power_Temp=80
Power_Target=-20
==========================

start.bat
=======================================
set GPU_MAX_HEAP_SIZE=100
set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_USE_SYNC_OBJECTS=1

teamredminer.exe -a cnv8 -o stratum+tcp://cal.cnpool.cc:32866 -u cberxts5ZZ8DQ.....................peB4osNpfD4bb92XjUcP1W1Tc5aFvs1XProMv71xM2QsC kT8hntKJXVaX.150000  -p %computername%  -d 0,1,2,3,4,5 --cn_config 15+15,15+15,15+15,15+15,15+15,15+15
==========================================

run SRBminer 1.6.9 with intensity=61
============================================
2018-11-05 14:09:59] Main pool: cal.cnpool.cc:32866
[2018-11-05 14:09:59] Connected to cal.cnpool.cc:32866
[2018-11-05 14:09:59] User logged in
[2018-11-05 14:09:59] Pool difficulty: 150000
[2018-11-05 14:09:59] Pool sent a new job (ID: 821908557589538)
[2018-11-05 14:10:10] GPU0 :    0 H/s [T: 50c, RPM: 3080, CC: 1408 MHz, MC: 1080 MHz][BUS:19]
[2018-11-05 14:10:10] GPU1 :    0 H/s [T: 49c, RPM: 3113, CC: 1408 MHz, MC: 1080 MHz][BUS:3]
[2018-11-05 14:10:10] GPU2 :    0 H/s [T: 51c, RPM: 3131, CC: 1408 MHz, MC: 1080 MHz][BUS:13]
[2018-11-05 14:10:10] GPU3 :    0 H/s [T: 48c, RPM: 3155, CC: 1408 MHz, MC: 1080 MHz][BUS:16]
[2018-11-05 14:10:10] GPU4 :    0 H/s [T: 48c, RPM: 3129, CC: 1408 MHz, MC: 1080 MHz][BUS:9]
[2018-11-05 14:10:10] GPU5 :    0 H/s [T: 48c, RPM: 3123, CC: 1408 MHz, MC: 1080 MHz][BUS:6]
[2018-11-05 14:10:10] Total:    0 H/s
[2018-11-05 14:10:21] GPU0 :    1316 H/s [T: 55c, RPM: 3464, CC: 1408 MHz, MC: 1080 MHz][BUS:19]
[2018-11-05 14:10:21] GPU1 :    1317 H/s [T: 53c, RPM: 3454, CC: 1408 MHz, MC: 1080 MHz][BUS:3]
[2018-11-05 14:10:21] GPU2 :    1318 H/s [T: 54c, RPM: 3515, CC: 1408 MHz, MC: 1080 MHz][BUS:13]
[2018-11-05 14:10:21] GPU3 :    1311 H/s [T: 52c, RPM: 3507, CC: 1408 MHz, MC: 1080 MHz][BUS:16]
[2018-11-05 14:10:21] GPU4 :    1317 H/s [T: 53c, RPM: 3461, CC: 1408 MHz, MC: 1080 MHz][BUS:9]
[2018-11-05 14:10:21] GPU5 :    1317 H/s [T: 53c, RPM: 3471, CC: 1408 MHz, MC: 1080 MHz][BUS:6]
[2018-11-05 14:10:21] Total:    7896 H/s
[2018-11-05 14:10:41] GPU0 :    1316 H/s [T: 59c, RPM: 4585, CC: 1408 MHz, MC: 1080 MHz][BUS:19]
[2018-11-05 14:10:41] GPU1 :    1317 H/s [T: 57c, RPM: 4444, CC: 1408 MHz, MC: 1080 MHz][BUS:3]
[2018-11-05 14:10:41] GPU2 :    1317 H/s [T: 58c, RPM: 4644, CC: 1408 MHz, MC: 1080 MHz][BUS:13]
[2018-11-05 14:10:41] GPU3 :    1312 H/s [T: 54c, RPM: 4061, CC: 1408 MHz, MC: 1080 MHz][BUS:16]
[2018-11-05 14:10:41] GPU4 :    1317 H/s [T: 57c, RPM: 4483, CC: 1408 MHz, MC: 1080 MHz][BUS:9]
[2018-11-05 14:10:41] GPU5 :    1316 H/s [T: 55c, RPM: 4083, CC: 1408 MHz, MC: 1080 MHz][BUS:6]
[2018-11-05 14:10:41] Total:    7895 H/s
[2018-11-05 14:10:52] Pool accepted result 0x00005ECE
[2018-11-05 14:11:09] Pool accepted result 0x00002CF0
==========================================================

6x Vega64 (2017.10.30manufactr)  Core 1408/900    mem 1045/900  powertarget -20%

16+14 or 15+15 only get 7.25kh   It seems too low .

My 6xvega56(flash to 64bios) 16+14 get 11.5k  (core:1337/900  mem：1025/900  power taget -20%)


15+15,15+15,15+15,15+15
          Team Red Miner version 0.3.6
[2018-11-05 11:21:49] Auto-detected AMD OpenCL platform 1
[2018-11-05 11:21:50] Initializing GPU 0.
[2018-11-05 11:21:54] Pool cal.cnpool.cc login succeeded.
[2018-11-05 11:21:54] Pool cal.cnpool.cc received new job. (job_id: 350770445476649)
[2018-11-05 11:21:54] Pool cal.cnpool.cc set difficulty to 150000
[2018-11-05 11:21:55] Dev pool connected and ready.
[2018-11-05 11:21:55] Initializing GPU 1.
[2018-11-05 11:21:57] Initializing GPU 2.
[2018-11-05 11:21:59] Initializing GPU 3.
[2018-11-05 11:22:03] Initializing GPU 4.
[2018-11-05 11:22:05] Initializing GPU 5.
[2018-11-05 11:22:07] Successfully initialized GPU 0: Vega with 64 CU (PCIe 19:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 2: Vega with 64 CU (PCIe 13:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 3: Vega with 64 CU (PCIe 16:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 4: Vega with 64 CU (PCIe 09:00.0) (CN 15+15)
[2018-11-05 11:22:07] Successfully initialized GPU 5: Vega with 64 CU (PCIe 06:00.0) (CN 15+15)
[2018-11-05 11:22:24] Stats GPU 0 - cnv8: 746.1 h/s, avg 1.206kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 1 - cnv8: 738.8 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 2 - cnv8: 743.5 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 3 - cnv8: 729.5 h/s, avg 1.207kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 4 - cnv8: 735.3 h/s, avg 1.211kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats GPU 5 - cnv8: 728.2 h/s, avg 1.213kh/s, pool   0.0 h/s 0/0
[2018-11-05 11:22:24] Stats Total - cnv8: 4.421kh/s, avg 7.251kh/s, pool   0.0 h/s
[2018-11-05 11:22:32] Pool cal.cnpool.cc received new job. (job_id: 573976627372422)
[2018-11-05 11:22:33] Pool cal.cnpool.cc share accepted. (GPU1) (1/1/0)
[2018-11-05 11:22:36] Pool cal.cnpool.cc received new job. (job_id: 175747342969107)
[2018-11-05 11:22:47] Pool cal.cnpool.cc share accepted. (GPU2) (2/2/0)
[2018-11-05 11:22:54] Stats GPU 0 - cnv8: 1.388kh/s, avg 1.334kh/s, pool   0.0 h/s 0/0

This is way too low. The 6 x Vega56 flashed look better. The Vega 64 rig should be at 12+ kh/s even at your rather low clocks. A few questions:

1) What OS and driver is this?
2) Have you been mining CNv8 with some other miner on the same rig?
3) A mistake of ours was to not include the "standard" environment vars you should have configured in our example .bat file. If not, can you add these to your .bat file or make sure they are set in your shell?


set GPU_MAX_HEAP_SIZE=100
set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_USE_SYNC_OBJECTS=1

[todxx]

also I am having this error

Code:

[2018-11-04 16:17:05] Pool xmr-eu1.nanopool.org failed to parse server rpc: {"id":4,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}

anything I can do about it?

Just so I understand, is the miner still mining ok with this error message, or it doesn't work at all? As long as its for shares only, we will lose track of a few shares, and our poolside hashrate in the miner will be a little lower, but everything is otherwise working ok.

I got that error also when mining to nanopool, after that it will reconnect to pool again. so I guess effective pool hash rate will go down because every time got that error it will reconnect to pool again.

Yes, you will likely be losing poolside hashrate when this error is occurring.  We are working on a work-around for pools like nanopool that violate the json rpc protocol.  We hope to have it included in the next release of the miner.
For the time being, supportxmr and monero ocean are two pool options that I have personally verified work correctly.  I would guess most other pools will also work fine.

[todxx]

Rig
===================================
CPU: Intel(R) Celeron(R) CPU G3930 @ 2.90GHz   core:   2  
RAM: 4G DDR3
Virtual mem: 50 GB
OS:  Windows 10 professional   1709 16299.15
6xVega64

vega driver 18.5.1
========================================

set this PP_PhmSoftPowerPlayTable reg for each vega
========================
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001]
"PP_PhmSoftPowerPlayTable"=hex:B6,02,08,01,00,5C,00,E1,06,00,00,EE,2B,00,00,1B,\
  00,48,00,00,00,80,A9,03,00,F0,49,02,00,8E,00,08,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,02,01,5C,00,4F,02,46,02,94,00,9E,01,BE,00,28,01,7A,00,8C,00,\
  BC,01,00,00,00,00,72,02,00,00,90,00,A8,02,6D,01,43,01,97,01,F0,49,02,00,71,\
  02,02,02,00,00,00,00,00,00,08,00,00,00,00,00,00,00,05,00,07,00,03,00,05,00,\
  00,00,00,00,00,00,01,08,84,03,84,03,84,03,84,03,84,03,84,03,84,03,84,03,01,\
  01,84,03,01,01,84,03,00,08,60,EA,00,00,00,40,19,01,00,01,80,38,01,00,02,DC,\
  4A,01,00,03,90,5F,01,00,04,00,77,01,00,05,90,91,01,00,06,6C,B0,01,00,07,01,\
  08,D0,4C,01,00,00,00,80,00,00,00,00,00,00,1C,83,01,00,01,00,00,00,00,00,00,\
  00,00,70,A7,01,00,02,00,00,00,00,00,00,00,00,88,BC,01,00,03,00,00,00,00,00,\
  00,00,00,38,C1,01,00,04,00,00,00,00,00,00,00,00,88,D5,01,00,05,00,00,00,00,\
  01,00,00,00,70,D9,01,00,06,00,00,00,00,01,00,00,00,00,26,02,00,07,00,00,00,\
  00,01,00,00,00,00,05,60,EA,00,00,00,40,19,01,00,00,80,38,01,00,00,DC,4A,01,\
  00,00,90,5F,01,00,00,00,08,28,6E,00,00,00,2C,C9,00,00,01,F8,0B,01,00,02,80,\
  38,01,00,03,90,5F,01,00,04,F4,91,01,00,05,D0,B0,01,00,06,C0,D4,01,00,07,00,\
  08,6C,39,00,00,00,24,5E,00,00,01,FC,85,00,00,02,AC,BC,00,00,03,34,D0,00,00,\
  04,68,6E,01,00,05,08,97,01,00,06,EC,A3,01,00,07,00,01,68,3C,01,00,00,01,04,\
  3C,41,00,00,00,00,00,50,C3,00,00,00,00,00,80,38,01,00,02,00,00,B0,AD,01,00,\
  04,00,00,01,08,00,98,85,00,00,40,B5,00,00,60,EA,00,00,50,C3,00,00,01,80,BB,\
  00,00,60,EA,00,00,94,0B,01,00,50,C3,00,00,02,00,E1,00,00,94,0B,01,00,40,19,\
  01,00,50,C3,00,00,03,78,FF,00,00,40,19,01,00,88,26,01,00,50,C3,00,00,04,40,\
  19,01,00,80,38,01,00,80,38,01,00,50,C3,00,00,05,80,38,01,00,DC,4A,01,00,DC,\
  4A,01,00,50,C3,00,00,06,00,77,01,00,00,77,01,00,90,5F,01,00,50,C3,00,00,07,\
  90,91,01,00,90,91,01,00,00,77,01,00,50,C3,00,00,01,18,00,00,00,00,00,00,00,\
  0B,E4,12,60,09,60,09,4B,00,0A,00,54,03,90,01,90,01,90,01,90,01,90,01,90,01,\
  90,01,00,00,00,00,00,02,04,31,07,DC,00,DC,00,DC,00,90,01,00,00,59,00,69,00,\
  4A,00,4A,00,5F,00,73,00,73,00,64,00,40,00,90,92,97,60,96,00,90,55,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,02,D4,30,00,00,02,10,60,EA,00,\
  00,02,10
========================

OverdriveNtool set for each Vega64
==============================
GPU_P0=852;900
GPU_P1=991;900
GPU_P2=1084;900
GPU_P3=1138;900
GPU_P4=1150;900
GPU_P5=1202;900
GPU_P6=1212;900
GPU_P7=1408;900
Mem_P0=167;900
Mem_P1=500;900
Mem_P2=800;900
Mem_P3=1080;900
Fan_Min=2388
Fan_Max=4900
Fan_Target=65
Fan_Acoustic=2400
Power_Temp=80
Power_Target=-20
==========================

start.bat
=======================================
set GPU_MAX_HEAP_SIZE=100
set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_USE_SYNC_OBJECTS=1

teamredminer.exe -a cnv8 -o stratum+tcp://cal.cnpool.cc:32866 -u cberxts5ZZ8DQ.....................peB4osNpfD4bb92XjUcP1W1Tc5aFvs1XProMv71xM2QsC kT8hntKJXVaX.150000  -p %computername%  -d 0,1,2,3,4,5 --cn_config 15+15,15+15,15+15,15+15,15+15,15+15
==========================================

run SRBminer 1.6.9 with intensity=61
============================================
2018-11-05 14:09:59] Main pool: cal.cnpool.cc:32866
[2018-11-05 14:09:59] Connected to cal.cnpool.cc:32866
[2018-11-05 14:09:59] User logged in
[2018-11-05 14:09:59] Pool difficulty: 150000
[2018-11-05 14:09:59] Pool sent a new job (ID: 821908557589538)
[2018-11-05 14:10:10] GPU0 :    0 H/s [T: 50c, RPM: 3080, CC: 1408 MHz, MC: 1080 MHz][BUS:19]
[2018-11-05 14:10:10] GPU1 :    0 H/s [T: 49c, RPM: 3113, CC: 1408 MHz, MC: 1080 MHz][BUS:3]
[2018-11-05 14:10:10] GPU2 :    0 H/s [T: 51c, RPM: 3131, CC: 1408 MHz, MC: 1080 MHz][BUS:13]
[2018-11-05 14:10:10] GPU3 :    0 H/s [T: 48c, RPM: 3155, CC: 1408 MHz, MC: 1080 MHz][BUS:16]
[2018-11-05 14:10:10] GPU4 :    0 H/s [T: 48c, RPM: 3129, CC: 1408 MHz, MC: 1080 MHz][BUS:9]
[2018-11-05 14:10:10] GPU5 :    0 H/s [T: 48c, RPM: 3123, CC: 1408 MHz, MC: 1080 MHz][BUS:6]
[2018-11-05 14:10:10] Total:    0 H/s
[2018-11-05 14:10:21] GPU0 :    1316 H/s [T: 55c, RPM: 3464, CC: 1408 MHz, MC: 1080 MHz][BUS:19]
[2018-11-05 14:10:21] GPU1 :    1317 H/s [T: 53c, RPM: 3454, CC: 1408 MHz, MC: 1080 MHz][BUS:3]
[2018-11-05 14:10:21] GPU2 :    1318 H/s [T: 54c, RPM: 3515, CC: 1408 MHz, MC: 1080 MHz][BUS:13]
[2018-11-05 14:10:21] GPU3 :    1311 H/s [T: 52c, RPM: 3507, CC: 1408 MHz, MC: 1080 MHz][BUS:16]
[2018-11-05 14:10:21] GPU4 :    1317 H/s [T: 53c, RPM: 3461, CC: 1408 MHz, MC: 1080 MHz][BUS:9]
[2018-11-05 14:10:21] GPU5 :    1317 H/s [T: 53c, RPM: 3471, CC: 1408 MHz, MC: 1080 MHz][BUS:6]
[2018-11-05 14:10:21] Total:    7896 H/s
[2018-11-05 14:10:41] GPU0 :    1316 H/s [T: 59c, RPM: 4585, CC: 1408 MHz, MC: 1080 MHz][BUS:19]
[2018-11-05 14:10:41] GPU1 :    1317 H/s [T: 57c, RPM: 4444, CC: 1408 MHz, MC: 1080 MHz][BUS:3]
[2018-11-05 14:10:41] GPU2 :    1317 H/s [T: 58c, RPM: 4644, CC: 1408 MHz, MC: 1080 MHz][BUS:13]
[2018-11-05 14:10:41] GPU3 :    1312 H/s [T: 54c, RPM: 4061, CC: 1408 MHz, MC: 1080 MHz][BUS:16]
[2018-11-05 14:10:41] GPU4 :    1317 H/s [T: 57c, RPM: 4483, CC: 1408 MHz, MC: 1080 MHz][BUS:9]
[2018-11-05 14:10:41] GPU5 :    1316 H/s [T: 55c, RPM: 4083, CC: 1408 MHz, MC: 1080 MHz][BUS:6]
[2018-11-05 14:10:41] Total:    7895 H/s
[2018-11-05 14:10:52] Pool accepted result 0x00005ECE
[2018-11-05 14:11:09] Pool accepted result 0x00002CF0
==========================================================

Hi netmebtc,

Those hashrates are definitely low, for both teamred and SRB.  Have you tried using the 18.6.1 drivers?
I mostly run in linux so I'm a bit fuzzy on the windows driver quirks, but have you enabled large pages for the cards?  I think some older drivers needed this to get good hashrates.

[vmozara]

netmebtc,
since you mentioned power target -20%, i assume you have wattman installed.
You need to reinstall the driver without wattman as very often it will conflict with miner, drop the hashrate or cause instability. Use DDU to clean up your driver, then install adrenalin driver ONLY, no amd settings, no amd problem reporting, no nothing. (just power tables because they get deleted when driver is reinstalled)
Finally, use video card restart sequence to restart your cards, apply the ODN settings, and start the miner. This will have your vegas hashing at top speed. If you don't have this let us know

[ArtSmart]

Hi, thanks for good product. Had newer drivers, but in this setup only 6GPU from 8GPUS were recognised. Installed 18.6.1 drivers - now get this error. Please help

https://image.ibb.co/fSQoQ0/Screen-Shot-2018-11-05-at-09-39-52.png

[netmebtc]

@vmozara @todxx,thanks you two guys, I'll try do as you say. Then return the result.