Any word on amd vega hash rates?

[BitTeo]

How much hashrate produces vega 64 with HSR? the Nvidia 1080ti make about 22mhs, and vega 56? thank you .

HSR is not memory-hyper-intensive algo, so don't expect better then 1080ti results from Vega ...

Understand thanks , and which is best coin/algo for amd vega ? power comsuption ? .

[Truthchanter]

I can control voltage in AB. Only difference is that i don't have SoftPowerPlayTable mod, cause that shit was crashing my system.
I had to reinstall blockchain drivers in order to get power limit slider working.. i could only set -1 0 +1 %.

so you have stock bios no flash correct?

blockchain drivers
msi ab.

which vega
what is  hashrate for xmr
what power draw for xmr

V56 stock bios, but use the custom power play table for undervolt, 1850-1910h/s depending on mem OC, 900-925mv core, 130-135w per gpu at the wall (one guy said as low as 110w using a slight core OC, I have yet to try that)

Have fun

[rednoW]

How much hashrate produces vega 64 with HSR? the Nvidia 1080ti make about 22mhs, and vega 56? thank you .

HSR is not memory-hyper-intensive algo, so don't expect better then 1080ti results from Vega ...

Understand thanks , and which is best coin/algo for amd vega ? power comsuption ? .

It was discussed many times in this thread.
Cryptonight, Cryptonight-Lite, ETH+LBC, ETH - are best for Vega.
Power consumption depends on your settings and algo and can be as low as 130watt (custom downvolt and monero) to as much as 500watt (vega64 liquid on stock with PL+50 and dual-mining). Last setting highly not recommended )))

[rubine2323]

Could someone help me?

I started mining with 8x Vega 64 with powertable and some changes in overdriventool.
First 24 hours without problems.

But now it wont work longer then 20 minutes bevore miner freezes?

https://imgur.com/a/FRYGu

Code:

/* 
 * Number of GPUs that you have in your system. Each GPU will get its own CPU thread.
 */
"gpu_thread_num" : 16,

/*
 * GPU configuration. You should play around with intensity and worksize as the fastest settings will vary.
 *      index    - GPU index number usually starts from 0
 *  intensity    - Number of parallel GPU threads (nothing to do with CPU threads)
 *   worksize    - Number of local GPU threads (nothing to do with CPU threads)
 * affine_to_cpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner.
 */
"gpu_threads_conf" : [ 

	{ "index" : 0, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 0, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 1, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 1, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 2, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 2, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 3, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 3, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 4, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 4, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 5, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 5, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 6, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 6, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 7, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
	{ "index" : 7, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },









],

/*
 * Platform index. This will be 0 unless you have different OpenCL platform - eg. AMD and Intel.
 */
"platform_index" : 1,

/*
 * TLS Settings
 * If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
 * to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel. 
 *
 * use_tls         - This option will make us connect using Transport Layer Security.
 * tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
 * tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
 */
"use_tls" : false,
"tls_secure_algo" : true,
"tls_fingerprint" : "",

/*
 * pool_address	  - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
 * wallet_address - Your wallet, or pool login.
 * pool_password  - Can be empty in most cases or "x".
 */
"pool_address": "pool.supportxmr.com:7777",
"wallet_address": "4AgjtJy5gMy1baooxQMWxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxbsgRP3BLSR1x5J9",
"pool_password": "MyWorker:xxxxxxxxxxxxxxxx",

/*
 * Network timeouts.
 * Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make 
 * sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for 
 * nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
 * long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
 * server usually takes to process our calls.
 *
 * call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
 * retry_time	- How long should we wait before another connection attempt.
 *                Both values are in seconds.
 * giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
 *                don't mine while the connection is lost, so your computer's power usage goes down to idle.
 */
"call_timeout" : 20,
"retry_time" : 20,
"giveup_limit" : 0,

/*
 * Output control.
 * Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
 * really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
 * performance monitors, there is very little reason to spew out pages of text instead of concise reports.
 * Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
 *
 * verbose_level - 0 - Don't print anything. 
 *                 1 - Print intro, connection event, disconnect event
 *                 2 - All of level 1, and new job (block) event if the difficulty is different from the last job
 *                 3 - All of level 1, and new job (block) event in all cases, result submission event.
 *                 4 - All of level 3, and automatic hashrate report printing 
 */
"verbose_level" : 3,

/*
 * Automatic hashrate report
 *
 * h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
 *                This option has no effect if verbose_level is not 4.
 */
"h_print_time" : 60,

/*
 * Daemon mode
 *
 * If you are running the process in the background and you don't need the keyboard reports, set this to true.
 * This should solve the hashrate problems on some emulated terminals.
 */
"daemon_mode" : false,

/*
 * Output file
 *
 * output_file  - This option will log all output to a file.
 *
 */
"output_file" : "",

/*
 * Built-in web server
 * I like checking my hashrate on my phone. Don't you?
 * Keep in mind that you will need to set up port forwarding on your router if you want to access it from
 * outside of your home network. Ports lower than 1024 on Linux systems will require root.
 *
 * httpd_port - Port we should listen on. Default, 0, will switch off the server.
 */
"httpd_port" : 16000,

/*
 * prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
 *               This setting will only be needed in 2020's. No need to worry about it now.
 */
"prefer_ipv4" : true,

[glph3k]

what is  hashrate for xmr
what power draw for xmr

On my Vega 56:

1550 at ~100 watts (power limit -50)
1800 at ~150 watts (power limit -25)
1950 at ~200 watts (power limit 0)
2050 at ~240 watts (power limit +20)

More power does not give better results because  further increasing the memory clock the card gets unstable.

Have a look at:
https://bitcointalk.org/index.php?topic=2256917

[Oakey22]

So tempted to get some Vegas with the hash rate on Monero. What holds me off is that Volta is just around the corner

[rednoW]

On my Vega 56:

1550 at ~100 watts (power limit -50)
1800 at ~150 watts (power limit -25)
1950 at ~200 watts (power limit 0)
2050 at ~240 watts (power limit +20)

More power does not give better results because  further increasing the memory clock the card gets unstable.

Have a look at:
https://bitcointalk.org/index.php?topic=2256917

Vega56 can do 1950h/s @ 130watt.
And no need of closed source 2% fee miner. Open source xmr-stak-amd is just fine ... except 1 thing - it doesn't work with nicehash.

[fmz89]

what is  hashrate for xmr
what power draw for xmr

On my Vega 56:

1550 at ~100 watts (power limit -50)
1800 at ~150 watts (power limit -25)
1950 at ~200 watts (power limit 0)
2050 at ~240 watts (power limit +20)

More power does not give better results because  further increasing the memory clock the card gets unstable.

Have a look at:
https://bitcointalk.org/index.php?topic=2256917

anyone testing hashrate with softplay mod?
speed/watt?
with amd-stak 4gpu i got 7700hs/675watt, on pool 24h average result 7850hs, earning around 3% above whattomine calculator
happy with stak,
vega seems most stable gpu like fury series

[frostedace]

So tempted to get some Vegas with the hash rate on Monero. What holds me off is that Volta is just around the corner

Still got a few months. If you can get any around MSRP then they may be worth it... for now at least.

[markos365]

Anyone found a way to use HBCC on 4+ cards?
I have a 6x Vega 64 rig and I only get around 1990 on 4 cards, the other two just ~1400MH/s.

[JuanHungLo]

Has anyone successfully installed and used Claymore 10.2 for XMR with these drivers in Win 7-64 https://bitcointalk.org/index.php?topic=2068446.0 with 4x Vega 56?  Or is Win 10 64 and Aug 28th Blockchain drivers essential?

[Peecha]

anyone testing hashrate with softplay mod?
speed/watt?
with amd-stak 4gpu i got 7700hs/675watt, on pool 24h average result 7850hs, earning around 3% above whattomine calculator
happy with stak,
vega seems most stable gpu like fury series

I ditched the afterburner. The frequencies jumped between values i set and boosted/reference values like crazy.

2x Vega 56, flashed with 64 bios, blockchain drivers, using oldcomer's softplay mod.
4GB DDR3, 70GB vram, HBCC on (don't have slider, but toggle)

Power draw from the wall is 320W (-50W pc, gives about 135W per card).

0,1 threads intensity: 2016, 1800
2,3 threads intensity: 1900, 1800 - i have monitor connected to the second vega

Initial hashrate:
http://imageshack.com/a/img924/2313/jQMSPb.png

But it wont stay up for long... in the first minute it drops by 300-400
http://imageshack.com/a/img922/2465/ECiaYk.png

Overdrive settings:
http://imageshack.com/a/img923/6934/dyAT3t.png

HWInfo:
http://imageshack.com/a/img924/8240/TOhS4c.png

Any thoughts why my hashrate is dropping?

[bill121]

Does anybody run 5 or 6 x Vega 56? is it true the maximum is only 4?

I have 4 vega 64s and one 56 and can't get all 5 going at the same time. Can get 3 64s and one 56 but can't get the 5th to register. Also with 4 one card is always buggy, I've had to rebuild the rig a few times and its always a different card on a different riser that acts up. That card has to be run at lower speeds than the rest mining eth or it crashes.

[bill121]

anyone testing hashrate with softplay mod?
speed/watt?
with amd-stak 4gpu i got 7700hs/675watt, on pool 24h average result 7850hs, earning around 3% above whattomine calculator
happy with stak,
vega seems most stable gpu like fury series

I ditched the afterburner. The frequencies jumped between values i set and boosted/reference values like crazy.

2x Vega 56, flashed with 64 bios, blockchain drivers, using oldcomer's softplay mod.
4GB DDR3, 70GB vram, HBCC on (don't have slider, but toggle)

Power draw from the wall is 320W (-50W pc, gives about 135W per card).

0,1 threads intensity: 2016, 1800
2,3 threads intensity: 1900, 1800 - i have monitor connected to the second vega

Initial hashrate:
http://imageshack.com/a/img924/2313/jQMSPb.png

But it wont stay up for long... in the first minute it drops by 300-400
http://imageshack.com/a/img922/2465/ECiaYk.png

Overdrive settings:
http://imageshack.com/a/img923/6934/dyAT3t.png

HWInfo:
http://imageshack.com/a/img924/8240/TOhS4c.png

Any thoughts why my hashrate is dropping?

I found this would happen when I had mem clock set to 1100 (best setting for ethereum) . I had to dial back to 1020 to get it stable now the only thing that causes a hashrate drop is when I switch monitor off. Doesn't matter if hdmi is connected to GPU or mb as soon as screen is off hash rate drops from 7500 to 6700.

2016/1600 intensity 1200/1020 clocks -10%power 210Wish per GPU only OCed using Wattman for now

[frostedace]

Whenever I try to use the blockchain drivers, my screen pixelates grey and then crashes. I've reinstalled the drives with ddu but still get the same end result. The regular drivers work fine though. Any thoughts?

[exsexs1]

Whenever I try to use the blockchain drivers, my screen pixelates grey and then crashes. I've reinstalled the drives with ddu but still get the same end result. The regular drivers work fine though. Any thoughts?

I have same issue. Do you have integrated gpu on your motherboard? If you have, uninstall drivers with DDU, reboot, set igpu to first in bios. Plug your monitor to igpu. Install driver again and try Hellae instructions.
I got 1850 h/s with sapphire vega 56

[BitTeo]

How much hashrate produces vega 64 with HSR? the Nvidia 1080ti make about 22mhs, and vega 56? thank you .

HSR is not memory-hyper-intensive algo, so don't expect better then 1080ti results from Vega ...

Understand thanks , and which is best coin/algo for amd vega ? power comsuption ? .

It was discussed many times in this thread.
Cryptonight, Cryptonight-Lite, ETH+LBC, ETH - are best for Vega.
Power consumption depends on your settings and algo and can be as low as 130watt (custom downvolt and monero) to as much as 500watt (vega64 liquid on stock with PL+50 and dual-mining). Last setting highly not recommended )))

Ok only ethereum based in fact , mhm more limited .

[Truthchanter]

anyone testing hashrate with softplay mod?
speed/watt?
with amd-stak 4gpu i got 7700hs/675watt, on pool 24h average result 7850hs, earning around 3% above whattomine calculator
happy with stak,
vega seems most stable gpu like fury series

I ditched the afterburner. The frequencies jumped between values i set and boosted/reference values like crazy.

2x Vega 56, flashed with 64 bios, blockchain drivers, using oldcomer's softplay mod.
4GB DDR3, 70GB vram, HBCC on (don't have slider, but toggle)

Power draw from the wall is 320W (-50W pc, gives about 135W per card).

0,1 threads intensity: 2016, 1800
2,3 threads intensity: 1900, 1800 - i have monitor connected to the second vega

Initial hashrate:


But it wont stay up for long... in the first minute it drops by 300-400


Overdrive settings:


HWInfo:


Any thoughts why my hashrate is dropping?

Either HBCC is turning off somehow (some other program or task starting?) or your fans aren't high enough (put em around at least 3000) to keep the HBM mem cool enough to sustain the high hashrate

[Yerba]

I followed hellaes instructions. Step by step. Vega 56 without flashing to vega 64.
Every time I turn off miner or restart it - all settings are gone and hashrate is again 600-600. I DDU drivers, reinstalled all again and it mines nicely around 1000 and 850 hash per card. Until restart..
What could be wrong?

[rednoW]

I followed hellaes instructions. Step by step. Vega 56 without flashing to vega 64.
Every time I turn off miner or restart it - all settings are gone and hashrate is again 600-600. I DDU drivers, reinstalled all again and it mines nicely around 1000 and 850 hash per card. Until restart..
What could be wrong?

It seems that driver crashes on miner exit. Maybe memory clocked to high or voltage is to low for you card