[Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s)

[tf2addict]

deleted

[Cyan_Antares]

So.. to sum it up, in order to keep the rig running all the time, after every restart and so on..

First, this is how my Cast XMR folder looks like, with Cast XMR, devcon and OverdriveNTool inside:

https://s18.postimg.org/d456tnk7d/Capture.jpg

Below is the bat file content (Mine.bat, which calls itself when the timer expires). I start numbering the Vegas with r1 and p1 to work with OverdriveNTool because I use the Intel iGPU. If you don't use an iGPU they should be numbered starting from r0 and p0.

cd
devcon.exe disable "PCI\VEN_1002&DEV_687F"
timeout /t 5
devcon.exe enable "PCI\VEN_1002&DEV_687F"
timeout /t 5
OverdriveNTool.exe -r1 -r2 -r3 -r4 -r5 -r6 -p1Vega56 -p2Vega56 -p3Vega56 -p4Vega56 -p5Vega56 -p6Vega56
timeout /t 1
cd

@echo off

echo -------------------------------------------------------------------
echo Restarts the miner every 40 minutes //you can set it to your own liking
echo -------------------------------------------------------------------
echo:

set executable=cast_xmr-vega.exe
set commandline=  -G 0,1,2,3,4,5 -S xmr-eu1.nanopool.org:14444 -u YourWalletAddress.RigNameOfYourChoice %*
set runforseconds=2400
set restartinseconds=2
set /a counter=0
timeout 2
:start
start "cast_xmr-vega" %executable% %commandline%
echo:
echo The program is going to run for %runforseconds% seconds
timeout %runforseconds%
taskkill /f /im %executable%
cd
Mine.bat
echo:
echo Restarting the app in %restartinseconds% seconds (%counter%)
timeout %restartinseconds%
set /a counter+=1
echo:
echo:
goto start

If you want your rig running ALL the time without you having to do anything even if you restart Windows or the computer powers off, you can call your own bat when Windows starts and you can automate the login process in Windows, following these steps:

Step 1: Configure BIOS Settings to power on the computer automatically if for whatever reason power is lost
Before we even get to Windows, make sure your mining computer’s BIOS settings are in order. Power on your computer, and press the “delete” key a few times immediately after power on. You should end up in the BIOS configuration area. Do the following, then save & exit:
Change power options so that the computer automatically turns itself on whenever power is restored. The reason for this is two-fold: first, it’ll make sure that your miner automatically starts up after a power outage. Second, it makes powering the computer on much easier if you don’t happen to have a power switch connected to the motherboard.
Disable all components that you don’t plan to use. This might save a little bit of power, and since your miner will likely be running 24/7, it’ll add up. For me, that meant disabling onboard audio, the USB 3.0 ports, one of the SATA controllers, the Firewire port, and the serial port.
If you’re running a lot of GPUs (4+), additional tweaks might be necessary to ensure that they’re all recognized by the OS. Exact tweaks vary by motherboard, but setting the PCIe speed to Gen1 is usually a good place to start. No need to change anything now, but make a mental note that you may need to come back and play around a bit if all of your GPUs don’t show up in the OS later.

Step 2: Configure automatic login
If you’re building a dedicated mining rig, then you probably want your mining rig to boot up and start mining automatically, without any user intervention. We’ll need to enable auto-login for that to be possible.
Right-click on the Start Menu and select “Run”. Type “netplwiz” (without the quotes) at the prompt, and click “ok”.
Uncheck the box that says “Users must enter a user name and password to use this computer”.
Click “Apply”. You’ll be prompted to enter your password to confirm the change.

Step 3: Configure your miner to start automatically
We want our rig to automatically start mining whenever it’s powered on or rebooted. That way, we keep mining losses to a minimum whenever a power outage occurs, and we don’t have to worry about manually starting it back up in other situations.
Open Windows Explorer and navigate to the folder where you created “mine.bat” in the previous step.
Right-click on your mine.bat file, and pick “Copy”.
Now, navigate to %AppData%\Microsoft\Windows\Start Menu\Programs\Startup (should be something like C:\Users\[YOUR WINDOWS USERNAME]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup).
Right-click anywhere on the empty background of the Startup folder and select “Paste shortcut”.
You should see a shortcut to your mine.bat file appear in the startup folder. Windows should automatically execute it upon bootup.

Note: This simple methods don't deal with hash rate drops you can experience when switching the VGA output on your iGPU and so on, there is the JJ script for that, but I don't experience that. This mostly works for rigs running 24/7 at home or remotely via Chrome Remote Desktop.

thank you for the tip. with this setting helps my vega rig run more stable without loss of hash rate. it helps also reduce the possibility of sudden freeze, that I think caused by HBM high temps/errors.

well, I would like to share some of my discoveries after some sleepless nights   over getting things stable --in addition to setting up the Vega 56 rig with 6 cards, I have a desktop computer with a single RX 570 and the program never failed, so overall Cast XMR tends to run well, I guess it depends on several factors.

STEP BY STEP GUIDE TO SET UP YOUR VEGA CARDS TO START MINING AT HIGH SPEED AND LOW POWER CONSUMPTION

So I finally managed to keep everything stable and these are my settings and bats. First of all, this is how the folder with the tools to start mining looks like:

https://s31.postimg.org/cwmzlv31n/Capture.jpg

Imho, it is a good idea to keep all the software you need in the same folder, to make things easier for you.

Note that now I have 2 bats, one called Mine.bat which only runs once at Windows startup.. and it disables then enables the Vega cards, AND finally it calls Mine2.bat (this one runs in an infinite loop). These are the contents of Mine.bat:

cd
devcon.exe disable "PCI\VEN_1002&DEV_687F"
timeout /t 5
devcon.exe enable "PCI\VEN_1002&DEV_687F"
timeout /t 5
OverdriveNTool.exe -r1 -r2 -r3 -r4 -r5 -r6 -p1Vega56 -p2Vega56 -p3Vega56 -p4Vega56 -p5Vega56 -p6Vega56
timeout /t 1
cd
Mine2.bat

Note1: the command line starts numbering the Vegas with r1 and p1 to work with OverdriveNTool because I use the Intel iGPU as the main GPU. If you don't use an iGPU they should be numbered starting from r0 and p0.

Note2: You shouldn't need to run devcon.exe more than once after you start the OS!! That's because once it disables and then re-enables the Vega cards they should never go below 1900Hs, except on very rare occasions where one of them can drop to 1700 something but in the next hash, it is back into the 1900s. However it might be useful to use that batch file again when you switch video output ports -say you use a HDMI headless ghost and you need to use an old VGA monitor with your rig, so you unplug the HDMI ghost and plug the monitor, that's normal and always causes a hash rate drop and the average hashrate drops from 1900+ to 1700 something for every card.

Note3: To keep everything automated with devcon.exe and any other mining program at startup so no program prompts you to let them run as an administrator, press the Windows key on the keyboard and search for user -or something similar- thus the Change User Account Control settings program appears, then just launch it and change the slider to Never notify.

IMPORTANT!!: OverdriveNTool.exe looks into a file called OverdriveNTool.ini for the parameters. These are my settings (I called the profile just like that, Vega56 but that parameter can be changed, and the OverdriveNTool command line needs to reflect that name (for Vega 64 owners, I have no experience with those, so the settings might differ):

[Profile_0]
Name=Vega56
GPU_P0=852;900
GPU_P1=991;900
GPU_P2=1084;900
GPU_P3=1138;900
GPU_P4=1150;900
GPU_P5=1202;900
GPU_P6=1212;905
GPU_P7=1407;935
Mem_P0=167;900
Mem_P1=500;900
Mem_P2=800;900
Mem_P3=935;900


FINAL NOTE: Where it says 935..., that's an important setting for stability. Vanilla Vega 56 cards can start complaining with any value above that, and this can cause random hangs in Cast XMR or devcon.exe (but you shouldn't need to use devcon.exe more than once, at startup, or in special situations), and those random hangs can mean quite a few minutes without mining til the corresponding bat file kills and restarts Cast XMR..., and that affects productivity a lot.

This amazing Vega mining guide I used to learn and helped me immensely when I started, which you can find here, http://vega.miningguides.com/ uses 950 as a value instead of 935. Don't! It works, it can go for hours or days without issue, but in my personal experience anything above 935MHz can be problematic and it ends up manifesting.

Then I have another one called Mine2.bat, which is called by Mine.bat after disabling and enabling the cards with devcon.exe to keep them mining at 1900Hs. These are the contents of the batch file (infinite thanks to FgTeamBR   who gave me the basis for this!!):

timeout /t 1
OverdriveNTool.exe -r1 -r2 -r3 -r4 -r5 -r6 -p1Vega56 -p2Vega56 -p3Vega56 -p4Vega56 -p5Vega56 -p6Vega56

@echo off

echo -------------------------------------------------------------------
echo Restarts the miner every 30 minutes //you can set it to your own liking, of course
echo -------------------------------------------------------------------
echo:

set executable=cast_xmr-vega.exe
set commandline=  -G 0,1,2,3,4,5 -S xmr-eu1.nanopool.org:14444 -u YourWalletAddress.RigNameOfYourChoice %*
set runforseconds=1800
set restartinseconds=2
set /a counter=0
timeout 2
:start
start "cast_xmr-vega" %executable% %commandline%
echo:
echo The program is going to run for %runforseconds% seconds
timeout %runforseconds%
taskkill /f /im %executable%
cd
Mine2.bat

This one ends up calling itself in an infinite loop, which is what we want.

VERY IMPORTANT!!: Note the OverdriveNTool.exe line at the very start of the batch file. I added this file after having issues and my own findings while running the cards for hours without apparent, superficial issues.

I repeat that you DO NOT need to call devcon.exe every time you restart Cast XMR, this reduces the stress on the cards plus you don't lose 20 seconds of mining while the cards are disabled and re-enabled.

HOWEVER, it is important that you refresh the OverdriveNTool settings in the cards from time to time, plus you restart Cast XMR, the entire process doesnt take up more than 3 seconds, and it's very convenient.

From personal experience, I have been running the Vegas for hours without an issue but for no apparent reason, I noticed that one of them was running at like 83ºC -had to use GPU-Z to check that- and it was as if it FORGOT their settings and aside from running hot, the fan speed dropped to 1500rpm for whatever mysterious reason, while the other cards kept their fans spinning at 3000+ rpm, the intended speed.

Plus, one of the cards permanently dropped the hashrate to 1700H/s, also for no apparent reason, so it seems like sometimes the cards can't recall their intended settings. After restarting their settings with OverdriveNTool, they go back to normal.

The temperature thing is very dangerous, it can significantly reduce your graphics card life for obvious reasons.

Finally, also from personal experience I'd wholeheartedly recommend Remote Chrome Desktop to use as a remote manager for your rig. It is easy to use and set up, just don't forget to have a mouse plugged into the physical machine so the mouse pointer is always visible and that's it. An excellent program!

Some additional tips to keep your rig running 24/7 with basically no intervention of yours -remember to run your .bat file with devcon.exe every time Windows starts and that's it.

If you want your rig running ALL the time without you having to do anything even if you restart Windows or the computer powers off, you can call your own bat when Windows starts and you can automate the login process in Windows, following these steps:

Step 1: Configure BIOS Settings to power on the computer automatically if for whatever reason power is lost
Before we even get to Windows, make sure your mining computer’s BIOS settings are in order. Power on your computer, and press the “delete” key a few times immediately after power on. You should end up in the BIOS configuration area. Do the following, then save & exit:
Change power options so that the computer automatically turns itself on whenever power is restored. The reason for this is two-fold: first, it’ll make sure that your miner automatically starts up after a power outage. Second, it makes powering the computer on much easier if you don’t happen to have a power switch connected to the motherboard.
Disable all components that you don’t plan to use. This might save a little bit of power, and since your miner will likely be running 24/7, it’ll add up. For me, that meant disabling onboard audio, the USB 3.0 ports, one of the SATA controllers, the Firewire port, and the serial port.
If you’re running a lot of GPUs (4+), additional tweaks might be necessary to ensure that they’re all recognized by the OS. Exact tweaks vary by motherboard, but setting the PCIe speed to Gen1 is usually a good place to start. No need to change anything now, but make a mental note that you may need to come back and play around a bit if all of your GPUs don’t show up in the OS later.

Step 2: Configure automatic login
If you’re building a dedicated mining rig, then you probably want your mining rig to boot up and start mining automatically, without any user intervention. We’ll need to enable auto-login for that to be possible.
Right-click on the Start Menu and select “Run”. Type “netplwiz” (without the quotes) at the prompt, and click “ok”.
Uncheck the box that says “Users must enter a user name and password to use this computer”.
Click “Apply”. You’ll be prompted to enter your password to confirm the change.

Step 3: Configure your miner to start automatically
We want our rig to automatically start mining whenever it’s powered on or rebooted. That way, we keep mining losses to a minimum whenever a power outage occurs, and we don’t have to worry about manually starting it back up in other situations.
Open Windows Explorer and navigate to the folder where you created “mine.bat” in the previous step.
Right-click on your mine.bat file, and pick “Copy”.
Now, navigate to %AppData%\Microsoft\Windows\Start Menu\Programs\Startup (should be something like C:\Users\[YOUR WINDOWS USERNAME]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup).
Right-click anywhere on the empty background of the Startup folder and select “Paste shortcut”.
You should see a shortcut to your mine.bat file appear in the startup folder. Windows should automatically execute it upon bootup.

Conclusion
Personal experiences might differ, but with those settings a Vega 56 rig could run 24/7 without hashrate drops and very stable, which is the point, at an average of 1940H/s or so.

This is all so unnecessary. I have now setup 3 Vega 64/56 rigs in the past month (16 Vega cards all different manufactures) and not one of them needs this crap script. If you do the reg mod/soft power play tables its beyond me why you need overdriven? Set the fan speed and temps in wattman and you are done. The rigs run 24/7 with no problems. If you need a script like this just understand that you are doing it wrong. The pools will hate the constant disconnect reconnect as they work to establish diff levels.


This kind a stuff just makes me laugh!


  

well, it works for me, because I set it every hour or (currently) two and the disconnect takes less than 3 seconds. How do you apply the soft power play table? I downloaded a registry (.reg) file but it doesn't add anything to the registry file. I am working in a 6 Vega 56 rig, the Vegas are unmodded 'cos they arent mine.

Also I fear not double checking the temperatures so I use OverdriveNTool thus the Vegas "recall" the correct settings because of my experience with one achieving 83º and having the fan spinning at just 1400-1500rpm, for whatever reason

[Cyan_Antares]

https://s14.postimg.org/agmftrsw1/Untitled.png

I am currently into a 2 hours restart cycle and as things get more and more stable like they've been for the last 24 hours ever since I made it fully stable (have been resetting the OverdriveNTool values every 45 minutes or so), I am going to increase the timer to 4 or more hours --the restart takes 3 seconds, 2 to remove Cast XMR process, 1 to set up OverdriveNTool options and restart Cast XMR.

Average hashrate for the last 6 hours have been 11,544.1 H/s, not bad for a 6 Vega 56 rig running at 935MHz. Temps are fine, too.

[commonorx]

So.. to sum it up, in order to keep the rig running all the time, after every restart and so on..

First, this is how my Cast XMR folder looks like, with Cast XMR, devcon and OverdriveNTool inside:

https://s18.postimg.org/d456tnk7d/Capture.jpg

Below is the bat file content (Mine.bat, which calls itself when the timer expires). I start numbering the Vegas with r1 and p1 to work with OverdriveNTool because I use the Intel iGPU. If you don't use an iGPU they should be numbered starting from r0 and p0.

cd
devcon.exe disable "PCI\VEN_1002&DEV_687F"
timeout /t 5
devcon.exe enable "PCI\VEN_1002&DEV_687F"
timeout /t 5
OverdriveNTool.exe -r1 -r2 -r3 -r4 -r5 -r6 -p1Vega56 -p2Vega56 -p3Vega56 -p4Vega56 -p5Vega56 -p6Vega56
timeout /t 1
cd

@echo off

echo -------------------------------------------------------------------
echo Restarts the miner every 40 minutes //you can set it to your own liking
echo -------------------------------------------------------------------
echo:

set executable=cast_xmr-vega.exe
set commandline=  -G 0,1,2,3,4,5 -S xmr-eu1.nanopool.org:14444 -u YourWalletAddress.RigNameOfYourChoice %*
set runforseconds=2400
set restartinseconds=2
set /a counter=0
timeout 2
:start
start "cast_xmr-vega" %executable% %commandline%
echo:
echo The program is going to run for %runforseconds% seconds
timeout %runforseconds%
taskkill /f /im %executable%
cd
Mine.bat
echo:
echo Restarting the app in %restartinseconds% seconds (%counter%)
timeout %restartinseconds%
set /a counter+=1
echo:
echo:
goto start

If you want your rig running ALL the time without you having to do anything even if you restart Windows or the computer powers off, you can call your own bat when Windows starts and you can automate the login process in Windows, following these steps:

Step 1: Configure BIOS Settings to power on the computer automatically if for whatever reason power is lost
Before we even get to Windows, make sure your mining computer’s BIOS settings are in order. Power on your computer, and press the “delete” key a few times immediately after power on. You should end up in the BIOS configuration area. Do the following, then save & exit:
Change power options so that the computer automatically turns itself on whenever power is restored. The reason for this is two-fold: first, it’ll make sure that your miner automatically starts up after a power outage. Second, it makes powering the computer on much easier if you don’t happen to have a power switch connected to the motherboard.
Disable all components that you don’t plan to use. This might save a little bit of power, and since your miner will likely be running 24/7, it’ll add up. For me, that meant disabling onboard audio, the USB 3.0 ports, one of the SATA controllers, the Firewire port, and the serial port.
If you’re running a lot of GPUs (4+), additional tweaks might be necessary to ensure that they’re all recognized by the OS. Exact tweaks vary by motherboard, but setting the PCIe speed to Gen1 is usually a good place to start. No need to change anything now, but make a mental note that you may need to come back and play around a bit if all of your GPUs don’t show up in the OS later.

Step 2: Configure automatic login
If you’re building a dedicated mining rig, then you probably want your mining rig to boot up and start mining automatically, without any user intervention. We’ll need to enable auto-login for that to be possible.
Right-click on the Start Menu and select “Run”. Type “netplwiz” (without the quotes) at the prompt, and click “ok”.
Uncheck the box that says “Users must enter a user name and password to use this computer”.
Click “Apply”. You’ll be prompted to enter your password to confirm the change.

Step 3: Configure your miner to start automatically
We want our rig to automatically start mining whenever it’s powered on or rebooted. That way, we keep mining losses to a minimum whenever a power outage occurs, and we don’t have to worry about manually starting it back up in other situations.
Open Windows Explorer and navigate to the folder where you created “mine.bat” in the previous step.
Right-click on your mine.bat file, and pick “Copy”.
Now, navigate to %AppData%\Microsoft\Windows\Start Menu\Programs\Startup (should be something like C:\Users\[YOUR WINDOWS USERNAME]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup).
Right-click anywhere on the empty background of the Startup folder and select “Paste shortcut”.
You should see a shortcut to your mine.bat file appear in the startup folder. Windows should automatically execute it upon bootup.

Note: This simple methods don't deal with hash rate drops you can experience when switching the VGA output on your iGPU and so on, there is the JJ script for that, but I don't experience that. This mostly works for rigs running 24/7 at home or remotely via Chrome Remote Desktop.

thank you for the tip. with this setting helps my vega rig run more stable without loss of hash rate. it helps also reduce the possibility of sudden freeze, that I think caused by HBM high temps/errors.

well, I would like to share some of my discoveries after some sleepless nights   over getting things stable --in addition to setting up the Vega 56 rig with 6 cards, I have a desktop computer with a single RX 570 and the program never failed, so overall Cast XMR tends to run well, I guess it depends on several factors.

STEP BY STEP GUIDE TO SET UP YOUR VEGA CARDS TO START MINING AT HIGH SPEED AND LOW POWER CONSUMPTION

So I finally managed to keep everything stable and these are my settings and bats. First of all, this is how the folder with the tools to start mining looks like:

https://s31.postimg.org/cwmzlv31n/Capture.jpg

Imho, it is a good idea to keep all the software you need in the same folder, to make things easier for you.

Note that now I have 2 bats, one called Mine.bat which only runs once at Windows startup.. and it disables then enables the Vega cards, AND finally it calls Mine2.bat (this one runs in an infinite loop). These are the contents of Mine.bat:

cd
devcon.exe disable "PCI\VEN_1002&DEV_687F"
timeout /t 5
devcon.exe enable "PCI\VEN_1002&DEV_687F"
timeout /t 5
OverdriveNTool.exe -r1 -r2 -r3 -r4 -r5 -r6 -p1Vega56 -p2Vega56 -p3Vega56 -p4Vega56 -p5Vega56 -p6Vega56
timeout /t 1
cd
Mine2.bat

Note1: the command line starts numbering the Vegas with r1 and p1 to work with OverdriveNTool because I use the Intel iGPU as the main GPU. If you don't use an iGPU they should be numbered starting from r0 and p0.

Note2: You shouldn't need to run devcon.exe more than once after you start the OS!! That's because once it disables and then re-enables the Vega cards they should never go below 1900Hs, except on very rare occasions where one of them can drop to 1700 something but in the next hash, it is back into the 1900s. However it might be useful to use that batch file again when you switch video output ports -say you use a HDMI headless ghost and you need to use an old VGA monitor with your rig, so you unplug the HDMI ghost and plug the monitor, that's normal and always causes a hash rate drop and the average hashrate drops from 1900+ to 1700 something for every card.

Note3: To keep everything automated with devcon.exe and any other mining program at startup so no program prompts you to let them run as an administrator, press the Windows key on the keyboard and search for user -or something similar- thus the Change User Account Control settings program appears, then just launch it and change the slider to Never notify.

IMPORTANT!!: OverdriveNTool.exe looks into a file called OverdriveNTool.ini for the parameters. These are my settings (I called the profile just like that, Vega56 but that parameter can be changed, and the OverdriveNTool command line needs to reflect that name (for Vega 64 owners, I have no experience with those, so the settings might differ):

[Profile_0]
Name=Vega56
GPU_P0=852;900
GPU_P1=991;900
GPU_P2=1084;900
GPU_P3=1138;900
GPU_P4=1150;900
GPU_P5=1202;900
GPU_P6=1212;905
GPU_P7=1407;935
Mem_P0=167;900
Mem_P1=500;900
Mem_P2=800;900
Mem_P3=935;900


FINAL NOTE: Where it says 935..., that's an important setting for stability. Vanilla Vega 56 cards can start complaining with any value above that, and this can cause random hangs in Cast XMR or devcon.exe (but you shouldn't need to use devcon.exe more than once, at startup, or in special situations), and those random hangs can mean quite a few minutes without mining til the corresponding bat file kills and restarts Cast XMR..., and that affects productivity a lot.

This amazing Vega mining guide I used to learn and helped me immensely when I started, which you can find here, http://vega.miningguides.com/ uses 950 as a value instead of 935. Don't! It works, it can go for hours or days without issue, but in my personal experience anything above 935MHz can be problematic and it ends up manifesting.

Then I have another one called Mine2.bat, which is called by Mine.bat after disabling and enabling the cards with devcon.exe to keep them mining at 1900Hs. These are the contents of the batch file (infinite thanks to FgTeamBR   who gave me the basis for this!!):

timeout /t 1
OverdriveNTool.exe -r1 -r2 -r3 -r4 -r5 -r6 -p1Vega56 -p2Vega56 -p3Vega56 -p4Vega56 -p5Vega56 -p6Vega56

@echo off

echo -------------------------------------------------------------------
echo Restarts the miner every 30 minutes //you can set it to your own liking, of course
echo -------------------------------------------------------------------
echo:

set executable=cast_xmr-vega.exe
set commandline=  -G 0,1,2,3,4,5 -S xmr-eu1.nanopool.org:14444 -u YourWalletAddress.RigNameOfYourChoice %*
set runforseconds=1800
set restartinseconds=2
set /a counter=0
timeout 2
:start
start "cast_xmr-vega" %executable% %commandline%
echo:
echo The program is going to run for %runforseconds% seconds
timeout %runforseconds%
taskkill /f /im %executable%
cd
Mine2.bat

This one ends up calling itself in an infinite loop, which is what we want.

VERY IMPORTANT!!: Note the OverdriveNTool.exe line at the very start of the batch file. I added this file after having issues and my own findings while running the cards for hours without apparent, superficial issues.

I repeat that you DO NOT need to call devcon.exe every time you restart Cast XMR, this reduces the stress on the cards plus you don't lose 20 seconds of mining while the cards are disabled and re-enabled.

HOWEVER, it is important that you refresh the OverdriveNTool settings in the cards from time to time, plus you restart Cast XMR, the entire process doesnt take up more than 3 seconds, and it's very convenient.

From personal experience, I have been running the Vegas for hours without an issue but for no apparent reason, I noticed that one of them was running at like 83ºC -had to use GPU-Z to check that- and it was as if it FORGOT their settings and aside from running hot, the fan speed dropped to 1500rpm for whatever mysterious reason, while the other cards kept their fans spinning at 3000+ rpm, the intended speed.

Plus, one of the cards permanently dropped the hashrate to 1700H/s, also for no apparent reason, so it seems like sometimes the cards can't recall their intended settings. After restarting their settings with OverdriveNTool, they go back to normal.

The temperature thing is very dangerous, it can significantly reduce your graphics card life for obvious reasons.

Finally, also from personal experience I'd wholeheartedly recommend Remote Chrome Desktop to use as a remote manager for your rig. It is easy to use and set up, just don't forget to have a mouse plugged into the physical machine so the mouse pointer is always visible and that's it. An excellent program!

Some additional tips to keep your rig running 24/7 with basically no intervention of yours -remember to run your .bat file with devcon.exe every time Windows starts and that's it.

If you want your rig running ALL the time without you having to do anything even if you restart Windows or the computer powers off, you can call your own bat when Windows starts and you can automate the login process in Windows, following these steps:

Step 1: Configure BIOS Settings to power on the computer automatically if for whatever reason power is lost
Before we even get to Windows, make sure your mining computer’s BIOS settings are in order. Power on your computer, and press the “delete” key a few times immediately after power on. You should end up in the BIOS configuration area. Do the following, then save & exit:
Change power options so that the computer automatically turns itself on whenever power is restored. The reason for this is two-fold: first, it’ll make sure that your miner automatically starts up after a power outage. Second, it makes powering the computer on much easier if you don’t happen to have a power switch connected to the motherboard.
Disable all components that you don’t plan to use. This might save a little bit of power, and since your miner will likely be running 24/7, it’ll add up. For me, that meant disabling onboard audio, the USB 3.0 ports, one of the SATA controllers, the Firewire port, and the serial port.
If you’re running a lot of GPUs (4+), additional tweaks might be necessary to ensure that they’re all recognized by the OS. Exact tweaks vary by motherboard, but setting the PCIe speed to Gen1 is usually a good place to start. No need to change anything now, but make a mental note that you may need to come back and play around a bit if all of your GPUs don’t show up in the OS later.

Step 2: Configure automatic login
If you’re building a dedicated mining rig, then you probably want your mining rig to boot up and start mining automatically, without any user intervention. We’ll need to enable auto-login for that to be possible.
Right-click on the Start Menu and select “Run”. Type “netplwiz” (without the quotes) at the prompt, and click “ok”.
Uncheck the box that says “Users must enter a user name and password to use this computer”.
Click “Apply”. You’ll be prompted to enter your password to confirm the change.

Step 3: Configure your miner to start automatically
We want our rig to automatically start mining whenever it’s powered on or rebooted. That way, we keep mining losses to a minimum whenever a power outage occurs, and we don’t have to worry about manually starting it back up in other situations.
Open Windows Explorer and navigate to the folder where you created “mine.bat” in the previous step.
Right-click on your mine.bat file, and pick “Copy”.
Now, navigate to %AppData%\Microsoft\Windows\Start Menu\Programs\Startup (should be something like C:\Users\[YOUR WINDOWS USERNAME]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup).
Right-click anywhere on the empty background of the Startup folder and select “Paste shortcut”.
You should see a shortcut to your mine.bat file appear in the startup folder. Windows should automatically execute it upon bootup.

Conclusion
Personal experiences might differ, but with those settings a Vega 56 rig could run 24/7 without hashrate drops and very stable, which is the point, at an average of 1940H/s or so.

This is all so unnecessary. I have now setup 3 Vega 64/56 rigs in the past month (16 Vega cards all different manufactures) and not one of them needs this crap script. If you do the reg mod/soft power play tables its beyond me why you need overdriven? Set the fan speed and temps in wattman and you are done. The rigs run 24/7 with no problems. If you need a script like this just understand that you are doing it wrong. The pools will hate the constant disconnect reconnect as they work to establish diff levels.


This kind a stuff just makes me laugh!


  

well, it works for me, because I set it every hour or (currently) two and the disconnect takes less than 3 seconds. How do you apply the soft power play table? I downloaded a registry (.reg) file but it doesn't add anything to the registry file. I am working in a 6 Vega 56 rig, the Vegas are unmodded 'cos they arent mine.

Also I fear not double checking the temperatures so I use OverdriveNTool thus the Vegas "recall" the correct settings because of my experience with one achieving 83º and having the fan spinning at just 1400-1500rpm, for whatever reason

Bios Flash
https://www.youtube.com/watch?v=yM2qKc1qXiM

Power Play Tables
https://www.youtube.com/watch?v=cdfjSVE5fvE&t=1s

[commonorx]

https://s14.postimg.org/agmftrsw1/Untitled.png

I am currently into a 2 hours restart cycle and as things get more and more stable like they've been for the last 24 hours ever since I made it fully stable, I am going to increase the timer to 4 or more hours --the restart takes 3 seconds, 2 to remove Cast XMR process, 1 to set up OverdriveNTool options and restart Cast XMR.

Average hashrate for the last 6 hours have been 11,544.1 H/s, not bad for a 6 Vega 56 rig running at 935MHz. Temps are fine, too.

I have 5 Vega 56 running at 9950 H/s. Flashed Vega 64 bios and power play tables.

[Cyan_Antares]

Bios Flash
https://www.youtube.com/watch?v=yM2qKc1qXiM

Power Play Tables
https://www.youtube.com/watch?v=cdfjSVE5fvE&t=1s

ah ok, thanks! I know that guy but hadn't seen the Vega bios mod video you shared. As I said, the Vegas aren't mine and that's the step I am most fearful to take, so I am going to talk to the owner of the rig and see what happens. Things are running fully stable now, although I am curious about power consumption. cheers!

[underdog13]

New version 8 works with my rx 4 and 5 mess. Now I can try clock them some ....THANK YOU SO MUCH AND MERRY CHRISTMAS!

[AlexanderDumas]

https://s14.postimg.org/agmftrsw1/Untitled.png

I am currently into a 2 hours restart cycle and as things get more and more stable like they've been for the last 24 hours ever since I made it fully stable, I am going to increase the timer to 4 or more hours --the restart takes 3 seconds, 2 to remove Cast XMR process, 1 to set up OverdriveNTool options and restart Cast XMR.

Average hashrate for the last 6 hours have been 11,544.1 H/s, not bad for a 6 Vega 56 rig running at 935MHz. Temps are fine, too.

I have 5 Vega 56 running at 9950 H/s. Flashed Vega 64 bios and power play tables.

Do you get those Hs rates for a prolonged period of time, or just for a few minutes?
to state that a card Hs at XXX it should average the rate for at least 6 hours.   
Would you be so kind to share OverdriveNT settings and which power table are you using?

I also have 3 of Vega 56 with Bios 64 and a "real" Vega 64, but they get shy of 1950Hs each.
Sometime they shoot 1 or 2 lines at 2300 Hs but that does not count.

Thank you!

[commonorx]

https://s14.postimg.org/agmftrsw1/Untitled.png

I am currently into a 2 hours restart cycle and as things get more and more stable like they've been for the last 24 hours ever since I made it fully stable, I am going to increase the timer to 4 or more hours --the restart takes 3 seconds, 2 to remove Cast XMR process, 1 to set up OverdriveNTool options and restart Cast XMR.

Average hashrate for the last 6 hours have been 11,544.1 H/s, not bad for a 6 Vega 56 rig running at 935MHz. Temps are fine, too.

I have 5 Vega 56 running at 9950 H/s. Flashed Vega 64 bios and power play tables.

Do you get those Hs rates for a prolonged period of time, or just for a few minutes?
to state that a card Hs at XXX it should average the rate for at least 6 hours.   
Would you be so kind to share OverdriveNT settings and which power table are you using?

I also have 3 of Vega 56 with Bios 64 and a "real" Vega 64, but they get shy of 1950Hs each.
Sometime they shoot 1 or 2 lines at 2300 Hs but that does not count.

Thank you!

1. I get the hash rate as long as I have CAST XMR running which is 24/7. I look at the miners about once a day. The only time the hash rate goes down is if I lose connection or turn it off.
2. I don't use OverdriveN tool i use wattman to set the fan speed and target/max temps
3. In the thread above I posted links to youtube that you can follow.
4. HBM 1100Mhz, SOC 1200Mhz, Mem power 900mv

My 6 card Vega 64 rig gets an average of 11,970 hash rate 24/7

I have posted many times on here about all that needs to be done to achieve consistent has rates. You can get the power play tables from the video here

Power Play Tables
https://www.youtube.com/watch?v=cdfjSVE5fvE&t=1s
 

[QuintLeo]

Just a quick question, is there a specific Vega 64 that i should look out for or are they pretty much the same?

 The reference cards should all be the same, as the guts are entirely provided by AMD.

 Aftermarket cards will vary a LOT though - like that Sapphire Nitro+ model with the INSANE 3 power connector setup.


 My single STOCK Vega 56 gets 1940-1950 consistantly long-term, I've not bothered playing with the BIOS as I'm not sure how long it's going to be pointed at Monero mining and it doesn't NEED a modded BIOS for it's later "long-term" home.

[TheRealSelector]

I really wanted to use this miner but it has a flaw… I’ve been using it for the past 3 weeks and I’ve been getting 10% submission errors… For now the XMR Stak is more stable for me with only 0.02% submission errors…

I’ve even tried using the —fastswitch feature but that lowers my hash rate by almost 200H\s per card… Plus, this one is 2% dev donation as opposed to Stak which is 1% and more stable…

[Sgsg666]

I really wanted to use this miner but it has a flaw… I’ve been using it for the past 3 weeks and I’ve been getting 10% submission errors… For now the XMR Stak is more stable for me with only 0.02% submission errors…

I’ve even tried using the —fastswitch feature but that lowers my hash rate by almost 200H\s per card… Plus, this one is 2% dev donation as opposed to Stak which is 1% and more stable…

Youre not the only one circusdad also got those error reports. I might have to try this for a week and see which miner is stable.

[Cyan_Antares]

My single STOCK Vega 56 gets 1940-1950 consistantly long-term, I've not bothered playing with the BIOS as I'm not sure how long it's going to be pointed at Monero mining and it doesn't NEED a modded BIOS for it's later "long-term" home.

more or less the same here. I cannot bother changing the BIOS, after talking about it, so I use OverdriveNTool with the settings I shared before, and it is incredibly stable now, both the program and the cards can be the entire day working at full speed, except if I get an internet connection error. Average hashrate of 6 Vega 56 is 11500H/s approx.

I really wanted to use this miner but it has a flaw… I’ve been using it for the past 3 weeks and I’ve been getting 10% submission errors… For now the XMR Stak is more stable for me with only 0.02% submission errors…

I’ve even tried using the —fastswitch feature but that lowers my hash rate by almost 200H\s per card… Plus, this one is 2% dev donation as opposed to Stak which is 1% and more stable…

which settings do you use? What's the speed of your Vega (56 or 64?) cards?

From personal experience, this program is slightly faster, and also more sensitive to changes or it pushes the Vegas a little more. If you have Vega 56 cards try to set them at 935MHz or slightly below, mining speed should be around 1920-1950 H/s, which is pretty good and they are 100% stable.

I've shown the settings I use before and I am getting 0 errors every 2 hours. This is a screenshot after exactly 1 hour (59 minutes 20 seconds) of mining:

https://s14.postimg.org/gdrowawfl/Untitled4.png

[AlexanderDumas]

I really wanted to use this miner but it has a flaw… I’ve been using it for the past 3 weeks and I’ve been getting 10% submission errors… For now the XMR Stak is more stable for me with only 0.02% submission errors…

I’ve even tried using the —fastswitch feature but that lowers my hash rate by almost 200H\s per card… Plus, this one is 2% dev donation as opposed to Stak which is 1% and more stable…

I think it is the other way around.
Cast is 1.5% donation and STAK is 2%.

At least on my case, --fastswitch may have lowered the reporting of Hs rate on the miner window, but it has actually increased the rate on the pool monitor, which is what matter at the end, since it is how we get paid.

Now I have been getting 9000Hs for the last 24 hours, on 4 Vega and one 580, at 830w at the wall. Before I was getting 8400Hs maximum.
It tend to lower the Hs rate if it runs without auto restarting for more than 2 hours, but if i put it on 60/90 minutes cycles, it keeps the average at 9000hs for 24 hours.
On the miner screen it shows 8650Hs yet at the pool I get 9000Hs.
I cannot complain....

For the Vegas these are the settings:

I have set up the rig using most of Circus Daddy's Vega Mining guide

Blockchain drivers august 23

1 vega 64
3 vega 56  bios 64

Regedit Power table 1100Mhz

P6 1212   890
P7 1408   890

P3 1100  870

Power 0%
Max temp and Target temp at 75
Fans at 2800, 4900


Cast has also lifted Hs rate on another PC on which I run 2 of RX580 and Andrenalin drivers. It run steady at 1900/2000Hs on both XMR and ETN, without any crashing. before I was only reaching 1750Hs for both 580 cards.
On the miner screen it shows a combined Hs rate of 1664Hs for both cards, yet at the pool I get 2000Hs.

I finally got it to run reliably.
I hope you get better luck.

[Cyan_Antares]

I really wanted to use this miner but it has a flaw… I’ve been using it for the past 3 weeks and I’ve been getting 10% submission errors… For now the XMR Stak is more stable for me with only 0.02% submission errors…

I’ve even tried using the —fastswitch feature but that lowers my hash rate by almost 200H\s per card… Plus, this one is 2% dev donation as opposed to Stak which is 1% and more stable…

I think it is the other way around.
Cast is 1.5% donation and STAK is 2%.

At least on my case, --fastswitch may have lowered the reporting of Hs rate on the miner window, but it has actually increased the rate on the pool monitor, which is what matter at the end, since it is how we get paid.

Now I have been getting 9000Hs for the last 24 hours, on 4 Vega and one 580, at 830w at the wall. Before I was getting 8400Hs maximum.
It tend to lower the Hs rate if it runs without auto restarting for more than 2 hours, but if i put it on 60/90 minutes cycles, it keeps the average at 9000hs for 24 hours.
On the miner screen it shows 8650Hs yet at the pool I get 9000Hs.
I cannot complain....

For the Vegas these are the settings:

I have set up the rig using most of Circus Daddy's Vega Mining guide

Blockchain drivers august 23

1 vega 64
3 vega 56  bios 64

Regedit Power table 1100Mhz

P6 1212   890
P7 1408   890

P3 1100  870

Power 0%
Max temp and Target temp at 75
Fans at 2800, 4900


Cast has also lifted Hs rate on another PC on which I run 2 of RX580 and Andrenalin drivers. It run steady at 1900/2000Hs on both XMR and ETN, without any crashing. before I was only reaching 1750Hs for both 580 cards.
On the miner screen it shows a combined Hs rate of 1664Hs for both cards, yet at the pool I get 2000Hs.

I finally got it to run reliably.
I hope you get better luck.

fastswitch sounds interesting, although I never used it, I gotta give it a try if I ever see errors. I have the cards running 100% stable now at the OverdriveNTool settings below, and to give you and idea, I get 480 shares with 0 errors every 1 hour 27 minutes (not a very orthodox number but that's the number that comes to my mind now). This is my OverdriveNTool.ini file (dont like AMD Settings utility much, both in the Vega rig and in my desktop computer with a RX 570):

[Profile_0]
Name=Vega56
GPU_P0=852;900
GPU_P1=991;900
GPU_P2=1084;900
GPU_P3=1138;900
GPU_P4=1150;900
GPU_P5=1202;900
GPU_P6=1212;905
GPU_P7=1407;935
Mem_P0=167;900
Mem_P1=500;900
Mem_P2=800;900
Mem_P3=935;900

I restart the miner and OverdriveNTool every 4 hours, for security reasons (the overall process takes 3 seconds. AMD drivers seem to sometimes forget the Vega 56 settings, whatever the reason, happened to me once or twice, and it's not fun, 'cos one of the Vegas can get really hot and the fan spins at slower speed than the minimum you've set.

[Cyan_Antares]

confirmed 662 shares 0 errors (2 hours) at 11600H/s average on 6 Vega 56 cards with these OverdriveNTool settings:

[Profile_0]
Name=Vega56
GPU_P0=852;900
GPU_P1=991;900
GPU_P2=1084;900
GPU_P3=1138;900
GPU_P4=1150;900
GPU_P5=1202;900
GPU_P6=1212;905
GPU_P7=1407;935
Mem_P0=167;900
Mem_P1=500;900
Mem_P2=800;900
Mem_P3=935;900

[TheRealSelector]

My single STOCK Vega 56 gets 1940-1950 consistantly long-term, I've not bothered playing with the BIOS as I'm not sure how long it's going to be pointed at Monero mining and it doesn't NEED a modded BIOS for it's later "long-term" home.

more or less the same here. I cannot bother changing the BIOS, after talking about it, so I use OverdriveNTool with the settings I shared before, and it is incredibly stable now, both the program and the cards can be the entire day working at full speed, except if I get an internet connection error. Average hashrate of 6 Vega 56 is 11500H/s approx.

I really wanted to use this miner but it has a flaw… I’ve been using it for the past 3 weeks and I’ve been getting 10% submission errors… For now the XMR Stak is more stable for me with only 0.02% submission errors…

I’ve even tried using the —fastswitch feature but that lowers my hash rate by almost 200H\s per card… Plus, this one is 2% dev donation as opposed to Stak which is 1% and more stable…

which settings do you use? What's the speed of your Vega (56 or 64?) cards?

From personal experience, this program is slightly faster, and also more sensitive to changes or it pushes the Vegas a little more. If you have Vega 56 cards try to set them at 935MHz or slightly below, mining speed should be around 1920-1950 H/s, which is pretty good and they are 100% stable.

I've shown the settings I use before and I am getting 0 errors every 2 hours. This is a screenshot after exactly 1 hour (59 minutes 20 seconds) of mining:

https://s14.postimg.org/gdrowawfl/Untitled4.png

I have 3 Vegas 64 on that specific rig, all have 1100Mhz power table.

GPU section:

State 6: 1212Mhz - 900mV
State 7: 1407Mhz - 905mV

Memory Section:

State 3: 1100Mhz - 900mV

https://imgur.com/a/fOnKZ

[Cyan_Antares]

My single STOCK Vega 56 gets 1940-1950 consistantly long-term, I've not bothered playing with the BIOS as I'm not sure how long it's going to be pointed at Monero mining and it doesn't NEED a modded BIOS for it's later "long-term" home.

more or less the same here. I cannot bother changing the BIOS, after talking about it, so I use OverdriveNTool with the settings I shared before, and it is incredibly stable now, both the program and the cards can be the entire day working at full speed, except if I get an internet connection error. Average hashrate of 6 Vega 56 is 11500H/s approx.

I really wanted to use this miner but it has a flaw… I’ve been using it for the past 3 weeks and I’ve been getting 10% submission errors… For now the XMR Stak is more stable for me with only 0.02% submission errors…

I’ve even tried using the —fastswitch feature but that lowers my hash rate by almost 200H\s per card… Plus, this one is 2% dev donation as opposed to Stak which is 1% and more stable…

which settings do you use? What's the speed of your Vega (56 or 64?) cards?

From personal experience, this program is slightly faster, and also more sensitive to changes or it pushes the Vegas a little more. If you have Vega 56 cards try to set them at 935MHz or slightly below, mining speed should be around 1920-1950 H/s, which is pretty good and they are 100% stable.

I've shown the settings I use before and I am getting 0 errors every 2 hours. This is a screenshot after exactly 1 hour (59 minutes 20 seconds) of mining:

https://s14.postimg.org/gdrowawfl/Untitled4.png

I have 3 Vegas 64 on that specific rig, all have 1100Mhz power table.

GPU section:

State 6: 1212Mhz - 900mV
State 7: 1407Mhz - 905mV

Memory Section:

State 3: 1100Mhz - 900mV

https://imgur.com/a/fOnKZ

nice numbers.. At which speed does XMR Kast mine?

I have no experience with the Vega 64, but for the looks of it, you might need to find the sweet spot for your Vega 64, MHz wise. Vega 56 sweet spot is around 930-935MHz, again, from personal experience, this might differ.

At anything above 940MHz, if I set a Vega as the main GPU, everything seems normal in your OS' desktop, but then after doing something as simple as using GPU-Z to check stats, screen artefacts start to show everywhere on the screen, like when you overclocked a card too much.

Using Cast XMR alone seems fine, though, your OS' desktop won't show artefacts and the cards will be running, BUT I got random hangs so I used a 10 minutes timer to restart Cast XMR and OnedriveNTool, and you get more errors. It's been 2 days the 6 Vega 56 rig is running stable and the difference is night and day, you can sleep well.

Also overclocking can lead to de-configuration of your card's settings, as if the card forget their own settings which you had set up at startup, and can get over 80º with the fan spinning at something like 1000rpm and be happy with it --this means the card can wear off and not last much.

[bostonvex]

My rigs would run fine for hours and then out of the blue Cast XMR hangs. I have JJs monitoring script running and because the values can be read from JSON it doesn't pick it up as a hang. Essentially the timestamp remains stagnant, bolded below, with no additional increments. Only solution is to force the Cast window closed and let the monitoring script restart the Cast cmd shell instance.

[16:36:35] GPU0 | 51°C | Fan 3245 RPM | 1913.2 H/s

I know I can modify the hash monitor script to do a check on the timestamp.

Anyone else seen this type of issue?


I have 2 rigs with the following config:
4GB Corsair RAM
ASUS Z270-a mobo
3 x Vega 56 stock bios, memclock at 920mhz for all

[amastronardi]

My rigs would run fine for hours and then out of the blue Cast XMR hangs. I have JJs monitoring script running and because the values can be read from JSON it doesn't pick it up as a hang. Essentially the timestamp remains stagnant, bolded below, with no additional increments. Only solution is to force the Cast window closed and let the monitoring script restart the Cast cmd shell instance.

[16:36:35] GPU0 | 51°C | Fan 3245 RPM | 1913.2 H/s

I know I can modify the hash monitor script to do a check on the timestamp.

Anyone else seen this type of issue?


I have 2 rigs with the following config:
4GB Corsair RAM
ASUS Z270-a mobo
3 x Vega 56 stock bios, memclock at 920mhz for all

Yes, it happens to me too. For what I read, Asus Z270-a is not the best mobo to run Vegas. I'm changing it tomorrow. Will let you know if it get more stable.