Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.7 (Windows/Linux)

Hello guys,

I am experiencing an issue.

I made a new rig with 6 Phantom Gaming D Radeon RX570 8G OC, the memory installed on the cards is Hynix.
They are not bios mod since I wanted to use -strap command directly in Claymore's miner.
I am using Claymore v14.7 miner, with driver 19.4.3 since it is with this driver that Claymore has most tests been performed.

Compute mode ON, with overclocking, I uninstalled and installed the driver in claymore to be able to use -strap command.
And I am mining at 22.5 MHs no matter what -strap I am using.
The strap is applied successfuly : "strap "POL8H1" is applied successfully" on each card.

but the hashrate just refuses to change ! (-rxboost does actually work and allow me to reach 24MHs)

Anyone can help me to get -strap working on my rig and to reach 30+ Mhs per card, maybe by also changing the OC settings?

I will give to the one who provides me with a solution 100$ worth of Ethereum Classic.

I'd suggest running @eliovp's AMDMemTweak tool to see if the strap settings are getting the modifications. Run it without -strap first and note some of the values (tCL, etc) and then run it with -strap to see if indeed they are being applied. There a thread in Mining (Altcoins) just for this program and the executable is up on GitHub.

I did it and with -strap 1 I am getting only 20.2MHs per card..

here is the screenshot without applying any -strap :
https://www.noelshack.com/2019-33-5-1565953173-captureamdmemorytweak.png

here is the screenshot after applying -strap 1 :
https://www.noelshack.com/2019-33-5-1565953247-captureavecstrap1.png

What's wrong ??

You're in windows correct? PLEASE refer to my post you WILL get 33 to 34 Mhs with that configuration. AMDmemTweak is a different forum, as much as i love the tool, and love that it was the tool that prompted Claymore to update, but this is a claymore forum. lets keep this to claymore.

Ensure you are in compute mode in wattman. just enabling compute in the command string does not necessarily kick the driver into compute mode. You need to go into the wattman and change it from graphic to compute.