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

[Mahaprajapati]

Add API and I am in

I second that
Need API for monitoring

SRB html monitor https://www.memrey.com/note/srb-dash-mon

https://imgur.com/a/eFYJnqr

[1715260960]

1715260960

[1715260960]

1715260960

[1715260960]

1715260960

[playfast]

I've been using xmr-stak for about a year now, but I just switched over to SRBMiner on my 4x RX 560 rig because the former program is seriously buggy when set to CNv8. Hashrate is just slightly higher than xmr-stak - 1765H/s vs. 1735H/s (not accounting for lost time due to crashes, stuck cards, etc...) - and power consumption is just slightly lower - 355W vs. 375W - but this is letting SRBMiner pick the intensity (double threads set to true). I much prefer to set intensity myself, however, so if anyone cares to share their settings for the 2GB RX 560 I'd appreciate it.

FYI, I had to downgrade from Adrenalin 18.6.1 to 18.5.1 to get SRBMiner to work; prior to that the driver would crash hard - blue screen reboot hard - as soon as it reported it had logged into the pool (so, presumably, as soon as it tried to generate the first share). I have no idea why 18.5.1 works when 18.6.1 didn't, but that's computers for you.

I have RX 560 2gb rig mining XMR. I use manual intensity, all cards needed lower intensity than the auto intensity. I recommend start at 26 and keep decreasing by 0.5 increment if not stable. Some of my cards had to go down to 24 and the lowest is 23.5
Core 1180@895mV/Mem 2000-2100, power limit +10% each card running 450-465 H/s and using ~36W with 18.6.1, the best driver for me. My cards needed +5 mV on the memory compared to v7. I tried 18.5.x it hashes a tiny bit more but uses more power ~40W
v8 is more hungry for virtual memory, I have it set at 3x total vram.
I also recommend using a reasonably low static difficulty with XMR, variable difficulty can get too high and cause stability/pool problems with weaker cards like the 560.

[MagicSmoker]

...I much prefer to set intensity myself, however, so if anyone cares to share their settings for the 2GB RX 560 I'd appreciate it.
...

I have RX 560 2gb rig mining XMR. I use manual intensity, all cards needed lower intensity than the auto intensity. I recommend start at 26 and keep decreasing by 0.5 increment if not stable. Some of my cards had to go down to 24 and the lowest is 23.5
Core 1180@895mV/Mem 2000-2100, power limit +10% each card running 450-465 H/s and using ~36W with 18.6.1, the best driver for me. My cards needed +5 mV on the memory compared to v7. I tried 18.5.x it hashes a tiny bit more but uses more power ~40W
v8 is more hungry for virtual memory, I have it set at 3x total vram.
I also recommend using a reasonably low static difficulty with XMR, variable difficulty can get too high and cause stability/pool problems with weaker cards like the 560.

Thanks for the reply - you got my last sMerit for it!

After making that post I poked around the log file created by SRB and found the intensity it was setting for the cards: all are at 26.0. I was using OverDrivenTool to set all the clocks and voltages for each power state but I found it cumbersome and once MSI AB was able to deal with 3+ AMD cards again (ie - v4.5.0) I switched back to it. Unfortunately, I haven't been able to unlock core voltage adjustment yet, and as I recall that was another reason why I switched from AB to ODT.

At any rate, my 4 cards are consistently doing 460, 420, 420, 460 and using an estimated 54W each (based on Kill-A-Watt monitor, minus the amount used by the system when not mining) and 1200 Core / 1900 Mem and -20% on the power limit, so you are totally kicking my ass in power consumption vs. hashrate. Clearly I have some more tweaking to do but right now I am just happy I got it working stably on v8.

[Zorg33]

@playfast
I don't wanna be spiteful, but 450h@36W(at the wall) is barely possible.
As all polaris GPUs are 100% consistent in relative consumption it would mean an RX 570 can do 900 h/s at 72W but it can't. (or very rarely at least, 1 out of 100 cards maybe)
Did you measure it with killawatt or it's some 'calculated' or GPU-Z value?

[mike_lovemonero]

i think the http://cryptonightv8.com is the best and easiest

[playfast]

@playfast
I don't wanna be spiteful, but 450h@36W(at the wall) is barely possible.
As all polaris GPUs are 100% consistent in relative consumption it would mean an RX 570 can do 900 h/s at 72W but it can't. (or very rarely at least, 1 out of 100 cards maybe)
Did you measure it with killawatt or it's some 'calculated' or GPU-Z value?

I have msi 560 that came with hynix mem and later core steppings, 1050 mV at stock core clock 1196.
They are great undervolters, doing 895 mV at 1180 on v8, they could do 885 mV with v7. gpuz reads a solid 36W, kill-a-watt doesn't go over 40W, bounces between 36-40W.
They were doing 29-30W on v7, so power consumption went up around 20%.

[Zorg33]

@playfast
I don't wanna be spiteful, but 450h@36W(at the wall) is barely possible.
As all polaris GPUs are 100% consistent in relative consumption it would mean an RX 570 can do 900 h/s at 72W but it can't. (or very rarely at least, 1 out of 100 cards maybe)
Did you measure it with killawatt or it's some 'calculated' or GPU-Z value?

I have msi 560 that came with hynix mem and later core steppings, 1050 mV at stock core clock 1196.
They are great undervolters, doing 895 mV at 1180 on v8, they could do 885 mV with v7. gpuz reads a solid 36W, kill-a-watt doesn't go over 40W, bounces between 36-40W.
They were doing 29-30W on v7, so power consumption went up around 20%.

OK, so ~40W at wall, that's more realistic.

I found my 550/560s need more voltage than 570/580s for the same freq to be stable, usually 1000mV+ for 1250MHz. But OK, maybe MSI 560 is a good series.

[playfast]

...I much prefer to set intensity myself, however, so if anyone cares to share their settings for the 2GB RX 560 I'd appreciate it.
...

I have RX 560 2gb rig mining XMR. I use manual intensity, all cards needed lower intensity than the auto intensity. I recommend start at 26 and keep decreasing by 0.5 increment if not stable. Some of my cards had to go down to 24 and the lowest is 23.5
Core 1180@895mV/Mem 2000-2100, power limit +10% each card running 450-465 H/s and using ~36W with 18.6.1, the best driver for me. My cards needed +5 mV on the memory compared to v7. I tried 18.5.x it hashes a tiny bit more but uses more power ~40W
v8 is more hungry for virtual memory, I have it set at 3x total vram.
I also recommend using a reasonably low static difficulty with XMR, variable difficulty can get too high and cause stability/pool problems with weaker cards like the 560.

Thanks for the reply - you got my last sMerit for it!

After making that post I poked around the log file created by SRB and found the intensity it was setting for the cards: all are at 26.0. I was using OverDrivenTool to set all the clocks and voltages for each power state but I found it cumbersome and once MSI AB was able to deal with 3+ AMD cards again (ie - v4.5.0) I switched back to it. Unfortunately, I haven't been able to unlock core voltage adjustment yet, and as I recall that was another reason why I switched from AB to ODT.

At any rate, my 4 cards are consistently doing 460, 420, 420, 460 and using an estimated 54W each (based on Kill-A-Watt monitor, minus the amount used by the system when not mining) and 1200 Core / 1900 Mem and -20% on the power limit, so you are totally kicking my ass in power consumption vs. hashrate. Clearly I have some more tweaking to do but right now I am just happy I got it working stably on v8.

Were you disabling P0-P6 in ODT? You should. Just click each one to grey it out.
Also ODT version 0.2.6 is very buggy for me, it has a problem setting core properly so i downgraded to 0.2.5 which works perfectly.
What I do is enable "extend official overclock limits" in Afterburner, then from there I only use ODT 0.2.5, you have to do that or you get mem clock setting error in ODT.

[gregv64]

Hey did you get a resolution to this? I also am having this problem. 1 V56 and 2 V64

Please help. I have one Vega56 and one RX580-8G. Got the following error when running SRBMinber 1.6.8. Tried different drivers (18.5.1, 18.5.2, 18.6.1), DDU clean install every time. Also tried the default kernel and compiled kernel.  One wired thing I noticed is that the miner recognizes my RX580 as "Radeon RX Vega [ellesmere]". The miner is working properly only when I use one card at a time to hash with fresh compiled kernel.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2018-10-25 14:17:10] Miner version: 1.6.8
[2018-10-25 14:17:10] Windows version: 10.0 build 17763
[2018-10-25 14:17:10] Video driver version: 24.20.11021.1000
[2018-10-25 14:17:11] AMD Platform ID: 0
[2018-10-25 14:17:11] AMD platform FOUND
[2018-10-25 14:17:11] Found 2 AMD devices
[2018-10-25 14:17:11] CPU AES-NI: FALSE
[2018-10-25 14:17:11] GPU0: Radeon RX Vega [ellesmere] [8192 MB][Intensity 61.0][W: 16][T: 2][K: 1][BUS: 15]
[2018-10-25 14:17:11] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 120.0][W: 16][T: 2][K: 1][BUS: 5]
[2018-10-25 14:17:11] ADL is enabled
[2018-10-25 14:17:11] CryptonightV8 mode enabled
[2018-10-25 14:17:11] Starting init of mining threads
[2018-10-25 14:17:11] Heating up system, please wait...
[2018-10-25 14:17:11] Created OCL context
[2018-10-25 14:17:11] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Loading kernel for DEVICE BUS ID 15 ...
[2018-10-25 14:17:12] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Error initing GPU's. Stopping miner process

[coke15]

i think the http://cryptonightv8.com is the best and easiest

seriously?

[mmex]

No. XMR-Stak and Cast_XMR work with a little bit lower hash rate.

Hey did you get a resolution to this? I also am having this problem. 1 V56 and 2 V64

Please help. I have one Vega56 and one RX580-8G. Got the following error when running SRBMinber 1.6.8. Tried different drivers (18.5.1, 18.5.2, 18.6.1), DDU clean install every time. Also tried the default kernel and compiled kernel.  One wired thing I noticed is that the miner recognizes my RX580 as "Radeon RX Vega [ellesmere]". The miner is working properly only when I use one card at a time to hash with fresh compiled kernel.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2018-10-25 14:17:10] Miner version: 1.6.8
[2018-10-25 14:17:10] Windows version: 10.0 build 17763
[2018-10-25 14:17:10] Video driver version: 24.20.11021.1000
[2018-10-25 14:17:11] AMD Platform ID: 0
[2018-10-25 14:17:11] AMD platform FOUND
[2018-10-25 14:17:11] Found 2 AMD devices
[2018-10-25 14:17:11] CPU AES-NI: FALSE
[2018-10-25 14:17:11] GPU0: Radeon RX Vega [ellesmere] [8192 MB][Intensity 61.0][W: 16][T: 2][K: 1][BUS: 15]
[2018-10-25 14:17:11] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 120.0][W: 16][T: 2][K: 1][BUS: 5]
[2018-10-25 14:17:11] ADL is enabled
[2018-10-25 14:17:11] CryptonightV8 mode enabled
[2018-10-25 14:17:11] Starting init of mining threads
[2018-10-25 14:17:11] Heating up system, please wait...
[2018-10-25 14:17:11] Created OCL context
[2018-10-25 14:17:11] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Loading kernel for DEVICE BUS ID 15 ...
[2018-10-25 14:17:12] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Error initing GPU's. Stopping miner process

[gregv64]

Can't figure how to PM you, but can you post the two thread lines from your AMD config setup for XMR stak please? Reason I wanted to go with this SRB miner is i can;t get the newest stak to fire up anymore.

Thanks,

No. XMR-Stak and Cast_XMR work with a little bit lower hash rate.

Hey did you get a resolution to this? I also am having this problem. 1 V56 and 2 V64

Please help. I have one Vega56 and one RX580-8G. Got the following error when running SRBMinber 1.6.8. Tried different drivers (18.5.1, 18.5.2, 18.6.1), DDU clean install every time. Also tried the default kernel and compiled kernel.  One wired thing I noticed is that the miner recognizes my RX580 as "Radeon RX Vega [ellesmere]". The miner is working properly only when I use one card at a time to hash with fresh compiled kernel.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2018-10-25 14:17:10] Miner version: 1.6.8
[2018-10-25 14:17:10] Windows version: 10.0 build 17763
[2018-10-25 14:17:10] Video driver version: 24.20.11021.1000
[2018-10-25 14:17:11] AMD Platform ID: 0
[2018-10-25 14:17:11] AMD platform FOUND
[2018-10-25 14:17:11] Found 2 AMD devices
[2018-10-25 14:17:11] CPU AES-NI: FALSE
[2018-10-25 14:17:11] GPU0: Radeon RX Vega [ellesmere] [8192 MB][Intensity 61.0][W: 16][T: 2][K: 1][BUS: 15]
[2018-10-25 14:17:11] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 120.0][W: 16][T: 2][K: 1][BUS: 5]
[2018-10-25 14:17:11] ADL is enabled
[2018-10-25 14:17:11] CryptonightV8 mode enabled
[2018-10-25 14:17:11] Starting init of mining threads
[2018-10-25 14:17:11] Heating up system, please wait...
[2018-10-25 14:17:11] Created OCL context
[2018-10-25 14:17:11] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Loading kernel for DEVICE BUS ID 15 ...
[2018-10-25 14:17:12] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Error initing GPU's. Stopping miner process

[heavyarms1912]

Can't figure how to PM you, but can you post the two thread lines from your AMD config setup for XMR stak please? Reason I wanted to go with this SRB miner is i can;t get the newest stak to fire up anymore.

Thanks,

you can add a pause at end of .bat script of xmr-stak and see the error message.  That'll help to troubleshoot.

[racminer]

Please help. I have one Vega56 and one RX580-8G. Got the following error when running SRBMinber 1.6.8. Tried different drivers (18.5.1, 18.5.2, 18.6.1), DDU clean install every time. Also tried the default kernel and compiled kernel.  One wired thing I noticed is that the miner recognizes my RX580 as "Radeon RX Vega [ellesmere]". The miner is working properly only when I use one card at a time to hash with fresh compiled kernel.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2018-10-25 14:17:10] Miner version: 1.6.8
[2018-10-25 14:17:10] Windows version: 10.0 build 17763
[2018-10-25 14:17:10] Video driver version: 24.20.11021.1000
[2018-10-25 14:17:11] AMD Platform ID: 0
[2018-10-25 14:17:11] AMD platform FOUND
[2018-10-25 14:17:11] Found 2 AMD devices
[2018-10-25 14:17:11] CPU AES-NI: FALSE
[2018-10-25 14:17:11] GPU0: Radeon RX Vega [ellesmere] [8192 MB][Intensity 61.0][W: 16][T: 2][K: 1][BUS: 15]
[2018-10-25 14:17:11] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 120.0][W: 16][T: 2][K: 1][BUS: 5]
[2018-10-25 14:17:11] ADL is enabled
[2018-10-25 14:17:11] CryptonightV8 mode enabled
[2018-10-25 14:17:11] Starting init of mining threads
[2018-10-25 14:17:11] Heating up system, please wait...
[2018-10-25 14:17:11] Created OCL context
[2018-10-25 14:17:11] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Loading kernel for DEVICE BUS ID 15 ...
[2018-10-25 14:17:12] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Error initing GPU's. Stopping miner process

Hi
Did you install the microsoft visual c++ 2017 redistributable package (x64) ?

[MagicSmoker]

...
At any rate, my 4 cards are consistently doing 460, 420, 420, 460 and using an estimated 54W each (based on Kill-A-Watt monitor, minus the amount used by the system when not mining) and 1200 Core / 1900 Mem and -20% on the power limit, so you are totally kicking my ass in power consumption vs. hashrate. Clearly I have some more tweaking to do but right now I am just happy I got it working stably on v8.

Were you disabling P0-P6 in ODT? You should. Just click each one to grey it out.
Also ODT version 0.2.6 is very buggy for me, it has a problem setting core properly so i downgraded to 0.2.5 which works perfectly.
What I do is enable "extend official overclock limits" in Afterburner, then from there I only use ODT 0.2.5, you have to do that or you get mem clock setting error in ODT.

I also have ODT 0.2.5 installed (not currently using it, however), but I only had P0 and P1 greyed out in my custom CN profile. I'm feeling more adventurous now that things have been running well for a day, but before I start giving myself a migraine I want to clarify a few things you've done:

• Run 18.6.1 for less power consumption or 18.5.1 for higher hashrate (marginal differences both).
• Use MSI AB to "extend official overclock limits." Q: are you using MSI AB or ODT to control the fans? I greatly prefer using AB to set a custom fan curve.
• Bump up PL in AB to +5%
• Use ODT 0.2.5 to set highest P state for core/mem clock/voltage, trying 1180MHz/895mV for core and 2000-2100MHz for mem. Q: What about memory voltage?
• Set intensity manually in SRB try 23 to 24 initially. Q: What about worksize? SRB is setting it to 32 automatically (also, double threads true and K auto set to 1).

And that should bring my power consumption down to around 40W per card with a slight boost to hashrate, correct?

[gregv64]

Perhaps him and I have the same issue...how do i completely disable my iGPU from doing any work? could it be crashing the system?

Please help. I have one Vega56 and one RX580-8G. Got the following error when running SRBMinber 1.6.8. Tried different drivers (18.5.1, 18.5.2, 18.6.1), DDU clean install every time. Also tried the default kernel and compiled kernel.  One wired thing I noticed is that the miner recognizes my RX580 as "Radeon RX Vega [ellesmere]". The miner is working properly only when I use one card at a time to hash with fresh compiled kernel.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2018-10-25 14:17:10] Miner version: 1.6.8
[2018-10-25 14:17:10] Windows version: 10.0 build 17763
[2018-10-25 14:17:10] Video driver version: 24.20.11021.1000
[2018-10-25 14:17:11] AMD Platform ID: 0
[2018-10-25 14:17:11] AMD platform FOUND
[2018-10-25 14:17:11] Found 2 AMD devices
[2018-10-25 14:17:11] CPU AES-NI: FALSE
[2018-10-25 14:17:11] GPU0: Radeon RX Vega [ellesmere] [8192 MB][Intensity 61.0][W: 16][T: 2][K: 1][BUS: 15]
[2018-10-25 14:17:11] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 120.0][W: 16][T: 2][K: 1][BUS: 5]
[2018-10-25 14:17:11] ADL is enabled
[2018-10-25 14:17:11] CryptonightV8 mode enabled
[2018-10-25 14:17:11] Starting init of mining threads
[2018-10-25 14:17:11] Heating up system, please wait...
[2018-10-25 14:17:11] Created OCL context
[2018-10-25 14:17:11] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Loading kernel for DEVICE BUS ID 15 ...
[2018-10-25 14:17:12] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Error initing GPU's. Stopping miner process

Hi
Did you install the microsoft visual c++ 2017 redistributable package (x64) ?

[mmex]

[
  { "index" : 0,
    "intensity" : 864, "worksize" : 16,
    "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2,
    "unroll" : 8, "comp_mode" : true
  },

  { "index" : 0,
    "intensity" : 864, "worksize" : 16,
    "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2,
    "unroll" : 8, "comp_mode" : true
  },

  { "index" : 1,
    "intensity" : 1920, "worksize" : 16,
    "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2,
    "unroll" : 8, "comp_mode" : true
  },

  { "index" : 1,
    "intensity" : 1920, "worksize" : 16,
    "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2,
    "unroll" : 8, "comp_mode" : true
  },
]

Can't figure how to PM you, but can you post the two thread lines from your AMD config setup for XMR stak please? Reason I wanted to go with this SRB miner is i can;t get the newest stak to fire up anymore.

Thanks,

No. XMR-Stak and Cast_XMR work with a little bit lower hash rate.

Hey did you get a resolution to this? I also am having this problem. 1 V56 and 2 V64

Please help. I have one Vega56 and one RX580-8G. Got the following error when running SRBMinber 1.6.8. Tried different drivers (18.5.1, 18.5.2, 18.6.1), DDU clean install every time. Also tried the default kernel and compiled kernel.  One wired thing I noticed is that the miner recognizes my RX580 as "Radeon RX Vega [ellesmere]". The miner is working properly only when I use one card at a time to hash with fresh compiled kernel.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2018-10-25 14:17:10] Miner version: 1.6.8
[2018-10-25 14:17:10] Windows version: 10.0 build 17763
[2018-10-25 14:17:10] Video driver version: 24.20.11021.1000
[2018-10-25 14:17:11] AMD Platform ID: 0
[2018-10-25 14:17:11] AMD platform FOUND
[2018-10-25 14:17:11] Found 2 AMD devices
[2018-10-25 14:17:11] CPU AES-NI: FALSE
[2018-10-25 14:17:11] GPU0: Radeon RX Vega [ellesmere] [8192 MB][Intensity 61.0][W: 16][T: 2][K: 1][BUS: 15]
[2018-10-25 14:17:11] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 120.0][W: 16][T: 2][K: 1][BUS: 5]
[2018-10-25 14:17:11] ADL is enabled
[2018-10-25 14:17:11] CryptonightV8 mode enabled
[2018-10-25 14:17:11] Starting init of mining threads
[2018-10-25 14:17:11] Heating up system, please wait...
[2018-10-25 14:17:11] Created OCL context
[2018-10-25 14:17:11] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Loading kernel for DEVICE BUS ID 15 ...
[2018-10-25 14:17:12] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Error initing GPU's. Stopping miner process

[mmex]

Yes. I even have Visual Studio 2017 Professional installed. Not sure if the latest Windows 10 (Version 1809, OS build 17763.55) caused the problem. Seems like we need help from @doktor83.

Please help. I have one Vega56 and one RX580-8G. Got the following error when running SRBMinber 1.6.8. Tried different drivers (18.5.1, 18.5.2, 18.6.1), DDU clean install every time. Also tried the default kernel and compiled kernel.  One wired thing I noticed is that the miner recognizes my RX580 as "Radeon RX Vega [ellesmere]". The miner is working properly only when I use one card at a time to hash with fresh compiled kernel.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2018-10-25 14:17:10] Miner version: 1.6.8
[2018-10-25 14:17:10] Windows version: 10.0 build 17763
[2018-10-25 14:17:10] Video driver version: 24.20.11021.1000
[2018-10-25 14:17:11] AMD Platform ID: 0
[2018-10-25 14:17:11] AMD platform FOUND
[2018-10-25 14:17:11] Found 2 AMD devices
[2018-10-25 14:17:11] CPU AES-NI: FALSE
[2018-10-25 14:17:11] GPU0: Radeon RX Vega [ellesmere] [8192 MB][Intensity 61.0][W: 16][T: 2][K: 1][BUS: 15]
[2018-10-25 14:17:11] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 120.0][W: 16][T: 2][K: 1][BUS: 5]
[2018-10-25 14:17:11] ADL is enabled
[2018-10-25 14:17:11] CryptonightV8 mode enabled
[2018-10-25 14:17:11] Starting init of mining threads
[2018-10-25 14:17:11] Heating up system, please wait...
[2018-10-25 14:17:11] Created OCL context
[2018-10-25 14:17:11] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Loading kernel for DEVICE BUS ID 15 ...
[2018-10-25 14:17:12] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Error initing GPU's. Stopping miner process

Hi
Did you install the microsoft visual c++ 2017 redistributable package (x64) ?

[playfast]

...
At any rate, my 4 cards are consistently doing 460, 420, 420, 460 and using an estimated 54W each (based on Kill-A-Watt monitor, minus the amount used by the system when not mining) and 1200 Core / 1900 Mem and -20% on the power limit, so you are totally kicking my ass in power consumption vs. hashrate. Clearly I have some more tweaking to do but right now I am just happy I got it working stably on v8.

Were you disabling P0-P6 in ODT? You should. Just click each one to grey it out.
Also ODT version 0.2.6 is very buggy for me, it has a problem setting core properly so i downgraded to 0.2.5 which works perfectly.
What I do is enable "extend official overclock limits" in Afterburner, then from there I only use ODT 0.2.5, you have to do that or you get mem clock setting error in ODT.

I also have ODT 0.2.5 installed (not currently using it, however), but I only had P0 and P1 greyed out in my custom CN profile. I'm feeling more adventurous now that things have been running well for a day, but before I start giving myself a migraine I want to clarify a few things you've done:

• Run 18.6.1 for less power consumption or 18.5.1 for higher hashrate (marginal differences both).
• Use MSI AB to "extend official overclock limits." Q: are you using MSI AB or ODT to control the fans? I greatly prefer using AB to set a custom fan curve.
• Bump up PL in AB to +5%
• Use ODT 0.2.5 to set highest P state for core/mem clock/voltage, trying 1180MHz/895mV for core and 2000-2100MHz for mem. Q: What about memory voltage?
• Set intensity manually in SRB try 23 to 24 initially. Q: What about worksize? SRB is setting it to 32 automatically (also, double threads true and K auto set to 1).

And that should bring my power consumption down to around 40W per card with a slight boost to hashrate, correct?

Depending on what brand 560's you have, they may not be able to go down to 40W and retain 450 h/s, it all depends on how well they can undervolt. I think it's impossible with the 18.5.1 drivers you must use 18.6.1 or no dice. For me 18.5.1 read 40w on gpu-z if I had tested on the wall I'm sure it would actually be 44-45w. 18.6.1 read 36w on gpu-z and goes no higher than 39.5w on the wall for me. The tiny ~5 H/s gain on 18.5.1 is definitely not worth the higher power draw. If you're desperate for lower undervolt you could try lower core clock than 1180, but at this point every step down is negative for hashrate.
I just use ODT at fixed fan speeds, my 6x rx560 2gb rig is in my bedroom so I try to keep it quiet like 1600 rpm, as long as my cards stay 65C or under it's okay.
On v7 I got max hashrate with -10% power limit. On v8 I have to increase to +10% for max hashrate. PL doesn't really effect consumption, the core voltage effects it most.
On v8, my 560's need 865 mV on mem voltage to be 100% stable, at 860 mV they can crash or lose hashrate after many hours. I had it on 860 mV before because it was stable with older v7, so v8 needed +5 mV.
Try 8 worksize first and then 12/16 and see if it improves hashrate, doesn't make sense for a 2gb card to go any higher than 16.

[thebestfool]

Hello . Can someone to give best settings for RX550 v8 algo. Thanks. I used xmrig but now is not stable. Greetings from Bulgaria!