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

GPU-Z down hashrate
when I run vega 64 with GPU-z
my hashrate start 2000 and after few min 1-2 drop 5-10 %
I don't run GPU-z and all work stable

I tried this but still get hashrate drop. Does the monitor still need to be on as well?

I can't use IGPU as my monitor only has DP input.

Does anyone know a way to get a real time log file out of XMR STAK ?
You can do xmr-stak-amd.exe >> log.txt , it will work , but you'll see nothing on the cmd screen nor in the log file before the programm is actually closed.

So any idea how to do this?

Monero hashrate drops when you disconnect your monitor (even if you are on IGP), or the screen power shut down after a while.
Simple disable screen power shut down, and do not disconnect your display while mining.

How did you calculate those numbers ?

125W per Cryptonight looks like the difference between the card idling but powered in the rig and mining.

What you really need is the diff between no card in the rig and mining.

My Vegas will pull ~30-35W just sitting there doing nothing so the real power usage is ~150-160W per card (@93% efficiency, pull from the wall).  For comparison, by MB, CPU, memory and M2 sata disk pull about 25-30W when idling (!)

Please also specify if your numbers include the power supply efficiency or not (and that efficiency if they do).

I haven't seen real 125W pulled from the wall per card yet, unless you severely undervolt and underclock, but then bye bye 2K h/s

Should all the tach lights stay on while mining or is it normal.for them to change? The last light on one of my cards 'blinks' on and off constantly while another does it every few seconds. The other two stay full on all the time. The cards run around the same temp and fans and are stable.on Wattman ( other than the occasional spike of GPU clock speed ). Is this normal or could it damage the card if ran long enough like that?

Hi guys,
I am just received new bios from asrock for h110 pro htc+.
It was because of my discusion with them about problem with booting with more than 9x vega64.
Unfortunatelly my rig with vegas is in a remote area. Is there someone who can try this bios?

So roughly around:

125W per card for CryptoNight @ 1950

150W per card for Etherium @ 44Mh

190W per card for Dual mining @ 44Mh / 1250Mh

Did some further testing regarding power draw today on single card test bed with an i3 8100 65W processor and a random Seasonic Bronze 430W PSU.

Card used: Vega56 flashed to 64. @ 800mv floor.


Idle powerdraw : 67-72W

Cryptonight powerdraw : 191-195W @ 1950H / 1400mhz / 1100Mhz

Etherium single mining powerdraw: 215-220W @ 44Mh /1200Mhz /1100Mhz

Etherium/DCR dual mining powerdraw: 255-260W @ 44Mh & 1250Mhs / 1200Mhz / 100Mhz


So roughly around:

125W per card for CryptoNight @ 1950

150W per card for Etherium @ 44Mh

190W per card for Dual mining @ 44Mh / 1250Mh

Is there any way to enable HBCC without opening radeon settings? The window always gets stuck so i cannot use wattman or other radeon settings ( even win reinstall didnt help). I am thinking of some registry or config edit? Thanks it would be much help!

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