Step-by-step tuning Vega 56 / Vega 64

vega

I myself am their lucky owner. And I would like to create a topic with the most complete information about Vega. And guides on their customization.

Instructions are basic working from foreign users

1) http://www.gandalph3000.com/cast_xmr/howto-mine-monero-rx-vega/
From the creator of the miner cast_xmr with mini settings.
– A simple instruction without tulsov, wattmans and other musicians.
2) http://vega.miningguides.com/
The assembled hodgepodge is here and flashing and turning on the shutdown when HBCC starts and editing the rest. Only for hard-core miners.

– My personal instruction, how it all worked for me.

1) Connect 1 Vega 56/64 to the 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 gemmoroya.) Only a clean installation from scratch.
3) Run the system.
3.1) We are installing this program
– https://miningclub.info/resources/vykljuchaem-lishnee-v-windows-10.157/ we kill updates, etc.
3.2) Increase the amount of virtual memory
Control Panel / System and Security / Advanced System Settings / Advanced
Click the Settings> Performance Options> Advanced>
We see the virtual memory letter and click Change to specify 15 gigabytes for each vega. (If there is not that much memory, you can also put 8 gigs per card, experienced from the forum say and so it works)
I have 4 of them so we will put 60,000 mb.
Original size 59000 – Maximum size 60,000 my case
Original size 32000- Maximum size 32000 – should work too
4) In the control panel we change the power parameters
Power supply / Changing the circuit parameters
Disable display: Never
Put your computer into sleep mode: Never
click Save changes.
5) Download the drivers Block from the official website of AMD
https://support.amd.com/en-us/kb-ar…eta-for-Blockchain-Compute-Release-Notes.aspx
6) Install the drivers and all their components and wait until the card calms down. During the installation, do not touch anything and do not pull, at the end of the installation the program will offer a reboot, usually when you click on it, it can also hang. We boldly let the system into reboot.
7) After installing the drivers, click on
Games> Global settings>
we will have two bars
1 – Global graphics (Radeon RX Vega)
2 – Global Wattman (Radeon Rx Vega)
in the first column, we need to press the HBCC Memory Segment button and turn it to the on position. And then click apply. The driver will go into reboot.
Here an important nuance. Sometimes a check mark is already enabled, but HBCC is actually out of the box. AMD is aware of this problem and, in principle, offers not to pay attention to it, that is, if HBCC is enabled and the hash is small, then just move the slider to the disabled position and the HBCC will actually work on the miracle.

then go to 2 – Global Wattman (Radeon Rx Vega)
and do not touch anything there except the cooler settings.
SPEED (RPM) Manually
Put the slider in the on position and raise the cooler’s rpm. It is necessary that when the first start of the miner the card does not heat up to 78 degrees and does not begin to smoke with gaskets.

8) Start the miner. In my case, this is cast_xmr.
Example of a batch file
cast_xmr-vega -S xmr-eu.dwarfpool.com:8100 -u 47BCGhAqrj8ZN5UQgLkW7x5qx7vrYQwMwHDiPsNEhQdMCbnC6UGYzP8GccsHPAUffN4c8NLJoU4bBMp2sjiXuwTx59gJZ7J -G 0% *
and look at the indicators Hashrate
there should be 1500-1900 depending on the map. If the values ​​are smaller, turn off the miner and go to the driver to turn on / off the HBCC Memory Segment.
Leave the miner to work so for 15-20 minutes.
9) Turn off the miner by pressing the q button. If you go crazy on a cross in a batnik, there’s a chance somewhere around 20 percent that the driver will fall off (not very good for us)
10) Transplant the map to the riser and start the miner again. If everything is OK, then we connect the second card. We connect the map to a separate scythe and a riser to a separate scythe. This is not 1050, it is very capricious in the runoff. 2 on the braid = hemorrhoids.
IMPORTANT! Do not connect 3-4 cards at once, out of the box they will ship the bp hard and the entire system flies to perpetual reboot or crashes the driver. AMD know this problem and promise to fix it.
When a second card is connected, a rectangle appears in the drivers
AMD CrossFire it should be in the Off position. (Deactivated that is)
Usually if you turn it on in turn, it’s immediately disabled, if not, then turn it off.
Now we have 4 columns, respectively, for each card its settings and Wattman.
Repeat steps 8 and 9. Preliminarily adding the following card to the batch file in the paragraph -G 0.1, we make changes.
11) Start the miner. And go to Wattman is played. Set -10 for the core and -5 for power and memory is left at standard values ​​(800).
As the work of the miner, every minute we throw -5 on the core and -1 on the power until we have the value -20 core – 10 Restriction of power consumption (%). Immediately put the parameters -30 / 950 / -10 I do not recommend, because sometimes it goes into artifacts and the devil would understand why.
After we fixed the local success, the same thing we do with the memory. Here the step can be time

As the work of the miner, every minute we throw -5 on the core and -1 on the power until we have the value -20 core – 10 Restriction of power consumption (%). Immediately put the parameters -30 / 950 / -10 I do not recommend, because sometimes it goes into artifacts and the devil would understand why.
After we fixed the local success, the same thing we do with the memory. Here the step can be different. I throw on 20, until it turns out 940. Where do I leave the drain, because Hynix is ​​not so Samsung (well, you understand, as Valera says)
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 timeline for three HBCC disabled for one is enabled while in fact works on all cards.
13) We start the miner and enjoy the stable work. When you connect 2 or more cards, sometimes a hashtad sags. At me it turns out where that 1650-1900 h / s in a second depending on a card. And 1 error on a 20,000 ball somewhere. It’s been working all week without stopping. Consumption is somewhere 220-240 per card.
P.S. Screenshots will soon add, so it was clearer.
If there are any incomprehensible moments, write try to explain.
Tomatoes I ask you not to throw, I know you are all bios sew one right and timings to one left and the registry from birth know. Wrote for beginners, takz like me. All the best!

Leave a Reply

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