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

[Cyan_Antares]

Is anyone using JJ's batch file to automate disable/enable (powershell), apply overdrive and commence mining?

I have a problem where windows will sometimes boot with 2 vega showing, sometimes with 3 and sometimes with 4.
I want to modify JJ's batch file (which automatically runs) to check how many Vega are detected, and reboot if not 4.

that sounds strange. Once the drivers are installed /blockchain, I mean/ all the Vegas are enabled and detected by default.

http://vega.miningguides.com/

I'd follow the guide above to uninstall the drivers cleanly and it takes a couple of minutes with DDU Uninstaller. I've experienced issues like risers giving me a hard time, but once the gpus were detected during the drivers installation they were never disabled or undetected by the OS.

It doesn't take much and might be worth it. If you have an SSD restarting and so on isn-t an issue.

[martyroz]

that sounds strange. Once the drivers are installed /blockchain, I mean/ all the Vegas are enabled and detected by default.

http://vega.miningguides.com/

I'd follow the guide above to uninstall the drivers cleanly and it takes a couple of minutes with DDU Uninstaller. I've experienced issues like risers giving me a hard time, but once the gpus were detected during the drivers installation they were never disabled or undetected by the OS.

It doesn't take much and might be worth it. If you have an SSD restarting and so on isn-t an issue.

When I first installed the blockchain drivers, 4 cards were present. So it worked on all.

The next reboot, I have 3 cards detected by Windows. I change nothing and reboot again, 4 cards appear and I can mine.

It is random between 2 and 4 cards detected by windows each boot. I am not complaining because I can quickly restart until it has found four cards, but in terms of automated recovery from a shutdown, it is hard to get right

[hariinfo]

I get errors with 6 RX 580 GPUs
Seems to work fine for 4 GPUs

cl_mem_object_allocation_failure

[Cyan_Antares]

I get errors with 6 RX 580 GPUs
Seems to work fine for 4 GPUs

cl_mem_object_allocation_failure

You ran out of memory. increase the size of virtual memory in Windows. you can see how in the guide below. For instance, say you have 6 Vega GPUs, they have 8 GB of mem each, so you multiply 8x6 equals 48. So you set virtual memory in Windows to 48000MB.

http://vega.miningguides.com/

that sounds strange. Once the drivers are installed /blockchain, I mean/ all the Vegas are enabled and detected by default.

http://vega.miningguides.com/

I'd follow the guide above to uninstall the drivers cleanly and it takes a couple of minutes with DDU Uninstaller. I've experienced issues like risers giving me a hard time, but once the gpus were detected during the drivers installation they were never disabled or undetected by the OS.

It doesn't take much and might be worth it. If you have an SSD restarting and so on isn-t an issue.

When I first installed the blockchain drivers, 4 cards were present. So it worked on all.

The next reboot, I have 3 cards detected by Windows. I change nothing and reboot again, 4 cards appear and I can mine.

It is random between 2 and 4 cards detected by windows each boot. I am not complaining because I can quickly restart until it has found four cards, but in terms of automated recovery from a shutdown, it is hard to get right

I think it would be worth it to uninstall the drivers with DDU Uninstaller and see if Windows detect them all again.

Btw, based on the bat by FgTeamBr I managed to not only restart the miner but also devcon and overdrivenTool settings. Some random hash rate drops or strange behaviour from the gpu1 were driving me nuts

[hariinfo]

I get errors with 6 RX 580 GPUs
Seems to work fine for 4 GPUs

cl_mem_object_allocation_failure

You ran out of memory. increase the size of virtual memory in Windows. you can see how in the guide below. For instance, say you have 6 Vega GPUs, they have 8 GB of mem each, so you multiply 8x6 equals 48. So you set virtual memory in Windows to 48000MB.

http://vega.miningguides.com/

Thanks, that fixed the issue

[gaalx01]

Miner -  Cast_XMR is only suitable for Vega or for other Reds too?

[DuxBellorum]

thanks for your miner software !
perf with rx580: 950h/s

[gaalx01]

thanks for your miner software !
perf with rx580: 950h/s

with what parameters?

[STT]

How do Ardenalin drivers work if you use them on a setup that has rx570 rx 580 and Vega included?

Any expirience with that?

Dont update past the blockchain drivers which is 17.11.1    Only they give priority to compute functions and the others are for gaming, if the latest release somehow can switch between gaming and compute priority then great but Ive not seen this so far.
Here is AMD people interviewed on a video reviewing most of the Adrenalin features, they are all about UI pretty much for mainstream use: https://www.youtube.com/watch?v=WjNPNMUeBY8&t=1497s

I've tried with memory clock near 1200mhz and it doesnt make up for the blockchain drivers advantage, but others might have made better progress.  Its only about 7.7% difference at best

[zachosan]

Ok, planning to support multiple GPU per instance. Personally found that running on instance per GPU very stable and more flexible, but there seem some reports that it does influence the other GPUs. Should be no big deal to implement.
Which kind of API would you suggest? Is there an standard?

Hello! I use 0.8 version cast-xmr miner with 5* his rx580 4gb (hynix+elpida) on windows 10. It shows 850 h/s per each, thats very good. But there is an issue with my system, sometimes (10 minutes from run or more) it stops show hashrates until i hit S button. When i hit S button it rapidly scroll and continue work, but all shares from that time are rejected by pool as obsolete.

I made a crutch: wrote autohotkey script which sends "S" key to miner's window every 60 seconds, but it's very inconvenient, i cannot make it to autostartup etc....

Could you make an update with new parameter to show statistics ("s" key pressed) every period of time?

[errata]

Ok, planning to support multiple GPU per instance. Personally found that running on instance per GPU very stable and more flexible, but there seem some reports that it does influence the other GPUs. Should be no big deal to implement.
Which kind of API would you suggest? Is there an standard?

Hello! I use 0.8 version cast-xmr miner with 5* his rx580 4gb (hynix+elpida) on windows 10. It shows 850 h/s per each, thats very good. But there is an issue with my system, sometimes (10 minutes from run or more) it stops show hashrates until i hit S button. When i hit S button it rapidly scroll and continue work, but all shares from that time are rejected by pool as obsolete.

I made a crutch: wrote autohotkey script which sends "S" key to miner's window every 60 seconds, but it's very inconvenient, i cannot make it to autostartup etc....

Could you make an update with new parameter to show statistics ("s" key pressed) every period of time?

In a command prompt window, if you click with your mouse anywhere within it, while window is in focus, the output will stop auto-scrolling. Your cursor should also change to white rectangle like this:
https://ibb.co/hiQEpm

If this is the case, then you should just press Enter (or whichever button actually) which will enable the auto-scrolling of the output once again.

If this solves your issue, then simply take care to always press Enter in the end if you are doing something in your miner's window (e.g. manually scrolling, selecting some text or whatever).

[zachosan]

Hello! I use 0.8 version cast-xmr miner with 5* his rx580 4gb (hynix+elpida) on windows 10. It shows 850 h/s per each, thats very good. But there is an issue with my system, sometimes (10 minutes from run or more) it stops show hashrates until i hit S button. When i hit S button it rapidly scroll and continue work, but all shares from that time are rejected by pool as obsolete.

I made a crutch: wrote autohotkey script which sends "S" key to miner's window every 60 seconds, but it's very inconvenient, i cannot make it to autostartup etc....

Could you make an update with new parameter to show statistics ("s" key pressed) every period of time?

In a command prompt window, if you click with your mouse anywhere within it, while window is in focus, the output will stop auto-scrolling. Your cursor should also change to white rectangle like this:
https://ibb.co/hiQEpm

If this is the case, then you should just press Enter (or whichever button actually) which will enable the auto-scrolling of the output once again.

If this solves your issue, then simply take care to always press Enter in the end if you are doing something in your miner's window (e.g. manually scrolling, selecting some text or whatever).

It's not my case: i leave cursor in normal form, miner works and shows hashrate with scroll. When I return after some time, cursor is normal, scroolling freezes. I hit S - miner backs to mining, but all shares are rejected. I think "S" procedure re-initilialize something which cause miner to freeze in my case.

[Chaser187]

Does this work with the new AMD Adrenalin driver?
Regarding that there should be a compute option in that driver.
Is the speed with that driver the same with the blockchain driver?
Would be interesting who are gaming and mining on the same pc.

[DMKmod]

Does --forcecompute option works with Adrenaline drivers and Vegas?

[naazz]

Hi,
I have a strange problem. Im getting really good perf. But sometime it just stop mining nothing appear in the console until i hit a enter or any key and it start back. Last time i notice it he wasnt sending hashes for like 8 minutes.
Any idea what could cause that?

Mining with 3 rx 580 8gb + 4gb ram.

[Morgon]

But sometime it just stop mining nothing appear in the console until i hit a enter or any key and it start back.

This typically occurs when you have your Windows Command Prompt windows enabled for 'Quick Edit', and you click the mouse inside the window to focus; but this tells the Command Prompt window that you want to quick copy content.

To fix: While the miner is running, click the Command Prompt icon, go to Properties, and unselect Quick Edit. Then go back to that menu, select Defaults, and uncheck it there so future windows apply this setting.

[huntingthesnark]

if you want to restart miner x time due hash drop here is simple script .
my miner restart every 30 min
Ps don't close script terminal.
creat bat file and put this.
Edit set commandline and set u config

Code:

@echo off

echo -------------------------------------------------------------------
echo Restart Cast miner every 30 min
echo -------------------------------------------------------------------
echo:

set executable=cast_xmr-vega.exe
set commandline= -S youpoolhere -u youwallet here and others cmd from you bat file. %* --fastjobswitch --forcecompute
set runforseconds=1800
set restartinseconds=2
set /a counter=0
timeout 2
:start
start "cast_xmr-vega" %executable% %commandline%
echo:
echo The software will run for %runforseconds% seconds
timeout %runforseconds%
taskkill /f /im %executable%
echo:
echo Restarting the software in %restartinseconds% seconds (%counter%)
timeout %restartinseconds%
set /a counter+=1
echo:
echo:
goto start

Thanks!! That is awesome stuff. Ever since I plugged 6 Vega either the drivers or the program are less stable and have to restart things over with a bat file, which I use, but it is manual and different than this one. How could your bat file be done to have onedrivetool and devcon.exe settings included too?  

I really want to switch the drivers to the new Adrenalin ones... but it seems like the hash rate is quite slower for Vega 56

here is script to restart video cards , start overdrive and start mining.
juts copy,creat new bat file and edit.
SET MinerOpts -S xmr-eu.dwarfpool.com:9100 -u .... etc
SET VidTool1= OverdriveNTool.exe -r0 -p0Vega56 -r0 -p1Vega56 ... etc
set runforseconds=1800 secs to restart , 30 min default.

sorry but bitcointalk does not let me post the complete script in the code

Credits @TheJerichoJones


http://fgteambr.esy.es/start.txt

Dumb question: I'm already using the excellent @TheJerichoJones script to restart video cards , start overdrive and start mining.

Works brilliantly, just currently needs restarting every hour or so. Would this bat be tweakable to run JJ's script, rather than the miner? (EDIT: using the script from your link seems to work! Testing now - Thanks!)

[zachosan]

Hi,
I have a strange problem. Im getting really good perf. But sometime it just stop mining nothing appear in the console until i hit a enter or any key and it start back. Last time i notice it he wasnt sending hashes for like 8 minutes.
Any idea what could cause that?

Mining with 3 rx 580 8gb + 4gb ram.

Hi I had a same issue! I made a script for autohotkey to send every minute S key to miner's window and fixed it, but it's very inconvenient!! I am no alone I think developer should make an update.

[wolverine5pl]

worst case just stick a hdmi dummy plug if you have one laying around, maybe that can help you.  Seriously though, i've never had this bug that hashrate goes down.  rock solid for me, but temps are low and I am not too greedy with the hashrate vs power consumption

It seems that if I have team viewer session on, it keeps the hash rate from dropping

I have same problem. after reboot my hashrate dropes. so what i do:
windows starts i restart cards with devcon x3 , yes THREE TIMES
if i do it once hashrate will drop. after 3 times hashrate stays .

[commonorx]

if you want to restart miner x time due hash drop here is simple script .
my miner restart every 30 min
Ps don't close script terminal.
creat bat file and put this.
Edit set commandline and set u config

Code:

@echo off

echo -------------------------------------------------------------------
echo Restart Cast miner every 30 min
echo -------------------------------------------------------------------
echo:

set executable=cast_xmr-vega.exe
set commandline= -S youpoolhere -u youwallet here and others cmd from you bat file. %* --fastjobswitch --forcecompute
set runforseconds=1800
set restartinseconds=2
set /a counter=0
timeout 2
:start
start "cast_xmr-vega" %executable% %commandline%
echo:
echo The software will run for %runforseconds% seconds
timeout %runforseconds%
taskkill /f /im %executable%
echo:
echo Restarting the software in %restartinseconds% seconds (%counter%)
timeout %restartinseconds%
set /a counter+=1
echo:
echo:
goto start

Thanks!! That is awesome stuff. Ever since I plugged 6 Vega either the drivers or the program are less stable and have to restart things over with a bat file, which I use, but it is manual and different than this one. How could your bat file be done to have onedrivetool and devcon.exe settings included too?  

I really want to switch the drivers to the new Adrenalin ones... but it seems like the hash rate is quite slower for Vega 56

here is script to restart video cards , start overdrive and start mining.
juts copy,creat new bat file and edit.
SET MinerOpts -S xmr-eu.dwarfpool.com:9100 -u .... etc
SET VidTool1= OverdriveNTool.exe -r0 -p0Vega56 -r0 -p1Vega56 ... etc
set runforseconds=1800 secs to restart , 30 min default.

sorry but bitcointalk does not let me post the complete script in the code

Credits @TheJerichoJones


http://fgteambr.esy.es/start.txt

Nice band-aid. What a waste of time though. You are better to figure out why the hash rate drops.

I have noticed that the hash rate drops in the following instances

1. Windows is not set to "Never Turn Monitor off" on the power settings
2. Making sure that windows never shuts off the HDD or SDD "Always on" in power settings
3. Locking the computer or sending it to the lock screen (drops hash rate instantly) Keep the computer logged in on the desktop!
4. If you can't leave a monitor hooked up to it (tuned off) then find a dummy plug.
5. Using remote desktop and logging off ( Sends computer to lock screen) Even team viewer can cause problems.
6. In some cases running miners on different pools (running multiple instances of CAST) can cause the has rate to drop, meaning its best to use a single instance and point them all at the same pool. Results differ per miner.
7. Using the onboard GPU or iGPU is recommended. Plugging displays into the VEGA mining cards directly is not really recommend but works fine for some. Find another GPU to plugin if you don't have onboard to use as a last resort.
8. Try not to mix cards, as this can cause problems as well unless you really know what you are doing.
9. For 6 Vegas you should have at a minimum of at least 49452 Virtual Memory specified in Windows. A 120GB SSD is fine and so is 4GB of ram to accomplish this, just make sure you have enough space on the drive to do this. Increase by 8GB for each additional card. Windows may display this in MB but it's fine. The math is as follows 1024*(number of vegas)*(8 megabytes/gigabytes - whatever windows)+ (300 for overhead) = 49452
You can probably get away with less but it works so who cares.
10. Boot into safe mode to remove AMD drivers using DDU or even the AMD driver removal tool.
11. Install [Suspicious link removed]pute drivers for VEGA! in normal Windows(not safe mode) Don't install anything you don't need.. like ReLive or Problem report tool... (many different opinions about Wattman. I use it and have no issues)
12. Keep your mining rig configuration simple and focused as possible and you will have few issues.
13. Device manager disable and re-enable VEGA's after every reboot before you start to mine.

Shutting down the miner all the time is a waste of time and money. Spend the time to figure out what is wrong by testing out your rig and finding out what works before using a band aid solution that is not great for mining.