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

TunerDude007

sr. member

Activity: 467

Merit: 252

Quote from: milicic on October 30, 2017, 04:09:02 PM

People, does anybody have the exact information about ethereum switching from Pow to Pos? I just read an article that Casper is coming earlier than planned and maybe with the next ethereum upgrade (maybe even before the end of year or early in 2018). What exactly that means for us miners? Some say that it will be hybrid Pow/Pos... But, if it is just Pos, and if it happens in a couple of months, are we doomed?

I wouldn't sweat it, the ethereum camp has been saying this for 2 years now. They cant seem to get their shit figured out...And when they do get it figured out not to worry, there are many other coins to mine my friend.

greatauror28

full member

Activity: 181

Merit: 101

Ethereum Miner

Quote from: TunerDude007 on October 31, 2017, 01:07:14 PM

Quote from: OXUS on October 30, 2017, 03:47:24 PM

Quote from: Victorio on October 30, 2017, 01:19:48 PM

Quote from: OXUS on October 30, 2017, 10:38:08 AM

EthDcrMiner64.exe -epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0xc86bb711033e00abd01b197a57be42421678a987 -epsw x -eworker rig1 -allcoins 1 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal neverrazor.1 -dpsw x

Your hashrate is at ~50% of your's equipment normal performance. I thought that mining intensity was set wrong (ethi and dcri). After runing a short test, I found that GTX1060 are not very sensible to dcri level (at least DCR). Cranking DCR intensity from 40 to 130, the DCR hashrate increased 190% and ETH hashrate decreased 10%. Such dcri level, to halven the ETH hashrate, should be within 200-300 range, that is either stupid or unsupported by Claymore miner.
Better define explicitly your ethi and dcri, say 16/40, 16/50.
Check your BIOS settings - enable Above 4G decoding/TOLUD (works only in UEFI-enabled systems) and PCI-E speed - switch it to Gen1 or Gen2.

i enabled 4g ... and tried different pci-e gen speed all same results ... the problem is ONLY in the hashrate of eth ... .. i tried another eth miner ... same problem

I seem to be having the same issue on my Asus Z270 board with 5 Rx 580's hashing all at around 23mg/h each, another one of my rigs with same config but older asrock H81 board and 6 rx 480 is 31mg/h each.

What version of Claymore do you use?
What AMD driver do you use?

TunerDude007

sr. member

Activity: 467

Merit: 252

Quote from: OXUS on October 30, 2017, 03:47:24 PM

Quote from: Victorio on October 30, 2017, 01:19:48 PM

Quote from: OXUS on October 30, 2017, 10:38:08 AM

EthDcrMiner64.exe -epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0xc86bb711033e00abd01b197a57be42421678a987 -epsw x -eworker rig1 -allcoins 1 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal neverrazor.1 -dpsw x

Your hashrate is at ~50% of your's equipment normal performance. I thought that mining intensity was set wrong (ethi and dcri). After runing a short test, I found that GTX1060 are not very sensible to dcri level (at least DCR). Cranking DCR intensity from 40 to 130, the DCR hashrate increased 190% and ETH hashrate decreased 10%. Such dcri level, to halven the ETH hashrate, should be within 200-300 range, that is either stupid or unsupported by Claymore miner.
Better define explicitly your ethi and dcri, say 16/40, 16/50.
Check your BIOS settings - enable Above 4G decoding/TOLUD (works only in UEFI-enabled systems) and PCI-E speed - switch it to Gen1 or Gen2.

i enabled 4g ... and tried different pci-e gen speed all same results ... the problem is ONLY in the hashrate of eth ... .. i tried another eth miner ... same problem

I seem to be having the same issue on my Asus Z270 board with 5 Rx 580's hashing all at around 23mg/h each, another one of my rigs with same config but older asrock H81 board and 6 rx 480 is 31mg/h each.

vapourminer

legendary

Activity: 4354

Merit: 3614

what is this "brake pedal" you speak of?

Quote from: digimonx on October 31, 2017, 09:12:23 AM

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

For AMD cards, set the following environment variables, especially if you have 2GB cards:

GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

Does this apply only to AMD cards, or Nvidia cards as well?

amd only.

ngdias

jr. member

Activity: 51

Merit: 1

I'm trying to figure out if the latest version is compatible with R9 Fury X cards. OP mentions "1. Install Catalyst v15.12 for old AMD cards; for Fury, Polaris and Vega cards use latest blockchain drivers." and then "This version is for recent AMD videocards only: 7xxx, 2xx and 3xx, 2GB or more."

First, what are "blockchain drivers"? Was this a mistake? It seems that Fury is ok from this part, but then this card is not included in the "recent AMD videocards only: 7xxx, 2xx and 3xx" group.

Can someone clarify please? Thanks.

digimonx

newbie

Activity: 4

Merit: 0

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

For AMD cards, set the following environment variables, especially if you have 2GB cards:

GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

Does this apply only to AMD cards, or Nvidia cards as well?

Thanks!

staman

newbie

Activity: 13

Merit: 0

Quote

Well, i strongly disagree. My personal experience (and plenty of others) is completely opposite to yours

1) how can you even say that out loud? that driver is not even 7 days old

2) OverdriveNTool has been working just fine with blockchain drv (23aug)
3) yes, it let you post it in device manager and yes, it let you mine with it.. but do try enable compute workload and see that mess if you are running 12 cards! And loosing 4mh's per card with NO-dag-driver * 12 cards.. hell no !

Please stay away from such a comments, you are fooling others!

Quote

really? this is where you want to be right? wow. fuck idiots... I guess

https://s1.postimg.org/7gtpwjcqjz/rts.png

see at the bottom: 2*10*570

also on 2) see this:
https://s1.postimg.org/2shog6jc5b/ovrd.png

Watch you language here dude!

1) Awesome.. congratulation! 13 and 25hours considered as stable?
2) what is your point here? look at my post from Saturday morning.. have you invented something in here?
3) WHERE IS YOUR ANSWER ON THIS ONE? Most important part?

Congratulation.. you are running 12 cards, 8 from it with Compute workload enabled, 4 without
It's the best you can get atm from 17.10.2 with Win10-1709, agreed on that one!

Your initial post wasn't showing anything and you shared this prntscr after.
peace!

uDwcHYO

full member

Activity: 363

Merit: 100

can I learn more about minor fixes?

Johnnydex

newbie

Activity: 10

Merit: 0

Quote from: Kukus on October 30, 2017, 08:12:33 AM

I did a try to install new AMD drivers. The clue is that I am unable to change "GPU workload" setting for one card in a rig. It remains at "Graphics" when I trying change it to "Compute". All other cards (similar ones) switched with no problems.

I had the same problem. Rig of 4 Fury X's with one Pro Duo and the Pro wouldn't switch to compute. I gave up and went back to blockchain drivers. Then I read somewhere someone said they had to restart for it to take effect so I reinstalled the drivers and gave it another shot and it worked. All the Fury x's switch fine with just the driver restart but for whatever reason when I enable it on both of the Pro Duo chips it "appears" like it doesn't work but after a reboot all is well.

I can confirm, at least for my Vega rig, that the new drivers seem more stable than the blockchain drivers. I could never dual mine (eth/dcr) on the blockchain drivers with Vega. I wasted countless hours trying. It's been up on the new drivers for a few days now without a hitch.

carlo_0000

legendary

Activity: 1281

Merit: 1003

Quote from: OXUS on October 30, 2017, 10:59:22 AM

Quote from: DJMorgan on October 30, 2017, 10:45:54 AM

Quote from: OXUS on October 30, 2017, 10:38:08 AM

Quote from: Victorio on October 30, 2017, 10:16:30 AM

Quote from: OXUS on October 30, 2017, 09:32:39 AM

i have problem with my rig running claymore .... i get low hashrate on eth for some reason ...

Post your miner configuration (the content of your .bat file).

EthDcrMiner64.exe -epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0xc86bb711033e00abd01b197a57be42421678a987 -epsw x -eworker rig1 -allcoins 1 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal neverrazor.1 -dpsw x

im mining ubiq which have smaller dagger file .....also the normal eth speed is low too

Try uninstalling the driver utility ddu and then install using the installer of wood in the system - for example after unpacking the driver 7zip can test after installing the driver Radeon Software Crimson ReLive Edition Beta for bc

its a nvidia 1060s cards ..... i did a fresh windows installations then put installed the driver now i even updated to the latest one 388.13 ....

strangly all another miners are okay doing the hashrate they should im getting normal hashes on all algos on nicehash miner ...everything is okay but eth

if you have nvidia at low eth speed = it s mean you need to update windows 10 to creator last update, and you problem will be solved

milicic

full member

Activity: 180

Merit: 100

Quote from: PB_SilentMiner on October 30, 2017, 05:12:39 PM

Quote from: wOvAN on October 28, 2017, 06:46:40 PM

Quote from: PB_SilentMiner on October 28, 2017, 03:28:04 PM

Before the Byzantium update, my average hashrate was withing 3-4MH of my reported rate. But as of late its nearer 25-28MH difference.

Any ideas?

Switch from Ethmine to Drawfpool. Share difficulty on E. 4000MH on D. 2000MH. so there should be less stales, or other pool with lower diff per share

press S to see current diff

My current diff is 4000MH. how is this any different to Dwarfpool?

Still does not explain the difference and why it is happening. I am now 31MH difference (this is a whole cards hashrate), I have restarted the rigs, updated miner software, reset clock/mem/power settings.

Made no difference, i really like ethermine and switching is not ideal as I need to mine a full coin before moving.

Anyone else have any ideas?.....

The same thing happens to me on Ethermine, for the last 5 days my average hashrate is at least 5% less then reported hashrate. And even reported hashrate seems to be a little lower then usual...

PB_SilentMiner

newbie

Activity: 36

Merit: 0

Quote from: wOvAN on October 28, 2017, 06:46:40 PM

Quote from: PB_SilentMiner on October 28, 2017, 03:28:04 PM

Before the Byzantium update, my average hashrate was withing 3-4MH of my reported rate. But as of late its nearer 25-28MH difference.

Any ideas?

Switch from Ethmine to Drawfpool. Share difficulty on E. 4000MH on D. 2000MH. so there should be less stales, or other pool with lower diff per share

press S to see current diff

My current diff is 4000MH. how is this any different to Dwarfpool?

Still does not explain the difference and why it is happening. I am now 31MH difference (this is a whole cards hashrate), I have restarted the rigs, updated miner software, reset clock/mem/power settings.

Made no difference, i really like ethermine and switching is not ideal as I need to mine a full coin before moving.

Anyone else have any ideas?.....

henrynguyen20

newbie

Activity: 6

Merit: 0

any one here still have issue with stale share from ethermine.org ?
I'm getting 20% stale share with using claymore v10.0 with eth-only with rig of 8 cards
Also I have another rig with 2 msi rx 570 4Gb, 1 rx 580 4Gb, 1x 1060 6Gb and 1x 1050ti 4Gb and it pull 620 watts after modded and undervoltage, is it normal ?
Thanks

milicic

full member

Activity: 180

Merit: 100

People, does anybody have the exact information about ethereum switching from Pow to Pos? I just read an article that Casper is coming earlier than planned and maybe with the next ethereum upgrade (maybe even before the end of year or early in 2018). What exactly that means for us miners? Some say that it will be hybrid Pow/Pos... But, if it is just Pos, and if it happens in a couple of months, are we doomed?

OXUS

full member

Activity: 253

Merit: 101

KEK

Quote from: Victorio on October 30, 2017, 01:19:48 PM

Quote from: OXUS on October 30, 2017, 10:38:08 AM

EthDcrMiner64.exe -epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0xc86bb711033e00abd01b197a57be42421678a987 -epsw x -eworker rig1 -allcoins 1 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal neverrazor.1 -dpsw x

Your hashrate is at ~50% of your's equipment normal performance. I thought that mining intensity was set wrong (ethi and dcri). After runing a short test, I found that GTX1060 are not very sensible to dcri level (at least DCR). Cranking DCR intensity from 40 to 130, the DCR hashrate increased 190% and ETH hashrate decreased 10%. Such dcri level, to halven the ETH hashrate, should be within 200-300 range, that is either stupid or unsupported by Claymore miner.
Better define explicitly your ethi and dcri, say 16/40, 16/50.
Check your BIOS settings - enable Above 4G decoding/TOLUD (works only in UEFI-enabled systems) and PCI-E speed - switch it to Gen1 or Gen2.

i enabled 4g ... and tried different pci-e gen speed all same results ... the problem is ONLY in the hashrate of eth ... .. i tried another eth miner ... same problem

greatauror28

full member

Activity: 181

Merit: 101

Ethereum Miner

Quote from: scryptr on October 30, 2017, 01:13:33 PM

Quote from: greatauror28 on October 23, 2017, 10:43:22 AM

Quote from: ?? on ??

Quote from: Kumic on October 22, 2017, 04:37:06 AM

Quote from: Call_Me_Bambi on October 21, 2017, 05:43:11 PM

Quote from: greatauror28 on October 21, 2017, 09:42:26 AM

Okay, after 3 months of mining during the last couple weeks rig has been freezing and the last line of the log file indicates:

GPU got incorrect temperature 511 ignore

Thoughts?

I got this error when one of the fans on an RX580 failed. I don't know how long it was running with one failed fan but when I noticed the failed fan the card was very very hot !

In that case, the temperature was so high that the card itself couldn't measure it and that's why you got GPU got incorrect temperature 511.
That's my guess.

No, the card didn't respond - so it returned an code meaning invalid, which is what you see.

Hey Wolf0 do you think this is a failing riser issue? I kinda ruled that out already because it takes days before this happen. I believe if it's a failing riser it would kinda happen right away?

I hate to think this is a GPU issue as they're barely 4 months old.

Quote from: Vann on October 22, 2017, 03:58:07 PM

Make sure Windows didn't update the drivers automatically. On Windows 10 Pro you can set Windows Update to not include drivers. Type 'gpedit' in the search box and in the Group Policy Editor navigate to Administrative Templates ==> Windows Components ==> Windows Update and set 'Do not include drivers with Windows Update' to enabled.

Good man, thanks for sharing this! Appreciated.

IT DEFINITELY COULD BE A RISER--

Risers do not always fail immediately. The riser can overheat, or short within a connection, and fail to work properly. Have you tried the card in a motherboard without a riser? By itself? If you then get the same result, your card is bad. However, it could have failed because of a bad riser, a riser with a short, or with a component that failed due to heat.

Have you swapped a fresh riser into the system? Have you swapped risers in the system to see if the riser produces the same result on another card?

The "511" readout is not good news, but it does not automatically mean the card is dead. And, failing risers can damage a card. Other things to look for is cable friction against a fan, spacing between cards, or placing the card in a hot point within the system (not good). --scryptr

I just disconnected/reconnected the cables, reseat the GPUs onto the riser ports and the problem hasn't resurfaced in more than 8 days now.

Fingers crossed.

Quote from: Jup1t3rR on October 30, 2017, 02:08:06 PM

Quote from: greatauror28 on October 30, 2017, 08:13:59 AM

Quote from: staman on October 30, 2017, 08:08:15 AM

Quote from: Ursul0 on October 30, 2017, 06:58:09 AM

ok gyus some good news:
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform

all good news indeed.

Well, i strongly disagree. My personal experience (and plenty of others) is completely opposite to yours

1) how can you even say that out loud? that driver is not even 7 days old

2) OverdriveNTool has been working just fine with blockchain drv (23aug)
3) yes, it let you post it in device manager and yes, it let you mine with it.. but do try enable compute workload and see that mess if you are running 12 cards! And loosing 4mh's per card with NO-dag-driver * 12 cards.. hell no !

Please stay away from such a comments, you are fooling others!

Actually what Ursul0 cited is pretty factual, as I've experienced it myself.
This driver, together with the Win10 FCU fixed my OpenCL issues - and i've tried everything under the sun to fix it. I used to use aug 23 blockchain driver and a recently-installed win10 pro without any updates.

I only run 8 cards but here's some proof that's it's stable.

Previously with the setup above, miner doesn't get past 3 hours without openCL issues.
It has the dag fix just like the blockchain drivers - and this version is fully-supported by AMD and not in Beta status.

Note that you have to enable *compute* settings in each card in the Radeon Settings for this to work.

whats your power usage mate?

i got rx580s 8gb hynix and would love you know what your power usage is

currently im running 6gpu @ 170MH - 790W

I pull ~1250w at the wall with 240Mh eth and 6.1Gh dcr.

I think ~123w per card doing eth-only is pretty high. I dual-mine so ~140w is really what the Nitros consume if properly undervolted.

ironeye

newbie

Activity: 1

Merit: 0

I am using a Nvidia 970 and a Nvidia 1050ti to mine but I am unable to find the setting that will stop my 970 from only hashing out 1.5 while my 1050ti is at 13.

Does anyone have an idea?

Cheers!

Jup1t3rR

newbie

Activity: 16

Merit: 0

Quote from: greatauror28 on October 30, 2017, 08:13:59 AM

Quote from: staman on October 30, 2017, 08:08:15 AM

Quote from: Ursul0 on October 30, 2017, 06:58:09 AM

ok gyus some good news:
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform

all good news indeed.

https://s1.postimg.org/1jpgnkmudb/10x570.png

Well, i strongly disagree. My personal experience (and plenty of others) is completely opposite to yours

1) how can you even say that out loud? that driver is not even 7 days old

2) OverdriveNTool has been working just fine with blockchain drv (23aug)
3) yes, it let you post it in device manager and yes, it let you mine with it.. but do try enable compute workload and see that mess if you are running 12 cards! And loosing 4mh's per card with NO-dag-driver * 12 cards.. hell no !

Please stay away from such a comments, you are fooling others!

Actually what Ursul0 cited is pretty factual, as I've experienced it myself.
This driver, together with the Win10 FCU fixed my OpenCL issues - and i've tried everything under the sun to fix it. I used to use aug 23 blockchain driver and a recently-installed win10 pro without any updates.

I only run 8 cards but here's some proof that's it's stable.

https://i.imgur.com/BH9cPKG.png

Previously with the setup above, miner doesn't get past 3 hours without openCL issues.
It has the dag fix just like the blockchain drivers - and this version is fully-supported by AMD and not in Beta status.

Note that you have to enable *compute* settings in each card in the Radeon Settings for this to work.

whats your power usage mate?

i got rx580s 8gb hynix and would love you know what your power usage is

currently im running 6gpu @ 170MH - 790W

Victorio

full member

Activity: 281

Merit: 100

Quote from: OXUS on October 30, 2017, 10:38:08 AM

EthDcrMiner64.exe -epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0xc86bb711033e00abd01b197a57be42421678a987 -epsw x -eworker rig1 -allcoins 1 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal neverrazor.1 -dpsw x

Your hashrate is at ~50% of your's equipment normal performance. I thought that mining intensity was set wrong (ethi and dcri). After runing a short test, I found that GTX1060 are not very sensible to dcri level (at least DCR). Cranking DCR intensity from 40 to 130, the DCR hashrate increased 190% and ETH hashrate decreased 10%. Such dcri level, to halven the ETH hashrate, should be within 200-300 range, that is either stupid or unsupported by Claymore miner.
Better define explicitly your ethi and dcri, say 16/40, 16/50.
Check your BIOS settings - enable Above 4G decoding/TOLUD (works only in UEFI-enabled systems) and PCI-E speed - switch it to Gen1 or Gen2.

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: greatauror28 on October 23, 2017, 10:43:22 AM

Quote from: ?? on ??

Quote from: Kumic on October 22, 2017, 04:37:06 AM

Quote from: Call_Me_Bambi on October 21, 2017, 05:43:11 PM

Quote from: greatauror28 on October 21, 2017, 09:42:26 AM

Okay, after 3 months of mining during the last couple weeks rig has been freezing and the last line of the log file indicates:

GPU got incorrect temperature 511 ignore

Thoughts?

I got this error when one of the fans on an RX580 failed. I don't know how long it was running with one failed fan but when I noticed the failed fan the card was very very hot !

In that case, the temperature was so high that the card itself couldn't measure it and that's why you got GPU got incorrect temperature 511.
That's my guess.

No, the card didn't respond - so it returned an code meaning invalid, which is what you see.

Hey Wolf0 do you think this is a failing riser issue? I kinda ruled that out already because it takes days before this happen. I believe if it's a failing riser it would kinda happen right away?

I hate to think this is a GPU issue as they're barely 4 months old.

Quote from: Vann on October 22, 2017, 03:58:07 PM

Make sure Windows didn't update the drivers automatically. On Windows 10 Pro you can set Windows Update to not include drivers. Type 'gpedit' in the search box and in the Group Policy Editor navigate to Administrative Templates ==> Windows Components ==> Windows Update and set 'Do not include drivers with Windows Update' to enabled.

Good man, thanks for sharing this! Appreciated.

IT DEFINITELY COULD BE A RISER--

Risers do not always fail immediately. The riser can overheat, or short within a connection, and fail to work properly. Have you tried the card in a motherboard without a riser? By itself? If you then get the same result, your card is bad. However, it could have failed because of a bad riser, a riser with a short, or with a component that failed due to heat.

Have you swapped a fresh riser into the system? Have you swapped risers in the system to see if the riser produces the same result on another card?

The "511" readout is not good news, but it does not automatically mean the card is dead. And, failing risers can damage a card. Other things to look for is cable friction against a fan, spacing between cards, or placing the card in a hot point within the system (not good). --scryptr

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