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

[npittas]

You have output video on your cards or your internal gpu?

This is my test bench machine with 1 GPU only. The output is directly from my GPU HDMI.

So besides that AfterBurner issue, what is your experience concerning the EPOCH hashrate drop? Did they fixed that on the current driver?

I managed to overclock my card to 2000, but I haven't restarted the miner since, so I may have a lock screen on DAG generation. I cannot confirm yet since I am away and playing with teamviewer, so if the PC freezes I won't be able to restart it. Still waiting for my smartplug from Amazon. This is not bad but I do not think this is a DAG resolving release. I was at 27.3 before, I am at 27.5 now but with 50Mhz more in memory clock, that could be the only factor raising my Hashrate. I would not recommend this release yet, since without Afterburner, I cannot check the same settings and be definite about any opinion.

Claymore and Wolf0 should be the ones to really answer this question, since they have the real means to test bench this release.

[int64]

Does anybody tries new driver? Does this drivers fixed problem with droping hash because of Dag? I am not shure exactly what version of driver should fix this

[preda]

Does anybody tries new driver? Does this drivers fixed problem with droping hash because of Dag? I am not shure exactly what version of driver should fix this

I heard that new 17.7.2 drivers they are very good for mining...
I didn't tried yet coz i am still using old 16.9.2 they are very good
Who tried out new drivers?

[npittas]

Read my answer a few replies ago about the new driver. Waiting for Claymore to confirm though.

[kkourmousis]

Besides, I expect a pretty big difficulty spike by the time a fix gets released.

So judging from the difficulty alone -even thought it may be a bit early to do that- should give us an idea that no, it does not fix the hashrate drop problem

[TechPark]

Does anybody tries new driver? Does this drivers fixed problem with droping hash because of Dag? I am not shure exactly what version of driver should fix this

I heard that new 17.7.2 drivers they are very good for mining...

Could you please provide the link to the source... Otherwise it's BS

[TechPark]

Who's gonna ban me? You? Jesus, I thought Claymore was sometimes a little pissy, but you're a bona fide dick.

I think he was talking to me.  Though I'm not sure why I would get banned for talking about a video card I have, that I'm looking forward to claymore's miner supporting.

Both of you. Does it not make sense to talk about Vega in a separate thread? I read all your posts and there was nothing about Claymore in it. Are you not get pissed off when you see a lot of rubbish around?

Who bans? There are moderators. And you will find it out rather soon

[cscheat]

DAG 136 and so far no fix for Polaris, everytime dag increases Nvidia fanboys make a party hehe

every week 1 party for nvidia fanboys

[BlackPrapor]

I wonder if anyone else is having same issues as me. Today the hash rate dropped on all my rigs, while they were mining on same DAG, no restarts no settings changes, nothing. Just dropped the hash rate from 816Mhs, to 806Mhs, and from 464Mhs to 458Mhs on the other address. 16Mhs lost out of 1280Mhs (1.25% exactly). I'm using claymore 9.7 and Crimson 16.12.2. Hash rate dropped on all RX480/470 cards, and not on R290 card.

[woodaxe]

Who's gonna ban me? You? Jesus, I thought Claymore was sometimes a little pissy, but you're a bona fide dick.

I think he was talking to me.  Though I'm not sure why I would get banned for talking about a video card I have, that I'm looking forward to claymore's miner supporting.

Both of you. Does it not make sense to talk about Vega in a separate thread? I read all your posts and there was nothing about Claymore in it. Are you not get pissed off when you see a lot of rubbish around?

Who bans? There are moderators. And you will find it out rather soon

 leave it out techpark we are all interested in the vega card and anything said on here will help build up
knowledge of the card  if the thread was strictly adhered too they would be less than 100 pages

[jimmykl]

what is causing these weird gaps and other colors to load in the claymore console?

You are overclocking too much!

Open an explorer window or blank notepad file (anything white) and you'll see the screen full of artifacts.

Reduce your overclock until you don't get them.

[Msobh]

DAG 136 and so far no fix for Polaris, everytime dag increases Nvidia fanboys make a party hehe

every week 1 party for nvidia fanboys

GOD help the RX AMD miners . HEEEEEEEEEEELLLLLLLLLLLPPPPPPPPPPP we are drowning drowning drowning LOL

[kkourmousis]

Simple - Claymore's miner cannot set MVDDC, and if it actually was putting the GDDR5 at 850mV, it likely would barely function at all...

So I guess this is obsolete?

-mvddc   set target GPU memory voltage, multiplied by 1000. For example, "-mvddc 1050" means 1.05V. You can also specify values for every card, for example "-mvddc 900,950,1000,970". Supports latest AMD 4xx cards only in Windows.
   Note: for NVIDIA cards this option is not supported.

[sir4o]

Simple - Claymore's miner cannot set MVDDC, and if it actually was putting the GDDR5 at 850mV, it likely would barely function at all...

So I guess this is obsolete?

-mvddc   set target GPU memory voltage, multiplied by 1000. For example, "-mvddc 1050" means 1.05V. You can also specify values for every card, for example "-mvddc 900,950,1000,970". Supports latest AMD 4xx cards only in Windows.
   Note: for NVIDIA cards this option is not supported.

For older GPUs, some support it via ADL. Claymore's miner will tell ADL to set it... and ADL ain't setting shit.

For me it works but I followed someone's advice (like 10-15 pages before this one): you need to use -mclock in order -mvddc to kick in. I can add that in order to use -mclock in claymore effectively, the GPU needs to be running at lower frequency before starting it (i think this was in the official docs on page 1).

[Harry5555]

Guys, I just tried the new AMD crimson driver 17.7.2, I would recomend to not update, it breaks compability, It's not possible to adjust anything other than the fan speed in 3rd party overclocking software such as Msi afterburner which is what I am using.

Nor does the claymore miner detect the temperature and fan speed anymore.

My GPU is a RX480 for anyone who wonders.

Best regards
Harry

[Valgard19]

Guys, I just tried the new AMD crimson driver 17.7.2, I would recomend to not update, it breaks compability, It's not possible to adjust anything other than the fan speed in 3rd party overclocking software such as Msi afterburner which is what I am using.

Nor does the claymore miner detect the temperature and fan speed anymore.

My GPU is a RX480 for anyone who wonders.

Best regards
Harry

Yeah i have the same problem, i go back to 17.7.1

[platitude]

rx580 cards + 17.7.2 driver + calymore 9.7 not possible to set the core/memory clock, voltage and fans. MSI Afterburner: core and memory not possible to set at all (it reverts back to 0)

[npittas]

Try if you want to change the memory/GPU clock from Wattman (AMD settings) and see if you see any improvement on the hashrate before you go back to any previous drivers. That way we could compare and see any improvement on the driver's DAG issue

[Harry5555]

Try if you want to change the memory/GPU clock from Wattman (AMD settings) and see if you see any improvement on the hashrate before you go back to any previous drivers. That way we could compare and see any improvement on the driver's DAG issue

I don't think this driver (17.7.2) does solve the DAG issue, it's probably the next driver that will do that. It should be released in the near coming weeks.

I will go back to 17.7.1 for now.

Edit: I played around a bit with the memory clock, There isn't much of a difference.

[Culture]

Try if you want to change the memory/GPU clock from Wattman (AMD settings) and see if you see any improvement on the hashrate before you go back to any previous drivers. That way we could compare and see any improvement on the driver's DAG issue

I tried it on my rig with BIOS-coded clocking (not setting clocks via Claymore, wattman, or anything else) and it performs equally to 16.9.2, excepting the above mentioned issue with fan speed and temperatures registering in Claymore.

When I say equally, I mean Sapphire RX 480 Nitro+ OC's running at 27.8-28.1 Mh/s ETH, 800-820 Mh/s DCR  (DCRI 29) which is what they were running with this new epoch 136(2.06GB).