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

Gunna01

sr. member

Activity: 306

Merit: 251

Quote from: Bibi187 on October 29, 2017, 09:33:04 PM

I would like to be honest, if i can escape your dev fee i will do it ...

It seems you made a lot of money and dont keep this one good has he can be with all found you get.

I expect some release with new algo top hashrate, more dual options, more detailed "s" report, like hashrate for 6hours, 12hours, 24hours.

The last update you made about DAG creation is ON YOUR is nice ...

Cause without this is more like 3,5% - 4% we loose ...

So thanks for this and do more good work please!

I would add where is checksum ? You earn some million dollars ... You have time to make a checksum ... Or pay someone for oO

Personally I think there should be a timer set for DEV mining. Where there is 2 hours of DEV mining then it stops or reduces to once every 12\24 hours. Counter is reset each time the miner restarts. Each miner then contributes 2 hours of hashing time towards the development of Claymore and then once or twice more daily. I really dont like the idea of ongoing DEV fee especially if my miner has an uptime of weeks\months.

Bibi187

full member

Activity: 420

Merit: 106

https://steemit.com/@bibi187

I would like to be honest, if i can escape your dev fee i will do it ...

It seems you made a lot of money and dont keep this one good has he can be with all found you get.

I expect some release with new algo top hashrate, more dual options, more detailed "s" report, like hashrate for 6hours, 12hours, 24hours.

The last update you made about DAG creation is ON YOUR is nice ...

Cause without this is more like 3,5% - 4% we loose ...

So thanks for this and do more good work please!

I would add where is checksum ? You earn some million dollars ... You have time to make a checksum ... Or pay someone for oO

greatauror28

full member

Activity: 181

Merit: 101

Ethereum Miner

Quote from: blackhwk77 on October 27, 2017, 02:18:32 PM

Quote from: Ursul0 on October 27, 2017, 12:05:19 PM

Quote from: Ursul0 on October 26, 2017, 03:15:08 PM

Quote from: Marvell2 on October 26, 2017, 12:58:38 PM

Quote from: Ursul0 on October 26, 2017, 05:33:50 AM

Quote from: Marvell2 on October 26, 2017, 05:08:45 AM

Quote from: bossbamboo on October 26, 2017, 04:03:39 AM

Quote from: Marvell2 on October 25, 2017, 05:09:52 PM

confirmed the wind 10 64 bit new drivers work for 10+ cards

I have a 10 GPU rig running now, what I did find is uninstalling afterburner first helps

also with so many GPU it would also sometimes hang on when u run claymore, I fixed this by using -gser 2 option

It still hangs when i try and dual mine so I need to do more tweaking.

ALso AMD settings and MSI after burner do not play nice togther, I decided to roll with wattman since I cannot set the voltages on this mortherboard

the ASUS 16 Slot one with MSI AB

Which GPU that you use on your rig?
pure AMD GPU or mix with nvidia?

No all Rx570 and 470 mix , no nividia cards

Are you saying actually that you're running 10 AMD cards on WinX with "amd latest driver" - is this correct?
And if so what rates are you getting on ethash with this driver?

12 cards actually, just added two more this AM. and Yes thats correct.
hash rates are the same as block chain driver, the kicker is my systems are way more stable with this new driver

I had one rig of six R9 nano I upgraded to this new driver with modded evilop bios that used to crash one a day, its been two days with the new driver and its rock solid.

I also have not yet seen the issue i had before with the robin hood and beta blockchain driver where I would see hashrate of 8.33 or some crap sometimes, but its still
early.

Only issue with the new drivers is they can be hard to install, sometimes taking multiple DDU cleanings to install, and I HAD to remoVE AB.

I might install it back , becase wattman is crap

that's interesting. is that a win update, or just driver? you should try to use overdriventool for clocks and volts, it's better then claymore - as you can set proper stages as well.
also AB is known to have nasty issues

not sure I follow you...please indicate the rates that you are getting from rx570 on ethereum with latest(version?) driver?

just tested some of the latest "crimson-relive-17.10.2-oct23"
and it doesnt not have the dag fix, so no matter if it supports over 8 cards (it also works better with the volts from overdriventool ...) but 23MH on ETH vs 30MH on 17.7.2 or whatever the ver number of blockchain drv...

Did you change the workload setting in AMD settings? I updated my 2 GPU rig and didn't lose any speed. Probably upgrading my 5 and 11 GPU rigs sometime this weekend.

I've been having this stupid OpenCL error for a whole week since last night and i've tried all the troubleshooting and tried-and-tested workarounds but to no avail - until I updated to Win10 Fall Creator's Update and AMD 17.10.3 last night.

MY RIG IS FINALLY STABLE AF! Grin

It's been running 15+ hrs now without any OpenCL errors nor any hiccups.

I'm so relieved to finally have it stable and working perfectly.

What a nice birthday present Wink

Kumic

full member

Activity: 533

Merit: 100

Has anyone tried Claymore's v10.1 Dual Ethereum AMD+NVIDIA GPU Miner?
I had some issues lately with AMD cards, I can say that they are working ok now,
but I would like to know how new miner does his job.

SnigglysMine

newbie

Activity: 9

Merit: 0

Need help please! Huh

I am configuring a mixed card rig (by mixed I mean Nvidia and AMD cards on the same rig). Using Claymore's latest release and I am unable to get the decred portion to work. It keep saying:

DCR: Authorization failed
: null

The hashrate shows up though (3640.5 Mhs)

Any ideas?

Here's my command line:

EthDcrMiner64.exe -epool us1.ethpool.org:3333 -esm 1 -di 01234 -ewal "walletaddress" -epsw x -dpool dcr.suprnova.cc:3252 -dwal "walletaddress.workername" -dpsw x -allpools 1

Victorio

full member

Activity: 281

Merit: 100

Quote from: rodney2250 on October 29, 2017, 03:09:04 PM

zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10

Any ideas?

The memory does not seem stable. If you get 1-3% of incorrect shares in solo mining, the memory lacks voltage or timings are wrong. Have you flashed your GPUs with modified BIOS?

Code:

I suppose your RX480/RX580 are equipped with Elpida memory and you flashed the timings from RX470/RX570 equipped with Samsung.

First of all, I would recommend checking the memory stability - run the cards at stock frequency and voltage. If you still get incorrect shares - you set wrong timings in the BIOS timings table.
Second, use OverdriveNTool to enforce voltage levels, say 900 mV for both core and memory.
Third, do the fine tuning for each GPU, until incorrect shares do not show up anymore.

I second the idea of MentalNomad that overheating might cause memory instability.

MentalNomad

member

Activity: 83

Merit: 10

Quote from: davescream on October 29, 2017, 03:47:12 PM

I think incorrect shares is faulty shares which were detected locally.
Rejected shares are incorrect shares which were send to pool, but pool rejected it.

I think that's right.

Quote from: rodney2250 on October 29, 2017, 03:09:04 PM

Ok. I think rejected and incorrect shares are different. Look at the example below (Claymore 9. Cool

:

Code:

GPU #0: Ellesmere, 4096 MB available, 36 compute units
GPU #1: Ellesmere, 4096 MB available, 36 compute units
GPU #2: Ellesmere, 4096 MB available, 36 compute units
GPU #3: Ellesmere, 4096 MB available, 32 compute units
GPU #4: Ellesmere, 8192 MB available, 32 compute units
GPU #5: Ellesmere, 8192 MB available, 32 compute units
ETH - Total Speed: 162.347 Mh/s, Total Shares: 13023(2222+2204+2132+2168+2187+2227), Rejected: 0, Time: 100:05
ETH: GPU0 27.513 Mh/s, GPU1 27.380 Mh/s, GPU2 26.206 Mh/s, GPU3 27.200 Mh/s, GPU4 27.025 Mh/s, GPU5 27.024 Mh/s
Incorrect ETH shares: GPU0 25, GPU1 76, GPU2 10
 1 minute average ETH total speed: 162.193 Mh/s
Pool switches: ETH - 0, DCR - 0
Current ETH share target: 0x00000000ffb34c02 (diff: 4300MH), epoch 34(1.27GB)
GPU0 t=73C fan=60%, GPU1 t=73C fan=50%, GPU2 t=72C fan=40%, GPU3 t=74C fan=49%, GPU4 t=69C fan=37%, GPU5 t=69C fan=38%

zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10

Any ideas?

I can see one incorrect share or two in some of my 24-hour logs, but not most of them. Maybe I've just never seen one, on-screen.

I do notice that you have six cards... and of the four cards over 70C, three are throwing incorrect shares. The two that are below 70C are clean.

I can tell you that I crank my fans way higher at those temps than you do; when the GPU core is that hot, the memory may be even hotter, and many cards can't handle it. I have cards that crap out entirely when they break 70C. Some cards can obviously go way hotter; varies between brands and models, and within a model, can vary by individual card and/or where it is in the rig (because of airflow.)

Also, side note: the power draw for fans goes up more than linearly as you go above 50%; the back pressure makes the fan noisy and less power-efficient. Backing off the OC may even be more cost-effective than pinning the fan at 100%.

kkourmousis

member

Activity: 119

Merit: 10

Quote from: rodney2250 on October 29, 2017, 03:09:04 PM

zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10

Any ideas?

Download HWinfo and check your gpus for memory errors. As long as you have errors you should drop clocks or increase voltage. When errors get to 0 ypu are not incorrect hashes free, I am not sure why, must be that tight memory straps of modded BIOS. In my case I stil have ~1% Incorrecr hashes (compared to accepted hashes)

davescream

newbie

Activity: 50

Merit: 0

Quote from: rodney2250 on October 29, 2017, 03:09:04 PM

Ok. I think rejected and incorrect shares are different. Look at the example below (Claymore 9. Cool

:

zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10

Any ideas?

I think incorrect shares is faulty shares which were detected locally.
Rejected shares are incorrect shares which were send to pool, but pool rejected it.

rodney2250

jr. member

Activity: 177

Merit: 2

Ok. I think rejected and incorrect shares are different. Look at the example below (Claymore 9. Cool

:

Code:

GPU #0: Ellesmere, 4096 MB available, 36 compute units
GPU #1: Ellesmere, 4096 MB available, 36 compute units
GPU #2: Ellesmere, 4096 MB available, 36 compute units
GPU #3: Ellesmere, 4096 MB available, 32 compute units
GPU #4: Ellesmere, 8192 MB available, 32 compute units
GPU #5: Ellesmere, 8192 MB available, 32 compute units
ETH - Total Speed: 162.347 Mh/s, Total Shares: 13023(2222+2204+2132+2168+2187+2227), Rejected: 0, Time: 100:05
ETH: GPU0 27.513 Mh/s, GPU1 27.380 Mh/s, GPU2 26.206 Mh/s, GPU3 27.200 Mh/s, GPU4 27.025 Mh/s, GPU5 27.024 Mh/s
Incorrect ETH shares: GPU0 25, GPU1 76, GPU2 10
 1 minute average ETH total speed: 162.193 Mh/s
Pool switches: ETH - 0, DCR - 0
Current ETH share target: 0x00000000ffb34c02 (diff: 4300MH), epoch 34(1.27GB)
GPU0 t=73C fan=60%, GPU1 t=73C fan=50%, GPU2 t=72C fan=40%, GPU3 t=74C fan=49%, GPU4 t=69C fan=37%, GPU5 t=69C fan=38%

zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10

Any ideas?

MentalNomad

member

Activity: 83

Merit: 10

Quote from: rodney2250 on October 29, 2017, 02:39:03 PM

Thanks. What about incorrect share (as reported by claymore's miner)?

I don't see incorrect shares reported in Claymore's on-screen metrics.

Claymore reports Total and Rejected. For example:

Code:

ETH - Total Speed: 253.379 Mh/s, Total Shares: 2809, Rejected: 0, Time: 12:05

It will also display responses it gets from the pool, such as "Share accepted"; the pool would report Incorrect or Stale shares.

I'm pretty sure that an Incorrect Share report from a pool is counted by Claymore as Rejected.

If you're looking at an incorrect share note in the Claymore logfile, I'd call that a lot file, not a metric. But it means the same thing - it's not a valid share; it's an incorrect result. For example:

Code:

19:12:40:853	fcff9700	GPU #1 got incorrect share. If you see this warning often, make sure you did not overclock it too much!

I think that's fairly self-explanatory. If not, please ask specifically about what's confusing you.

MentalNomad

member

Activity: 83

Merit: 10

Quote from: TerranGas on October 29, 2017, 02:28:25 PM

Hello, Guys. I'm asking for help as I got stuck with a problem. I read through the topic and tried many things. but didn't work out.

I have two farms mining ETH+DCR for 6 and 4 cards. The problem with a second farm.

I have 4 RX570 cards, motherboard ASrock z97. It used to give me 100 mh/s stable. However, then miner started to crash with the message:
"NO AMD OPENCL or NVIDIA CUDA GPUs found, exit".

ok... uninstall drivers, update cards with Crimson ReLive beta Blockchain Driver, patch drivers, restart and launch miner again.

The problem arises exactly in 120 minutes again... not 119 or 121, it is exactly two hours before it crashes again. The monitor blinks a couple of time. speed goes to 0, and the end.

I tried to repatch cards via bios (atiflash), played with graphic cards, nothing works. The only thing I noticed that if I launch 3 cards from 4... they work fine for a relatively long time without crashes. Notable, that I tried each of the card, and they seem to be normal.

However, when i start all 4... it works only 120 minute and "NO AMD OPENCL...".

Please, let me know if there are any ideas, I can provide you with more info, whatever you ask.

I don't have a solution, but if it's really exactly 120 minutes, one workaround is to set the rig to auto-reboot after 119 minutes.

I've used that as a workaround on rigs running Win 10 Ent trial, which is good for 90 days... after 90 days, it expires, and will shut down after 60 minutes. So I set the machine up to reboot in 59 minutes. With a rig on SSD, it actually mines 98% as much as usual despite doing the reboots, so it's a good workaround until you have time to fix it properly.

rodney2250

jr. member

Activity: 177

Merit: 2

Quote

Total Shares: the sum count of all shares found by your GPUs since the last time you started Claymore.

Rejected share: share that you computed and sent to your mining pool, but which the mining pool rejected as not being correct. This might point to memory on your GPU being corrupted, perhaps because of overheating or because of an OC that is too high. If the memory is not faulty, a restart can clear it up, if it doesn't get driven too hard again.

Stale share: a share that you found and sent to the pool and was confirmed as correct, but which arrived too late; you sent a share when the pool had already moved on to a new block. This may point to a slow network connection, or perhaps your system is overtaxed and is unable to move your GPUs to the new work quickly enough when new work comes in. Everyone will have some small portion of stale shares, unless their miners are pretty much directly connected to the pool's servers and can get new work notices with almost no delay (which is pretty much impossible, unless you're running the pool servers and install the miners next to them.) If your pool provides multiple addresses, ping them and see which is "closest" to you (has the shortest time delay) and make sure you work with that address.

Thanks. What about incorrect share (as reported by claymore's miner)?

TerranGas

newbie

Activity: 4

Merit: 0

Hello, Guys. I'm asking for help as I got stuck with a problem. I read through the topic and tried many things. but didn't work out.

I have two farms mining ETH+DCR for 6 and 4 cards. The problem with a second farm.

I have 4 RX570 cards, motherboard ASrock z97. WIN 10 It used to give me 100 mh/s stable. However, then miner started to crash with the message:
"NO AMD OPENCL or NVIDIA CUDA GPUs found, exit".

ok... uninstall drivers, update cards with Crimson ReLive beta Blockchain Driver, patch drivers, restart and launch miner again.

The problem arises exactly in 120 minutes again... not 119 or 121, it is exactly two hours before it crashes again. The monitor blinks a couple of time. speed goes to 0, and the end.

I tried to repatch cards via bios (atiflash), played with graphic cards, nothing works. The only thing I noticed that if I launch 3 cards from 4... they work fine for a relatively long time without crashes. Notable, that I tried each of the card, and they seem to be normal.

However, when i start all 4... it works only 120 minute and "NO AMD OPENCL...".

Please, let me know if there are any ideas, I can provide you with more info, whatever you ask.

MentalNomad

member

Activity: 83

Merit: 10

Quote from: rodney2250 on October 29, 2017, 12:26:40 PM

Hey guys,

Could someone clarify the meaning of the different shares metrics in claymores' output?

Rejected shares - is this the same as stale shares?
Incorrect shares - invalid shares?
Total shares - is this the sum of valid+incorrect+rejected shares?

Thank you

Total Shares: the sum count of all shares found by your GPUs since the last time you started Claymore.

Rejected share: share that you computed and sent to your mining pool, but which the mining pool rejected as not being correct. This might point to memory on your GPU being corrupted, perhaps because of overheating or because of an OC that is too high. If the memory is not faulty, a restart can clear it up, if it doesn't get driven too hard again.

Stale share: a share that you found and sent to the pool and was confirmed as correct, but which arrived too late; you sent a share when the pool had already moved on to a new block. This may point to a slow network connection, or perhaps your system is overtaxed and is unable to move your GPUs to the new work quickly enough when new work comes in. Everyone will have some small portion of stale shares, unless their miners are pretty much directly connected to the pool's servers and can get new work notices with almost no delay (which is pretty much impossible, unless you're running the pool servers and install the miners next to them.) If your pool provides multiple addresses, ping them and see which is "closest" to you (has the shortest time delay) and make sure you work with that address.

MentalNomad

member

Activity: 83

Merit: 10

Quote from: Snowykingdom on October 28, 2017, 11:56:15 PM

Goodbye clayclay fee Cheesy

No need to pay clayclay after so many versions...

Yes, he has great miner but clayclay is fed well already and should lower the fee instead of getting more greedy.

There's a much easier way to avoid the Claymore miner dev fees.

Use a different miner.

Quote from: Snowykingdom on October 29, 2017, 09:16:04 AM

Stop for being fuckin hypocrite in this crypto world, even your friends will kill you for each penny you have Cheesy

Go learn what friends are; you apparently haven't had any.

rodney2250

jr. member

Activity: 177

Merit: 2

Hey guys,

Could someone clarify the meaning of the different shares metrics in claymores' output?

Rejected shares - is this the same as stale shares?
Incorrect shares - invalid shares?
Total shares - is this the sum of valid+incorrect+rejected shares?

Thank you

Vann

hero member

Activity: 1036

Merit: 606

You need a monitor or dummy plug in the primary GPU for the AMD driver to read the fan speed and temps.

UMICHStatistican

newbie

Activity: 7

Merit: 0

Guys, I'm experiencing a problem on all my rigs with Remote Manager. If I log onto any of my rigs remotely and startup Claymore's batch file, I can see all the fan speeds, temps, etc. in Claymore's remote manager. It's great. However, if I set claymore to autostart mining by placing a batch script within a scheduled task to run the batch script on startup, Claymore executes and starts mining, and I can see all the statistics in Claymore's remote manager, except fan speeds and temps are not displayed. It seems only when Claymore is executed in an unattended mode does this happen. Is there anyway to get the fan and temp stats to display in the remote manager with an autostart of Claymore?

Thanks.

Snowykingdom

newbie

Activity: 29

Merit: 0

Quote

So your argument is that @Claymore earned more than you think he should have (through his work, not by luck or cheat) ?

First of all, mentioning the method this guy uses to cheat is pretty much an invitation @Claymore to lock it up.

Secondly, do you see a single outcome on this that can result in better mining for us all? Claymore getting pissed and stopping support of his miner would be much more catastrophic than your 1% fee

Stop for being fuckin hypocrite in this crypto world, even your friends will kill you for each penny you have Cheesy

BTFW, you are not the only person who never used a proprietary software without breaking it aren't you?

BS.

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