Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[TigTex]

I didn't get the chance to set original ROM but I did remove overclock. Not only it didn't help but it got worse! In fact, while I was trying different OC settings I noticed that the lower I was setting my clocks, the more unstable my rig became.

My rig usually freezes after a GPU hangs or after a share gets rejected. The clocks I am using and the ROM I am using have been stable for months now with previous drivers and miner version

One more thing I have noticed is that after a rig restart (following a freeze) the miner starts, the clocks and voltages are being set normally but I get~ 3.5% less performance than usual. Once I restart the miner it gets back at 100%. Does anyone else have the same issue?

Me. And I have to completly shutdown the computer (PSU switch) for that to stop happening.
Also, I've set the default rom, just for testing, without any OC. I still get invalid shares on ethereum and a warning to check my overclock. (eu1.ethermine.org)


In case anyone is having the issue with rx500 series gpu's that can't reduce voltage below +/-0.9v, that is caused by the VRAM voltage. So if you have your vram at 2000mhz @ 1v, your core won't go any lower than 1v (under load, it drops a little). Because the default vram voltage on my sapphire rx580 4gb pulse is 950mv, the lowest possible voltage is 950mv. So, I did this:

-Download OverdriveNTool from guru3d foruns.
-Disable ALL P-States on memory and core except the higher state. (to disable click on P0, P1, P2,...)
-Set your gpu clock frequency and desired voltage on the last P state (P7). My example: 1250MHZ @ 900mv
-Set your ram clock frequency and the same voltage as your gpu on last P state (P2). My example: 2050mhz @ 900mv
-Save and give a name to that profile. My example: "2050"
-Now put overdriveNtool on the same folder as your "start.bat".
-Edit your .bat file and remove all overclock options from the claymore miner and add this before starting the miner:

Code:

OverdriveNTool.exe -r0 -r1 -r2 -r3 -r4 -p0"0" -p1"2050" -p2"2050" -p3"2050" -p4"2050"
timeout 5

That will reset the cards, apply the profile named "2050" to gpu0+1+2+3+4 and wait 5 seconds before starting claymore.
Enjoy your lower power consuption. Make sure that you tweak the dcri value if you change your gpu clock. Higher clock = higher dcri

Are you doing this on Blockchain drivers?

Yes I am 

[Odetas]

Curious if anyone has actually tested vs Genoil and the claims of much higher hash rates

[NavyCuda]

I'm running the aug. 11 Radeon Pro public beta for Vega FE.

I was running blockchain drivers but they require too much cvddc and the hbm2 gets over 80C and starts to throttle.

An earlier reading from the wall suggested 511w but that was with my previous power supply which was in the process of dying and a much higher cvddc setting.  Setting of 1050, where with the aug 11 vega fe beta drivers I can run cvddc at 950.

[badfad]

Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?

Well my findings are the opposite, vega 56 with moded bios can do 42-43Mhs. I can't measure the power consumption. Also the 64bios can let you clock the memory on the 56 to 1100Mhz.
Dual-mining  works fine with all drivers.

Setting lower voltages in wattman seems to lower the power consumtion, but I relly can't test much without a damned watt-o-meter.

[Lontonbit]

Hey, I connected a rx 480 to a PCI slot. Not pcie. It smoked! Now my card is not recognized. I've tried in different pc's. Is there a fuse or capacitor that might have blown on the cards board?

[stannicek]

Hello.

With GTX 1070 I got strange errors after some time (very random) :

08:02:50:826   d98   parse packet: 247
08:02:50:826   d98   ETH: job is the same
08:02:50:826   d98   new buf size: 0
08:02:55:248   14ec   GPU 4, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:248   14ec   GPU 4, GpuMiner kx failed 1
08:02:55:248   14ec   Set global fail flag, failed GPU4
08:02:55:248   14ec   GPU 4 failed
08:02:55:248   1b40   GPU 4, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:248   1b40   GPU 4, GpuMiner kx failed 1
08:02:55:248   1b40   Set global fail flag, failed GPU4
08:02:55:248   1b40   GPU 4 failed
08:02:55:264   d70   GPU 7, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:264   d70   GPU 7, GpuMiner kx failed 1
08:02:55:264   d70   Set global fail flag, failed GPU7
08:02:55:264   dbc   GPU 6, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:264   dbc   GPU 6, GpuMiner kx failed 1
08:02:55:264   dbc   Set global fail flag, failed GPU6
08:02:55:264   d70   GPU 7 failed
08:02:55:264   dbc   GPU 6 failed
08:02:55:264   17c4   GPU 6, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:264   17c4   GPU 6, GpuMiner kx failed 1
08:02:55:264   11a4   GPU 7, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:264   17c4   Set global fail flag, failed GPU6
08:02:55:264   17c4   GPU 6 failed
08:02:55:264   11a4   GPU 7, GpuMiner kx failed 1
08:02:55:264   11a4   Set global fail flag, failed GPU7
08:02:55:264   11a4   GPU 7 failed
08:02:55:295   1b20   GPU 2, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:295   1b20   GPU 2, GpuMiner kx failed 1
08:02:55:295   1b20   Set global fail flag, failed GPU2
08:02:55:295   1b20   GPU 2 failed
08:02:55:295   1b24   GPU 2, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:295   1b24   GPU 2, GpuMiner kx failed 1
08:02:55:295   1b24   Set global fail flag, failed GPU2
08:02:55:295   1b24   GPU 2 failed
08:02:55:311   1124   GPU 3, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:311   1124   GPU 3, GpuMiner kx failed 1
08:02:55:311   1124   Set global fail flag, failed GPU3
08:02:55:311   1124   GPU 3 failed
08:02:55:311   1b28   GPU 3, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:311   1b28   GPU 3, GpuMiner kx failed 1
08:02:55:311   1b28   Set global fail flag, failed GPU3
08:02:55:311   1b28   GPU 3 failed
08:02:55:311   17e4   GPU 0, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:311   17e4   GPU 0, GpuMiner kx failed 1
08:02:55:326   17e4   Set global fail flag, failed GPU0
08:02:55:326   17e4   GPU 0 failed
08:02:55:326   1b38   GPU 0, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:326   1b38   GPU 0, GpuMiner kx failed 1
08:02:55:326   1b38   Set global fail flag, failed GPU0
08:02:55:326   1b38   GPU 0 failed
08:02:55:326   12bc   GPU 5, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:326   12bc   GPU 5, GpuMiner kx failed 1
08:02:55:326   12bc   Set global fail flag, failed GPU5
08:02:55:326   12bc   GPU 5 failed
08:02:55:326   17b0   GPU 5, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:326   17b0   GPU 5, GpuMiner kx failed 1
08:02:55:326   17b0   Set global fail flag, failed GPU5
08:02:55:326   17b0   GPU 5 failed
08:02:55:342   17e0   GPU 1, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:342   17e0   GPU 1, GpuMiner kx failed 1
08:02:55:342   17e0   Set global fail flag, failed GPU1
08:02:55:342   17e0   GPU 1 failed
08:02:55:342   ab8   GPU 1, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:342   ab8   GPU 1, GpuMiner kx failed 1
08:02:55:342   ab8   Set global fail flag, failed GPU1
08:02:55:342   ab8   GPU 1 failed


Strange is, that all GPU fails at once. I'm using Nvidia 384.94 drivers.

Any suggestions?

[dukemc]

I would say thanks to Claymore for his work on the Claymore Miner and the possibilty do monitoring the Miner with the intgerated tool. Good Work!

[NewbieMiner17]

Hey guys my first post here!

I've installed the new blockchain driver on my RX480 Nitro+ 4GB and having the cards running at around 25Mh for all 6 cards (thanks to Memshift Rom file from Anoraks. The readings on Claymore itself are coming up as 0 for all fans and GPU temps (GPU0 t=0C fan=0%, GPU1 t0c fan=0%.... etc) but I'm getting readings no problem from afterburner. Currently one of the GPUs is running at a steady 80C where as the rest of the cards are running at a steady 65C (all fans running at 100% due to GPU2).
I've applied the following settings to try and regulate the temperature through claymore but would they be working if all the information displayed on claymore is 0?

-tt 75 -ttdcr 79 -ttli 81 -tstop 85

1) Is it safe to run at this temperature or should I stop it until I get a fix?
2) How can I have claymore display the correct temperatures (is it the anorak bios that is affecting it?)
3) Does anyone have another bios they recommend instead of anorak? I've tried their overclocked bios but as soon as dual mining is turned on it goes over 1200w and my PSU restarts. 

[Ursul0]

In case anyone is having the issue with rx500 series gpu's that can't reduce voltage below +/-0.9v, that is caused by the VRAM voltage. So if you have your vram at 2000mhz @ 1v, your core won't go any lower than 1v (under load, it drops a little). Because the default vram voltage on my sapphire rx580 4gb pulse is 950mv, the lowest possible voltage is 950mv. So, I did this:

this is not a problem of rx 5** series exclusively. rx4* have the same limitation: the core voltage is tied to VRM voltage (btw NOT memory voltage, which is always about 1v but only the mem controller as Wolf0 insists) also setting vrm offsets may help if available

[Ursul0]

I've installed the new blockchain driver on my RX480 Nitro+ 4GB and having the cards running at around 25Mh for all 6 cards (thanks to Memshift Rom file from Anoraks. The readings on Claymore itself are coming up as 0 for all fans and GPU temps (GPU0 t=0C fan=0%, GPU1 t0c fan=0%.... etc) but I'm getting readings no problem from afterburner. Currently one of the GPUs is running at a steady 80C where as the rest of the cards are running at a steady 65C (all fans running at 100% due to GPU2).
I've applied the following settings to try and regulate the temperature through claymore but would they be working if all the information displayed on claymore is 0?

you should be getting 28MH ETH & 650MH DCR at least at about 850mv with 1080:2000 clocks.
These are all 470s: 1*Nitro+, 3*Nitro, 1*Ref


EDIT: also 80 is too high and 100% fans is too much... give more free airflow to your setup
EDIT2: and don't use AB, better try not to install it EVER

[NewbieMiner17]

I've installed the new blockchain driver on my RX480 Nitro+ 4GB and having the cards running at around 25Mh for all 6 cards (thanks to Memshift Rom file from Anoraks. The readings on Claymore itself are coming up as 0 for all fans and GPU temps (GPU0 t=0C fan=0%, GPU1 t0c fan=0%.... etc) but I'm getting readings no problem from afterburner. Currently one of the GPUs is running at a steady 80C where as the rest of the cards are running at a steady 65C (all fans running at 100% due to GPU2).
I've applied the following settings to try and regulate the temperature through claymore but would they be working if all the information displayed on claymore is 0?

you should be getting 28MH ETH & 650MH DCR at least at about 850mv with 1080:2000 clocks.
These are all 470s: 1*Nitra+, 3*Nitra, 1*Ref
https://s26.postimg.org/uvpt6ngg9/nitrz47.png

EDIT: also 80 is too high and 100% fans is too much... give more free airflow to your setup

Thanks but there is around half a meter minimum either side of the rig and in a fairly big area... What Bios are you running? I'm mining ETH and SIA with 25 on ETH and 750Mh on Sia. Any idea why I'm getting 0 readings from Claymore?

[Ursul0]

Thanks but there is around half a meter minimum either side of the rig and in a fairly big area... What Bios are you running? I'm mining ETH and SIA with 25 on ETH and 750Mh on Sia. Any idea why I'm getting 0 readings from Claymore?

space is not the key - air exchange is, make the air flow in.
you probably have some issues with APIs accesss, drivers and shitty stuff like AB.
do uninstall of AB, do DDU, setup drivers manually: point+click in device manager for blockchain beta driver folder (don't run amd EXE), patch signature, mod bois, run claymore 9.8+ = enjoy

[NewbieMiner17]

Thanks but there is around half a meter minimum either side of the rig and in a fairly big area... What Bios are you running? I'm mining ETH and SIA with 25 on ETH and 750Mh on Sia. Any idea why I'm getting 0 readings from Claymore?

space is not the key - air exchange is, make the air flow in.
you probably have some issues with APIs accesss, drivers and shitty stuff like AB.
do uninstall of AB, do DDU, setup drivers manually: point+click in device manager for blockchain beta driver folder (don't run amd EXE), patch signature, mod bois, run claymore 9.8+ = enjoy

So AB is that bad aye? OK on the uninstal and Display Driver Uninstaller. I originally ran the express install for the crimson blockchain driver... How would I do the point and click installation instead?  Patch signature ok. What are you using to Mod the bios? I have 0 experience in it so wasn't comfortable moding ( which is why I chose to go with anorak bios). Sorry if dumb questions but trying to not make a mess of this

[fmz89]

Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?

Well my findings are the opposite, vega 56 with moded bios can do 42-43Mhs. I can't measure the power consumption. Also the 64bios can let you clock the memory on the 56 to 1100Mhz.
Dual-mining  works fine with all drivers.

Setting lower voltages in wattman seems to lower the power consumtion, but I relly can't test much without a damned watt-o-meter.

vega 56 43.7 mhs 155watt at the wall, 1600 hs xmr

[notbatman]

Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?

Well my findings are the opposite, vega 56 with moded bios can do 42-43Mhs. I can't measure the power consumption. Also the 64bios can let you clock the memory on the 56 to 1100Mhz.
Dual-mining  works fine with all drivers.

Setting lower voltages in wattman seems to lower the power consumtion, but I relly can't test much without a damned watt-o-meter.

vega 56 43.7 mhs 155watt at the wall, 1600 hs xmr

Gonna have to do better than that, I'll get more RX460s and stack 'em!

[fmz89]

Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?

mining monero with vega 56 better profit than dual mine and more stable

[fmz89]

Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?

Well my findings are the opposite, vega 56 with moded bios can do 42-43Mhs. I can't measure the power consumption. Also the 64bios can let you clock the memory on the 56 to 1100Mhz.
Dual-mining  works fine with all drivers.

Setting lower voltages in wattman seems to lower the power consumtion, but I relly can't test much without a damned watt-o-meter.

vega 56 43.7 mhs 155watt at the wall, 1600 hs xmr

Gonna have to do better than that, I'll get more RX460s and stack 'em!

yeah maybe waiting 2000 hs on monero with strap, at this price, its equal with dual rx 470, with same price/speed,

[Demarsac]

Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?

mining monero with vega 56 better profit than dual mine and more stable

What is Vega 56 give on stock clocks for ETH?
I understand your ~43 MH/s is with OC'ed Vega right?

[fmz89]

Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?

mining monero with vega 56 better profit than dual mine and more stable

What is Vega 56 give on stock clocks for ETH?
I understand your ~43 MH/s is with OC'ed Vega right?

43mhs at 932 mhz,
default stock vega 56 (bios 64) its 1630 mhz,
massive underclocked

[Demarsac]

Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?

mining monero with vega 56 better profit than dual mine and more stable

What is Vega 56 give on stock clocks for ETH?
I understand your ~43 MH/s is with OC'ed Vega right?

43mhs at 932 mhz,
default stock vega 56 (bios 64) its 1630 mhz,
massive underclocked

Thanks

Do you remember when it was stock how much ETH Hash did it give you before you bios modded it?
And how much Power consumption?