plbartie
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 76
Merit: 10
ALTCOM wallet: AYGDb1Zwf3vfs2xC4D1G63wwy9RLU5Kb5r
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 12:57:49 PM |
|
Love this miner, thanks to the creator! EVGA GTX 1070 8gb Micron Memory AB: Power 75 Temp 80 Core +100 Mem +700 Dual Mine ETH + SIA ETH - Total Speed: 31.452 Mh/s SC - Total Speed: 314.522 Mh/s https://imgur.com/46Im1Do
|
|
|
|
fmz89
Legendary
Offline
Activity: 1764
Merit: 1002
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 01:00:27 PM |
|
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?
mining monero with vega 56 better profit than dual mine and more stable What is Vega 56 give on stock clocks for ETH? I understand your ~43 MH/s is with OC'ed Vega right? 43mhs at 932 mhz, default stock vega 56 (bios 64) its 1630 mhz, massive underclocked Thanks Do you remember when it was stock how much ETH Hash did it give you before you bios modded it? And how much Power consumption? 37-38 mhs with bios stock around 200 watt 43-44 bios 64 around 145-150 watt
|
|
|
|
Demarsac
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 01:41:03 PM |
|
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?
mining monero with vega 56 better profit than dual mine and more stable What is Vega 56 give on stock clocks for ETH? I understand your ~43 MH/s is with OC'ed Vega right? 43mhs at 932 mhz, default stock vega 56 (bios 64) its 1630 mhz, massive underclocked Thanks Do you remember when it was stock how much ETH Hash did it give you before you bios modded it? And how much Power consumption? 37-38 mhs with bios stock around 200 watt 43-44 bios 64 around 145-150 watt Great thanks for your info. I will pm you for more...
|
|
|
|
laineux
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 02:21:15 PM |
|
Hello everybody I am new miner and want to thank Claymore and all people speaking here It was helpfull to me First computer at about 109 MH on ETH only (1x 1050 Ti + 3x 1070) I had some issues to calculate threads affinity from binary to hexa, so I make a small javascript tool here http://www.toutjavascript.com/tools/convert-online-binary-hexa-decimal.php?lang=enHope this will help If you have other needs to compute some stuff online, just tell me... I will try to push it.
|
|
|
|
thevictimofuktyranny
Legendary
Offline
Activity: 1092
Merit: 1004
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 02:55:51 PM Last edit: September 11, 2017, 03:29:09 PM by thevictimofuktyranny |
|
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.
|
|
|
|
Ursul0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 03:10:49 PM Last edit: September 11, 2017, 03:42:03 PM by Ursul0 |
|
Thanks but there is around half a meter minimum either side of the rig and in a fairly big area... What Bios are you running? I'm mining ETH and SIA with 25 on ETH and 750Mh on Sia. Any idea why I'm getting 0 readings from Claymore?
space is not the key - air exchange is, make the air flow in. you probably have some issues with APIs accesss, drivers and shitty stuff like AB. do uninstall of AB, do DDU, setup drivers manually: point+click in device manager for blockchain beta driver folder (don't run amd EXE), patch signature, mod bois, run claymore 9.8+ = enjoy So AB is that bad aye? OK on the uninstal and Display Driver Uninstaller. I originally ran the express install for the crimson blockchain driver... How would I do the point and click installation instead? Patch signature ok. What are you using to Mod the bios? I have 0 experience in it so wasn't comfortable moding ( which is why I chose to go with anorak bios). Sorry if dumb questions but trying to not make a mess of this 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
|
|
|
|
P00P135
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 03:52:39 PM |
|
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](https://bitcointalk.org/Smileys/default/rolleyes.gif)
|
|
|
|
Kukus
Newbie
Offline
Activity: 57
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 03:56:55 PM |
|
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.
|
|
|
|
miner1337
Newbie
Offline
Activity: 36
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 04:12:19 PM |
|
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](https://bitcointalk.org/Smileys/default/rolleyes.gif) 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.
|
|
|
|
arjet
Newbie
Offline
Activity: 15
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 04:53:51 PM |
|
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
|
|
|
|
laineux
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 05:14:50 PM |
|
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
|
|
|
|
thevictimofuktyranny
Legendary
Offline
Activity: 1092
Merit: 1004
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 05:47:16 PM |
|
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](https://bitcointalk.org/Smileys/default/rolleyes.gif) 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!
|
|
|
|
rednoW
Legendary
Offline
Activity: 1510
Merit: 1003
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 05:59:36 PM |
|
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
|
|
|
|
Ursul0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 06:12:02 PM |
|
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
|
|
|
|
thevictimofuktyranny
Legendary
Offline
Activity: 1092
Merit: 1004
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 06:22:50 PM |
|
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.
|
|
|
|
greatauror28
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 181
Merit: 101
Ethereum Miner
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 06:26:03 PM |
|
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.
|
I build and sell rigs! I also sell ssd clones of the most stable Windows+Claymore+AMD driver combo you'd ever used.
|
|
|
thevictimofuktyranny
Legendary
Offline
Activity: 1092
Merit: 1004
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 06:34:13 PM |
|
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.
|
|
|
|
rednoW
Legendary
Offline
Activity: 1510
Merit: 1003
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 06:53:16 PM |
|
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 ))
|
|
|
|
laineux
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 07:17:35 PM |
|
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% ?
|
|
|
|
NavyCuda
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 107
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 11, 2017, 07:47:53 PM |
|
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.
|
|
|
|
|