Author

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

sr. member
Activity: 518
Merit: 250
I am a meat Popsicle
I cannot seem to find an answer for this

I want each of my rigs to appear as a worker on the Ethereum pool, now the Pool states after your etereum address put .

for for example

-ewal 0xdc01a716e6fdf9d8ddba77971f4d5ffd3bd3c22b.1

when I do this I get an error message and disconnect from pool, so this is not working for me.

How can I distinguish each rig as a separate worker on the pool of which I cannot create workers to begin with
newbie
Activity: 36
Merit: 0
My 24hr averages are usually very close to reported hashrate.

Even on a VEGA 64 that is OC to 41MH?  

Any other GPU I've used in the past the 24 avg lines up with reported ( within ~1MH ).  

Vega 64 is stuck at 32 MH for 24 hour average for me.  It lends credence to the stories about how the reported hashrate is incorrect for the VEGA 64.

My theory?  Some throttling is happening due to some setting.  In Claymore spam the statistics button 's' (I mean really spam, try to get a few reports a second).  I see it is sometimes 41 MH then sometimes I see as low as 23 MH.   I think the card is throttling for a quarter second every second or so.

Anyway, something weird is definitely going on.  I'm holding my breath for someone to post legit mining results.  Lets see your ethermine page, average and all of a OC Vega 64 running 41MH and actually getting close to that in 24hr avg.  Again, I can get my card to 41 MHs reported no problem, still comes out as 32MH for 24 hours avg.

member
Activity: 107
Merit: 10
My 24hr averages are usually very close to reported hashrate.
sr. member
Activity: 465
Merit: 252
The MEGA files are infected with viruses / trojans, but the GOOGLE ones are fine....

This is why I kept repeating over and over and over again to Claymore.

POST THE HASHES OR THE SIGNATURES OF YOUR EXECUTABLES and he never listens.

His MEGA account might of been compromised.

Is this true? Can someone without a doubt confirm this? and If this is the case what can or should we do to reverse any damages done to our miners?
newbie
Activity: 36
Merit: 0
It looks like the people posting bullshit power draws and error or misreported hashrates on miners or bullshit memory OCs that don't work, etc are simply trying to trick crypto-miners into paying inflated prices for RX Vega GPUs.

They are probably tied into GPU distributors or wholesalers!
O yeah! You should better buy this completely well-known gtx1060 and then discover its shitty hynix mem with max 19mhs speed ))) Same goes to gtx1070, forget about samsung 2400mem, pray for micron ... but probably will get hynix too )) And this is for $500 ))
Or overpriced $800 gtx1080ti that is good only on non-memory related algos ... forget about eth, xmr and neoscrypt with it


Not trying to pick a fight nor come off offensive as it seems people are very sensitive about the subject of mining.

I love my VEGA 64 for mining.

I've got it mining at 37.5MH + 1450 DCR.  Stable for weeks.  On Ethermine the reported is consistently 37MH.  The 24 average has never once gone above 32MH.  I tried Blockchain driver for 2 weeks, 17.8 for a week and 17.9 for 2 days.  I realize the time difference confounds the research quite a bit but this shit has only been out a few weeks.

Anyway, I do not for a second disbelieve people are pushing these numbers.  In fact I can easily get my card to single mine at 41MH.

What I am suggesting is that something is fishy.  Even solo mining with reported at 41MH I cannot get above 24 average of 32MH.  Something is definitely weird about these results.  On other cards after a few days the 24hr average is usually within 1MH of the reported.  With the VEGA 64 it is always 32MH, no matter what the reported is saying.

There is a lot yet to learn with the VEGA 64 and I heard because people see posts like mine and get really sensitive and start whining "FUDer" that this problem with no be fixed.
newbie
Activity: 5
Merit: 0
What driver to use for AMD RX550 4GB?

Thank you!
member
Activity: 107
Merit: 10
More than one person reporting hashrates in the 40's.  What I can tell you is that Vega is very heat sensitive.  If the memory gets above 80C performance falls off dramatically.  Core temp also has a major effect on performance.  It seems likely to me the doubters are not optimizing their settings or lost the silicon lottery.

I've got near a month of mining at 40 and 42Mh/s with managable temps and apparently decent power consumption.
full member
Activity: 206
Merit: 100
Dear all,
anyone can hel me to make script so i can choose GPU 1-3 ETH only and GPU 4-6 ETH+DCR?


Hello

Use 2 launchers with option -di 012 for first one
and -di 345 for second



don't think it's a proper advice. you should try something like this:

#0,1,2 GPUs are in ETH only mode:
-mode 1-012

Thanks, I discover this option
What about fee ? Is-it 1% or 2% ?
legendary
Activity: 1510
Merit: 1003
If you could post Claymore screenshot, GPU-Z screenshot as well as kill-a-watt photo, that'd be nice.

It would give credibility to the findings you reported, as apparently lots are doubtful with your experiment.

I bet many would be swayed to buy a 56 if these were indeed a fact.

No need of so much data. All you need is to run Vega with memclock 1080-1100mhs keeping gpu voltage <=900mV
gpu clock can be from ~900 to ~1400mhz.
With this you will get 43-44mhs eth or 1500-1600xmr (depending of gpu clock) with 130-160watt from the wall.
All you need is blockchain driver, win10 and HBCC mode enabled.
The main problem is to make it run under 900mV keeping memclock high.
There are several hacks to do it but they are being kept private now. Maybe soon somebody makes it public and we won't find cheap vega's at stores anymore ))
legendary
Activity: 1092
Merit: 1004
Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?


Well my findings are the opposite, vega 56 with moded bios can do 42-43Mhs. I can't measure the power consumption. Also the 64bios can let you clock the memory on the 56 to 1100Mhz.
Dual-mining  works fine with all drivers.

Setting lower voltages in wattman seems to lower the power consumtion, but I relly can't test much without a damned watt-o-meter.
vega 56 43.7 mhs 155watt at the wall, 1600 hs xmr

If you could post Claymore screenshot, GPU-Z screenshot as well as kill-a-watt photo, that'd be nice.

It would give credibility to the findings you reported, as apparently lots are doubtful with your experiment.

I bet many would be swayed to buy a 56 if these were indeed a fact.

Plenty of people have at least one RX Vega 56 or 64 GPU - most of us know this kinds of spam slippery posts are bullshit.
full member
Activity: 181
Merit: 101
Ethereum Miner
Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?


Well my findings are the opposite, vega 56 with moded bios can do 42-43Mhs. I can't measure the power consumption. Also the 64bios can let you clock the memory on the 56 to 1100Mhz.
Dual-mining  works fine with all drivers.

Setting lower voltages in wattman seems to lower the power consumtion, but I relly can't test much without a damned watt-o-meter.
vega 56 43.7 mhs 155watt at the wall, 1600 hs xmr

If you could post Claymore screenshot, GPU-Z screenshot as well as kill-a-watt photo, that'd be nice.

It would give credibility to the findings you reported, as apparently lots are doubtful with your experiment.

I bet many would be swayed to buy a 56 if these were indeed a fact.
legendary
Activity: 1092
Merit: 1004
It looks like the people posting bullshit power draws and error or misreported hashrates on miners or bullshit memory OCs that don't work, etc are simply trying to trick crypto-miners into paying inflated prices for RX Vega GPUs.

They are probably tied into GPU distributors or wholesalers!
O yeah! You should better buy this completely well-known gtx1060 and then discover its shitty hynix mem with max 19mhs speed ))) Same goes to gtx1070, forget about samsung 2400mem, pray for micron ... but probably will get hynix too )) And this is for $500 ))
Or overpriced $800 gtx1080ti that is good only on non-memory related algos ... forget about eth, xmr and neoscrypt with it


Hey, I agree with you on that - plenty of super-crap prices on the Nvidia side as well.

All of that bullshit, that Nvidia GPUs can mine at plus 1000mhz using samsung.

Got my hands on 1060 3GB with samsung memory - find out that over 800mhs - the cards does not mine properly.

People, keep posting bullshit memory speeds for Nvidia GPUs as well, and they don't work either.
sr. member
Activity: 857
Merit: 262
Dear all,
anyone can hel me to make script so i can choose GPU 1-3 ETH only and GPU 4-6 ETH+DCR?


Hello

Use 2 launchers with option -di 012 for first one
and -di 345 for second



don't think it's a proper advice. you should try something like this:

#0,1,2 GPUs are in ETH only mode:
-mode 1-012
legendary
Activity: 1510
Merit: 1003
It looks like the people posting bullshit power draws and error or misreported hashrates on miners or bullshit memory OCs that don't work, etc are simply trying to trick crypto-miners into paying inflated prices for RX Vega GPUs.

They are probably tied into GPU distributors or wholesalers!
O yeah! You should better buy this completely well-known gtx1060 and then discover its shitty hynix mem with max 19mhs speed ))) Same goes to gtx1070, forget about samsung 2400mem, pray for micron ... but probably will get hynix too )) And this is for $500 ))
Or overpriced $800 gtx1080ti that is good only on non-memory related algos ... forget about eth, xmr and neoscrypt with it
legendary
Activity: 1092
Merit: 1004
Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?


Well my findings are the opposite, vega 56 with moded bios can do 42-43Mhs. I can't measure the power consumption. Also the 64bios can let you clock the memory on the 56 to 1100Mhz.
Dual-mining  works fine with all drivers.

Setting lower voltages in wattman seems to lower the power consumtion, but I relly can't test much without a damned watt-o-meter.
vega 56 43.7 mhs 155watt at the wall, 1600 hs xmr

What with these bullshit posts?

RX Vega 56 tops out at 35.5mhs for 200 watts.

1) RX 580/570 Beta Drivers produce buggy misreported hashrates for RX Vega cards - 35.5mhs becomes 38mhs.

2) RX Vega 56 memory tops out at 930mhz - speeds above find less shares, and hashrate increase is a misreport.

3) A badly mining RX Vega 56 - will have artificially low watts draw. Yes, when they are mining badly and not finding many shares, you will know because the power draw is kinda low.

4) The reference blower fan is very inefficient and draws up to 28watts - I'm sure when AIB version comes out there will be 15watt-20watt reduction with energy saving fans.  





I guess everyone is just bullshitting and you can't possibly be wrong?   Roll Eyes


I made a post not to many pages ago that went completely ignored because everyone just wants see higher numbers.  

Blockchain drivers vs Non-Blockchain drivers.  Stock vs all these fancy OC settings people are sharing.  
- Two weeks of mining on blockchain my avg hashrate is 32 yet reported it 37.  
- A week mining on 17.8 drivers, avg is 32 reported is 32.
- 48 hours mining with OC settings to get a reported of 41MH, still avg to 32.

All on EtherMine.



You have 1 post and are FUD spreading.  Maybe we'd be listening if someone with some credibility and half a brain on how to actually test things chimed in.

I created an account to come inform people my findings.  Ignore it all you want.  I don't care.  

Also here for some help which if you don't want to give then why are you here?  Where is your research and data?  Have you shared 1 piece of evidence?

It looks like the people posting bullshit power draws and error or misreported hashrates on miners or bullshit memory OCs that don't work, etc are simply trying to trick crypto-miners into paying inflated prices for RX Vega GPUs.

They are probably tied into GPU distributors or wholesalers!
full member
Activity: 206
Merit: 100
Dear all,
anyone can hel me to make script so i can choose GPU 1-3 ETH only and GPU 4-6 ETH+DCR?


Hello

Use 2 launchers with option -di 012 for first one
and -di 345 for second

newbie
Activity: 15
Merit: 0
Dear all,
anyone can hel me to make script so i can choose GPU 1-3 ETH only and GPU 4-6 ETH+DCR?

so far my script just like this:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool asia1.ethermine.org:4444 -ewal XXXXXXXXXXXXXXXXXXXXXXXXXXXXX.Rig1 -epsw x


thanks for the help.

Regards from Indonesia
newbie
Activity: 36
Merit: 0
Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?


Well my findings are the opposite, vega 56 with moded bios can do 42-43Mhs. I can't measure the power consumption. Also the 64bios can let you clock the memory on the 56 to 1100Mhz.
Dual-mining  works fine with all drivers.

Setting lower voltages in wattman seems to lower the power consumtion, but I relly can't test much without a damned watt-o-meter.
vega 56 43.7 mhs 155watt at the wall, 1600 hs xmr

What with these bullshit posts?

RX Vega 56 tops out at 35.5mhs for 200 watts.

1) RX 580/570 Beta Drivers produce buggy misreported hashrates for RX Vega cards - 35.5mhs becomes 38mhs.

2) RX Vega 56 memory tops out at 930mhz - speeds above find less shares, and hashrate increase is a misreport.

3) A badly mining RX Vega 56 - will have artificially low watts draw. Yes, when they are mining badly and not finding many shares, you will know because the power draw is kinda low.

4) The reference blower fan is very inefficient and draws up to 28watts - I'm sure when AIB version comes out there will be 15watt-20watt reduction with energy saving fans.  





I guess everyone is just bullshitting and you can't possibly be wrong?   Roll Eyes

I made a post not to many pages ago that went completely ignored because everyone just wants see higher numbers.  

Vega 64 here.

Blockchain drivers vs Non-Blockchain drivers.  Stock vs all these fancy OC settings people are sharing.  
- Two weeks of mining on blockchain drivers my avg hashrate is 32 yet reported it 37.  
- A week mining on 17.8 drivers, avg is 32 reported is 32.
- 48 hours mining with OC settings on 17.9 to get a reported of 41MH, still avg to 32.

All on EtherMine.  

newbie
Activity: 57
Merit: 0
AB may solve some issues with certain ease, but installing it may have impact on other apps using/accessing GPU drivers/configs.
Overall you should try to spend few hours or even days and find alternative solution(to using AB) as it may save you more time in the long run.  
This AB stuff is just too fucking invasive and persistent for my taste.

Re bios mod: Look in my recent posts, you can find there all the numbers&info on what I do with 470s.

Drivers installed the way I like: 1) don't run crimson-whatever.exe, instead unzip it 2) open device manager and find your graphic adapters(should be not identified at this point) and choose there option to "update driver"-> select folder manually 3) repeat 2) if needed for other card/s

I using the BIOS mods in same way you do but after switching to Claymore 10.0 something strange happens with one rig - it does not work with config.txt imported from v9.8, cases:
1) system completely hangs during initialization
2) some cards do not start to hash at all (0.0MH speed)
3) some cards starts with slower speeds (for example 22MH/s or lower)

Checked via HWinfo - it shows similar voltages and frequencies (of course exept case 1).
So rolled this rig back to 9.8 which gives stable mining.
full member
Activity: 1123
Merit: 136
Issues with Vega 56:

Blockchain drivers lockup if attempting to mine with more than 1 card.
Blockchain drivers crash dual mining.

Using 17.9.2:
Can be bios modded with Vega 64 bios, however this makes mining slower slightly, and changing mem clock has no effect.
Slightly slower than blockchain drivers, but works better, and can dual mine.
Lowering power limit or dual mining without raising ~+20 makes mem constantly throttle to 700MHz.
Setting voltage doesn't really seem to affect power usage at all.
Clockspeed seems to have 0 impact on power usage, very little impact dual mining.
Setting clockspeed doesn't set at a fixed speed, it somewhat affects it, but it has a mind of its own.
Mem can be set ~950MHz, possibly up to ~980MHz.
CM 9.8 slightly faster ETH it seems.
Best profit seems dual mining ~34.5MHz ETH, 140MHz LBRY, +20% power, 1300 core, 9xx voltage.


Anyone have anything to add or suggestions?


Well my findings are the opposite, vega 56 with moded bios can do 42-43Mhs. I can't measure the power consumption. Also the 64bios can let you clock the memory on the 56 to 1100Mhz.
Dual-mining  works fine with all drivers.

Setting lower voltages in wattman seems to lower the power consumtion, but I relly can't test much without a damned watt-o-meter.
vega 56 43.7 mhs 155watt at the wall, 1600 hs xmr

What with these bullshit posts?

RX Vega 56 tops out at 35.5mhs for 200 watts.

1) RX 580/570 Beta Drivers produce buggy misreported hashrates for RX Vega cards - 35.5mhs becomes 38mhs.

2) RX Vega 56 memory tops out at 930mhz - speeds above find less shares, and hashrate increase is a misreport.

3) A badly mining RX Vega 56 - will have artificially low watts draw. Yes, when they are mining badly and not finding many shares, you will know because the power draw is kinda low.

4) The reference blower fan is very inefficient and draws up to 28watts - I'm sure when AIB version comes out there will be 15watt-20watt reduction with energy saving fans.  





I guess everyone is just bullshitting and you can't possibly be wrong?   Roll Eyes
Jump to: