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

[NumbNuts]

Can you mine ok in Eth only mode?  Remove everything after -epsw x and add  -mode 1.  If that works then maybe you need to try someone elses bat file as a test.

Here's my bat file if you wanted to try it for a few seconds as a test.
ethdcrminer64.exe -epool us2.ethermine.org:4444 -ewal 0xc9e765d936f877e3f39d313f7dcb9a5e596d1c6c.MainPC -epsw x -dpool dcr.suprnova.cc:3252 -dwal NumbNuts.numbnuts -dpsw x -allpools 1

[Yohow]

Hi all,

I have done quite a lot of research but haven't found a resolution to this problem - hopefully someone can help me on this.

Mining rig:
3 x MSI RX 580 8 GB cards (not Armor/Sapphire etc) - has single 8 pin power connector, single fan, no BIOS switch
Windows 10
SSD with 4 GB RAM
Installed Claymore version 10 Dual miner - Ethereum mining running well and stable but issue is that I cannot get Decred to authorize

Getting:
Socket was closed remotely (by pool)
 DCR: Job timeout, disconnect, retry in 20 sec...

Start.bat command:
EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal 0x31be6e3~~~~~~~~~~~~~~~~~98c6.miner2 -dpool dcr.suprnova.cc:3252 -dwal myloginname.miner1 -dpsw 2222 -allpools 1

Troubleshooting:
- I have changed the password for the worker to match Claymore (x, 2222, other) - unable to leave the password blank for the worker
- verified Suprnova login (though there is an "x" in the active column?)
- attempted both weblogin name as well as email address used for profile
- added port 3252 in Windows firewall for both incoming and outgoing connections
- added miner to router's DMZ
- tried with/without stratum+tcp
- attempted -dpool dcr.suprnova.cc:3252 -dwal suprnova.1 -dpsw x -allpools 1 as detailed on suprnova's website
- though I can't recall which other decred pools I used but all got the same error

Any assistance or suggestions would be greatly appreciated!!

Try to change "miner1" to your "worker name" and write "-dpsw x" command too.

Appreciations here (ETH) 0x57137Aecf8d11b60522d53eD2b0Baf0215FD0b61

Suprnova already has "miner1" as a worker name - and have tried -dpsw x and with specific password as well - no change

Okay but your worker real name is miner1? Or another? You should put the real worker name on start.bat and in supernova, however try to "update worker" on dcr.suprnova.cc account settings and keep the "-dpsw x" command. Of course you must write the "-epsw x" command before "-dpool" command on start.bat

No dice.

Here is the updated start.bat:

EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal 0x31be6e3~~~~~~~~~8998c6.miner2 -epsw x -dcoin dcr -dpool dcr.suprnova.cc:3252 -dwal webloginname.worker1 -dpsw x -allpools 1

My "webloginname" of course matches the username I use for Suprnova and although I previously used Miner1 as my worker name, I changed to worker1/worker2 (intend to run both rigs) but still running into same error as in original post.

What's especially frustrating is that is says that I'm connected to Suprnova but then the pool disconnects me.  Is there anything within Suprnova I need to do other than register an account and create a worker? There is an "x" in the Active column when looking at my configured workers - or is this just a reflection that they're not connecting?

Note - I tried this on another rig - same issues.

Try to write "webloginname.webloginname" or "miner1.miner1" or "worker1.worker1" (or the name you had choosen for your worker) on start.bat and update your worker on account settings. "-dcoin dcr" isn't necessary. You also can create a new worker. The X means your worker isn't active

[idothemining]

First off, I wanted to thank you, Claymore! Keep up the great work!

One little (annoying) issue, though (v 10.0): when mining with a 1070 and a Vega 56, the miner will not detect the 1070. If I shut it down and unplug the Vega, the miner will see the 1070 and mine away without issue.

Very confused.

Any help would be greatly appreciated!

System:
Win10
ASUS GTX 1070
Driver updated in August
Sapphire Vega 56
Blockchain driver, fresh install
16 GB RAM

Attempt at a fix:
Plugged the Vega into different PCI-e slots on the mobo (x1 and x16, both above and below the 1070), no change.

[cdnminer]

Hi all,

I have done quite a lot of research but haven't found a resolution to this problem - hopefully someone can help me on this.

Mining rig:
3 x MSI RX 580 8 GB cards (not Armor/Sapphire etc) - has single 8 pin power connector, single fan, no BIOS switch
Windows 10
SSD with 4 GB RAM
Installed Claymore version 10 Dual miner - Ethereum mining running well and stable but issue is that I cannot get Decred to authorize

Getting:
Socket was closed remotely (by pool)
 DCR: Job timeout, disconnect, retry in 20 sec...

Start.bat command:
EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal 0x31be6e3~~~~~~~~~~~~~~~~~98c6.miner2 -dpool dcr.suprnova.cc:3252 -dwal myloginname.miner1 -dpsw 2222 -allpools 1

Troubleshooting:
- I have changed the password for the worker to match Claymore (x, 2222, other) - unable to leave the password blank for the worker
- verified Suprnova login (though there is an "x" in the active column?)
- attempted both weblogin name as well as email address used for profile
- added port 3252 in Windows firewall for both incoming and outgoing connections
- added miner to router's DMZ
- tried with/without stratum+tcp
- attempted -dpool dcr.suprnova.cc:3252 -dwal suprnova.1 -dpsw x -allpools 1 as detailed on suprnova's website
- though I can't recall which other decred pools I used but all got the same error

Any assistance or suggestions would be greatly appreciated!!

Try to change "miner1" to your "worker name" and write "-dpsw x" command too.

Appreciations here (ETH) 0x57137Aecf8d11b60522d53eD2b0Baf0215FD0b61

Suprnova already has "miner1" as a worker name - and have tried -dpsw x and with specific password as well - no change

Okay but your worker real name is miner1? Or another? You should put the real worker name on start.bat and in supernova, however try to "update worker" on dcr.suprnova.cc account settings and keep the "-dpsw x" command. Of course you must write the "-epsw x" command before "-dpool" command on start.bat

No dice.

Here is the updated start.bat:

EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal 0x31be6e3~~~~~~~~~8998c6.miner2 -epsw x -dcoin dcr -dpool dcr.suprnova.cc:3252 -dwal webloginname.worker1 -dpsw x -allpools 1

My "webloginname" of course matches the username I use for Suprnova and although I previously used Miner1 as my worker name, I changed to worker1/worker2 (intend to run both rigs) but still running into same error as in original post.

What's especially frustrating is that is says that I'm connected to Suprnova but then the pool disconnects me.  Is there anything within Suprnova I need to do other than register an account and create a worker? There is an "x" in the Active column when looking at my configured workers - or is this just a reflection that they're not connecting?

Note - I tried this on another rig - same issues.

Try to write "webloginname.webloginname" or "miner1.miner1" or "worker1.worker1" (or the name you had choosen for your worker) on start.bat and update your worker on account settings. "-dcoin dcr" isn't necessary. You also can create a new worker. The X means your worker isn't active

Still no dice but here's an update...I've used the bat file as provided by NumbNuts above this last post (thanks for that by the way!!!) and got the same issue...so maybe this is a network issue?

I tried "weblogin.weblogin" and I also tried some BS entry after -dwal and got the exact same error.  I couldn't use worker.worker as I would need to create a new Suprnova profile unless I misunderstood your suggestion above.

Have you added the environmental variables to the start.bat file as well?  So what I've done in the start.bat (in full):

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 us1.ethermine.org:4444 -ewal 0x31be6~~~~~~~~~~~~~~8998c6.miner2 -epsw x -dpool dcr.suprnova.cc:3252 -dwal cd$$$ner.cd$$$ner -dpsw x

I should say that Ether is mining just fine.  I can let Claymore run as is all night and Ether will continue to mine with Decred erroring.

Any AV / firewall / router things I should be looking for?  Keep in mind I've added port 3252 to Windows Firewall, disabled Windows Firewall, added rig to router DMZ and disabled AV - all to no avail.

[NumbNuts]

I don't use the variables in the bat file as I think they are only necessary for AMD cards and I have Nvidia.
If it did the same with my bat file then I'd say your bat file is fine, not sure what would be causing the issue though.

[th00ber]

Update. Vega 56
36MH/s 135W at wall (wattmeter)

-15% powerlimit (But I guess it's not usefull because I reduce a lot the GPU clock, I 'll check the effect of this later
Core 925
Mem 970
Fan 80%

https://imgur.com/a/VCXm7

Setting the GPU core clocks to low impairs share find times!

May make you feel good to see 36mhs, but you won't be getting hashing rewards at that rate!

I guess, you'll need to run it for week to see whether you are getting what the calculator says you should be getting for 36mhs (minus fees).

I reckon it will be something much lower.

I was averaging 2% stale shares with a core clock of 852Mhz with VegaFE.

Take a GTX 1070 as an example: Run it without touching the GPU clock; plus 500mhz on the memory and 65% on power slider.

That will be your baseline for successful solutions sent back to the pool.

Run it with minus 125mhz on the GPU core and plus 500mhz on the memory and 65% on power slider.

It will be 3% less successful at pool doing work and you will get 3% less shares, which equates to 3% less coin rewards.

Dwarfpool, show 105 MH/s reported on pool for 108 on claymore.
Seems ok for me with Vega 56

[Yohow]

Hi all,

I have done quite a lot of research but haven't found a resolution to this problem - hopefully someone can help me on this.

Mining rig:
3 x MSI RX 580 8 GB cards (not Armor/Sapphire etc) - has single 8 pin power connector, single fan, no BIOS switch
Windows 10
SSD with 4 GB RAM
Installed Claymore version 10 Dual miner - Ethereum mining running well and stable but issue is that I cannot get Decred to authorize

Getting:
Socket was closed remotely (by pool)
 DCR: Job timeout, disconnect, retry in 20 sec...

Start.bat command:
EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal 0x31be6e3~~~~~~~~~~~~~~~~~98c6.miner2 -dpool dcr.suprnova.cc:3252 -dwal myloginname.miner1 -dpsw 2222 -allpools 1

Troubleshooting:
- I have changed the password for the worker to match Claymore (x, 2222, other) - unable to leave the password blank for the worker
- verified Suprnova login (though there is an "x" in the active column?)
- attempted both weblogin name as well as email address used for profile
- added port 3252 in Windows firewall for both incoming and outgoing connections
- added miner to router's DMZ
- tried with/without stratum+tcp
- attempted -dpool dcr.suprnova.cc:3252 -dwal suprnova.1 -dpsw x -allpools 1 as detailed on suprnova's website
- though I can't recall which other decred pools I used but all got the same error

Any assistance or suggestions would be greatly appreciated!!

Try to change "miner1" to your "worker name" and write "-dpsw x" command too.

Appreciations here (ETH) 0x57137Aecf8d11b60522d53eD2b0Baf0215FD0b61

Suprnova already has "miner1" as a worker name - and have tried -dpsw x and with specific password as well - no change

Okay but your worker real name is miner1? Or another? You should put the real worker name on start.bat and in supernova, however try to "update worker" on dcr.suprnova.cc account settings and keep the "-dpsw x" command. Of course you must write the "-epsw x" command before "-dpool" command on start.bat

No dice.

Here is the updated start.bat:

EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal 0x31be6e3~~~~~~~~~8998c6.miner2 -epsw x -dcoin dcr -dpool dcr.suprnova.cc:3252 -dwal webloginname.worker1 -dpsw x -allpools 1

My "webloginname" of course matches the username I use for Suprnova and although I previously used Miner1 as my worker name, I changed to worker1/worker2 (intend to run both rigs) but still running into same error as in original post.

What's especially frustrating is that is says that I'm connected to Suprnova but then the pool disconnects me.  Is there anything within Suprnova I need to do other than register an account and create a worker? There is an "x" in the Active column when looking at my configured workers - or is this just a reflection that they're not connecting?

Note - I tried this on another rig - same issues.

Try to write "webloginname.webloginname" or "miner1.miner1" or "worker1.worker1" (or the name you had choosen for your worker) on start.bat and update your worker on account settings. "-dcoin dcr" isn't necessary. You also can create a new worker. The X means your worker isn't active

Still no dice but here's an update...I've used the bat file as provided by NumbNuts above this last post (thanks for that by the way!!!) and got the same issue...so maybe this is a network issue?

I tried "weblogin.weblogin" and I also tried some BS entry after -dwal and got the exact same error.  I couldn't use worker.worker as I would need to create a new Suprnova profile unless I misunderstood your suggestion above.

Have you added the environmental variables to the start.bat file as well?  So what I've done in the start.bat (in full):

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 us1.ethermine.org:4444 -ewal 0x31be6~~~~~~~~~~~~~~8998c6.miner2 -epsw x -dpool dcr.suprnova.cc:3252 -dwal cd$$$ner.cd$$$ner -dpsw x

I should say that Ether is mining just fine.  I can let Claymore run as is all night and Ether will continue to mine with Decred erroring.

Any AV / firewall / router things I should be looking for?  Keep in mind I've added port 3252 to Windows Firewall, disabled Windows Firewall, added rig to router DMZ and disabled AV - all to no avail.

Did you create a Decred Wallet first? You must put it in account settings (Details/Payment Address). Try another version of Claymore, v9.6 or 9.8 and tell me. It shouldn't be the miner but try all options. Try to put 8GB RAM too. Do you select 16GB or more for Virtual Memory?. Reset the ports configuration, Windows firewall ask you for open ports when you try another version of Claymore, so don't need to select it manually. At the end you must create a new worker, add on dcr.suprnova.cc and write the command again on start.bat but this time choose the same worker name than your webloging name (the name of my worker is the same than the webloging)

[Ursul0]

Still no dice but here's an update...I've used the bat file as provided by NumbNuts above this last post (thanks for that by the way!!!) and got the same issue...so maybe this is a network issue?

This is how it works for me since the last POW update of decreed, no matter what version of the miner I use:
-dcoin dcr
-dcri 23
-dpool dcr.suprnova.cc:3252
-dwal web_login.worker_name
-dpsw worker_pass


You can try to ask ocminer - the op of the pool in his thread. Maybe your IP is sort of blacklisted for too many connection attempts or something
Also I suggest to use "config.txt" which makes things cleaner

[Coinebauer]

Does the blockchain driver from AMD improve hashrate all around (for Vega56 explicitly in my case) or is it just countering the DAG-generation degradation for Polaris & Co.?

[P00P135]

Update. Vega 56
36MH/s 135W at wall (wattmeter)

-15% powerlimit (But I guess it's not usefull because I reduce a lot the GPU clock, I 'll check the effect of this later
Core 925
Mem 970
Fan 80%

https://imgur.com/a/VCXm7

Setting the GPU core clocks to low impairs share find times!

May make you feel good to see 36mhs, but you won't be getting hashing rewards at that rate!

I guess, you'll need to run it for week to see whether you are getting what the calculator says you should be getting for 36mhs (minus fees).

I reckon it will be something much lower.

I was averaging 2% stale shares with a core clock of 852Mhz with VegaFE.

Take a GTX 1070 as an example: Run it without touching the GPU clock; plus 500mhz on the memory and 65% on power slider.

That will be your baseline for successful solutions sent back to the pool.

Run it with minus 125mhz on the GPU core and plus 500mhz on the memory and 65% on power slider.

It will be 3% less successful at pool doing work and you will get 3% less shares, which equates to 3% less coin rewards.

This is just spreading misinformation.  I solo mine Eth on 1070's at 1350mhz Core and they average way above my reported hashrate without any stale shares.  You probably are using a shit pool or have a bad connection to it.

[shadabahmed]

I tried plugging pcie riser to pci slot and killed my rx 480 8gb ( /slitwrists

not sure I understand what you did...maybe you just killed the pcie slot on the motherboard ?  try your GPU in another computer !

No. I plugged a PCIE riser 1x to 16x, the 1x connector in to a PCI slot (different than pci express) they do fit in there the same. When I powered on the pc, smoke started coming out of the pci slot so I pulled it out quickly but it was too late. The damage was done. Ive tried connecting it to a pcie slot on to different pc's and both are unable to recognize the graphic card. Either in device manager or amd driver download. Error 175 or 182 on amd code.

burned card can be replaced.. i did it 2 times

Can it be fixed? What do I need to do? Thnx

goto their service center they will replace ur card

[AzzAz]

Hi all,
3 x MSI RX 580 8 GB cards
Getting:
Socket was closed remotely (by pool)
 DCR: Job timeout, disconnect, retry in 20 sec...

try with -ethi8 -dcri6 and -esm 1... if working experiment with values

[thevictimofuktyranny]

Update. Vega 56
36MH/s 135W at wall (wattmeter)

-15% powerlimit (But I guess it's not usefull because I reduce a lot the GPU clock, I 'll check the effect of this later
Core 925
Mem 970
Fan 80%

https://imgur.com/a/VCXm7

Setting the GPU core clocks to low impairs share find times!

May make you feel good to see 36mhs, but you won't be getting hashing rewards at that rate!

I guess, you'll need to run it for week to see whether you are getting what the calculator says you should be getting for 36mhs (minus fees).

I reckon it will be something much lower.

I was averaging 2% stale shares with a core clock of 852Mhz with VegaFE.

Take a GTX 1070 as an example: Run it without touching the GPU clock; plus 500mhz on the memory and 65% on power slider.

That will be your baseline for successful solutions sent back to the pool.

Run it with minus 125mhz on the GPU core and plus 500mhz on the memory and 65% on power slider.

It will be 3% less successful at pool doing work and you will get 3% less shares, which equates to 3% less coin rewards.

This is just spreading misinformation.  I solo mine Eth on 1070's at 1350mhz Core and they average way above my reported hashrate without any stale shares.  You probably are using a shit pool or have a bad connection to it.

It was tested over 6 weeks - at same pool, which I have accurate information on their share proportions for 1 MHS going back 2 years for Ethereum mining.

The average measured, over one month was always 3% lower.

Putting, the GPU core back to it's normal speed and it was 3% higher.

[idothemining]

Hello guys and @Claymore

I have a problem with my miners with blockchain aug23 driver, claymore 10 and my RX 580s.
Always when miner loses connection and claymore reconnect to pool, clocks stay at 300mhz or 600mhz. How can I fix this problem? Is there anyway to force to card work in the higher P state?

Much appriciated.

I've also had this problem when attempting to OC any kind of AMD card (480, 580, 570) with afterburner: they always get "stuck" at 300 MHz, but only when mining. For some reason afterburner works with my 1070, though.

cclock changes P states across the board in Wattman, but the card doesn't "listen."

[P00P135]

Update. Vega 56
36MH/s 135W at wall (wattmeter)

-15% powerlimit (But I guess it's not usefull because I reduce a lot the GPU clock, I 'll check the effect of this later
Core 925
Mem 970
Fan 80%

https://imgur.com/a/VCXm7

Setting the GPU core clocks to low impairs share find times!

May make you feel good to see 36mhs, but you won't be getting hashing rewards at that rate!

I guess, you'll need to run it for week to see whether you are getting what the calculator says you should be getting for 36mhs (minus fees).

I reckon it will be something much lower.

I was averaging 2% stale shares with a core clock of 852Mhz with VegaFE.

Take a GTX 1070 as an example: Run it without touching the GPU clock; plus 500mhz on the memory and 65% on power slider.

That will be your baseline for successful solutions sent back to the pool.

Run it with minus 125mhz on the GPU core and plus 500mhz on the memory and 65% on power slider.

It will be 3% less successful at pool doing work and you will get 3% less shares, which equates to 3% less coin rewards.

This is just spreading misinformation.  I solo mine Eth on 1070's at 1350mhz Core and they average way above my reported hashrate without any stale shares.  You probably are using a shit pool or have a bad connection to it.

It was tested over 6 weeks - at same pool, which I have accurate information on their share proportions for 1 MHS going back 2 years for Ethereum mining.

The average measured, over one month was always 3% lower.

Putting, the GPU core back to it's normal speed and it was 3% higher.

This doesn't prove anything as there are too many other factors to consider.

[greatauror28]

Okay I have found a way. Because we can't undervolt via Claymore, I change voltage value in bios, then flash, in order to bypassing Claymore undervolting ^^

Did it work on you? What miner version are you using and what AMD driver?

It works. I have set voltage and frequency with PolariosBiosEditor, flash it with atiflash. Then, I use AfterBurner to preset core/memory frequency (boot with windows), and HWmonitor or any monitor read my settings : 1266MHz/900mV and 2250MHz/900mv On the wall I have around 720W with my 4 RX580, like before blockchain driver, and everything running well.
But I still waiting claymore update to try lower voltage without flash bios at each change ^^'

Out of all the countless hours I've spent tweaking my 580 dual OC, i've come to this conclusion as well.

This card maxes out the memory at 2050 and nothing more. One more Mhz over and it'll crash on you.

Update. Vega 56
36MH/s 135W at wall (wattmeter)

-15% powerlimit (But I guess it's not usefull because I reduce a lot the GPU clock, I 'll check the effect of this later
Core 925
Mem 970
Fan 80%

https://imgur.com/a/VCXm7

118 GPU power draw and 135 at the wall? Something's not right here.

Please post picture of wall meter.

[thevictimofuktyranny]

Got bad news on RX Vega 56 - managed to do a test with the Beta Blockchain Drivers (solely released to fix the Dag file memory issue for the RX 580/480 and 570/470 GPUs).

RX Vega 56

-24% Powertune
HMB2 925mhz
Default Clock ranging between 1136mhz to 1260mhz.
PSU Efficiency is 90%
Power Draw 152watts

Miner produced a Claymore result of 35.4mhs for 153watts.

Pool shares 40 minutes never above the rate for 36mhs.
Pool shares next 40 minutes around the rate for 25.5mhs.

Average pool shares found averaged around 31mhs for Ethereum - the same as the main official drivers. The Beta Blockchain Drivers are for the RX 580s and RX 570s, when used on RX Vega GPUs they produce fake hashrate figures, which are incorrect by 4mhs.

Beta Blockchain drivers do reduce powerdraw by 13watts per GPU, compared to the official drivers for RX Vega 56. This is why people are using them!

[P00P135]

Got bad news on RX Vega 56 - managed to do a test with the Beta Blockchain Drivers (solely released to fix the Dag file memory issue for the RX 580/480 and 570/470 GPUs).

RX Vega 56

-24% Powertune
HMB2 925mhz
Default Clock ranging between 1136mhz to 1260mhz.
PSU Efficiency is 90%
Power Draw 152watts

Miner produced a Claymore result of 35.4mhs for 153watts.

Pool shares 40 minutes never above the rate for 36mhs.
Pool shares next 40 minutes around the rate for 25.5mhs.

Average pool shares found averaged around 31mhs for Ethereum - the same as the main official drivers. The Beta Blockchain Drivers are for the RX 580s and RX 570s, when used on RX Vega GPUs they produce fake hashrate figures, which are incorrect by 4mhs.

Beta Blockchain drivers do reduce powerdraw by 13watts per GPU, compared to the official drivers for RX Vega 56. This is why people are using them!

Nothing like a definitive 40min no name pool test to prove things. 

[thevictimofuktyranny]

Got bad news on RX Vega 56 - managed to do a test with the Beta Blockchain Drivers (solely released to fix the Dag file memory issue for the RX 580/480 and 570/470 GPUs).

RX Vega 56

-24% Powertune
HMB2 925mhz
Default Clock ranging between 1136mhz to 1260mhz.
PSU Efficiency is 90%
Power Draw 152watts

Miner produced a Claymore result of 35.4mhs for 153watts.

Pool shares 40 minutes never above the rate for 36mhs.
Pool shares next 40 minutes around the rate for 25.5mhs.

Average pool shares found averaged around 31mhs for Ethereum - the same as the main official drivers. The Beta Blockchain Drivers are for the RX 580s and RX 570s, when used on RX Vega GPUs they produce fake hashrate figures, which are incorrect by 4mhs.

Beta Blockchain drivers do reduce powerdraw by 13watts per GPU, compared to the official drivers for RX Vega 56. This is why people are using them!

Nothing like a definitive 40min no name pool test to prove things.  

RX Vega has 2 stacks of 4GB HBM2 memory modules - how would it have Dag size memory problem?

You can stick the entire Ethereum Dag file on one module or the other module.  

I not going to waste extra money on electricity for 1 week of testing, when most people have figured out those hashrate screenshots are fakes for Ethereum mining.

[P00P135]

Got bad news on RX Vega 56 - managed to do a test with the Beta Blockchain Drivers (solely released to fix the Dag file memory issue for the RX 580/480 and 570/470 GPUs).

RX Vega 56

-24% Powertune
HMB2 925mhz
Default Clock ranging between 1136mhz to 1260mhz.
PSU Efficiency is 90%
Power Draw 152watts

Miner produced a Claymore result of 35.4mhs for 153watts.

Pool shares 40 minutes never above the rate for 36mhs.
Pool shares next 40 minutes around the rate for 25.5mhs.

Average pool shares found averaged around 31mhs for Ethereum - the same as the main official drivers. The Beta Blockchain Drivers are for the RX 580s and RX 570s, when used on RX Vega GPUs they produce fake hashrate figures, which are incorrect by 4mhs.

Beta Blockchain drivers do reduce powerdraw by 13watts per GPU, compared to the official drivers for RX Vega 56. This is why people are using them!

Nothing like a definitive 40min no name pool test to prove things.  

RX Vega has 2 stacks of 4GB HBM2 memory modules - how would it have Dag size memory problem?

You can stick the entire Ethereum Dag file on one module or the other module.  

I not going to waste extra money on electricity for 1 week of testing, when most people have figured out those hashrate screenshots are fakes for Ethereum mining.

HBM is stacked memory.  I don't think its one 4GB Module its like four 1GB modules stacked ontop of each other.