I had been getting a lot of help related questions (which is OK) but I thought a chat forum might help me keep things sorted as I balance mining with the "Dad" part of CircusDad. It has done far better by providing a great way for us Vega miners to connect. You should join!

*** CLICK HERE TO JOIN THE VEGA MINING SLACK GROUP ***

If your looking for troubleshooting assistance, make sure you checked the FAQ first (It typically has what you need :-). The #general channel is a great place to ask questions. If you do need to reach me directly, you can shoot me a direct message in the Slack. I go by, @CircusDad. If your looking for troubleshooting assistance,(It typically has what you need :-). Thechannel is a great place to ask questions. If you do need to reach me directly, you can shoot me a direct message in the Slack. I go by, @CircusDad.

Howdy, I'm @CircusDad . Getting my setup running has been a fun journey with many a late night. I have made several new online friends and have leveraged the experiences of those that have gone before. It's been a fun ride. This guide will not re-create the ride.This guide summarizes what I found that works and consolidates, step by step, the details you need to get there too. In many cases this info does not originate with me. However, I found no one reference available with all the links that worked for me. Here are all the details in one place. Enjoy. Good Luck! Remember, YMMV.





Have a headless computer with scripts that will reliably start a robust Vega miner. No Wattman. No flaky HBCC. Once up and running the system is hashing with CPU, Nvidia GPU and AMD (Vega) GPU's. The setup self monitors and resolves any Vega "hash drop" problems so you can focus on other things. The rig offers the ability to check the status via a web interface from any computer or phone. Note: This is primarily a Vega miner so of course the focus is Cryptonight currency (i.e. Monero, ETN, ITNS, SUMO, KRB, XLC, Nicehash Cryptonight...).





Note: The graphic above is from my original post but it no longer fully defines my mining rig. I now have two rigs. One is a 5 Vega miner (2x The graphic above is from my original post but it no longer fully defines my mining rig. I now have two rigs. One is a 5 Vega miner (2x 64's and 3x 56's ). The second has two Vega's (both 64's ), 1 old GTX-750, and 3x Rx 550's . The graphic above is also from an earlier version of XMR-Stak miner. The new version of XMR-Stak (2.2) gives me a better hash rate on the 64 (2040h/s) as can be seen here

The Equipment used in my rig is listed below. You do not need to use the same equipment in order to use this guide. The listing below includes details to help you find what you do need.



3. Card Installation and Placement

This is helpful because, as you will see, every time you start the computer each Vega will be "disabled" and then "re-enabled". It makes things smoother when you don't have to disable the display the computer is using for display... by having a reliable (not needing to be disabled) card in the main PCI slot is saves some heartburn. People run systems with 100% Vega's all the time (In fact, I have experience doing it now too) so this is NOT the only way (you don't need a Nvidia card)... but it is a convenience if you are using a non-Vega GPU in your system. My Motherboard has two full 16x-long PCI slots and 3x short PCIe slots (yours may differ). If you do not have an iGPU then the long PCI slot closest to your CPU becomes your primary GPU (there may be a short PCIe slot closer to the CPU but the long one is primary). If your rig is going to include a non-Vega GPU, it is helpful if you put it in that first long 16x slot (it can be via riser ). In my case it gets the GTX-750 (via PCIe riser).



HDMI dummy plug will go in the main GPU (GTX-750 in my case) after system is set up (I used a monitor during setup so the plug was not installed in the earlier stages). You do not need plugs for the other cards. Just the "primary". Your computer is smart enough to know when a monitor is off or is not attached and yet we are going to be changing setting to ensure Windows never puts the monitor to sleep. Since we don't want to waste energy 24hrs a day, we use the HDMI dummy plug to make the computer happy.

The Vega install order doesn't matter. The PCIe slots on MB's are spaced such that if I want to use all the slots then you need to use risers (or the card covers more then one slot). The exception is the final 16xPCI location (farthest from CPU). I was able to use that slot directly without a riser as there is nothing to the right of it for my card to obstruct. My order, starting with the slot closes to the CPU is, Vega 64, GTX-750 (in 16x slot via riser), Vega 56, Vega 56, Vega 64 (directly mounted to MB 16x PCI slot without riser).



The Vega install order doesn't matter. The PCIe slots on MB's are spaced such that if I want to use all the slots then you need to use risers (or the card covers more then one slot). The exception is the final 16xPCI location (farthest from CPU). I was able to use that slot directly without a riser as there is nothing to the right of it for my card to obstruct. My order, starting with the slot closes to the CPU is, Vega 64, GTX-750 (in 16x slot via riser), Vega 56, Vega 56, Vega 64 (directly mounted to MB 16x PCI slot without riser).





Note: Originally my guide did not spell out Windows install / driver removal in such detail but I found this foundation drives many of peoples troubleshooting issues later so I have added detail.

I recommend a clean install of Windows 10 (you don't need to start fresh... but I did).

Before starting the clean install, perform the following while powered down:



Physically install all the cards per, "Card Installation and Placement"





Plug the monitor into the proper card per, "Card Installation and Placement"





Boot-up the computer with the installation media and perform clean install.

Force Windows updates until you have the Fall Creators Update or higher

Note: This guide was once updated to state, "Version 1709, Build 16299" but both of my systems are now running the April 2018 Version with no issue (ver. 1803) so I will leave it as "or higher" until such time that I encounter an update that requires a guide change.



(People have reported issues with more then 3 Vega's unless they have this update)



Windows Start button, type "Check for updates", select, "Check for updates"



Repeat that step after every Windows reboot until it tells you it is "up to date".



Be patient... really patient... this may be the slowest part of the entire project



Open command prompt and type: "winver". Confirm it says, "Build 16299" or higher.

(Optional) Create a System Restore point called "Fall Creators Update" (doesn't take long)

Create a System Restore point called "Fall Creators Update" (doesn't take long) If you did the recommended fresh windows installation then jump to "Install GPU Drivers"

Download and install the guru3d.com Display Driver Uninstaller DDU

Download links are near the bottom of the webpage; it is a lightweight program.

If you did not do a clean Windows installation then the following steps will guide your through uninstall of prior drivers and movement of cards to their proper location:

If you have an iGPU then it will not be moving so you do not need to uninstall it.



If you have an Nvidia that will remain in the current location then you do not need to uninstall it's driver. If it will be removed and/or moved:



Restart the computer in safe mode (Instructions here if needed)





Run DDU; Select "Nvidia" in the upper right and then have it shutdown (vs. restart) so you can physically remove the card after power down.



If you ever previously tried to install the AMD drivers, or if you need to move a Vega's physical location: now is the time to uninstall



Restart the computer in safe mode (Instructions here if needed)





Run DDU; Select "AMD" in the upper right and then have it shutdown (vs. restart) so you can physically shuffle cards after power down.



OK, the computer is powered down and you have a clean slate to configure as needed.



Get every card into physical position per, "Card Installation and Placement"



While powered down, plug the monitor into the proper graphics card:



The iGPU (if you have one). If not,





Into the non-Vega GPU located in the first long PCI slot.





If you have no iGPU and non-Vega, then plug monitor into the Vega located in the first long PCI slot





If you have a mix of Vega 56's and Vega 64's then I recommend a 64 for this first PCI slot (not critical).





Boot-up computer (May be slow as it detects all the new hardware)

(Optional) Create a System Restore point called "Cards With No Drivers" (doesn't take long)

Create a System Restore point called "Cards With No Drivers" (doesn't take long) Don't skip this optional step :-)



5. Mining Related Windows Settings POWER SETTINGS: Set screen and Hard Drive to never sleep

Set screen and Hard Drive to never sleep Windows Start button: type "run" (or press Windows logo key + R)



Type: "powercfg.cpL"



Select "Change plan settings" for the plan that is selected



Set "Turn off the display" to "Never"



Set "Put the computer to sleep" to "Never"



Select "Change advanced power settings"



Expand "Hard disk" and set "Turn off hard disk after" to "0"



Select "Apply", then "OK" and then "Save Changes"



Close window



(Note: Setting hard drive to never sleep is thought to help prevent hash-rate drops when the miner is using virtual memory)

VIRTUAL MEMORY: Set up windows virtual memory (hat tip to u/hellae).

Set up windows virtual memory (hat tip to u/hellae). Windows Start button



Type: "Advanced System Settings"



Performance Settings



Advanced Tab



Virtual Memory --> change button



Deselect "Automatically mange"



Toggle Custom size: 60000MB / Maximum Size: 60000MB



Hit "SET" Button... (Don't forget this step... several have!)



Hit "OK" LARGE PAGE SIZE: Let's your miner access the memory it needs.

Let's your miner access the memory it needs. Open gpedit.exe



If you have Windows 10 Education/enterprise or Professional:





Windows start key --> type: "gpedit" and hit enter.





If you have Windows 10 Home (or Single Language Edition), you do have gpedit but it is disabled and you need to enable it. Hat tip to askvg.com who provides a bat file that will do all this work for you.





Go to askvg.com site here







Scroll down to "Method 1: Only for Windows 10 Users"







Follow instructions to download and run bat file.







Restart your computer per the instructions.







Windows start key --> type: "gpedit.msc" and hit enter.



With gpedit open:



Expand "Windows Settings"





Expand "Security Settings"





Expand "Local Policies"





Select "User Rights Assignment"





In the right side screen, Scroll down and select: "Lock Pages in Memory"





Select, "Add User or Group"





Type the user name you use when you log into windows and select, "check names"





If it is an e-mail address you include the @domain.com portion in the name





It will put an underline under your name when you know it worked.





Hit "OK" and then close the main local security policy screen. You need to restart computer before running the miner but don't do it now... a restart will come naturally later.





The graphic below shows you the screens you will have just seen. Click the photo to expand it and make it a useful size (the black boxes are where I blacked out my user name).

REMOTE DESKTOP SOFTWARE (and other support software) Install and configure a remote desktop software options, I can affirm that Google Chrome Remote Desktop is EASY to use and does not cause hash drops during mining when setup as follows: Install Google Chrome. Disable Google Chrome hardware acceleration: Open Google Chrome Settings: "chrome://settings/" In the settings search field type: "Use hardware acceleration when available" Toggle the slider to off (we need the GPU's focused on mining) Select the "Relaunch" button Install Chrome Remote Desktop extension (authorize for the computer) I recommend you do a practice remote login to ensure you know it works Note: After the driver install step (that occurs later) you are free to shutdown your computer, unplug your monitor and replace it with the HDMI dummy plug and then remote login for all the remaining steps.



OPTIONAL TWEAKS

(Optional) Download and install Notepad++ . It is a lightweight and user friendly editor that does not cause hash drops during mining and enables you to have more then one text file open at a time... you will be doing lots of text editing

. It is a lightweight and user friendly editor that does not cause hash drops during mining and enables you to have more then one text file open at a time... you will be doing lots of text editing

(Optional) Prepare Windows File Explorer to enable file extensions to be changed:

to enable file extensions to be changed:

Open Windows Explorer (Windows Button + E)





Select "View" tab, "Options", "View" tab again and then:





Uncheck the box next to: "Hide extensions for known file types" / Apply





Select "Apply to Folder" - "Yes"



(Optional) Disable Windows Auto Updates . This step is obviously up you. You should still install them from time to time for security reasons but now you can do it at the time of your choosing (maybe a weekend) vs. when Windows might otherwise break your miner (and maybe shutdown your machine) without warning.

. This step is obviously up you. You should still install them from time to time for security reasons but now you can do it at the time of your choosing (maybe a weekend) vs. when Windows might otherwise break your miner (and maybe shutdown your machine) without warning.

The process to do it is clearly defined in this Forbes article. Go to the link and scroll down to the section that says, "Option 3: Group Policy Editor".





Windows Home users remember that you now have "gpedit.msc" so you do not need to "sit this one out." (Windows button, type "run", "gpedit.msc")





Also, while there, enable the feature that tells windows not to include drivers with windows updates for those times when you DO decide to update. (photo here)



(Optional) Disable automatic driver updates . If AMD puts out a new driver that might be OK, but it would be nice to try it out on our own terms vs. an unplanned driver update.

. If AMD puts out a new driver that might be OK, but it would be nice to try it out on our own terms vs. an unplanned driver update.

Windows Start button; Type: "View Advanced System Settings"





Select the "Hardware Tab" then, "Device Installation Settings"





Toggle, "No" so windows will not try to change your system when you already have it working (I put some screen captures of the screens here if they help - Note that "Yes" is still toggled when I took the screen capture).



If you have a non-Vega card then install that driver now (GTX-750 in my case)

Restart the computer

Download the AMD blockchain driver / 64 bit / file name shows Aug 23 release.

Recommendation: If you have 4+ Vega's then I suggest you point an external fan at your Vega's during this step. Driver install is slow and the cards can get hot because the driver is not present to tell them to speed up their fans. I think AMD simply did not design the process to expect more then 2 Vegas at a time. In my case I believe a card throttled itself and caused installation to fail (Screen Shot of Error). I did this twice before I got wise to use a fan. With the fan I had no issue.

If you have 4+ Vega's then I suggest you point an external fan at your Vega's during this step. Driver install is slow and the cards can get hot because the driver is not present to tell them to speed up their fans. I think AMD simply did not design the process to expect more then 2 Vegas at a time. In my case I believe a card throttled itself and caused installation to fail (Screen Shot of Error). I did this twice before I got wise to use a fan. With the fan I had no issue. Run the Executable, let it extract itself.

Select Custom Install when prompted.

Note: I have had greater hash drop stability since I rebuilt my system and installed only the AMD driver (without the other software). If you do choose to installed the full AMD application, NEVER EVER open the AMD application. In other guides you will hear references to Wattman. Ignore them. You will hear references to HBCC sliders. Ignore them. Opening the driver software works for some people but I have had to uninstall and re-install the drivers ground up because of opening the driver. Don't do it. You need the driver installed and that is it.

Uncheck all boxes except the box for the AMD Display Driver

Select "Install" ( Note: After driver install it will invite you to restart the computer again... DON'T. We have an additional step to do before the restart.)

After driver install it will invite you to restart the computer again... DON'T. We have an additional step to do before the restart.) If you have many Vega's in your system then this process will be very slow and the screen will go black for several minutes at a time. Be patient and keep the cards cool.

Do NOT restart the computer when it gives you the option at the end of installation. u/Slithus7 suggested the disable crossfire auto link steps be preformed pre-reboot so it never has a chance to cause us a problem...

TURN OFF AMD CROSSFIRE DETECTION

Whenever Windows starts the AMD driver tries to detect other Vega cards to establish "crossfire". We don't want crossfire and even searching for it is not good for driver stability. We also don't want it polling to see about power states when your mining. Here are manual steps to disable "EnableUlps" and "EnableCrossFireAutoLink" (take note of the Vega registry ID numbers as we will need them again later)

Windows Start key --> "regedit"



Be careful to only change entries that this guide says to change, you can mess up your computer with this program.



Navigate to the proper directory by either drilling down per the photo below (easier) or you can search and let Windows find it via:



Select Edit --> Find (Ctrl-F)





Type "EnableUlps" and select the 'Find Next' button (case sensitive)





It may take a long time to search... let it work





The search windows will eventually go away having driven down into your registry and selected a field "EnableUlps" with a value of 1 (true) - click to expand pic if needed.



Note the Device Description: "Raedon RX Vega".



Note the registry number ID for the card. "0001" in the case above.



Double click on "EnableUlps" and change the value to "0" (false)



Double click on "EnableCrossFireAutoLink" and change the value of to "0" (false)



If you have only one Vega you are done. If more then one, you need to select the remaining ID's you see on the left and find your other Vegas. In my case 0000 is my Nvidia and 0001, 0002, 0003, and 0004 are all Vega's.



For each Vega:



set "EnableUlps" to "0"





set "EnableCrossFireAutoLink" to "0"





Note the device ID (i.e. 0001)





If you have a mixture of Vega64's and Vega56's, you need to know which device ID goes to which kind of card. Scroll to the "MatchingDeviceId" field and note if the device ID is for a Vega 64 (ends in "687f&rev_ c1 ") or a Vega 56 (ends in "687f&rev_ c3 ").

you have a mixture of Vega64's and Vega56's, you need to know which device ID goes to which kind of card. Scroll to the "MatchingDeviceId" field and note if the device ID is for a Vega 64 (ends in "687f&rev_ ") or a Vega 56 (ends in "687f&rev_ ").

Make sure you write down/remember the device ID's of each Vega



Backup the registry display section: In the right hand side right click on the parent "{4d36e968-e325-11ce-bfc1-08002be10318}" and select, "export". Save the file.



Note: We will later be adding something called a "soft power play table". If your computer ever does not like such a table you can (1) double-click this file you just saved (2) find and delete for each Vega the entry called, "PP_PhmSoftPowerPlayTable" (3) restart your computer... and it is like you never applied the soft power play table (that's what makes it "soft").



7. Reset Vega drivers with Device Manager The AMD blockchain driver is flaky and this trick we learned from Mythic solves the problems. People will tell you to resolve flakiness via Wattman HCBB sliders. Don't. Never open AMD driver software.

This little section will tell you how to do manually what you will ultimately do automatically with a script. It is good to (1) know what the script is doing and (2) get the system working manually so you can focus on hashing and can decouple script troubleshooting from Vega troubleshooting: Windows Start button



Type: "Device Manger"



Expand "Display adapters"



Select first vega, right click, disable



If you don't see your Vega(s), close device manager and reopen until they show up



Select first Vega, right click, enable



Repeat for all Vegas



Close device manager

If Vega's ever act weird this process will need to be repeated (until you get the script working). This is easy so don't overthink it. This needs to be done EVERY TIME WINDOWS STARTS which is why Note: If you do not have your monitor/dongle plugged into an iGPU or a Nvidia then the screen may go black during the disable and enable functions.If Vega's ever act weird this process will need to be repeated (until you get the script working). This is easy so don't overthink it. This needs to be done EVERY TIME WINDOWS STARTS which is why we will use a script to automate this later . Now you know what that script will be doing.



8. Prep GPU Configuration Software Download OverDriveNTool straight to your desktop (does not require an install)

The file comes compressed as a .z7 (you can use 7-zip.org to uncompress it)

Run the OverDriveNTool executable.

Select your first Vega in the upper left-hand drop down menu. Verify that it provides a screen of values like this (Your numbers may not match exactly and that's OK): Note: If at any time, when you select a Vega in this menu, OverDriveNTool gives you "This GPU is not supported" then sadly, that is a sign your driver is corrupted and you need to: (a) Revert to an earlier Windows restore point or (b) uninstall/reinstall the block-chain driver and repeat registry edits (click here).

If you have all Vega 56's or all Vega 64's, you can skip to the next step. If you, like me, have a mix of 56's and 64's, follow the steps below to determine which order OverdriveNTool detects the cards (record this as you will need this info later)

Use the drop down in the upper left to select your first vega



Look at the value in GPU P7.



If it says 1630 then that slot ID has a Vega 64





If it says 1590 then that slot ID has a Vega 56



Cycle through each slot ID until you have identified and recorded the ID and style for for each Vega (In my case, 0=GTX750, 1-Vega64, 2-Vega56, 3-Vega56, 4-Vega64)



Note: If you already altered the baseline GPU P7 values through previous attempts at configuration then you can use this brute force method to determine card order.

Force OverdriveNTool to create an .ini file by creating a scrap profile. Under Profile select "save" and give it name "scratch". --> Close the GUI.

Use a text editor to open the "OverdriveNTool.ini" file. Delete the files contents and replace with the text below; Save file.

the text below; Save file. Note: If you have a Liquid Cooled Vega you will need to set Fan_Target=40 or you will get an error.

NOTICE: I have been testing (and sharing with many via Reddit/chat/direct messages) a new set of .ini parameters since just before the start of the year... point is, it's been about 3 weeks of testing and I have seen better stability and know of no bad effects. As of today (1/17/2018) I am making them the guide standard. While OverdriveNTool cannot adjust the GPU_P0 to P5 and Mem_P0 to Mem_P2, it can disable them and that is what this new file does. These are great for mining but be advised that if you do not have a dedicated miner then the GPU will continue to work in the higher power P-states even when you are not mining. (They can be easily enabled with a separate bat file that calls profiles that reactivate them)

[Profile_0] Name=Vega64 GPU_P0=852;900;0 GPU_P1=991;900;0 GPU_P2=1084;900;0 GPU_P3=1138;900;0 GPU_P4=1150;900;0 GPU_P5=1202;900;0 GPU_P6=1212;905;0 GPU_P7=1408;925 Mem_P0=167;900;0 Mem_P1=500;900;0 Mem_P2=800;900;0 Mem_P3=1100;905 Fan_Min=3000 Fan_Max=4900 Fan_Target=75 Fan_Acoustic=2400 Power_Temp=85 Power_Target=0 [Profile_1] Name=Vega56 GPU_P0=852;900;0 GPU_P1=991;900;0 GPU_P2=1084;900;0 GPU_P3=1138;900;0 GPU_P4=1150;900;0 GPU_P5=1202;900;0 GPU_P6=1212;905;0 GPU_P7=1407;950 Mem_P0=167;900;0 Mem_P1=500;900;0 Mem_P2=800;900;0 Mem_P3=950;900 Fan_Min=3000 Fan_Max=4900 Fan_Target=75 Fan_Acoustic=2400 Power_Temp=85 Power_Target=0 Note: The OverdriveNTool GUI and .ini appear to control a lot of values but much of this is actually controlled by the Windows registry and is not configurable via OverdriveNTool. GPU_P6, GPU_P7, Mem_P3, Fan and Power targets ARE configurable. Changes to other lower level P states require registry edits (which we will do later). Note: These profiles are a starting point that should get you stable at the expense of power optimization. Once you are up and running you will want to tweak the GPU_P6, P7 and Mem_P3 values to get lower power consumption for the same hash rate. Hold off for now to ensure you have a safe base to tweak from.



Create a new file on the desktop called, "Run_OverdriveNTool.bat" that when run, will call OverdriveNTool.exe and have it (1) clear the settings from each of your Vega's and (2) Set the desired settings for each Vega per the .ini file you made in previous step.

Open you text editor



Select "File" -> "Save as type:" and select "all files". Give your file the name 'Run_OverdriveNTool.bat'



The .bat file will have one line of text formatted as follows: OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Vega64 -p2Vega56 -p3Vega56 -p4Vega64



Note: The FILE MUST BE CONFIGURED FOR YOUR SETUP. The provided text is for my specific configuration of cards. You need a "-r#" for each of the card ID's that needs to be reset, and then a -p#<ProfileName> to reset parameters for either a Vega 56 or Vega 64 parameter as required by your setup.

The FILE MUST BE CONFIGURED FOR YOUR SETUP. The provided text is for my specific configuration of cards. You need a "-r#" for each of the card ID's that needs to be reset, and then a -p#<ProfileName> to reset parameters for either a Vega 56 or Vega 64 parameter as required by your setup.

Your computer will be unhappy if you start mining on a Vega 56 that has the Vega 64 OverdriveNTool profile applied to it. See the FAQ if you are still unsure of your OverdriveNTool card order.



Note also: "-r0" in my case is my GTX-750 so I have no command with "-r0" or "-p0". Your setup may differ. Good luck :-). If you open the OverDriveNTool.exe GUI you will see a menu that lists each of your cards in order.

"-r0" in my case is my GTX-750 so I have no command with "-r0" or "-p0". Your setup may differ. Good luck :-). If you open the OverDriveNTool.exe GUI you will see a menu that lists each of your cards in order. Double Click your "Run_OverdriveNTool.bat" file. You will see a black screen flash up and disappear.

Confirm that your bat file worked for each card:

If you are by your machine you can just confirm that the fan of each Vega is now spinning fast (you just set the minimum to 3000RPM)



If you are remote from your system; Double Click on "OveredriveNTool.exe" to open the GUI. Cycle through your cards. Ignore most of the numbers for now as they will not yet take... you know the .bat file worked if the "Fan_Min" is set to 3000rpm for each card. (don't expect all the other numbers to match yet)



10. Install the Miner - XMR-Stak Create an "xmr-stak" directory on C drive, 'c:\xmr-stak' (or location of your choice)

In Windows defender, set XMR-stak directory as an exception

Windows Start --> Type: "Windows Defender Security Center"



Select "Virus & threat protection"



Select: "Virus & threat protection settings"



Select: "Add or remove exclusions" under the "Exclusions" section



Select the plus sign by, "Add an exclusion", "Folder" and select folder, "XMR-Stak".

Select your miner. I recommend XMR-STAK (There is also a valid option to use Cast_XMR as your Vega GPU miner). I use and will outline step-by-step setup of XMR-STAK because:

It gives the same performance (slightly better for me actually - YMMV)



Includes a really handy web interface so I can check my hashrate/connection from any computer on my LAN



It is compatible with JJs_HashMonitor which we will discuss later (that last reason is the best reason of all!)

Download XMR-STAK (you want the file called: "xmr-stak-win64.zip")

Chrome will call any miner malware and prevent the download. The xmr_stak code is not bad but so many people are using miners as malware so the browser assumes you are not aware of what your doing. Here are instructions on how to do this if you need them...



Click the link and let Chrome prevent the download.





Hit "Ctrl-J" to open the chrome download manager





XMR-Stak will be the top file: Select, "Keep Dangerous File" Extract the zip file to the c:\xmr-stak\ directory you created previously.

Give the xmr_stak.exe file administrative privileges so it has the right to control efficient blocks of memory for fast mining (the "large page sizes" you setup earlier).

Right click on the file and select "properties"



Select the "Compatibility" tab and tic box for: "Run this program as an administrator"

You may need two libraries (msvcp140.dll and vcruntime140.dll) which are available from the Microsoft server (do NOT use a random internet download of .dll files).

The needed files will install as part of VC_redist.x64.exe. The 64 bit version is here if you need them (small installation): https://go.microsoft.com/fwlink/?LinkId=746572



11. Get Ready to Mine Note: Vegas are really good at mining the CryptoNight algorithm and can be effective mining a number of coins; Monero (XMR), ETN, ITNS, SUMO, KRB, XLC, Nicehash CryptoNight to name a few. You can skip this section if you are familiar with mining and already have a coin address and target pool. This section will set you up mining Monero with a stable pool as a stable baseline. Once you are up and running you will want to explore different coin options and it is easy to switch between CryptoNight Coins.

Get a Monero address if you don't have one.

The official getmonero.org site provides some wallet options here.



MoneroMoo is a trusted Monero developer and provides the easiest way to get an address via this downloadable wallet generator (https://github.com/moneromooo-monero/monero-wallet-generator).



A hosted version of the MoneroMoo wallet generator is located here (https://moneroaddress.org).... but it is better if you download the github file.





Enter a value of your choice into the "Custom entropy" field.





Select: "Generate Wallet"





Print or in some way save this very valuable and unique information. Never share the Mnemonic seed or spend key. The "Public address" can be made public (thus the clever name) and will be needed in the next section so your mining pool knows where to send the mining profit.

Select a mining pool

A list of available pools can be found here: http://moneropools.com/



I use and highly recommend https://supportXMR.com. They have an active Chatango chat group that is very helpful. They have always paid me out the amount that they should exactly when they should. The two that run the place, @Snipa22 and @m5m400, are accessible via chat if you ever need any assistance. Of course as always, YMMV and you are free to do as you please.



This guide will assume you select supportXMR and will use pool.supportxmr.com:7777 as the assumed pool address when setting up the miner. You can fill in whichever you picked.



12. Configure the Miner - XMR-Stak Assuming you have already reset your Vega's via device manager since your last windows restart... Double click and run, xmr-stak.exe.

Windows will block execution to "Protect your PC". Select, "More info" and then "Run anyway"

It will ask if you want to use the HTTP interface. You do!

Enter the number: 420 (easy to change later)

It will ask you to enter the currency you want to mine. Enter: 'monero7'

Note: "monero7" is specific to monero, if you use an alt-coin you will likely need "cryptonight"

It will ask for your pool address. Enter: pool.supportxmr.com:7777

It will ask for your user name: Enter your public wallet address

It will ask for your password. This is not really a password. It is an identifier unique to your computer so that:

1) If you have multiple computers working, you can see how much this one is contributing toward your total hashrate



2) If you include an e-mail address, supportXMR will send you an e-mail if your computer stops hashing (this is really handy if windows ever makes a random update/restart and you would be otherwise unaware).



Enter your choice in format: "ComputerName:email@gmail.com" (don't enter actual quotes)



i.e. VegaPC:YourEmail@gmail.com or, if you don't want e-mail,





i.e. VegaPC

It will ask for your "Rig identifier". This is not supported by most pools yet so just hit 'enter'

It will ask if your pool supports TLS/SSL. SupportXMR actually does support TLS/SSL (and you should consider using it..) BUT, this may require more configuration for your machine so say 'N' for now to limit the variables you are messing with (it's easy to change later).

It will ask if you want to use Nicehash: Enter 'n' for No.

It will ask if you want to use multiple pools: Enter 'n' for No (easy to change later)

You made your first hash. Yea. Now close the miner :-).

If you saw messages about "precompiled cod" not being found that is OK and expected.



If you type 'h' in the screen before closing you will see your hash rate report. It will be nowhere near the rate you want... don't panic

It generated several files: config.txt, pools.txt, cpu.txt, amd.txt, maybe a nvidia.txt (depends if you have a Nvidia card or not). Each file needs to be optimized. The tuning guide is here but I will get you started with a few things.

Skip this step unless you did not enter a port address during the previous step... or if you entered the wrong port number. Open Config.txt

Open Config.txt



Scroll down to the bottom where is says: "httpd_port" : 0,



Change the 0 to a number of your choosing (i.e. 420)



When the miner is running you can now check your hash rate from your browser with address: http://localhost:420/h (where 420 is whatever number you picked)



If you know your computers i.p address, you can do it from any computer (or phone) on your LAN using: http://IPaddress:420/h



That last step is important. As you will see later, set a port number even if you don't think you will use the web interface much.



Save and close.

Open cpu.txt

At the bottom you will see something like (its specific to your CPU): "cpu_threads_conf" : [ { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 }, { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 }, { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 4 }, ]



Optimizing your CPU is beyond the scope of this guide. The key for this step it to pick which CPU will be reserved to instruct the GPU's.



If your CPU "hyperthreads" then you will see missing numbers ("1", "3" and "5" are missing in example above). Note a missing number (we will use "1") and exit the file without editing it.





If your CPU does not "hyperthread" then there will be no missing number. If that is the case, you will want to reserve one core for your GPU. Pick a number (say "0") and type "//" (without quotes) in the front of the line and then save & exit.

Open amd.txt (this is where the Vega optimization magic will happen)

(this is where the Vega optimization magic will happen) You will see something like the box below but there will be an index number and bracket pair { } for each Vega in your system (the example below is for a hypothetical two Vega system): "gpu_threads_conf" : [ // gpu: gfx901 memory:3920 // compute units: 64 { "index" : 0, "intensity" : 1536, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true }, // gpu: gfx901 memory:3920 // compute units: 64 { "index" : 1, "intensity" : 1536, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true }, ],



Vega's are special and can handle two threads for each index, each with a very high intensity. Each card was given an index number. For each Vega, delete the complete auto-generated bracket pair { } and replace it with the double line of text in the block below (The example text below is for a hypothetical two Vega system)



The intensity and worksize values are the same whether Vega 56 or 64.





You need two lines for each Vega so ensure you update the index for each pair.





You will need to update the "affine_to_cpu" number to be whichever CPU number you selected in the "cpu.txt" section above ("1" in our example).





You use the same affine_to_cpu number for each Vega, no matter how many you have. (if you have have an Nvidia.txt file it should be modified to use that same affine_to_cpu number as well)





WARNING: Hopefully you are using an iGPU or non-Vega GPU to serve your HDMI dongle (or monitor). If you must have your monitor/dongle plugged into a Vega then that index pair needs to have a lower intensity then what is shown below. Use 1800 for both threads of the Vega that must serve a dongle/monitor. Only the index that serves the monitor has to be reduced. Don't stress, it will cost you only about 2h/s total on a Vega 64. You will know you need this if your screen fills with artifacts while mining.

Hopefully you are using an iGPU or non-Vega GPU to serve your HDMI dongle (or monitor). Use 1800 for both threads of the Vega that must serve a dongle/monitor. Only the index that serves the monitor has to be reduced. Don't stress, it will cost you only about 2h/s total on a Vega 64. You will know you need this if your screen fills with artifacts while mining.

"gpu_threads_conf" : [ { "index" : 0, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : 1, "strided_index" : true, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true }, { "index" : 0, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : 1, "strided_index" : true, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true }, { "index" : 1, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : 1, "strided_index" : true, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true }, { "index" : 1, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : 1, "strided_index" : true, "mem_chunk" : 2, "unroll" : 8, "comp_mode" : true }, ],



Save and exit.



13. Test the Miner To mine, you do the following every time you start the computer. (you do not need a fresh windows boot every time)

Use the device manager to disable and re-enable each Vega (as defined in this section above)

Double click the "Run_OverDriveNTool.bat" file you created.

Double click the xmr-stak.exe executable

Windows may ask to allow the program access to your network... of course mining requires the internet so answer yes.

Your mining!

If your not mining... read back over the guide and ensure you did not miss a step. Many many people have affirmed that guide works so be optimistic... you're almost there. If that does not reveal the problem, visit the FAQ VIEW YOUR STATS VIEW YOUR STATS Now that your mining I will show you how to check your miner statistics from another computer using the XMR-Stak web interface.

If you don't know it already, find your computers local IP address

Open command prompt (windows key --> "cmd")



Type "ipconfig"



Look for the line that says: "IPv4 Address. . . . . . . . . . . : 192.168.xxx.yyy"

The following steps can be done from your mining computer but it is better, if you are able, to do this from another computer so you do not disturb your miner.

Open a web browser on a computer connected to your Local Area Network (LAN)



Type your IP address, a colon, and your XMR-stak port number into the address bar



: (i.e. 192.168.1.10:480 )

Woot! You can watch your money being made :-)

The main screen shows your hash rate (this screen capture of my now updated rig with Nvidia replaced with a Vega). There is also a results screen and a connection screen. When I start my miner I just remote in using remote desktop, use the script you are about to install below, and then log out of remote desktop while the Vegas are just starting to reset. I then do all my system monitoring from a different computer via this interface



If you know how to log into your router you can also forward the port that you are using for XMR-Stak. Then, if you know your public IP address (find it here) then you can use the same method to check your miner from your phone wherever you have internet access. (be careful... it can be addicting ;-). (Ok, that works and is doable but can't this be simplified with a script? Yes... keep reading) (Ok, that works and is doable but can't this be simplified with a script? Yes... keep reading)



14. Auto Start Miner with Hash Monitor HUGE frustration and can make mining with Vega's really high maintenance. @TheJerichoJones has developed a program to manage the madness. The program, "JJ's Precious Guardian", is a one shot method to starting your miner. It does all the things we did previously:

Disable Vega's,

Enable Vega's,

call OverdriveNTool,

and start xmr-stak.... but it ALSO monitors and manages the hash drop problem. Precious Guardian detects when hash drop has happened and automatically restarts the Vega's back up to full speed. Vega mining with 56's and 64's is can be the fire-and-forget miner you expected it to be. If you have spent any time mining with Vega's you know the drivers are flaky and can be prone to "hash drop". That means they can be running at full speed for a few hours or days and then BAM! For seemingly no reason they throttle down to 1600h/s and you are loosing 20% of your output until you check on your system and catch the problem. This is afrustration and can make mining with Vega's really high maintenance. @TheJerichoJones has developed a program to manage the madness. The program, "JJ's Precious Guardian", is a one shot method to starting your miner. It does all the things we did previously:but itmonitors and manages the hash drop problem. Precious Guardian detects when hash drop has happened andthe Vega's back up to full speed. Vega mining with 56's and 64's is can be the fire-and-forget miner you expected it to be.

The hash monitor REQUIRES that you are using xmr-stak ( The hash monitor REQUIRES that you are using xmr-stak ( as we installed above ). Keep in mind you ALREADY have a functioning miner. This step is totally worth it but is not required.

Note: While his original program was to be supported by donations... they were extremely rare so he has now designed Precious Guardian to mine for himself (TheJerichoJones) for the first 5 minutes after every restart. This equates to about 1 cent for a Vega restart. Even though I actually contributed with the initial concept of the program, I personally have no issue paying him this fee on my two miners because it is (a) really small and (b) because I want him to stay engaged to offer bug fixes and updates. My systems (and hopefully yours) are pretty stable so it costs a trivial amount to use the program... and when it does kick in, that means I hash dropped and thus I find it totally worth it. YMMV.

If you are not interested in hash monitoring, TheJerichoJones provides a free script that will reset the Vega's and start the miner but does not monitor for hash drop. That version is located HERE (and will also work for CastXMR ).

DOWNLOAD AND CONFIGURE JJ's PRECIOUS GUARDIAN

download "Precious Guardian"



If using XMR-stak version 2.5.1 or higher: Click HERE.





If using XMR-stak version 2.3 or higher: Click HERE.



Unzip contents INTO THE DIRECTORY that contains XMR_Stak.exe, OverdriveNTool.exe and OverdriveNTool.ini



(Windows 7 users only: I am told you need Management Framework 3.0 which can be downloaded from Microsoft HERE)



Open PreciousGuardian_Config.txt to edit three parameters

(1) Scroll down a few lines until you see:

Scroll down a few lines until you see:



_httpd_port=" 420 " (roughly line 14)

"





Change the number ("420") to be the same port number you used in xmr-stak config.txt



(2) Scroll down ~10 lines and find the line that says:

Scroll down ~10 lines and find the line that says:



_hdiff = " 300 " (roughly line 25)

"





This is your hash drop trigger (in h/s). Change the number as you desire. I recommend you change the trigger to at least 100h/s for each Vega in your system. If CPU mining is also being performed your hash rate may fluctuate a little when you use your computer so you might want a little more margin.







Note: A Vega hash drop looses ~300h/s per Vega





(3) The program would technically work now but we want it to call OverdriveNTool every time the Vega's reset. Scroll way down to the Video Tools management section and find the line that says:

The program would technically work now but we want it to call OverdriveNTool every time the Vega's reset. Scroll way down to the Video Tools management section and find the line that says:



#_vidTool= " OverdriveNTool.exe -r1 -p1Vega64" (roughly line 125)







(a) Remove the pound sign (#) from the front of the line







(b) Replace the value in quotes with the contents of your Run_OverDriveNTool.bat file. In my case:







_vidTool= " OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Vega64 -p2Vega56 -p3Vega56 -p4Vega64 "

"



Save and close. (you can come back later and setup email / text / or Slack Channel alerts to let you know when hash drop is detected)

START MONITORED MINING

Your set. Double click PreciousGuardian.exe and you are mining!



The very first time will receive a windows warning because an "unsigned program" is trying to run. Select "More info" and then "Run Anyway"





As mentioned before, the monitor will mine for the developer (TheJerichoJones) for 5 minutes and then restart and mine for you indefinitely (there is no back and forth). That first restart is per the programs design.

(optional) Right click on "PreciousGuardian.exe" and select, "create shortcut".



(optional) Rename the shortcut (i.e. "Start Miner") and move it to your desktop.

WARNING/DISCLAIMER: In addition to the bogus throttling that Vega's will do because of flaky drivers, there is also a legitimate reason to throttle. Vega's will legitimately throttle themselves if the memory on the cards (HBM) get's too hot. In such a case, the throttling was actually good because it protected your cards. That should not be the case for you because we used OverdriveNTool to set the min fan speed to 3000rpm which should keep things nice and cool. That said, USE THIS SCRIPT AT YOUR OWN RISK. Restarts should be rare. If you start getting back to back restarts, you need to get involved.



15. Set Windows to Auto Start Miner at Login

If you are at this point in the guide then hopefully your rig is stable and mining effectively. This entire section is an optional bonus for those that want their miners to start automatically when the computer boots up.