Did anyone have similar issue? I tried 1.7.9 but it just did not work.
The start.bat is like this: SRBMiner-CN.exe --enablecoinforking --config Config\config-normalv8.txt --pools pools.txt --logfile %LOGTIME%
Then I got these messages: [2019-03-02 14:50:01] Pool sent a new job (ID: EsT3qBkxMlv2gP5Ut8M+XRGst5JT) [normalv8] [2019-03-02 14:50:39] Pool sent a new job (ID: vYg30yr7ESz53hwvUGRkCnUIpYgn) [normalv8] [2019-03-02 14:50:43] Pool sent a new job (ID: icq/pwvRhBq6pd6/dQ8onFL3Enze) [normalv8] [2019-03-02 14:50:45] Warning: Too many compute errors -> GPU BUS_ID[1] (15) [2019-03-02 14:50:48] Warning: Too many compute errors -> GPU BUS_ID[1] (16) [2019-03-02 14:50:51] Warning: Too many compute errors -> GPU BUS_ID[38] (15) [2019-03-02 14:50:53] Warning: Too many compute errors -> GPU BUS_ID[34] (15) [2019-03-02 14:50:54] Warning: Too many compute errors -> GPU BUS_ID[1] (17) [2019-03-02 14:50:58] Warning: Too many compute errors -> GPU BUS_ID[38] (16) [2019-03-02 14:51:00] Warning: Too many compute errors -> GPU BUS_ID[1] (18) [2019-03-02 14:51:00] Warning: Too many compute errors -> GPU BUS_ID[34] (16) [2019-03-02 14:51:01] Pool difficulty: 6116 [2019-03-02 14:51:01] Pool sent a new job (ID: dT5RnimnnevJqgAMSnugDs3bqi6B) [normalv8] [2019-03-02 14:51:02] Warning: Too many compute errors -> GPU BUS_ID[1] (19) [2019-03-02 14:51:06] Warning: Too many compute errors -> GPU BUS_ID[1] (20) [2019-03-02 14:51:07] Warning: Too many compute errors -> GPU BUS_ID[1] (21) [2019-03-02 14:51:09] Warning: Too many compute errors -> GPU BUS_ID[1] (22)[/color] [2019-03-02 14:51:13] Pool sent a new job (ID: eQa+/CACHH+sNVKvzYDwjI7/kwo0) [normalv8] [2019-03-02 14:51:20] Warning: Too many compute errors -> GPU BUS_ID[34] (17) [2019-03-02 14:51:23] Warning: Too many compute errors -> GPU BUS_ID[1] (23) [2019-03-02 14:51:25] Warning: Too many compute errors -> GPU BUS_ID[38] (17) [2019-03-02 14:51:25] Warning: Too many compute errors -> GPU BUS_ID[1] (24) [2019-03-02 14:51:27] Warning: Too many compute errors -> GPU BUS_ID[1] (25)
|
|
|
I tried 1.7.9 but it just did not work.
The start.bat is like this: SRBMiner-CN.exe --enablecoinforking --config Config\config-normalv8.txt --pools pools.txt --logfile %LOGTIME%
Then I got these messages: [2019-03-02 14:50:01] Pool sent a new job (ID: EsT3qBkxMlv2gP5Ut8M+XRGst5JT) [normalv8] [2019-03-02 14:50:39] Pool sent a new job (ID: vYg30yr7ESz53hwvUGRkCnUIpYgn) [normalv8] [2019-03-02 14:50:43] Pool sent a new job (ID: icq/pwvRhBq6pd6/dQ8onFL3Enze) [normalv8] [2019-03-02 14:50:45] Warning: Too many compute errors -> GPU BUS_ID[1] (15) [2019-03-02 14:50:48] Warning: Too many compute errors -> GPU BUS_ID[1] (16) [2019-03-02 14:50:51] Warning: Too many compute errors -> GPU BUS_ID[38] (15) [2019-03-02 14:50:53] Warning: Too many compute errors -> GPU BUS_ID[34] (15) [2019-03-02 14:50:54] Warning: Too many compute errors -> GPU BUS_ID[1] (17) [2019-03-02 14:50:58] Warning: Too many compute errors -> GPU BUS_ID[38] (16) [2019-03-02 14:51:00] Warning: Too many compute errors -> GPU BUS_ID[1] (18) [2019-03-02 14:51:00] Warning: Too many compute errors -> GPU BUS_ID[34] (16) [2019-03-02 14:51:01] Pool difficulty: 6116 [2019-03-02 14:51:01] Pool sent a new job (ID: dT5RnimnnevJqgAMSnugDs3bqi6B) [normalv8] [2019-03-02 14:51:02] Warning: Too many compute errors -> GPU BUS_ID[1] (19) [2019-03-02 14:51:06] Warning: Too many compute errors -> GPU BUS_ID[1] (20) [2019-03-02 14:51:07] Warning: Too many compute errors -> GPU BUS_ID[1] (21) [2019-03-02 14:51:09] Warning: Too many compute errors -> GPU BUS_ID[1] (22)[/color] [2019-03-02 14:51:13] Pool sent a new job (ID: eQa+/CACHH+sNVKvzYDwjI7/kwo0) [normalv8] [2019-03-02 14:51:20] Warning: Too many compute errors -> GPU BUS_ID[34] (17) [2019-03-02 14:51:23] Warning: Too many compute errors -> GPU BUS_ID[1] (23) [2019-03-02 14:51:25] Warning: Too many compute errors -> GPU BUS_ID[38] (17) [2019-03-02 14:51:25] Warning: Too many compute errors -> GPU BUS_ID[1] (24) [2019-03-02 14:51:27] Warning: Too many compute errors -> GPU BUS_ID[1] (25)
Here is how it started. Everything is normal. Initializing OpenCL devices, please wait...
GPU0: Radeon RX 570 Series [ellesmere] [4096 MB][I: 58.0][W: 16][T: 2][F: 1][BUS: 34] GPU1: Radeon RX 570 Series [ellesmere] [4096 MB][I: 58.0][W: 16][T: 2][F: 1][BUS: 30] GPU2: Radeon RX 570 Series [ellesmere] [4096 MB][I: 58.0][W: 16][T: 2][F: 1][BUS: 31] GPU3: Radeon RX 570 Series [ellesmere] [4096 MB][I: 58.0][W: 16][T: 2][F: 1][BUS: 38] GPU4: Radeon RX 570 Series [ellesmere] [4096 MB][I: 58.0][W: 16][T: 2][F: 1][BUS: 1] GPU5: Radeon RX 570 Series [ellesmere] [4096 MB][I: 58.0][W: 16][T: 2][F: 1][BUS: 35]
-------------------------------------------------------------------------------------- SRBMiner Cryptonight AMD GPU miner 1.7.9 DevFee ~0.85%
Press 's' to display stats Press 'h' to display hashrate Press 'r' to reload pools Press 'p' to switch to the next pool Press 'o' to switch to the previous pool Press 0-9 to disable/enable GPU while mining --------------------------------------------------------------------------------------
Recommended drivers : Adrenalin 18.5.1, 18.5.2 or 18.6.1 Algorithm : Cryptonight V8 Algo switching : enabled Startup monitor : enabled Gpu watchdog : enabled [normal mode] Coin forking : enabled
[2019-03-02 14:47:40] Pools defined -> 2 [2019-03-02 14:47:40] Loading [normalv8] kernel for DEVICE BUS_ID[34] [2019-03-02 14:47:41] Loading [normalv8] kernel for DEVICE BUS_ID[34] [2019-03-02 14:47:41] Loading [normalv8] kernel for DEVICE BUS_ID[30] [2019-03-02 14:47:41] Loading [normalv8] kernel for DEVICE BUS_ID[30] [2019-03-02 14:47:41] Loading [normalv8] kernel for DEVICE BUS_ID[31] [2019-03-02 14:47:41] Loading [normalv8] kernel for DEVICE BUS_ID[31] [2019-03-02 14:47:41] Loading [normalv8] kernel for DEVICE BUS_ID[38] [2019-03-02 14:47:42] Loading [normalv8] kernel for DEVICE BUS_ID[38] [2019-03-02 14:47:42] Loading [normalv8] kernel for DEVICE BUS_ID[1] [2019-03-02 14:47:42] Loading [normalv8] kernel for DEVICE BUS_ID[1] [2019-03-02 14:47:42] Loading [normalv8] kernel for DEVICE BUS_ID[35] [2019-03-02 14:47:42] Loading [normalv8] kernel for DEVICE BUS_ID[35] [2019-03-02 14:47:42] ADL initialised successfully [2019-03-02 14:47:43] Connected to pool.supportxmr.com:7777 [2019-03-02 14:47:43] User logged in [2019-03-02 14:47:43] Pool difficulty: 25000 [2019-03-02 14:47:43] Pool sent a new job (ID: ak9BIZU8qQfFQVr7nfLNfO+v7KXw) [normalv8] [2019-03-02 14:47:46] Pool sent a new job (ID: s27C6DFowm1ldVC9wZtYaHALtpoh) [normalv8] [2019-03-02 14:49:01] Pool difficulty: 13761 [2019-03-02 14:49:01] Pool sent a new job (ID: V+ppzAaKSof9lJioBz+EmUKBCwvQ) [normalv8]
|
|
|
I checked and see that I only have the large eight card boards not the six card ones
Thanks. @philipma1957. I will wait to see if my motherboard can last longer. If it dies, I will try to change it by myself.
|
|
|
@philipma1957
Anyone still own ONDA D1800 mining motherboard? The heatsink on mine failed and almost stop working. Any idea where I can get parts or anyway to fix it? TIA
|
|
|
Thanks Livada. I used this table and the power consumption is 30w less with almost same hashrate. Let's see if it can be stable for a while. My cards are all reference cards with 64 bios so it may consumes more power I guess.
if you use GPU_P7=1552mz thi use more power. try with 1440mhz and see. my card use 70W more if i use 1500+mhz for 100hr and temp go up 3-4C Thanks for the information, Livada. I will leave it for a while to make sure that one is stable. To me, stability is more important.
|
|
|
I am using two PSUs with a combined 1900w. The PSU is fine but the breaker is tripped. I also use overdriventool so the power consumption is around 1250w which is not bad at all for monero v8. It is just every few days I got this power surge. And after this happens, I have to start the miner few times to get a 1250w cause the first few starts always get a 1900w power so i have to stop the miner and restarted it.
It could be your intensity or overclock to much. Sometimes a gpu may crash and reset to default settings. Which on vega will increase power a lot. If ppt mod this won't happen. Its not the software. Its your settings I would say It makes sense. Could you take a look at my overdriventool setting? It is a vega 56 with 64 bios. memeory is set to 1100. GPU_P0=852;800;0 GPU_P1=991;900;0 GPU_P2=1084;950;0 GPU_P3=1138;1000;0 GPU_P4=1200;1050;0 GPU_P5=1401;1100;0 GPU_P6=1536; 1150;0 GPU_P7=1552; 840Mem_P0=167;800;0 Mem_P1=500;800;0 Mem_P2=800; 950;0 Mem_P3=1100; 875Fan_Min=2750 Fan_Max=3500 Fan_Target=65 Fan_Acoustic=2400 Power_Temp=75 Power_Target=0 This is the v8 setting for miner. { "cryptonight_type" : "normalv8", "intensity" : 120, "worksize" : 16, "double_threads" : true } Your PPT tabvle is BAD. This is not good. USe this : 1130W form the WALL on v8 - i have 2*700W PSU only and all work fine with 6*vega 56 nitro+ GPU_P0=852;900;0 GPU_P1=991;900;0 GPU_P2=1084;900;0 GPU_P3=1138;900;0 GPU_P4=1150;900;0 GPU_P5=1202;900;0 GPU_P6=1212;900;0 GPU_P7=1442;900 Mem_P0=167;900;0 Mem_P1=500;900;0 Mem_P2=800;900;0 Mem_P3=1100;900 Fan_Min=2300 Fan_Max=4900 Fan_Target=56 Fan_Acoustic=2400 Power_Temp=75 Power_Target=0 or this for low consumation power GPU_P0=852;800;0 GPU_P1=991;801;0 GPU_P2=1084;802;0 GPU_P3=1100;803;0 GPU_P4=1125;804;0 GPU_P5=1150;805;0 GPU_P6=1212;830;0 GPU_P7=1442;850 Mem_P0=167;800;0 Mem_P1=500;800;0 Mem_P2=800;802;0 Mem_P3=1100;860 Fan_Min=2300 Fan_Max=3500 Fan_Target=55 Fan_Acoustic=2400 Power_Temp=75 Power_Target=0 Thanks Livada. I used this table and the power consumption is 30w less with almost same hashrate. Let's see if it can be stable for a while. My cards are all reference cards with 64 bios so it may consumes more power I guess.
|
|
|
I am pretty sure the power consumption isnt just 'growing' because of the miner, if that was the case then there would be reports of it already and a lot of dead rigs  Please, do not get me wrong. I think it is a great miner and I am using it for months. The other guy mentioned it may be the setting issue and i believe it makes sense. Could you take a look at the settings?
|
|
|
I am using two PSUs with a combined 1900w. The PSU is fine but the breaker is tripped. I also use overdriventool so the power consumption is around 1250w which is not bad at all for monero v8. It is just every few days I got this power surge. And after this happens, I have to start the miner few times to get a 1250w cause the first few starts always get a 1900w power so i have to stop the miner and restarted it.
It could be your intensity or overclock to much. Sometimes a gpu may crash and reset to default settings. Which on vega will increase power a lot. If ppt mod this won't happen. Its not the software. Its your settings I would say It makes sense. Could you take a look at my overdriventool setting? It is a vega 56 with 64 bios. memeory is set to 1100. GPU_P0=852;800;0 GPU_P1=991;900;0 GPU_P2=1084;950;0 GPU_P3=1138;1000;0 GPU_P4=1200;1050;0 GPU_P5=1401;1100;0 GPU_P6=1536;1150;0 GPU_P7=1552;840 Mem_P0=167;800;0 Mem_P1=500;800;0 Mem_P2=800;950;0 Mem_P3=1100;875 Fan_Min=2750 Fan_Max=3500 Fan_Target=65 Fan_Acoustic=2400 Power_Temp=75 Power_Target=0 This is the v8 setting for miner. { "cryptonight_type" : "normalv8", "intensity" : 120, "worksize" : 16, "double_threads" : true }
|
|
|
Hello Doktor. Is there any changes in 1.7.4 on heavy algo - 580 8gb (ellesmere)? With v1.7.2 - 1250+ With v1.7.4 - 1000-  Nothing has changed you should have the same speed or maybe a few hashes more. To doctor83:
Thanks doctor this is an awesome miner. However, I have a problem with my 6x Vega 56 rig. Every a few days, 2 or 3 days actually, the miner seemed to reach to a very high power consumption and the power surge tripped the breaker. It happened a few times so it does not look like an accident. Any idea how this could happen? TIA.
Maybe your PSU is weak for 6 vegas + algo you are using ? You should probably tune your cards with PPT and overdriventtool if you haven't done so yet. I am using two PSUs with a combined 1900w. The PSU is fine but the breaker is tripped. I also use overdriventool so the power consumption is around 1250w which is not bad at all for monero v8. It is just every few days I got this power surge. And after this happens, I have to start the miner few times to get a 1250w cause the first few starts always get a 1900w power so i have to stop the miner and restarted it.
|
|
|
To doctor83:
Thanks doctor this is an awesome miner. However, I have a problem with my 6x Vega 56 rig. Every a few days, 2 or 3 days actually, the miner seemed to reach to a very high power consumption and the power surge tripped the breaker. It happened a few times so it does not look like an accident. Any idea how this could happen? TIA.
|
|
|
Here is my rig with 6x 470 4gb. Is this normal for a 470 at 800ish hashrate?
[2018-12-24 12:30:37] GPU0 : 818 H/s [T: 51c, RPM: 1916, CC: 1140 MHz, MC: 2050 MHz][BUS:8] [2018-12-24 12:30:37] GPU1 : 818 H/s [T: 52c, RPM: 1921, CC: 1140 MHz, MC: 2050 MHz][BUS:3] [2018-12-24 12:30:37] GPU2 : 816 H/s [T: 51c, RPM: 1982, CC: 1140 MHz, MC: 2050 MHz][BUS:7] [2018-12-24 12:30:37] GPU3 : 816 H/s [T: 47c, RPM: 1900, CC: 1140 MHz, MC: 2050 MHz][BUS:5] [2018-12-24 12:30:37] GPU4 : 818 H/s [T: 49c, RPM: 1870, CC: 1140 MHz, MC: 2050 MHz][BUS:6] [2018-12-24 12:30:37] GPU5 : 817 H/s [T: 44c, RPM: 1921, CC: 1140 MHz, MC: 2050 MHz][BUS:1]
|
|
|
This is strange. I added a 580 in rig and one gpu is the rig just did not work well.
[2018-12-24 11:45:40] GPU0 : 915 H/s [T: 53c, RPM: 2105, CC: 1155 MHz, MC: 2050 MHz][BUS:1] [2018-12-24 11:45:40] GPU1 : 927 H/s [T: 56c, RPM: 2555, CC: 1155 MHz, MC: 2050 MHz][BUS:5] [2018-12-24 11:45:40] GPU2 : 939 H/s [T: 46c, RPM: 1801, CC: 1155 MHz, MC: 2050 MHz][BUS:7] [2018-12-24 11:45:41] GPU3 : 929 H/s [T: 57c, RPM: 2581, CC: 1155 MHz, MC: 2050 MHz][BUS:8] [2018-12-24 11:45:41] GPU4 : 601 H/s [T: 54c, RPM: 2539, CC: 1155 MHz, MC: 2050 MHz][BUS:11]
I set the compute mode and they are use the same driver. Anyone get any idea what is happening? TIA.
better to restart win) I actually did. did not help. Update: I restarted the third time and everything is working now... Thanks a lot!
|
|
|
This is strange. I added a 580 in rig and one gpu is the rig just did not work well.
[2018-12-24 11:45:40] GPU0 : 915 H/s [T: 53c, RPM: 2105, CC: 1155 MHz, MC: 2050 MHz][BUS:1] [2018-12-24 11:45:40] GPU1 : 927 H/s [T: 56c, RPM: 2555, CC: 1155 MHz, MC: 2050 MHz][BUS:5] [2018-12-24 11:45:40] GPU2 : 939 H/s [T: 46c, RPM: 1801, CC: 1155 MHz, MC: 2050 MHz][BUS:7] [2018-12-24 11:45:41] GPU3 : 929 H/s [T: 57c, RPM: 2581, CC: 1155 MHz, MC: 2050 MHz][BUS:8] [2018-12-24 11:45:41] GPU4 : 601 H/s [T: 54c, RPM: 2539, CC: 1155 MHz, MC: 2050 MHz][BUS:11]
I set the compute mode and they are use the same driver. Anyone get any idea what is happening? TIA.
|
|
|
So i have some issues with one rx 480. Sometimes everything works with it running at 900 h/s. Most times it is running at 650 h/s, with or without video cable on it. What could be the issue? Anyone has similar problem? TIA.
|
|
|
That actually is pretty good. V8 is much more power hungry. Your power is 208 watts per Vega 56. My seven average 225 watts. Can you provide what your Core P6/P7 frequency/mv are set to and the MEM_P3 frequency/mv is. Thanks Here you go. GPU_P0=852;800;0 GPU_P1=991;900;0 GPU_P2=1084;950;0 GPU_P3=1138;1000;0 GPU_P4=1200;1050;0 GPU_P5=1401;1100;0 GPU_P6=1536;1150;0 GPU_P7=1552;840 Mem_P0=167;800;0 Mem_P1=500;800;0 Mem_P2=800;950;0 Mem_P3=1100;875 Fan_Min=2750 Fan_Max=3500 Fan_Target=65 Fan_Acoustic=2400 Power_Temp=75 Power_Target=0
|
|
|
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 !~!
Did you bios mod your cards? Did you use soft power play table? XMR-stak did not work anymore for me so I am trying to use srbminer now. Any link or pointer would be appreciated.
|
|
|
Anyone has idea how to use SRBMiner to run vega 56 flashed with 64 bios? I only found guide for vega 64. Thanks.
|
|
|
You can install Anydesk which is a free software and does not limit you like Teamviewer does after a certain number of connections. Setup an unattended password and you remotely login to your rig at anytime, there is no problem if your client PC is updated and the remote one is not. Anydesk software does not care about this.
Wow Anydesk is great. Thanks!
|
|
|
|