Step-by-Step Setup AMD Radeon Vega 56 / Vega 64 (Configure)

vega Пошаговая настройка Vega 56/ Vega 64

Customization AMD Radeon Vega 56 / Vega 64

I myself am the proud owner of them. And I would like to create a topic with the most complete information about Vega. And guides for setting them up.

Instructions from foreign users

1) http://www.gandalph3000.com/cast_xmr/howto-mine-monero-rx-vega/
From the creator of the cast_xmr miner with mini settings. – Simple instruction without tools, wattmans and other tambourines.

2) http://vega.miningguides.com/
A prefabricated hodgepodge here and flashing and turning off when starting HBCC and editing the registry. For seasoned miners only.

My personal setup instructions AMD Vega 56 / Vega 64 (how it all worked for me)

1) Plug Vega 56 / Vega 64 into PCI-Express X4 or X16 slot without risers directly to the motherboard.

2) Format the HDD / SSD with Windows and install Windows 10 (this is important! Zero Windows, which was installed on the Nvidia card, adds hemorrhoids. Only a clean installation from scratch.

3) We start the system.

Control Panel / System and Security / Advanced System Settings / Advanced

Click on the button Options> Performance Options> Advanced>

We see the inscription virtual memory and click Change, we indicate 15 gigabytes for each veg. (If you don’t have that much memory, you can put 8 gigs per card, experienced from the forum say and it works like that)

I have 4 of them so we will put 60,000 MB.
Original size 59000 – Max size 60,000 my case
Original size 32000 – Max size 32000 – should work too

4) Change the power settings in the control panel

  • We expose the power plan “High performance”
  • Power supply / Changing circuit parameters – Disable display: – Never
  • Put your computer to sleep: – Never
  • Click “Save Changes”

5) Download and Install AMD Blockchain Drivers

On our website you can also get a complete overview of these drivers and their settings: AMD Blockchain Driver — driver overview, installation, download

6) Install the drivers and all their components and wait for the card to calm down. During installation, we do not touch or pull anything, at the end of the installation the program will offer a restart, usually when you click on it, it can also freeze. Feel free to reboot the system.

Radeon Software Crimson ReLive Edition Beta for Blockchain Compute Driver for Windows® 10 64-bit

Radeon Software Crimson ReLive Edition Beta for Blockchain Compute Driver for Windows® 10 32-bit​

Radeon Software Crimson ReLive Edition Beta for Blockchain Compute Driver for Windows® 7 64/32 bit

7) After installing the drivers, click on:

Games> Global Settings>

  • we will have two columns:
    • 1 – Global Graphics (Radeon RX Vega)
    • 2 – Global Wattman (Radeon Rx Vega)
  • in the first column, we need to click on the HBCC Memory Segment button and move it to the on position. And then click apply. The driver will reboot.
  • There is an important nuance here. Sometimes the checkbox is already enabled, but HBCC is actually disabled. AMD knows about this problem and, in principle, propose not to pay attention to it, that is, if HBCC is enabled and the hashrate is small, then just move the slider to the disabled position and, lo and behold, HBCC will actually work.

Then go to 2 – Global Wattman (Radeon Rx Vega)

and we don’t touch anything there except for the cooler settings.
SPEED (RPM) Manual
Put the slider in the on position and raise the cooler speed. This is necessary so that when you first start the miner, the card does not heat up to 78 degrees and does not start to smoke with gaskets.



8)
We launch the miner. In my case, this is cast_xmr.

An example of a batch file:

cast_xmr-vega -S xmr-eu.dwarfpool.com:8100 -u 47BCGhAqrj8ZN5UQgLkW7x5qx7vrYQwMwHDiPsNEhQdMCbnC6UGYzP8GccsHPAUffN4c8NLJoU4bBMp2sjiXuwTx59gJZ7J -G 0 %*

And we look at the Hashrate indicators.
There should be 1500-1900h / s depending on the card. If the values are less, turn off the miner and go to the driver to enable / disable HBCC Memory Segment.
Leave the miner to work like this for 15-20 minutes.

9) Turn off the miner through the “q” button. If you zhahnut on a cross in a batch file, there is a chance somewhere around 20 percent that the drivers will fall off (not very good for us)

10) We transfer the card to the riser and launch the miner again. If everything is ok, then connect the second card. We connect the map to a separate braid and a riser to a separate braid. It’s not 1050 she’s very moody in stock. 2 per braid = hemorrhoids.

IMPORTANT! Do not connect 3-4 cards at once, they load the power supply hard out of the box and the whole system flies into an eternal reboot or crashes the drivers. AMD knows this problem and promises to fix it.

  • When the second card is connected, the AMD CrossFire rectangle will appear in the drivers; it should be in the Off position. (Disabled)
  • Usually, if you turn it on in turn, it is immediately disabled, if not, then turn it off.
  • Now we have 4 columns, respectively, each map has its own settings and Wattman.
  • We repeat points 8 and 9. Having previously added the following card to the batch file in point -G 0.1, we make changes.

11) Launch the miner and go to play Wattman. We set -10 for the core and -5 for the power supply and leave the memory at the standard values (800). As the miner is running, every minute we add -5 for the core and -1 for power until we have a value of -20 core – 10 Power consumption limitation. (%). I do not recommend setting the parameters -30 / 950 / -10 right away, because sometimes it goes into artifacts and the devil would understand why. After we have recorded local success, we do the same with memory. Here the step can be different. I throw 20, until it turns out to be 940. I leave a stock somewhere, because Hynix is far from Samsung.

12) If there are 3 and 4 cards, add them in turn and repeat the whole process. Sometimes it looks ridiculous, 4 maps in the global chart for three HBCC is disabled, one is enabled, while in fact it works on all maps.

13) We launch the miner and enjoy stable work. When connecting 2 or more cards, the hash rate sometimes drops. I get somewhere between 1650-1900 h / s per second, depending on the card. And 1 mistake for 20,000 balls somewhere. Everything has been working non-stop for a week. Consumption is somewhere between 220-240 per card.

Please do not throw tomatoes, I know you sew all bios with one right and the timings with one left and you understand the registry from birth. I wrote for newbies like me. Success to everyone!

Recommended related articles:

This post is also available in: Русский

Leave a Reply

Your email address will not be published. Required fields are marked *