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

[ManDoneKTM]

Algorithm: Cryptonight V4 (R) - after 1 minute of work produces multiple errors!

Same here , i switched to another miner , until this will solved

[duketasos]

thinking of bios modification to my ref vegas 56. Can someone please (that has done it) tells me a good stable config and the pros/cons of all this? does it worth it? already stable 56's with 1880h/s each

[doktor83]

Algorithm: Cryptonight V4 (R) - after 1 minute of work produces multiple errors!

Same here , i switched to another miner , until this will solved

Maybe you guys could give a little more info, because i can't really help you if you say 'it s not working'.
I have rx550,560, rx470,480,570,580 4g and 8g. Vega56 and its working on every rig. Also i guess it works for the majority because this forum thread would be flooded with 'not working' messages.

[doktor83]

How to write startup_script: -cclock, -mclock, -cvddc, -mvddc and run it?
Thank.

First download a Claymore miner, then try those commands.

I asked about startup_script.

SRBMiner does not have cclock, -mclock, -cvddc, -mvddc parameters

[ManDoneKTM]

btw , i use latest amd driver . i had issues with 18.6.1 and then i updated to the latest and no issues found , for ex rig frozen or dropping hashrate .

[JuanHungLo]

thinking of bios modification to my ref vegas 56. Can someone please (that has done it) tells me a good stable config and the pros/cons of all this? does it worth it? already stable 56's with 1880h/s each

You cannot mod the BIOS of a Vega 56, you can only modify PowerPlay tables for Vega.  Alternatively, you can use Win10 and the latest beta version of OverdriveNTool 0.2.8beta1.  Also, you can swap the Vega 56 BIOS with the Vega 64 BIOS.  But you cannot mod a Vega BIOS.

[Prolow]

I had an issue where my vega rig crashed after about 8-9 hours when I upgraded from SRB 1.8.0 to 1.8.2, I was using 18.5.1. After that I tried installing the 19.4.1 and install all the windows updates, and now it seems to be working as it should. However I do get a few shares rejected due to low diff, not really sure why though.

[duketasos]

thinking of bios modification to my ref vegas 56. Can someone please (that has done it) tells me a good stable config and the pros/cons of all this? does it worth it? already stable 56's with 1880h/s each

You cannot mod the BIOS of a Vega 56, you can only modify PowerPlay tables for Vega.  Alternatively, you can use Win10 and the latest beta version of OverdriveNTool 0.2.8beta1.  Also, you can swap the Vega 56 BIOS with the Vega 64 BIOS.  But you cannot mod a Vega BIOS.

HEllo thanks for your reply, yes i meant swapping bios..do you know any drawbacks like high temperatures etc or all just the same, my problems is that im living in a country with high ambient temps so i cant bear to set the fans any higher already i have a vega fan headache.already using overdrive (older version) to config vegas everything seted up via vega mining guide and powertable

[doktor83]

Because some reported 'random miner crashes not related to gpu crashes', i made a little tool as a workaround, until i find the bug(s) and fix them.
This tool serves as a replacement for scripts you can set up to monitor the miner process and start it if it's not running.


SRB-RESTARTER

Only 3 parameters :

--interval value_in_seconds [def. is 10]
Specifies how often to check is the SRBMiner process running

--instance number
Use it if you run multiple SRBMiner instances on the same machine, example is below
You must use the following file naming :
SRBMiner-CN-n.exe where n is the instance number

--run filename [name of .bat file to run]
Name of .bat you want to run if SRBMiner process in not running


Note:
Miner is considered 'not running' after 2 checks!

Examples:

1.
SRB-Restarter.exe
[This will set interval to 10 seconds, and start.bat if SRBMiner process is not running. It will monitor for a process named SRBMiner-CN.exe]

2.
SRB-Restarter.exe --interval 5 --run turtle-coin.bat
[This will set interval to 5 seconds and run turtle-coin.bat if SRBMiner process is not running. It will monitor for a process named SRBMiner-CN.exe]

3.
SRB-Restarter.exe --interval 30 --run start-heavy.bat --instance 1
[This will set interval to 30 seconds and run start-heavy.bat if SRBMiner process is not running. It will monitor for a process named SRBMiner-CN-1.exe]


If you copy the whole folder from the .zip into SRBMiner folder, you have an example SRB-Restart.bat inside that will check for the SRBMiner-CN.exe process every 5 seconds, and run start.bat that is in the main miner folder (that's why the '..\start.bat', it means one level back).

Link is on the first page or HERE

[JuanHungLo]

thinking of bios modification to my ref vegas 56. Can someone please (that has done it) tells me a good stable config and the pros/cons of all this? does it worth it? already stable 56's with 1880h/s each

You cannot mod the BIOS of a Vega 56, you can only modify PowerPlay tables for Vega.  Alternatively, you can use Win10 and the latest beta version of OverdriveNTool 0.2.8beta1.  Also, you can swap the Vega 56 BIOS with the Vega 64 BIOS.  But you cannot mod a Vega BIOS.

HEllo thanks for your reply, yes i meant swapping bios..do you know any drawbacks like high temperatures etc or all just the same, my problems is that im living in a country with high ambient temps so i cant bear to set the fans any higher already i have a vega fan headache.already using overdrive (older version) to config vegas everything seted up via vega mining guide and powertable

IMO, temps are a big problem for vegas.  If you don't maintain the HBM2 temps BELOW 70 C, you will lose hashrate.  I didn't not notice a huge increase in temps when swapping 56 BIOS with 64.  Greater range for clocks and memory frequency increases temps proportionally.  Before messing with swapping BIOS, I'd solve your temp problem first.  In other words, why increase the clocks and frequency capability when it is simply going to throttle back?

[coinzzzman]

thinking of bios modification to my ref vegas 56. Can someone please (that has done it) tells me a good stable config and the pros/cons of all this? does it worth it? already stable 56's with 1880h/s each

You cannot mod the BIOS of a Vega 56, you can only modify PowerPlay tables for Vega.  Alternatively, you can use Win10 and the latest beta version of OverdriveNTool 0.2.8beta1.  Also, you can swap the Vega 56 BIOS with the Vega 64 BIOS.  But you cannot mod a Vega BIOS.

HEllo thanks for your reply, yes i meant swapping bios..do you know any drawbacks like high temperatures etc or all just the same, my problems is that im living in a country with high ambient temps so i cant bear to set the fans any higher already i have a vega fan headache.already using overdrive (older version) to config vegas everything seted up via vega mining guide and powertable

IMO, temps are a big problem for vegas.  If you don't maintain the HBM2 temps BELOW 70 C, you will lose hashrate.  I didn't not notice a huge increase in temps when swapping 56 BIOS with 64.  Greater range for clocks and memory frequency increases temps proportionally.  Before messing with swapping BIOS, I'd solve your temp problem first.  In other words, why increase the clocks and frequency capability when it is simply going to throttle back?

Totally agree; I've found success with keeping core volts below 950, memory to 800, fans set to 3200 min with a 4900 max, and set target temperature to 66 (you can even try lower if you don't mind the loud noise of the fans).

I've also had cases where the cards run much hotter for no apparent reason and my only guess its a radeon software or driver issue whereby it's ignoring my minimum core volts, driving more volts through the card and making them hotter.  A reboot and disable/enable in device manager for each card has fixed this, and then they run 10c cooler until it mysteriously happens again.

I'm on a mixed rig of nvidia and amd, and often wonder if that's not causing me some weird issues.

Cheers

[fmz89]

thinking of bios modification to my ref vegas 56. Can someone please (that has done it) tells me a good stable config and the pros/cons of all this? does it worth it? already stable 56's with 1880h/s each

You cannot mod the BIOS of a Vega 56, you can only modify PowerPlay tables for Vega.  Alternatively, you can use Win10 and the latest beta version of OverdriveNTool 0.2.8beta1.  Also, you can swap the Vega 56 BIOS with the Vega 64 BIOS.  But you cannot mod a Vega BIOS.

HEllo thanks for your reply, yes i meant swapping bios..do you know any drawbacks like high temperatures etc or all just the same, my problems is that im living in a country with high ambient temps so i cant bear to set the fans any higher already i have a vega fan headache.already using overdrive (older version) to config vegas everything seted up via vega mining guide and powertable

IMO, temps are a big problem for vegas.  If you don't maintain the HBM2 temps BELOW 70 C, you will lose hashrate.  I didn't not notice a huge increase in temps when swapping 56 BIOS with 64.  Greater range for clocks and memory frequency increases temps proportionally.  Before messing with swapping BIOS, I'd solve your temp problem first.  In other words, why increase the clocks and frequency capability when it is simply going to throttle back?

Core1450mhz/906mv, mem 1090mhz/906mv fan at 3400/4900 with taget temp set to 67 you should be fine, at 32°C ambient temp, no problem happen on my rigs
CNv4/R
Vega56(bios64) : 1960hs
Vega64 : 2040hs
6x vega56 : 11750hs/1200watt

[Prolow]

Figured I'd post some settings I have bee successful running on my 6x mixed vega rig.
I previously ran srb 1.8.0 with amd driver 18.5.1. But after I updated to 1.8.2 my rig just kept crashing and srb stopped running.

So I used windows update and updated everything. And after that I did DDU followed by just installing the graphics driver (19.4.1) and not amd settings++.
Something to keep in mind here, is that PPT is no longer required as I understand.

With ambient temp of around 21c and these settings, my rig is running stable with temps within 50c-55c while fans are running at ~3200rpm / 60%.
I have not been able to check power draw of this rig, but considering the low temps/fan rpm it should be pretty low.

vega56 ~1850 h/s
vega64 ~1950 h/s

At some later point I will test power draw and reapply thermal paste.
OverDriveNtool profiles. ( OverDriveNtool version 2.8.1 beta is needed )

[Profile_0]
Name=vega64
GPU_P0=852;800;0
GPU_P1=991;800;0
GPU_P2=1084;800;0
GPU_P3=1138;800;0
GPU_P4=1150;800;0
GPU_P5=1202;800;0
GPU_P6=1212;805;0
GPU_P7=1360;880
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;895;0
Mem_P3=1090;895
Mem_TimingLevel=0
Fan_Min=2800
Fan_Max=3500
Fan_Target=55
Fan_Acoustic=2400
Power_Temp=70
Power_Target=0
Fan_P0=30;60
Fan_P1=40;60
Fan_P2=50;60
Fan_P3=60;65
Fan_P4=65;70
Fan_ZeroRPM=0

[Profile_1]
Name=vega56
GPU_P0=852;800;0
GPU_P1=991;800;0
GPU_P2=1084;800;0
GPU_P3=1138;800;0
GPU_P4=1150;800;0
GPU_P5=1202;800;0
GPU_P6=1212;880;0
GPU_P7=1360;880
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;895;0
Mem_P3=935;905
Mem_TimingLevel=0
Fan_Min=2800
Fan_Max=3500
Fan_Target=55
Fan_Acoustic=2400
Power_Temp=70
Power_Target=0
Fan_P0=30;60
Fan_P1=40;60
Fan_P2=50;60
Fan_P3=60;65
Fan_P4=65;70
Fan_ZeroRPM=0

[jasonyslai]

Hi,
  Thanks for the awesome miner app
   1.8.2 is much more stable, but still crash occasionally.
   
Situation :
  - 2 of rigs have this issue
  - others work fine
  - All rigs have the same specification

Event log :
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2019-04-09T17:46:17.651645100Z" />
  <EventRecordID>26957</EventRecordID>
  <Channel>Application</Channel>
  <Computer>DESKTOP-OV6CFL9</Computer>
  <Security />
  </System>
- <EventData>
  <Data>SRBMiner-CN.exe</Data>
  <Data>1.8.2.0</Data>
  <Data>00000000</Data>
  <Data>SRBMiner-CN.exe</Data>
  <Data>1.8.2.0</Data>
  <Data>00000000</Data>
  <Data>c0000005</Data>
  <Data>000000000004ca53</Data>
  <Data>19f4</Data>
  <Data>01d4ed52356ec726</Data>
  <Data>C:\Users\miner2\Downloads\SRBMiner-CN-V1-8-2\SRBMiner-CN-V1-8-2\SRBMiner-CN.exe</Data>
  <Data>C:\Users\miner2\Downloads\SRBMiner-CN-V1-8-2\SRBMiner-CN-V1-8-2\SRBMiner-CN.exe</Data>
  <Data>e8bb546e-3bc2-4dd2-abb4-099ed974501b</Data>
  <Data />
  <Data />
  </EventData>
  </Event>

[zeef]

Because some reported 'random miner crashes not related to gpu crashes', i made a little tool as a workaround, until i find the bug(s) and fix them.
This tool serves as a replacement for scripts you can set up to monitor the miner process and start it if it's not running.


SRB-RESTARTER

Only 3 parameters :

--interval value_in_seconds [def. is 10]
Specifies how often to check is the SRBMiner process running

--instance number
Use it if you run multiple SRBMiner instances on the same machine, example is below
You must use the following file naming :
SRBMiner-CN-n.exe where n is the instance number

--run filename [name of .bat file to run]
Name of .bat you want to run if SRBMiner process in not running


Note:
Miner is considered 'not running' after 2 checks!

Examples:

1.
SRB-Restarter.exe
[This will set interval to 10 seconds, and start.bat if SRBMiner process is not running. It will monitor for a process named SRBMiner-CN.exe]

2.
SRB-Restarter.exe --interval 5 --run turtle-coin.bat
[This will set interval to 5 seconds and run turtle-coin.bat if SRBMiner process is not running. It will monitor for a process named SRBMiner-CN.exe]

3.
SRB-Restarter.exe --interval 30 --run start-heavy.bat --instance 1
[This will set interval to 30 seconds and run start-heavy.bat if SRBMiner process is not running. It will monitor for a process named SRBMiner-CN-1.exe]


If you copy the whole folder from the .zip into SRBMiner folder, you have an example SRB-Restart.bat inside that will check for the SRBMiner-CN.exe process every 5 seconds, and run start.bat that is in the main miner folder (that's why the '..\start.bat', it means one level back).

Link is on the first page or HERE

Thanks for the tool doc

[AVP]

How to check intensity that is automatically set by 0 setting?

I have RX 470s that keep crashing on 0 setting, I want to try lower intensity but don't know where to start, anyone here using RX 470s that wants to share their intensity setting?

Thanks.

[doktor83]

How to check intensity that is automatically set by 0 setting?

I have RX 470s that keep crashing on 0 setting, I want to try lower intensity but don't know where to start, anyone here using RX 470s that wants to share their intensity setting?

Thanks.

When the miner starts it writes out the found gpu's and the settings. There you can see I:number where that number is the intensity.
You can find on the first page how to manually set gpu's, by using gpu_conf.

Code:

"gpu_conf" :
[
{ "id" : 0, "intensity" : 50 , "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 53 , "worksize" : 16, "threads" : 2}
]

[AVP]

I'm using reboot_script_gpu_watchdog to execute a reboot bat script, but I've noticed that there sometimes a 2-3 min delay between 0 hash speed and script being executed.

Is there a way to increase frequency of the Watchdog so that 0 hash rate is detected more often, basically as soon as hash rate goes to 0 reboot script would get executed instantly ?

[AVP]

How to check intensity that is automatically set by 0 setting?

I have RX 470s that keep crashing on 0 setting, I want to try lower intensity but don't know where to start, anyone here using RX 470s that wants to share their intensity setting?

Thanks.

When the miner starts it writes out the found gpu's and the settings. There you can see I:number where that number is the intensity.
You can find on the first page how to manually set gpu's, by using gpu_conf.

Code:

"gpu_conf" :
[
{ "id" : 0, "intensity" : 50 , "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 53 , "worksize" : 16, "threads" : 2}
]

You're right, thanks for quick reply!

[sgnl.dsrptr]

Why am I getting a lot of rejected shares? "Pool rejected result 0x000074E1 for job[2] [low difficulty share]" By a lot I mean some, most shares are ofcourse accepted but still, quite frequent.

Pool difficulty is set at 120000 by default. May I change it for better results?

The pool I'm using is nanopool.org btw.

You get low diff shares when your gpu returns a bad result. So loosen on your OC , or depending of your card, maybe you use 'bad' mem. straps.

Is there any way to see what GPU that is getting this error, if it's just one or all GPUs? I can see how many errors and frequency in %. It just says what job number it is?

95,5% accepted shares. Maybe not much to care about in about one hour?

Yes, it would be nice if the "low difficulty" error actually reported which GPU caused the error. With multiple GPUs, how am I supposed to know exactly which one is causing the problem so I can tweak settings?