Author

Topic: [Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s) - page 123. (Read 206388 times)

legendary
Activity: 2294
Merit: 1182
Now the money is free, and so the people will be
And Vegas are sold out and or priced wayyy too high around me and have been for some time.  I guess people are stocking up on them Smiley
newbie
Activity: 60
Merit: 0
No need to toggle the HBCC before starting a miner. In fact you don't have to touch it at all.
Just go to Device Manager->DisplayAdapters->RightMouseClick on Vega to Disable and then Reanable it again.
You have to do it after every windows restart.

BTW here is a nice guide for mining with Vegas and not using Radeon software: vega.miningguides.com

Cast XMR gives me better results than Stak XMR when mining with Vega56.
hero member
Activity: 714
Merit: 512
Hey guys... I cannot get past 1300 on my VEGA-64

Resetting the HBCC setting has no effect.

Thoughts ?

----------

*EDIT* -- Rebooted whole system and suddenly the HBCC tweak worked. Seeing ~1880 so far.

Thanks Dev.

Little tweaking... 1825 once it settles down with 210-watts at the wall (GOLD PSU).
full member
Activity: 305
Merit: 148
Theranos Coin - IoT + micro-blood arrays = Moon!

Quote

I use wattman with no problems. Day after day of stability at over 2K average hash rate on 4 vega 64's. It's not Wattman that is the problem, but I concede that it of course is far from perfect.

Make sure you have 8MB of Virtual Mem per card set in your virtual mem space (windows10). 1024 * 16 for (2 cards) = 16384 + 300 for overhead =16684 total. OR maybe better settings 2 (cards) 1024 *16 *1.5 = 24576VM.
Make sure crossfire is turned off (should not be an option if using the blockchain driver so generally ignore people saying this)
If using wattman sometimes it is best to toggle the HBCC on off after PC reboot. (leave it off on all cards)
My fans are set to 2500RPM min with a target 70C and max of 75C - You will need to adjust fan speed per your climate.If you can keep the cards at 70C and lower, all the better.
turn the monitor settings in windows to never turn off.

That is about all really.


Fire up the script and let it run. You can turn your monitor off and on and the hash rate should stay the same.

Wattman is a problem.  And Crossfire *can* be randomly turned on by Wattman even if using the Block chain drivers, which is all I have ever used with Vega.  So check Crossfire in Wattman, if you are still using Wattman, which is not recommended.

Wattman has not been a problem for me so I disagree with the news that it is. I don't have a crossfire option in Wattman, I use on board video. Everything is working great. Windows 10 is a bigger problem.

It works well for you, great.  But there are at least four different threads about getting Vega to work and many people have reported issues when using Wattman.
hero member
Activity: 714
Merit: 512
Hey guys... I cannot get past 1300 on my VEGA-64

Resetting the HBCC setting has no effect.

Thoughts ?

----------

*EDIT* -- Rebooted whole system and suddenly the HBCC tweak worked. Seeing ~1880 so far.

Thanks Dev.
newbie
Activity: 99
Merit: 0

Quote

I use wattman with no problems. Day after day of stability at over 2K average hash rate on 4 vega 64's. It's not Wattman that is the problem, but I concede that it of course is far from perfect.

Make sure you have 8MB of Virtual Mem per card set in your virtual mem space (windows10). 1024 * 16 for (2 cards) = 16384 + 300 for overhead =16684 total. OR maybe better settings 2 (cards) 1024 *16 *1.5 = 24576VM.
Make sure crossfire is turned off (should not be an option if using the blockchain driver so generally ignore people saying this)
If using wattman sometimes it is best to toggle the HBCC on off after PC reboot. (leave it off on all cards)
My fans are set to 2500RPM min with a target 70C and max of 75C - You will need to adjust fan speed per your climate.If you can keep the cards at 70C and lower, all the better.
turn the monitor settings in windows to never turn off.

That is about all really.


Fire up the script and let it run. You can turn your monitor off and on and the hash rate should stay the same.

Wattman is a problem.  And Crossfire *can* be randomly turned on by Wattman even if using the Block chain drivers, which is all I have ever used with Vega.  So check Crossfire in Wattman, if you are still using Wattman, which is not recommended.

Wattman has not been a problem for me so I disagree with the news that it is. I don't have a crossfire option in Wattman, I use on board video. Everything is working great. Windows 10 is a bigger problem.
full member
Activity: 305
Merit: 148
Theranos Coin - IoT + micro-blood arrays = Moon!

Quote

I use wattman with no problems. Day after day of stability at over 2K average hash rate on 4 vega 64's. It's not Wattman that is the problem, but I concede that it of course is far from perfect.

Make sure you have 8MB of Virtual Mem per card set in your virtual mem space (windows10). 1024 * 16 for (2 cards) = 16384 + 300 for overhead =16684 total. OR maybe better settings 2 (cards) 1024 *16 *1.5 = 24576VM.
Make sure crossfire is turned off (should not be an option if using the blockchain driver so generally ignore people saying this)
If using wattman sometimes it is best to toggle the HBCC on off after PC reboot. (leave it off on all cards)
My fans are set to 2500RPM min with a target 70C and max of 75C - You will need to adjust fan speed per your climate.If you can keep the cards at 70C and lower, all the better.
turn the monitor settings in windows to never turn off.

That is about all really.


Fire up the script and let it run. You can turn your monitor off and on and the hash rate should stay the same.

Wattman is a problem.  And Crossfire *can* be randomly turned on by Wattman even if using the Block chain drivers, which is all I have ever used with Vega.  So check Crossfire in Wattman, if you are still using Wattman, which is not recommended.
newbie
Activity: 19
Merit: 0
Windows Defender found this:

Trojan:Win32/Tilken.B!cl



Any idea why Windows Defender thinks the miner is a Trojan?, I know it is normal for Antivirus to detect Miners as virus, but with Moderate risk and not Trojans, this is marked as Severe risk, any ideas?, I have been using this miner for several days with no problems now I have it quarantined.

Thx
newbie
Activity: 99
Merit: 0
Finally I set up my rig. all good but what I noticed hashrate dropes from 1850 to 1600 on my vega. Currently I have one vega 56 and 480. next vega 64 comming. Damn hard to buy them at the moment.
BUt why hashrate droppes? any fix for it?

Can you describe better how the hash rate is dropping? Do you see it happen before your eyes? Or is it loging back in from a lock screen? Have you read all 32 pages of posts here?
jr. member
Activity: 194
Merit: 4
Okay, one thing i find interesting, is the lack of multiple threads. Unlike sgminer, you can't request the miner to run 2 threads on a single GPU. On sgminer and on Windows, this actually brought extra h/s.

Ofc this uses multiple threads Smiley There is no way to get 2kh/s out of vega by single thread.

Interface simply shows only the total hashrate.

Or you probl knew this alrd, but then again, its optimized only for vega, since OP previously only had vega cards.

Yea i knew that, still decided to test it. And yea, its testd on RX480/580.

I said this, because, it really shows up only 1 thread working - GPU0 and nothing else. No idea if its the same for Vega.
sr. member
Activity: 437
Merit: 250
Finally I set up my rig. all good but what I noticed hashrate dropes from 1850 to 1600 on my vega. Currently I have one vega 56 and 480. next vega 64 comming. Damn hard to buy them at the moment.
BUt why hashrate droppes? any fix for it?
newbie
Activity: 99
Merit: 0
Hello everyone!
I also have 2 GPU Vega 56 and when I add the -G 0,1 line everything crashes and I have to restart.
Otherwise using only one card i get 1950h/s, even 2000 if i put power usage to 0%.
It crashes even if use WinMiner and a very low power setting on Wattman.

I am afraid that the PC crashes using 2 gpu, because the motherboard may not be strong enough it is a 3 years old Gygabite, maybe is not recent enough. It is supposed to support 2 AMD Gaming GPU (even in crossfire) though...


On a different note, For those who gets Hs drops after a while it may be because the fan are below 3000rpm.



Pretty much as I stated above...
it is not the mobo, I followed step-by step to setup my rig http://vega.miningguides.com/ I have 2 Vega 64 on a 5 years old Asus P8H61-M LE and i get stable 1960 H/s per card, your problem is the Wattman.. quote from the site: "If you installed the full AMD application, NEVER EVER open the AMD application.  In other guides you will hear references to Wattman.  Ignore them.  You will hear references to HBCC sliders.  Ignore them.  Opening the driver software works for some people but I have had to uninstall and re-install the drivers ground up because of opening the driver.  Don't do it.  You need it installed and that is it.  (If you did open it and have problems that require uninstall"

I use wattman with no problems. Day after day of stability at over 2K average hash rate on 4 vega 64's. It's not Wattman that is the problem, but I concede that it of course is far from perfect.

Make sure you have 8MB of Virtual Mem per card set in your virtual mem space (windows10). 1024 * 16 for (2 cards) = 16384 + 300 for overhead =16684 total. OR maybe better settings 2 (cards) 1024 *16 *1.5 = 24576VM.
Make sure crossfire is turned off (should not be an option if using the blockchain driver so generally ignore people saying this)
If using wattman sometimes it is best to toggle the HBCC on off after PC reboot. (leave it off on all cards)
My fans are set to 2500RPM min with a target 70C and max of 75C - You will need to adjust fan speed per your climate.If you can keep the cards at 70C and lower, all the better.
turn the monitor settings in windows to never turn off.

That is about all really.


Fire up the script and let it run. You can turn your monitor off and on and the hash rate should stay the same.
full member
Activity: 167
Merit: 100
Thank you for the tip!

I will uninstall clean and re install the drivers, redo the settings as per the set up in the guide and never open the Wattman and see if it works.
Il repost the results.



try to use ndrivetool its far better than afterburner for AMD
newbie
Activity: 206
Merit: 0
Thank you for the tip!

I will uninstall clean and re install the drivers, redo the settings as per the set up in the guide and never open the Wattman and see if it works.
Il repost the results.

newbie
Activity: 48
Merit: 0
Hello everyone!
I also have 2 GPU Vega 56 and when I add the -G 0,1 line everything crashes and I have to restart.
Otherwise using only one card i get 1950h/s, even 2000 if i put power usage to 0%.
It crashes even if use WinMiner and a very low power setting on Wattman.

I am afraid that the PC crashes using 2 gpu, because the motherboard may not be strong enough it is a 3 years old Gygabite, maybe is not recent enough. It is supposed to support 2 AMD Gaming GPU (even in crossfire) though...


On a different note, For those who gets Hs drops after a while it may be because the fan are below 3000rpm.



Pretty much as I stated above...
it is not the mobo, I followed step-by step to setup my rig http://vega.miningguides.com/ I have 2 Vega 64 on a 5 years old Asus P8H61-M LE and i get stable 1960 H/s per card, your problem is the Wattman.. quote from the site: "If you installed the full AMD application, NEVER EVER open the AMD application.  In other guides you will hear references to Wattman.  Ignore them.  You will hear references to HBCC sliders.  Ignore them.  Opening the driver software works for some people but I have had to uninstall and re-install the drivers ground up because of opening the driver.  Don't do it.  You need it installed and that is it.  (If you did open it and have problems that require uninstall"
newbie
Activity: 206
Merit: 0
Hello everyone!
I also have 2 GPU Vega 56 and when I add the -G 0,1 line everything crashes and I have to restart.
Otherwise using only one card i get 1950h/s, even 2000 if i put power usage to 0%.
It crashes even if use WinMiner and a very low power setting on Wattman.

I am afraid that the PC crashes using 2 gpu, because the motherboard may not be strong enough it is a 3 years old Gygabite, maybe is not recent enough. It is supposed to support 2 AMD Gaming GPU (even in crossfire) though...


On a different note, For those who gets Hs drops after a while it may be because the fan are below 3000rpm.

member
Activity: 124
Merit: 10
hi,

thanks for your support of rx4xx.
i have 4 x rx470 8g modbios, with claymore 760h/s, with cast-xmr 810h/s

i have a little problem.
i see only the hashrate of 1 gpu.

newbie
Activity: 48
Merit: 0

Hi there

Love the app, getting +400h/s more than any other app I've tried. However there is a problem, when I enter the -G 0,1 in the bat file and run the app, it's crashes my whole pc and I have to force reboot my pc, I do have 2 x RX VEGA 64 card's on riser cables with plans to get a third card in the next couple of days, win 10 pro 64bit, 8gig ram and the beta software as recommended in your setup procedure. Side note: HBCC toggle switch is no where to be located in the AMD software. I am a real noob at this, so maybe I've done something wrong/something. Some assistance would be greatly appreciated
[/quote]

did you increase the windows virtual memory? you need about 60GB to mine with Vega 64... also because the beta blockchain driver is buggy you have to disable/enable your GPUs in the device manager every time before start mining... anyway, here is a great guide about the settings for Vega GPUs, strongly recommended article for a "noob" Smiley http://vega.miningguides.com/
MHB
newbie
Activity: 13
Merit: 0
http://
Yay, 1920 H/s mining to nicehash!
Windows 10, Stock Vega 56, 950MHz HBM, -3% power, temp target 70C, min fan 2200

cast_xmr-vega-win64_060>cast_xmr-vega -G 0 --opencl 2 -S cryptonight.eu.nicehash.com:3355 -u "YOURwallet".castxmr


mmmm, I've applied -20% power but min fan doesn't apply at all....

what's the reason to write --opencl 2??

my bat file is like that and I'm mining 1920 H/s

cast_xmr-vega -G 1 -S cryptonight.eu.nicehash.com:3355 -u "mywallet" %*



I need to add --opencl 2 because I have a GTX1070 installed. I also have onboard Intel graphics (currently disabled).

https://i.imgur.com/VRVBz4R.jpg

Well, seems like I spoke too soon. Checked this morning and my hash rate drops to 1680h/s after 20-30min.
That doesnt sound too bad, right? Well it gets worse, as it also has a reject rate of over 30%.

https://i.imgur.com/EpxOqlZ.png

Switched my Vega back to NH with Claymore AMD, 1420 H/s 24/7 stable.  Huh


newbie
Activity: 1
Merit: 0
Cast XMR - Highspeed CryptoNight (Monero/Bytecoin/DigitalNote/Intense) Miner for Radeon RX Vega GPUs

Update to version 0.6 on 2017/10/27

Cast XMR reaches hash rates of more then 2050 CryptoNight Hashes/s on an single RX Vega 56 or Vega 64 GPU.

http://www.gandalph3000.com/images/cast_xmr.png

Features

- Full support for CryptoNight/CryptoNote based currencies:
  • Monereo (XMR)
  • Bytecoin (BCN)
  • DigitalNote (XDN)
  • Intense (ITNS)
- Fastest miner for AMD Radeon RX Vega GPU series (more then 2KHash/s)
- Optimized cores for RX Vega Blockchain driver
- RX Vega Blockchain driver detection
- Multiple GPU support for upto 8 Vega GPUs
- Monitor temperature and fan speed of each GPU
- Full pool support
- Nicehasher support
- only 1.5% dev fee

Requirements

  - Windows 8/8.1/10 64 bit
  - AMD Radeon RX Vega 56/64 GPU with at least 8GB RAM
  - or AMD Radeon RX 480/RX 580 GPU with a least 4GB RAM
  - For about 80% higher hash rates the ReLive Edition Beta for [Suspicious link removed]pute Driver Version 17.30.1029 has to be installed

Version History

Cast XMR Version 0.6 (2017/10/27)

  - improved queue sync which results in an 0.1% higher average hash rate
  - experimental support for Radeon RX 480/580 GPUs added
  - pessing 's' key prints the current statistics
  - count outdated and invalid shares separate
  - fixed random crash when quitting app
  - bugfix: invalid command line arguments did hang app

Cast XMR Version 0.5 (2017/10/19)

  - support for multiple Vega GPUs. Specify multiple GPUs comma separated with the -G switch like "-G 0,1,2,3"
  - monitor temperature and fan speed for each GPU
  - subtle performance improvements in core

Cast XMR Version 0.4 (2017/10/13)

  - performance optimizations result in 1 - 2% higher hash rates
  - reduced dev fee to 1.5%

Cast XMR Version 0.3 (2017/10/10)

  - performance optimizations result in 5 - 10% higher hash rates
  -  breaking the 2 KHashes/s barrier with working overclocking settings for RX Vega 64 and RX Vega 56

Cast XMR Version 0.2 (2017/09/27)

  - performance improvement result in 1% higher hashrates
  - Improved support for RX Vega 56 (now goes faster then a Vega 64 !?)
  - Detection if Blockchain driver is installed
  - Fix for Sikka and Intense pools

Cast XMR Version 0.1 (2017/09/22)

  - Initial Release

How To

cast_xmr has a command line interface. For a minimal configuration run:

cast_xmr -S [pool server] -u [username or wallet address]

For a complete list of configuration options run:

cast_xmr --help

Read here how to get the best mining performance with a Radeon RX Vega 56/64 GPU

Download Cast XMR 0.6 for Windows (64bit)

Linux version to follow soon ...

Hi there

Love the app, getting +400h/s more than any other app I've tried. However there is a problem, when I enter the -G 0,1 in the bat file and run the app, it's crashes my whole pc and I have to force reboot my pc, I do have 2 x RX VEGA 64 card's on riser cables with plans to get a third card in the next couple of days, win 10 pro 64bit, 8gig ram and the beta software as recommended in your setup procedure. Side note: HBCC toggle switch is no where to be located in the AMD software. I am a real noob at this, so maybe I've done something wrong/something. Some assistance would be greatly appreciated
Jump to: