Topic: Any word on amd vega hash rates? - page 65. (Read 202725 times)

Dang nice. Have you flashed your 56 to the 64 BIOS? I heard they should has about the same after that. And very curious of your power draw per card. I know HWinfo/GPUz is not reliable, but what do they say your cards are each pulling?

Which version of WIN10 did you go with? I've got 4 56's coming tomorrow and setting up win machine (my current rigs are all Ubuntu for RX470/570s) so kinda restarting with my knowdledge base....

I've been reading through the threads trying to glean a little knowledge and it's things like this that light me up.  

I've got the latest stable hwinfo64 5.60-3280.  When simply disabling GPU I2C support (that single check-box), my hash-rate drops.  Any other options I should be adding/dropping?  ... I think that it might be working now if I keep hwinfo64 open, reset my vegas, and then check temps.  Is that what you mean?  

Also, since talking temps, you said you set target to 50.  Is that via Wattman in Radeon Settings?  For some reason I was under the impression that the temp targets in wattman weren't effective and that it all had to be done manually.  Yes, I'm talking LC here.  I'm also interested in keeping fans down if possible. You said hbm temp 65-67 C.  Would you say over 70 is dangerous?  

My Vega 56's are consistently hitting 37-39 MH/s
My Vega 64's are consistently hitting around 43.5 MH/s

I read something about a maximum of four vega gpu:s per system. Is that correct ?
Is it the driver that dont support more then four cards ?

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 a fix for reduced hashrate and a method for running 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 it.
6. Wait a few seconds.
7. Right click on the Vega you just disabled.
8. Re-enable it.
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.

New Procedure

1. Get your hands on the Windows Device Console (Devcon.exe). This will let you disable/enable devices from console.
2. Create a batch file in the same folder as devcon.exe with the following lines in it:
3. This will selectively disable/enable all the Vega cards you currently have in your system. Thanks to bytiges for noting that killing all the display adapters might not be a good idea for those using iGPU.
4. Run the batch file as an administrator at login, or whenever you lose hashrate on your cards. Enjoy never having to toggle the HBCC switch again.

Outdated Procedure

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:
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:
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

Any ideas of what could be being triggered with the disable/enable method?

So is the august blockchain driver still required? Or has 17.11.1 update finally fixed all the issues when toggling compute? Haven't had time to play around with drivers lately

hwinfo64 works fine with vega, no speed decrease or lockups. Just disable GPU I2C Support in settings.

I made an script to run devcon, overdriventool and finally cast xmr. I set the Task Scheduler to run this script at statup whether user is logged or not. When booting the pc and not login the script will run in background, without opening the cmd prompt.
This result in a consumption of around 1015W in a 6x Vega 64 rig.
If I run the script manually, so it shows the cmd prompt, the power consumption is  between 100 and 150W higher.
I don't understand why this happen. I would like to know if you can replicate this results.
Of course, the downside of this is that you cannot know the hashrate you are getting.

I bought only one Vega 56 in order to test it, 1940 H/s stable on XMR since 3 days now.
Damn, if only I bought more when it was on sale...

Oh fucking hell the Z370's ONLY support 8th gen CPUs even those the socket is the same. Fuck you Intel.

Currently using a Z170A MSI M5 board. Guess it's back to MC to try a Z270 board.

Currently using a Z170A MSI M5 board. Guess it's back to MC to try a Z270 board.

No, building them with 6 all the time

Let us know how that works out. Which mobo did you use so far out of interest?

I read something about a maximum of four vega gpu:s per system. Is that correct ?
Is it the driver that dont support more then four cards ?