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

[vessk0]

Does that mean that we can now run more than 4 cards in one rig?
I thought the Blockchain driver is limiting us to only 4 ?!

[1714327603]

1714327603

[1714327603]

1714327603

[1714327603]

1714327603

[1714327603]

1714327603

[1714327603]

1714327603

[jim1211]

Dear all

Im running on 4 64vega and i couldnt mange to get more than 1500hash for my other 3 cards. this is my conf cast_xmr-vega -G 0,1,2,3 -S xmr-asia1.nanopool.org:14444 -u 42MfZppKJUHQxxxxxxxxx.MiningRig1 -p x

Core Frequency: -10%
Memory Clock: 1025 MHz
Power Limit: -23%

Running 23Aug Blockchain Driver
Win10 64

Any help guys,tried the HBCC method but wont do the trick. Another thing there is no toggle on my HBCC Memory Segment beside Enable and Disable Switch, is that normal?

https://imgur.com/KNihmg4

[billhinge]

Doing OK after 30 min on latest code averaging 2123

6:09:07] Shares: 132 Accepted, 0 Errors | Hash Rate Avg: 2123.6 H/s | Avg Search Time: 14.7 sec
[16:09:07] GPU0 | 66°C | Fan 3395 RPM | 2127.4 H/s
[16:09:12] GPU0 | 65°C | Fan 3395 RPM | 2119.5 H/s
[16:09:12] GPU0 Found Nonce, submitting...
[16:09:12] Share Accepted -> +1
[16:09:12] Shares: 133 Accepted, 0 Errors | Hash Rate Avg: 2123.6 H/s | Avg Search Time: 14.7 sec
[16:09:17] GPU0 | 65°C | Fan 3395 RPM | 2126.2 H/s
[16:09:18] GPU0 Found Nonce, submitting...
[16:09:19] Share Accepted -> +1
[16:09:19] Shares: 134 Accepted, 0 Errors | Hash Rate Avg: 2123.6 H/s | Avg Search Time: 14.6 sec
[16:09:22] GPU0 | 65°C | Fan 3396 RPM | 2122.8 H/s

[Pool: 'xmrpool.eu:5555' | Connected: 2017-12-02 15:36:42]
  0:32:42 (100%) Online
  0:00:00 (  0%) Offline

[Job: #19 | Difficulty: 30000 | Running: 21.0 sec | Avg Job Time: 107.8 sec]

[Hash Rate Avg: 2123.6 H/s]

[Shares Found: 138 | Avg Search Time: 14.6 sec]
 134 ( 97%) Accepted
   0 (  0%) Rejected by pool
   0 (  0%) Invalid result computation failed
   0 (  0%) Could not be submit because of network error
   4 (  3%) Outdated because of job change

[16:09:27] GPU0 | 65°C | Fan 3395 RPM | 2127.0 H/s
[16:09:32] GPU0 | 65°C | Fan 3423 RPM | 2119.9 H/s

[R0mi]

Getting SOCKET ERROR - Job Error: invalid target: 00000000
Any ideas?
Haven't set any parameters (apart from pool address, wallet and password)...


EDIT: trying on a bone stock Vega56

You usually also need to set (as a parameter) "-O" for --opencl and then argument ("0" or "1" or "2"), so -O 1 for example.  Put that after cast_xmr-vega in your .bat file

Also, if you have more than one card, you need to set "-G" and put in cards, so if I have 4 Vegas, "-G 0,1,2,3"

[Chaser187]

"[Suspicious link removed]pute Driver NOT detected."

Is there any other way to restart the driver without reinstallation?
Because this hbcc method doesnt work. Iam only getting 900 H/s right now. :-(

Plz help

[xeridea]

P.S. Is there any analog of nvidia-smi for AMD?

overdriventool can be called via command line to set clocks, volts, fans, etc, but can't query information.

It's sad. I need go query info, as it seems that it is the only way to make vega's work most of the time.

Why do you need to query information? I just set clocks via ODT from a batch file, I don't have any problems. And another that uses devcon to fix driver bug.

[xeridea]

"[Suspicious link removed]pute Driver NOT detected."

Is there any other way to restart the driver without reinstallation?
Because this hbcc method doesnt work. Iam only getting 900 H/s right now. :-(

Plz help

Go to device manager, disable then enable all the cards, waiting a few seconds between. You can also search this forum for devcon method, you can do it via a batch file with command   devcon.exe restart PCI*DEV_687F

[Chipychop]

hey guys, one noob question about receive nicehash payments

Nicehash always pay me on friday, so if today I change the adress for recieving payments, they will pay all on the new adress provided or they will pay some amount to first adress and the rest on the new??

Thanks!!

[R0mi]

has anyone tried butchering jj's hashmonitor powershell script to monitor castxmr now that it has an API?

i would but my programming leaves a lot to be desired....

I posted this on another thread and also helping some redditor, but you can try this:

I have modified the script slightly to work with 1 of my Vega card. You can modified it accordingly to fit your rig.

Download link below:
https://drive.google.com/open?id=0B2XFJ__I0jzLWlBZMTVCMWZDZ3YwRDZiRkh6cldKWnc1Wjlz

Some changes I made:

If you are executing the run_HashMonitor.cmd, make sure you change the file name in it accordingly to reflect CastXMR_HashMonitor_v2.6.ps1 (Or any name that you saved as).
Notable change I have made in this ps script includes:
Line 168 - 172 : I am using the script to call Cast-XMR directly, and Line 169 is the usual config including my wallet address, mining pool etc (the usual you put in a .bat) & also --remoteaccess in this case. Line 170 - 172 is to assign the localhost & port accordingly (7777)
Line 187: The main address for local/remote monitoring
Line 191 - 201: I didn't use $hdiff variable, but make a new variable for min Vega Hashrate before restart $global:vegahash @ line 201 (multiply by 1,000 since the reported value in the web is in actual hash rate)
Line 392 - 397 : Initial Vega hashrate for comparison (Not really needed since we have a reset trigger down below, but it's the same as the next)
Line 476 - 479 : Vega hashrate used for monitoring in order for restart.
Line 483 - 484 : Nothing major, just changing monitoring from 1 minute to every 30 secs
7: Line 486 : Most important part, condition to restart (Here to check my Vega hashrate against my preset target -> ~1.75kH/s @ Line 201)
This should set you up in the right direction to start with;
Do take note that I am running only 1 Vega to check against, hence I can use the total_hash_rate for comparison; if you are running multiple Vegas rig, you might need to divide it by number of GPU instances before you make the comparison. Alternatively is to loop through the "devices" in the hashrate report JSON to check if any of them drop, but I find total_hash_rate to be easier. You can also use total_hash_rate_avg in the report, as current total_hash_rate might be too sensitive for occasional dip.
And remember to change the CMDLine in Line 169, or else you would be mining to my wallet instead.
Let me know if you have any further question. I will try my best to help set up.

thanks! i'll get on this (probably next week)

StellarX88, Thank you!!!

It's working! Sweet!

Okay, when running multiple Vega's, your start up lines for Cast might look like this:

$global:CAST_XMRexe = "cast_xmr-vega.exe"   # The miner. Expects to be in same folder as this script
$global:CAST_XMRcmdline = "-S mine.xmrpool.net:7777 -u [Your_Wallet_Address].[Your_Rig_Name] -p x -O 1 -G 0,1,2,3,4 -I 8 -R"  #"Cast_XMRcmdline = values you had put into your .bat file, with some reordering

I moved the --opencl to the end (the "-O 1" is my opencl value) -O is the same thing as earlier "--opencl"
The "-G" command I also moved to the end.
"-R" works, is equivalent to, --remoteaccess but for some reason using "--remoteaccess" did not work.  But "-R" does !

Vid tools is where you put your OverDriveNTool profiles to apply:

#### Vid Tool 1
$vidTool += 'OverdriveNTool.exe -r0 -r1 -r2 -r3 -r5 -p0Vega -p1Vega -p2Vega -p3Vega -p5Vega'   #-r4 is an Nvidia card, that is why "4" is skipped over here
                              # Expects to be in same folder as this script
                              # Delete or REMARK if you don't want use it
#### Vid Tool 2
$vidTool += 'regedit.exe /S 000.reg'   # Expects to be in same folder as this script               #from Kekso on Reddit, if you want to try this, move a copy of RegEdit into your Cast folder. These are my SoftPowerPlay mods.
                               # Delete or REMARK if you don't want use it
#### Vid Tool 3
$vidTool += 'regedit.exe /S 001.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it
#### Vid Tool 4
$vidTool += 'regedit.exe /S 002.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it
#### Vid Tool 5
$vidTool += 'regedit.exe /S 003.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it
#### Vid Tool 6
$vidTool += 'regedit.exe /S 004.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it   
#### Vid Tool 7
$vidTool += 'regedit.exe /S 005.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it   
#### Vid Tool 8
$vidTool += 'regedit.exe /S 006.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it   
##### End VidTools
$global:Url = "http://$CAST_XMRIP`:$CAST_XMRPort" # <-- DO NOT CHANGE THIS !!

Nice!  So happy to have auto-restart if Hash rate drops.

[QuintLeo]

P.S. Is there any analog of nvidia-smi for AMD?

 Not as such, though up to the 15.12 drivers you could do most of the same stuff using amd-config commands - but no "dashboard" display like the nvidia-smi -l command.

[QuintLeo]

Whatever addresss your miner was pointed at while mining to the nicehash pool is the address that will get that payment.

[R0mi]

has anyone tried butchering jj's hashmonitor powershell script to monitor castxmr now that it has an API?

i would but my programming leaves a lot to be desired....

I posted this on another thread and also helping some redditor, but you can try this:

I have modified the script slightly to work with 1 of my Vega card. You can modified it accordingly to fit your rig.

Download link below:
https://drive.google.com/open?id=0B2XFJ__I0jzLWlBZMTVCMWZDZ3YwRDZiRkh6cldKWnc1Wjlz

Some changes I made:

If you are executing the run_HashMonitor.cmd, make sure you change the file name in it accordingly to reflect CastXMR_HashMonitor_v2.6.ps1 (Or any name that you saved as).
Notable change I have made in this ps script includes:
Line 168 - 172 : I am using the script to call Cast-XMR directly, and Line 169 is the usual config including my wallet address, mining pool etc (the usual you put in a .bat) & also --remoteaccess in this case. Line 170 - 172 is to assign the localhost & port accordingly (7777)
Line 187: The main address for local/remote monitoring
Line 191 - 201: I didn't use $hdiff variable, but make a new variable for min Vega Hashrate before restart $global:vegahash @ line 201 (multiply by 1,000 since the reported value in the web is in actual hash rate)
Line 392 - 397 : Initial Vega hashrate for comparison (Not really needed since we have a reset trigger down below, but it's the same as the next)
Line 476 - 479 : Vega hashrate used for monitoring in order for restart.
Line 483 - 484 : Nothing major, just changing monitoring from 1 minute to every 30 secs
7: Line 486 : Most important part, condition to restart (Here to check my Vega hashrate against my preset target -> ~1.75kH/s @ Line 201)
This should set you up in the right direction to start with;
Do take note that I am running only 1 Vega to check against, hence I can use the total_hash_rate for comparison; if you are running multiple Vegas rig, you might need to divide it by number of GPU instances before you make the comparison. Alternatively is to loop through the "devices" in the hashrate report JSON to check if any of them drop, but I find total_hash_rate to be easier. You can also use total_hash_rate_avg in the report, as current total_hash_rate might be too sensitive for occasional dip.
And remember to change the CMDLine in Line 169, or else you would be mining to my wallet instead.
Let me know if you have any further question. I will try my best to help set up.

One other section that people might find confusing, though StellarX88 explained it:

Drop trigger section is dependent on the number of Vegas that you have installed.

When hash rate drops, if it drops for 1 card from 1950 down to 1600 the difference = 350.  So if it drops for 5 cards, then 5 x 350 = 1750 BUT you need to add three "000" to match /json output of Cast 0.70.
So my $hdiff = 1750000

Similarly, if my normal total hash rate is aroud 9.6KH/s, and if I want to restart if that total drops to 8KH/s, I have to express that value by adding three "000" onto the end.  

$global:vegaHash =  8KH/s = 8000000

#########################################################################
# Set drop trigger and startup timeout
#########################################################################
$hdiff = 1750000         # This is the drop in total hash rate where we
#                  trigger a restart (Starting HASHRATE-$hdiff)
#
$timeout = 60         # (STARTUP ONLY)How long to wait for CAST_XMR to
#                  return a hashrate before we fail out and
#                  restart. There is no limiter on the number of restarts.
#                  Press CTRL-C to EXIT
#                  
$CAST_XMRstable = 20      # How long to wait for the hashrate to stabilize.
#
$global:vegaHash = 8000000   # Minimum vega hash rate before we also trigger
#                  a restart
#########################################################################
###################### END USER DEFINED VARIABLES #######################
#################### MAKE NO CHANGES BELOW THIS LINE ####################

#####  BEGIN FUNCTIONS #####

[xeridea]

hey guys, one noob question about receive nicehash payments

Nicehash always pay me on friday, so if today I change the adress for recieving payments, they will pay all on the new adress provided or they will pay some amount to first adress and the rest on the new??

Thanks!!

Each Bitcoin address for NH is essentially a completely separate account. The old address would get payout according to their payout rules based on amount like normal (weekly 0.01, daily 0.1), new is completely separate.

[GRABNGO57]

Help
How to connect to stratum+tcp://  (minergate) pool?

Any update on this one?

[StellarX88]

has anyone tried butchering jj's hashmonitor powershell script to monitor castxmr now that it has an API?

i would but my programming leaves a lot to be desired....

I posted this on another thread and also helping some redditor, but you can try this:

I have modified the script slightly to work with 1 of my Vega card. You can modified it accordingly to fit your rig.

Download link below:
https://drive.google.com/open?id=0B2XFJ__I0jzLWlBZMTVCMWZDZ3YwRDZiRkh6cldKWnc1Wjlz

Some changes I made:

If you are executing the run_HashMonitor.cmd, make sure you change the file name in it accordingly to reflect CastXMR_HashMonitor_v2.6.ps1 (Or any name that you saved as).
Notable change I have made in this ps script includes:
Line 168 - 172 : I am using the script to call Cast-XMR directly, and Line 169 is the usual config including my wallet address, mining pool etc (the usual you put in a .bat) & also --remoteaccess in this case. Line 170 - 172 is to assign the localhost & port accordingly (7777)
Line 187: The main address for local/remote monitoring
Line 191 - 201: I didn't use $hdiff variable, but make a new variable for min Vega Hashrate before restart $global:vegahash @ line 201 (multiply by 1,000 since the reported value in the web is in actual hash rate)
Line 392 - 397 : Initial Vega hashrate for comparison (Not really needed since we have a reset trigger down below, but it's the same as the next)
Line 476 - 479 : Vega hashrate used for monitoring in order for restart.
Line 483 - 484 : Nothing major, just changing monitoring from 1 minute to every 30 secs
7: Line 486 : Most important part, condition to restart (Here to check my Vega hashrate against my preset target -> ~1.75kH/s @ Line 201)
This should set you up in the right direction to start with;
Do take note that I am running only 1 Vega to check against, hence I can use the total_hash_rate for comparison; if you are running multiple Vegas rig, you might need to divide it by number of GPU instances before you make the comparison. Alternatively is to loop through the "devices" in the hashrate report JSON to check if any of them drop, but I find total_hash_rate to be easier. You can also use total_hash_rate_avg in the report, as current total_hash_rate might be too sensitive for occasional dip.
And remember to change the CMDLine in Line 169, or else you would be mining to my wallet instead.
Let me know if you have any further question. I will try my best to help set up.

thanks! i'll get on this (probably next week)

StellarX88, Thank you!!!

It's working! Sweet!

Okay, when running multiple Vega's, your start up lines for Cast might look like this:

$global:CAST_XMRexe = "cast_xmr-vega.exe"   # The miner. Expects to be in same folder as this script
$global:CAST_XMRcmdline = "-S mine.xmrpool.net:7777 -u [Your_Wallet_Address].[Your_Rig_Name] -p x -O 1 -G 0,1,2,3,4 -I 8 -R"  #"Cast_XMRcmdline = values you had put into your .bat file, with some reordering

I moved the --opencl to the end (the "-O 1" is my opencl value) -O is the same thing as earlier "--opencl"
The "-G" command I also moved to the end.
"-R" works, is equivalent to, --remoteaccess but for some reason using "--remoteaccess" did not work.  But "-R" does !

Vid tools is where you put your OverDriveNTool profiles to apply:

#### Vid Tool 1
$vidTool += 'OverdriveNTool.exe -r0 -r1 -r2 -r3 -r5 -p0Vega -p1Vega -p2Vega -p3Vega -p5Vega'   #-r4 is an Nvidia card, that is why "4" is skipped over here
                              # Expects to be in same folder as this script
                              # Delete or REMARK if you don't want use it
#### Vid Tool 2
$vidTool += 'regedit.exe /S 000.reg'   # Expects to be in same folder as this script               #from Kekso on Reddit, if you want to try this, move a copy of RegEdit into your Cast folder. These are my SoftPowerPlay mods.
                               # Delete or REMARK if you don't want use it
#### Vid Tool 3
$vidTool += 'regedit.exe /S 001.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it
#### Vid Tool 4
$vidTool += 'regedit.exe /S 002.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it
#### Vid Tool 5
$vidTool += 'regedit.exe /S 003.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it
#### Vid Tool 6
$vidTool += 'regedit.exe /S 004.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it   
#### Vid Tool 7
$vidTool += 'regedit.exe /S 005.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it   
#### Vid Tool 8
$vidTool += 'regedit.exe /S 006.reg'   # Expects to be in same folder as this script
                               # Delete or REMARK if you don't want use it   
##### End VidTools
$global:Url = "http://$CAST_XMRIP`:$CAST_XMRPort" # <-- DO NOT CHANGE THIS !!

Nice!  So happy to have auto-restart if Hash rate drops.

Hey! Glad that you got it working! I didn't noticed I was mixing the old and new commandline arguments after checking --help, but as long as either works then I guess that's good! Wonder what's the prereq to use the old vs new commandline, I imagine you are using win10 as well?

I have a question on the regedit.exe, dont you need to restart your PC after you have modify the powerplay table with that? Or it's not required?

Anyway happy hashing! I have made a similar modification on JJs script v2.9 as well, folder link with similar changelog below:

https://drive.google.com/open?id=1TnicWxpB1TtGQCe_cuXND8ha-XsgQsU1

Don't think there's any major enough change to warrant a change on your side as long as JJs v2.6 works well enough for you.

[StellarX88]

has anyone tried butchering jj's hashmonitor powershell script to monitor castxmr now that it has an API?

i would but my programming leaves a lot to be desired....

I posted this on another thread and also helping some redditor, but you can try this:

I have modified the script slightly to work with 1 of my Vega card. You can modified it accordingly to fit your rig.

Download link below:
https://drive.google.com/open?id=0B2XFJ__I0jzLWlBZMTVCMWZDZ3YwRDZiRkh6cldKWnc1Wjlz

Some changes I made:

If you are executing the run_HashMonitor.cmd, make sure you change the file name in it accordingly to reflect CastXMR_HashMonitor_v2.6.ps1 (Or any name that you saved as).
Notable change I have made in this ps script includes:
Line 168 - 172 : I am using the script to call Cast-XMR directly, and Line 169 is the usual config including my wallet address, mining pool etc (the usual you put in a .bat) & also --remoteaccess in this case. Line 170 - 172 is to assign the localhost & port accordingly (7777)
Line 187: The main address for local/remote monitoring
Line 191 - 201: I didn't use $hdiff variable, but make a new variable for min Vega Hashrate before restart $global:vegahash @ line 201 (multiply by 1,000 since the reported value in the web is in actual hash rate)
Line 392 - 397 : Initial Vega hashrate for comparison (Not really needed since we have a reset trigger down below, but it's the same as the next)
Line 476 - 479 : Vega hashrate used for monitoring in order for restart.
Line 483 - 484 : Nothing major, just changing monitoring from 1 minute to every 30 secs
7: Line 486 : Most important part, condition to restart (Here to check my Vega hashrate against my preset target -> ~1.75kH/s @ Line 201)
This should set you up in the right direction to start with;
Do take note that I am running only 1 Vega to check against, hence I can use the total_hash_rate for comparison; if you are running multiple Vegas rig, you might need to divide it by number of GPU instances before you make the comparison. Alternatively is to loop through the "devices" in the hashrate report JSON to check if any of them drop, but I find total_hash_rate to be easier. You can also use total_hash_rate_avg in the report, as current total_hash_rate might be too sensitive for occasional dip.
And remember to change the CMDLine in Line 169, or else you would be mining to my wallet instead.
Let me know if you have any further question. I will try my best to help set up.

One other section that people might find confusing, though StellarX88 explained it:

Drop trigger section is dependent on the number of Vegas that you have installed.

When hash rate drops, if it drops for 1 card from 1950 down to 1600 the difference = 350.  So if it drops for 5 cards, then 5 x 350 = 1750 BUT you need to add three "000" to match /json output of Cast 0.70.
So my $hdiff = 1750000

Similarly, if my normal total hash rate is aroud 9.6KH/s, and if I want to restart if that total drops to 8KH/s, I have to express that value by adding three "000" onto the end.  

$global:vegaHash =  8KH/s = 8000000

#########################################################################
# Set drop trigger and startup timeout
#########################################################################
$hdiff = 1750000         # This is the drop in total hash rate where we
#                  trigger a restart (Starting HASHRATE-$hdiff)
#
$timeout = 60         # (STARTUP ONLY)How long to wait for CAST_XMR to
#                  return a hashrate before we fail out and
#                  restart. There is no limiter on the number of restarts.
#                  Press CTRL-C to EXIT
#                  
$CAST_XMRstable = 20      # How long to wait for the hashrate to stabilize.
#
$global:vegaHash = 8000000   # Minimum vega hash rate before we also trigger
#                  a restart
#########################################################################
###################### END USER DEFINED VARIABLES #######################
#################### MAKE NO CHANGES BELOW THIS LINE ####################

#####  BEGIN FUNCTIONS #####

Actually, as mentioned in the changes that I have made, $hdiff does nothing in restarting the rig since I have changed it to solely check against $global:vegaHash variable. I was using it with my RX 480 + CPU mining together with the Vega using XMR-stak, but ultimately I switched to mine on Vega using Cast-XMR hence the condition has been change to specifically read $global:vegaHash only.

But if you would like to set a reset using either hash rate drop ($hdiff) or vega hash rate minimum threshold ($gloabl:vegaHash), you can edit Line 486 to:

while (($global:currHash -gt $global:vegaHash) -and ($global:currHash -gt $global:rTarget))

2nd condition meaning to check against (in your case) your vega rig total hashrate to be more than (9.6-1.75) = 7.85kH, but by that logic the first condition of 8kH check would already been suffice to trigger a reset. Hence, a moot variable for a full Vega mining rig.

[drogasi]

Hello ,
I have this problem, after some hours of mining, cast xmr stop submitting share but doesn't crash,
to restart it  just close it and open it again but 3 or 4 hours later the problem is still here


<a href="https://ibb.co/ncXLUb"><img src="https://preview.ibb.co/idLUNw/IMG_1535.png" alt="IMG_1535" border="0"></a>

[Jo82]

Hi i m getting 6200hs on my mixed rig, however i m getting alot 0.0hs lines in the miner...
Who can help me solve this?

does someones has the --help working?

thnx

[MickDaster]

has anyone tested the latest drivers from AMD are they good?

[djkice]

has anyone tested the latest drivers from AMD are they good?

I saw them but decided not to bother, a lot of blood... sweat and tears went into getting the rigs to work so far.

It's stable with hash monitor, don't try fix it unless it's broken!!