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

big al

member

Activity: 140

Merit: 10

Quote

Exactly. With each newer version, you've to find out the best overclocking/etc. values once again. I figured it out and now loving your newer version of miner, with better hash-rate & stability (I just upgraded to your v11.5 from v7, that's an upgrade after a long time).

When you toss in ram straps then it gets really complicated. I'm guessing the guys will have to come up with ones for the new kernel

Prelude

legendary

Activity: 1596

Merit: 1000

Quote from: Claymore on March 14, 2018, 01:05:40 PM

v11.5:

- added "-oldkernels" option (AMD GPUs only), you can try "-oldkernels 1" to use old-style GPU kernels from v10, they can be more stable for hard OC and custom BIOSes.
- a bit reduced stale shares for Nvidia GPUs.

I've tested the old kernel on my Hawaii rigs for the last 16 hours or so, and it solves the issue introduced by 11.x with Hawaii GPUs. Cheesy

Marvell2

full member

Activity: 1148

Merit: 132

Quote from: Claymore on March 14, 2018, 06:31:13 AM

Quote from: RuMiner on March 14, 2018, 06:28:37 AM

Quote from: Claymore on March 14, 2018, 05:59:36 AM

I see some people have problems with latest versions because they use hard OC and/or custom bioses created for old versions. They work fine with old GPU kernels, but I modified kernels in v11.2 and you need to readjust your settings.
For those who cannot do it (or don't want to do it) I can revert some changes and release a version with "old-style" binaries. So I will release v11.5 within a few hours and it will be the only change in this version, so don't upgrade if v11.4 works fine for you.

does it mean 11.5 will have issue with stale shares again? I like 3% stale instead of 8% for 11.1, but a couple of rigs began very rare crashing since updating to 11.2.

No, stale shares will be same as for 11.4 (i.e. almost zero) because it is not related to GPU kernels directly.

stale shares have never been near zero with claymore, I get 3% stale shares
on ethermine no matter what version i use

Raja_MBZ

legendary

Activity: 1862

Merit: 1505

Quote from: Claymore on March 14, 2018, 01:12:19 PM

Let me explain: some people apply OC and memory straps to get best hashrate. They spend a lot of time to find best values, and finally it works. But it works only for some specific GPU kernel, it may fail as soon as you try to start some different miner or even same miner but with updated GPU kernel. After that you can blame the miner of course, but the reason is in your settings, you need to readjust them for new kernel.
I added "-oldkernels 1" option so now you can use old kernels in latest version, hope it will help.

Exactly. With each newer version, you've to find out the best overclocking/etc. values once again. I figured it out and now loving your newer version of miner, with better hash-rate & stability (I just upgraded to your v11.5 from v7, that's an upgrade after a long time).

Digital_Seytan

jr. member

Activity: 222

Merit: 2

[email protected]

Just ran a 6 hour experiment on the exact same 1060 rigs.

Average shares per hour:

Claymore 11.5: 152
Phoenix 2.6: 174

Extrapolated over the month, Phoenix provides 0.08 more ETH over Claymore.

phoenixminer 2.7c crashes every so often for me, my virus program deleted the executable so I've gone back to 2.6.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Let me explain: some people apply OC and memory straps to get best hashrate. They spend a lot of time to find best values, and finally it works. But it works only for some specific GPU kernel, it may fail as soon as you try to start some different miner or even same miner but with updated GPU kernel. After that you can blame the miner of course, but the reason is in your settings, you need to readjust them for new kernel.
I added "-oldkernels 1" option so now you can use old kernels in latest version, hope it will help.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

v11.5:

- added "-oldkernels" option (AMD GPUs only), you can try "-oldkernels 1" to use old-style GPU kernels from v10, they can be more stable for hard OC and custom BIOSes.
- a bit reduced stale shares for Nvidia GPUs.

big al

member

Activity: 140

Merit: 10

Quote from: dumada on March 14, 2018, 12:37:51 PM

Quote from: big al on March 14, 2018, 12:24:07 PM

Quote from: Claymore on March 14, 2018, 05:59:36 AM

I see some people have problems with latest versions because they use hard OC and/or custom bioses created for old versions. They work fine with old GPU kernels, but I modified kernels in v11.2 and you need to readjust your settings.
For those who cannot do it (or don't want to do it) I can revert some changes and release a version with "old-style" binaries. So I will release v11.5 within a few hours and it will be the only change in this version, so don't upgrade if v11.4 works fine for you.

So what would work better on an rx580:

- stock bios with 11.4
- modified bios with 11.5

or is it just a matter of testing? Is it no longer worth strapping the ram?

The 11.5 should be slightly slower than 11.4

So Claymore optimizing has made ram strap modifications moot?

dumada

full member

Activity: 154

Merit: 100

Quote from: big al on March 14, 2018, 12:24:07 PM

Quote from: Claymore on March 14, 2018, 05:59:36 AM

I see some people have problems with latest versions because they use hard OC and/or custom bioses created for old versions. They work fine with old GPU kernels, but I modified kernels in v11.2 and you need to readjust your settings.
For those who cannot do it (or don't want to do it) I can revert some changes and release a version with "old-style" binaries. So I will release v11.5 within a few hours and it will be the only change in this version, so don't upgrade if v11.4 works fine for you.

So what would work better on an rx580:

- stock bios with 11.4
- modified bios with 11.5

or is it just a matter of testing? Is it no longer worth strapping the ram?

The 11.5 should be slightly slower than 11.4

big al

member

Activity: 140

Merit: 10

Quote from: LucianoBM on March 14, 2018, 12:01:17 PM

Exacly
Seems like if you have 11.4 running stable means that you didn't OCed to the max before.

I have to disagree. My cards are stable up to 1230 and 2225 and beyond on 11.0. It seems like any version above that even 1180/2135 I get 4% incorrect and no amount of underclocking gets rid of them. Anything faster causes instability. For me the faster speeds on 11.0 is a much better deal. I can go a lot faster than 1230/2225 on 11.0 as well.

But I do have timing straps done on rx580 micron ram. I have a feeling that is the issue much more than OC speeds. Especially since the Nvidia guys don't seem to have any problems.

big al

member

Activity: 140

Merit: 10

Quote from: Claymore on March 14, 2018, 05:59:36 AM

I see some people have problems with latest versions because they use hard OC and/or custom bioses created for old versions. They work fine with old GPU kernels, but I modified kernels in v11.2 and you need to readjust your settings.
For those who cannot do it (or don't want to do it) I can revert some changes and release a version with "old-style" binaries. So I will release v11.5 within a few hours and it will be the only change in this version, so don't upgrade if v11.4 works fine for you.

So what would work better on an rx580:

- stock bios with 11.4
- modified bios with 11.5

or is it just a matter of testing? Is it no longer worth strapping the ram?

Viaggiatore

newbie

Activity: 56

Merit: 0

Quote from: Metroid on March 14, 2018, 10:32:52 AM

Quote from: Vann on March 14, 2018, 10:26:10 AM

I have the same amount of ETH incorrect shares dual mining with v11.4 as before over two rigs, at most 1 or 2 per 1000 shares. If you're getting more incorrect shares with v11.4, if probably means your settings were too high to begin with or a Bios mod with too aggressive timings. Use HwInfo to check for memory errors and adjust the memory clock down by 50 MHz until there are no more errors.

For most cases that will work, few cases if no memory errors then incorrect shares occur. Friend has many gpus with no memory errors and sometimes many incorrect shares. If any of you are getting incorrect shares, just lower memory clock speed until there are not any anymore.

Sorry but considering I have zero memory errors, which is the point of using a "faster" version if I need to lower memory freqs thus lowering the hash rate?

LucianoBM

newbie

Activity: 15

Merit: 0

Quote from: peterboy1 on March 14, 2018, 10:45:59 AM

Quote from: dragonmike on March 14, 2018, 10:01:42 AM

I flashed my RX 570's back in April 2017.
Claymore's miner has been working stable in version 11.4, 11.3 and any previous version just as well.

I think you guys complaining about crashes must have dodgy memory straps or are just overclocking too far. Just check the log, identify the GPU going down and dial back that OC.

maybe you are right. but i think i/we just maxed our clock/mods with previous version with stability.

now that claymore adjusted the client (i dont know, maybe because the competition has higher hashrate), all those maxed out settings are not compatible anymore, hence, the stability issues.

Exacly
Seems like if you have 11.4 running stable means that you didn't OCed to the max before.

ddjjxxiiaa

newbie

Activity: 3

Merit: 0

Hello guys,
I am a noob miner since 2 months. From 10.6 to 11.4, i have got a same problem.

I have 6 RX588 rig, 30M hashrate for each card.

Sometimes after restarting the Claymore, or after reboot the machine and then start the Claymore, the Hashrate will down to 26 or 27, it may be return to 30 by itself after one or two hour, maybe not.

If i disable the GPU by clicking the number for 5 sec, and then enable it, the hashrate will be return to 30.

Does anyone has the same problem or the solution?

Thanks ~~~~~~~~~~~

sir4o

newbie

Activity: 67

Merit: 0

Quote from: ?? on ??

Quote from: Claymore on April 11, 2016, 11:30:36 AM

Claymore's Dual Ethereum + Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak AMD+NVIDIA GPU Miner.
=========================

Latest version is v11.4:

- fixed issue with stale shares.
- fixed issue with incorrect shares.
- a few minor bug fixes and improvements.

Клeймop ты мeня yдивляeшь в oчepeднoй paз. Oчeнь и oчeнь кpивo нaпиcaнный мaйнep. C кaждoй вepcиeй бoльшe глюкoв. B нoвoй вepcии 11.4 мнoгиe видeoкapты нe дepжyт cвoи cтapыe чacтoты. Ужac!!! Кaк мoжнo выпycкaть cыpoй, нeкaчecтвeнный пpoдyкт. Eщё зa этo бpaть дeньги, кoмиccию. Tы в cвoём yмe или пoтepялcя пo жизни ?

Пpибeжaлa pyccкoгoвopящaя oбeзьянa, кинyлa гoвнoм и yбeжaлa.

He is more or less right in giving out. I can confirm the so called 'optimizations' come at increased Watts (at least for me). Made several tests with different versions and the outcome is 3.30% more Watts and 1.79% more hashes. These are without any power limit set. Probably to make it more 'tempting' so people switch to the newest version always...

ddjjxxiiaa

newbie

Activity: 3

Merit: 0

Quote from: zafa on March 14, 2018, 09:23:13 AM

Hi, I was using v11 before using the latest version. In latest version when the DEVFEE starts Claymore creates DAG again.
Why Claymore creating DAG file again?

Yes, I have the same question. And for my RX580 pulse, every time to create DAG, it has the risk to freeze the windows. So with the old version, not so often to create the DAG so more stable for me.

Dark Oopa

newbie

Activity: 83

Merit: 0

Hello guys,

just a quick question:

is it worth it to use the cuda 9 version of claymore on 1060 3Gb (the good ones ^^)? If yes, what driver do you use?

the drivers I have the less problem with are the 382.53 but they do not support the latest cuda.
Thx for your reply

BPina

newbie

Activity: 20

Merit: 1

What I have to say about version 13.4...

1) I'm mining on Nanopool since early feb, and I've never seen the average line so close to reported hashrate line as I'm seeing now.
2) Since version 11, I've started to get many invalid shares I wasn't getting before. Since 11.4, I haven't gotten any invalid/rejected share.
3) About increase on hashing... I was getting 341.9/342.2mh/s on 11.2. I am getting now a stable 342.8mh/s.

Great job!!

peterboy1

newbie

Activity: 168

Merit: 0

Quote from: dragonmike on March 14, 2018, 10:01:42 AM

I flashed my RX 570's back in April 2017.
Claymore's miner has been working stable in version 11.4, 11.3 and any previous version just as well.

I think you guys complaining about crashes must have dodgy memory straps or are just overclocking too far. Just check the log, identify the GPU going down and dial back that OC.

maybe you are right. but i think i/we just maxed our clock/mods with previous version with stability.

now that claymore adjusted the client (i dont know, maybe because the competition has higher hashrate), all those maxed out settings are not compatible anymore, hence, the stability issues.

Metroid

sr. member

Activity: 2142

Merit: 353

Xtreme Monster

Quote from: Vann on March 14, 2018, 10:26:10 AM

I have the same amount of ETH incorrect shares dual mining with v11.4 as before over two rigs, at most 1 or 2 per 1000 shares. If you're getting more incorrect shares with v11.4, if probably means your settings were too high to begin with or a Bios mod with too aggressive timings. Use HwInfo to check for memory errors and adjust the memory clock down by 50 MHz until there are no more errors.

For most cases that will work, few cases if no memory errors then incorrect shares occur. Friend has many gpus with no memory errors and sometimes many incorrect shares. If any of you are getting incorrect shares, just lower memory clock speed until there are not any anymore.

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 321. (Read 6590565 times)