Any word on amd vega hash rates?

[ingyenfrag]

Disable-enable method works well but my hashrate drops in few minutes to 11500H/s to ~9500H/s for the 6*vega56@64 rig.
Any idea?

And thank you for the information.

[1714036670]

1714036670

[1714036670]

1714036670

[1714036670]

1714036670

[1714036670]

1714036670

[1714036670]

1714036670

[1714036670]

1714036670

[car1999]

I hadn't originally planned on putting this out there, but some other asshole decided to charge a fee for this info. Fuck that guy. Here's how you run 4+ Vega at full speed while mining XMR.

Basic Users:

1. Use the Blockchain drivers.
2. Open up your device manager.
3. Open up the "Display Adapters" dropdown.
4. Right click on one of your Vega's.
5. Disable that fucker.
6. Wait a few seconds.
7. Right click on the Vega you just disabled.
8. Re-enable that fucker.
9. Repeat steps 4-8 for the rest of your cards.
10. Enjoy mining at full speed with as many Vega as you damn well please. Probably.

Advanced Users:

The previously described process is a bit of a pain in the ass. Let's automate it.

1. Get your hands on the Windows Device Console (Devcon.exe). This will let you disable/enable devices from console.
2. Run the command devcon.exe FindAll * to generate a list of all the currently attached devices and their hardware IDs.
3. Search your newly generated list for "Radeon RX Vega." You should find something like this:

Code:

PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&3AAC35E3&0&000000E7 : Radeon RX Vega

4. The part to the left of the colon is what you need. Shocking, I know. Put that thing into a batch file that looks something like this:

Code:

@echo on
cd C:\Users\Mythic\Desktop\Startup
timeout /t 5
devcon.exe disable PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&3AAC35E3&0&000000E7
timeout /t 15
devcon.exe enable PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&3AAC35E3&0&000000E7
timeout /t 15
OverdriveNTool.exe -p0Vega0 -p1Vega1 -p2Vega2 -p3Vega3 -p4Vega4 -p5Vega5 -p6Vega6
timeout /t 10
cd C:\Users\Mythic\Desktop\xmr-stak-amd
xmr-stak-amd.exe

5. Run your batch file at startup as an administrator. Enjoy never having to toggle the HBCC switch again.

FAQ:

Q: So, Mythic, how exactly does this enable HBCC on cards 5-7?

A: It doesn't! HBCC Does nothing to improve your hashrate! Turns out the drivers are just shit and are bugged when Windows first boots up. Who would have guessed?

Q: But Mythic, does that mean I don't need 16 GB of ram to run my cards at full speed?

A: Correct! 4 GB of ram is completely sufficient!

Q: If I wanted to donate some pizza money to the broke ass college student that typed this up, how would I do so?

A: You ask the best questions! I doubt I'll get anything before more well known people/websites copy everything I just said (with no credit, obviously), but here are some addresses just in case.
          XMR: 42e8AWjcirkBDzCNnSjPxeGJeht71kFfWcoxxCWsxe8HZqP29NruDsxcvVSjbKw17AUDepopK7ZYCUn mRvcGS9kBT5XWhMQ
          ETH: 0x74Ed2CA095Dd3aE98D88d5ca1dDb77E752152938

Thank's it's working great.  So it's more a bug in the driver with the HBCC option. With this in my batch, i don't need anymore to disable/enable HBCC on each card, i have full XMR hashing speed (1900 by card / 4 VEGA 56@64BIOS)

what's your power play table settings , fan  speed and GPU  temp?

[MingMining]

Disable-enable method works well but my hashrate drops in few minutes to 11500H/s to ~9500H/s for the 6*vega56@64 rig.
Any idea?

And thank you for the information.

Check your power options in control panel and make sure it won't sleep.

[mutual.consent]

Is OverdriveNTool working good? There has been reports, that changing values with it doesn't really do much (same as Wattmann). But I guess it has been updated and working fine since then?

OverdriveNTool is working fine for me, but I basically only use it to adjust voltages. I use the registry mod for GPU and MEM clocks.

I can run the batch file as admin manually, and it works great.

When I run it in my startup folder it doesn't run as admin and doesn't work.

How are you getting it to run on startup as admin?

Use the task scheduler to execute your batch file at startup. See here: https://superuser.com/a/929227

Thanks for your contribution Mythic - just tested with my Vega 64 and your solution works great. I've tweaked your automation a little further to disable and enable all Radeon cards in a rig at startup - see below for my contribution (note: this doesn't have code to execute xmr-stak-amd or overdriventool as those are straight forward commands and can be added to the end. If I have some time I might just add some parameters at the top for ease of editing and add some error handling to idiot proof the whole process):

Code:

@echo on
set currentdir=%cd%
cd C:\Program Files (x86)\Windows Kits\10\Tools\x64
devcon findall * | findstr Radeon > %currentdir%\radeoncards.txt
for /F "tokens=1 delims=:" %%a in (%currentdir%\radeoncards.txt) do (
	devcon disable "@%%a"
	timeout /t 15
	devcon enable "@%%a"
	timeout /t 15 
)
del %currentdir%\radeoncards.txt
cd %currentdir% 

[piim]

Disable-enable method works well but my hashrate drops in few minutes to 11500H/s to ~9500H/s for the 6*vega56@64 rig.
Any idea?

And thank you for the information.

Try to get your temps lower. Mine stay stable at around ~60C but some start throttling at ~65C.

[Mythic]

Thanks for your contribution Mythic - just tested with my Vega 64 and your solution works great. I've tweaked your automation a little further to disable and enable all Radeon cards in a rig at startup - see below for my contribution (note: this doesn't have code to execute xmr-stak-amd or overdriventool as those are straight forward commands and can be added to the end. If I have some time I might just add some parameters at the top for ease of editing and add some error handling to idiot proof the whole process):

Code:

@echo on
set currentdir=%cd%
cd C:\Program Files (x86)\Windows Kits\10\Tools\x64
devcon findall * | findstr Radeon > %currentdir%\radeoncards.txt
for /F "tokens=1 delims=:" %%a in (%currentdir%\radeoncards.txt) do (
	devcon disable "@%%a"
	timeout /t 15
	devcon enable "@%%a"
	timeout /t 15 
)
del %currentdir%\radeoncards.txt
cd %currentdir% 

After reading the documentation for devcon, I've found that you can actually just do

Code:

cd %~dp0
timeout /t 5
devcon.exe disable =Display
timeout /t 5
devcon.exe enable =Display

Where devcon.exe is placed in the same folder as the batch file. This ought to simplify things a bit.

[VoskCoin]

What’s the general consensus on building a new Vega rig @ today’s rates? (Card price vs earnings)
Yes no wait never 

[twofreckles]

What’s the general consensus on building a new Vega rig @ today’s rates? (Card price vs earnings)
Yes no wait never 

Never say never, but currently IMO price/hashrate ratio isn't in favour of vega. RX 470/480/570/580 gives better results.

[bytiges]

Thanks for your contribution Mythic - just tested with my Vega 64 and your solution works great. I've tweaked your automation a little further to disable and enable all Radeon cards in a rig at startup - see below for my contribution (note: this doesn't have code to execute xmr-stak-amd or overdriventool as those are straight forward commands and can be added to the end. If I have some time I might just add some parameters at the top for ease of editing and add some error handling to idiot proof the whole process):

Code:

@echo on
set currentdir=%cd%
cd C:\Program Files (x86)\Windows Kits\10\Tools\x64
devcon findall * | findstr Radeon > %currentdir%\radeoncards.txt
for /F "tokens=1 delims=:" %%a in (%currentdir%\radeoncards.txt) do (
	devcon disable "@%%a"
	timeout /t 15
	devcon enable "@%%a"
	timeout /t 15 
)
del %currentdir%\radeoncards.txt
cd %currentdir% 

After reading the documentation for devcon, I've found that you can actually just do

Code:

cd %~dp0
timeout /t 5
devcon.exe disable =Display
timeout /t 5
devcon.exe enable =Display

Where devcon.exe is placed in the same folder as the batch file. This ought to simplify things a bit.

This is correct by you don't want to disable the iGPU on rigs that use it (like mine).
You can instead call

Code:

devcon.exe disable "PCI\VEN_1002&DEV_687F"
timeout /t 2
devcon.exe enable "PCI\VEN_1002&DEV_687F"

This is enable/disable ALL devices that match the prefix.

Just my 2p

[tarui]

What’s the general consensus on building a new Vega rig @ today’s rates? (Card price vs earnings)
Yes no wait never 

Never say never, but currently IMO price/hashrate ratio isn't in favour of vega. RX 470/480/570/580 gives better results.

even for monero?

[aws-premium]

What’s the general consensus on building a new Vega rig @ today’s rates? (Card price vs earnings)
Yes no wait never 

Never say never, but currently IMO price/hashrate ratio isn't in favour of vega. RX 470/480/570/580 gives better results.

even for monero?

Monero does only work with Windows on Vega if i'm correct, so no love for Linux Rigs. Windows is to much work for me, wait till Vega works with Linux like with Windows.
(Driver Issues?)

[Django69]

anyone have tested more than 8 vega under windows?

[Mythic]

This is correct by you don't want to disable the iGPU on rigs that use it (like mine).
You can instead call

Code:

devcon.exe disable "PCI\VEN_1002&DEV_687F"
timeout /t 2
devcon.exe enable "PCI\VEN_1002&DEV_687F"

This is enable/disable ALL devices that match the prefix.

Just my 2p

Even better! I disable the iGPU on all of my systems, so I wasn't really thinking about that. Can anyone confirm whether the vendor defined identifier (DEV_687F) is the same for all the Vega variants (V56, V64, V64L)?

[dexxa05]

Hi guys,

Just a small question :

I have an issue using 3 Vega 56 on my MSI z170 pro gaming carbon.

Just 2 are showing, do you know the right bios configuration to get 3 and more to work ? (i think is bios related)

Thx in advance

Dexx

[Ledipaa]

What’s the general consensus on building a new Vega rig @ today’s rates? (Card price vs earnings)
Yes no wait never 

Never say never, but currently IMO price/hashrate ratio isn't in favour of vega. RX 470/480/570/580 gives better results.

You cant be serious? ETH profitability has been about as badish for months, dropping rapidly after june 13. Monero instead is still the best for gpu mining. Even if you would need to pay 500€ per V56 versus 300€ to RX580. You can make a dollar per RX580 in a day (120W) versus vega +2,5$ per day (150W).

[bytiges]

This is correct by you don't want to disable the iGPU on rigs that use it (like mine).
You can instead call

Code:

devcon.exe disable "PCI\VEN_1002&DEV_687F"
timeout /t 2
devcon.exe enable "PCI\VEN_1002&DEV_687F"

This is enable/disable ALL devices that match the prefix.

Just my 2p

Even better! I disable the iGPU on all of my systems, so I wasn't really thinking about that. Can anyone confirm whether the vendor defined identifier (DEV_687F) is the same for all the Vega variants (V56, V64, V64L)?

These are Vega 56 from Sapphire.

You can push the wirldcard a little more, by using just PCI\VEN_1002. This will disable all AMD adapters.
I'm using devcon.exe from Windows 10 1607 (not sure if older versions have this wildcard functionality).

[philipma1957]

What’s the general consensus on building a new Vega rig @ today’s rates? (Card price vs earnings)
Yes no wait never 

Never say never, but currently IMO price/hashrate ratio isn't in favour of vega. RX 470/480/570/580 gives better results.

From pm discussions    4 vega 56's  can be had for about 1700-1800 usd  put in with a ryzen 1700  and a proper mobo.

Build is about 2200.   it will do 8000-8500 for cryptonight/monero  under 700 watts.  so roi is under a year.

how good is that? I am not sure.  What I don't like is  if xmr tanks  the card does not have a lot of value.

[MoneroCrusher]

I'm having problems with the script. The manual disable/enable works fine.

output of script:
C:\Users\monero\Desktop>devcon.exe disable "PCI\VEN_1002&DEV_687F"
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&2AF6ADFE&0&000000E6: Disable failed
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&2C451A81&0&000000E0: Disable failed
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&21DB5B6B&0&00000008: Disable failed
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&9C9E801&0&000000EB: Disable failed
No matching devices found.

C:\Users\monero\Desktop>timeout /t 5

Obviously it found 4 Cards but was not able to disable it?
I'm on build 1703 and I downloaded devcon.exe the following way:
https[Suspicious link removed]

Thanks for your awesome contribution Mythic

[cpnl]

I'm having problems with the script. The manual disable/enable works fine.

output of script:
C:\Users\monero\Desktop>devcon.exe disable "PCI\VEN_1002&DEV_687F"
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&2AF6ADFE&0&000000E6: Disable failed
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&2C451A81&0&000000E0: Disable failed
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&21DB5B6B&0&00000008: Disable failed
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&9C9E801&0&000000EB: Disable failed
No matching devices found.

C:\Users\monero\Desktop>timeout /t 5

Obviously it found 4 Cards but was not able to disable it?
I'm on build 1703 and I downloaded devcon.exe the following way:
https[Suspicious link removed]

Thanks for your awesome contribution Mythic

Did you run it as admin?

[MoneroCrusher]

I'm having problems with the script. The manual disable/enable works fine.

output of script:
C:\Users\monero\Desktop>devcon.exe disable "PCI\VEN_1002&DEV_687F"
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&2AF6ADFE&0&000000E6: Disable failed
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&2C451A81&0&000000E0: Disable failed
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&21DB5B6B&0&00000008: Disable failed
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&9C9E801&0&000000EB: Disable failed
No matching devices found.

C:\Users\monero\Desktop>timeout /t 5

Obviously it found 4 Cards but was not able to disable it?
I'm on build 1703 and I downloaded devcon.exe the following way:
https[Suspicious link removed]

Thanks for your awesome contribution Mythic

Did you run it as admin?

I right clicked the batch file and run it as admin, yes.
Anything else I couldve missed?