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

[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).

[1713994121]

1713994121

[1713994121]

1713994121

[1713994121]

1713994121

[1713994121]

1713994121

[Piradoxlanieve]

The drivers will be compatible with bios mod? In a month and a half I went from 180mh / s to 166mh/s
on rx480 and rx580 nitro oc 8GB

As I said before, AMD is going to fix the DAG issue for both Vega and Polaris, and new drivers will be available soon.

[Culture]

The drivers will be compatible with bios mod? In a month and a half I went from 180mh / s to 166mh/s
on rx480 and rx580 nitro oc 8GB

You need to use the PixelClockPatcher (to sign the bios), but other than that, yes - the driver is compatible with bios mods, and also works with up to 8 GPUs without "mixing."

[BlackPrapor]

The drivers will be compatible with bios mod? In a month and a half I went from 180mh / s to 166mh/s
on rx480 and rx580 nitro oc 8GB

As I said before, AMD is going to fix the DAG issue for both Vega and Polaris, and new drivers will be available soon.

Weird, mine went from 178 to 172. I hope AMD does fix this soon, otherwise I would have to....omg, mine another coin. What a tragedy  

[BigHashMiner]

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.

i think i have it sable at +650 on the mem clock. anything above that and i was getting crazy colors all over the screen and the system was non rsponsive. at +650 on these cards it seems right on the money for stability.

looking at the cmd prompt right now there are no gaps or color issues, its looking regular. it just come and goes it looks like.

[boysie]

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

Agreed same here, back on 17.7.1 with all working again.

[Ursul0]

...and if it actually was putting the GDDR5 at 850mV, it likely would barely function at all...

why would you say that? I've got lots of 470s running at 850mv just fine.

also what's with the hashrate degradation? is it really fixable(will be) by drivers update?

[Tarv]

It depends on GPU, settings, selected coin, it's price and net diff. For example, for SIA on stock 1070 ccminer shows 1400MH/s. In dual mode in v9.7 I get 650MH/s SIA (so 45% of pure SIA speed) with only 2% ETH lost (about 25.8MH/s instead of 26.4MH/s).
DCR speed is not so good, agreed.

After seeing this comment I spent some time today testing my 1070's with different -dcri settings.  I wasn't getting anywhere near that SC hash.  About 30.6mh/s eth and 309mh/s sia with default -dcri 30.

While testing on my main PC, I came to the conclusion that a -dcri 60 was about the best trade off for loss of ETH hash vs. gains of SC hash.  I was now getting around 29.5mh/s eth and 660mh/s sia.

I moved these new settings to the mining rig and the ETH hash just tanked.  Checking around I noticed that the cards wanted to draw more power with this new -dcri setting.  The 1070's in my rig are overclocked and the power was decreased.  Originally when I set up the rig, I tested the miner with ETH only and found I could get away with 75% power on the cards with no change to hash.

Increasing the -dcri seems to require more power.  I tried pushing the power to 112% and the hash rates just flew.  29.6mh/s and 693mh/s respectively.

Seems like quite a lot more power for that extra SIA hash.  Just posting as it's something people might want to consider.

TL;DR

-dcri 30, 75% power = 30.6mh/s eth, 307mh/s sia
-dcri 30, 112% power = 30.9mh/s eth, 309mh/s sia

-dcri 60, 75% power = 24.5mh/s eth, 490mh/s sia
-dcri 60, 112% power = 29.6mh/s eth, 693mh/s sia

Did you try experimenting with core clocks while dual mining?  I found 75dcri with a higher core clock for my 1070's gave me higher results for both ETH/SIA at the cost of even more power.  In the end I just decided dual mining wasnt worth the added power, heat, and stress along with the 2% eth tax.

I didn't this time, but as before I found that core didn't really effect ETH hash.  I had my core underclocked to reduce power/heat.

Good point about the extra tax, especially since I was running with low SIA hash.  Will have to think about it some more.

On the other hand, mining on my main PC I don't mind power/heat so I'll be playing with my OC's a bit more.

[P00P135]

Nice 1billion+ memory errors 

[Piradoxlanieve]

my rig: http://subefotos.com/ver/?d32676a7bb2f0bde552d6dfc13e03d37o.jpg
rx580--clock 1130 and memory 2100mhz fan 50-60%
rx480 --clock 1130 and memory 2060mhz 60-70%

[Ursul0]

Nice 1billion+ memory errors  

if you refer to my pic above, I assure you it means nothing on ethash, as long as you don't get invalid shares.
I'd guess that all these are read errors being fixed in real time...
(EDIT: hynix mem with 1500 straps)

[Ursul0]

...and if it actually was putting the GDDR5 at 850mV, it likely would barely function at all...

why would you say that? I've got lots of 470s running at 850mv just fine.

Believe me or don't - there's no I2C control on ANY of the RX series I've found (and I've got likely a majority of the models out, at least one.) I even wrote a toolset for very low-level (direct) VRM control on Linux. I2C bus confirms you ain't got shit that is controllable that is feeding MVDDC. On the other paw, my ASUS Direct CU II 290X has an IR3567B for the core - main loop feeds core, other one not active - but ALSO if you poke the bus, you'll find a friendly uP1801 (or similar) that feeds the memory.

Ghmm.... I'm not really sure what your claim here is, besides probably being educationally precise and insisting that VRM voltage should not be called memory voltage:)

[teru]

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

Agreed same here, back on 17.7.1 with all working again.

Me too.And the claymore's cvddc and mvddc options don't seem to be available.

[kkourmousis]

On the other paw

lmao hahaha 

VRM voltage should not be called memory voltage:)

Well that would explain our confusion

[cashen]

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

Agreed same here, back on 17.7.1 with all working again.

Me too.And the claymore's cvddc and mvddc options don't seem to be available.

I had the same issue. WattTool would not work. HAd to use WattMan which was slower than slow. went back to my trusty 16.5 or whatever it is.

[ayiphelmy]

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

Agreed same here, back on 17.7.1 with all working again.

Me too.And the claymore's cvddc and mvddc options don't seem to be available.

I had the same issue. WattTool would not work. HAd to use WattMan which was slower than slow. went back to my trusty 16.5 or whatever it is.

16.3 or 16.9.2 the best

[MinerosYV]

Thats' BS, Vega will probably be around 750-800 USD.

I'm shooting at $400. if performance is lower than 1080 then $400 is the maximum it will cost.

RX580 is $400 nowdays...

RX580 MSRP is not $400 and if RXVega is over $700+ with lower than a regular 1080's performance it will be dead in the water.

We got 100 Saphire 580 8 GB for $254 each, that was a couple of weeks before it went crazy, will get 100 more when it comes down, and it will.

[Branko]

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

Agreed same here, back on 17.7.1 with all working again.

Me too.And the claymore's cvddc and mvddc options don't seem to be available.

I had the same issue. WattTool would not work. HAd to use WattMan which was slower than slow. went back to my trusty 16.5 or whatever it is.

Also, OC through wattman seems to work (both wattman and hwinfo show changed frequencies), but doesn't affect speed of mining at all???

[fjriosp]

Hi all,

If I mine ETH only all works fine with a hashrate of 181MHs.
When I try to dual mine ETH+DCR (-dcri 30) I get 180MHs (ETH) + 5000MHs (DCR).

The problem is that while dual mining I got almost 1% of incorrect shares and looking the hashrate at poolsize I got under 170MHs (-6%).

Could someone help me to figure out where is the problem?

Thanks!!

[KGV]

Hi all,

If I mine ETH only all works fine with a hashrate of 181MHs.
When I try to dual mine ETH+DCR (-dcri 30) I get 180MHs (ETH) + 5000MHs (DCR).

The problem is that while dual mining I got almost 1% of incorrect shares and looking the hashrate at poolsize I got under 170MHs (-6%).

Could someone help me to figure out where is the problem?

Thanks!!

Config?