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

[coke15]

hi
i'm still on blockain with 4 vega 56@64 and powertable 1100 mhz of the "Monero and Vega - the definitive guide  MoneroMining"
it draw 700w at the wall  with 1408@850 and 1100@900

i tried with the 18.3.4,same hashrate +/- 7900h no power table but 1408@850 and 1100@900  with overdrivetool.

But there is a massive difference:it draw 1000w at the wall

i don't kwnow why,core and mee was same  exept powertable.

where can i find powertable for adrenaline 18.3.4 or 18.5.1? or make them even i'm not understanding all :/

thanks

[1714607396]

1714607396

[logicus]

I have rig with 4 vega 56@64.
I just unistall block chain driver with display driver uninstaller. Reboot and install 18.3.4 and same powertable reg file i used with old drivers (1408@850 and 1100@900),disable crossfire and all is ok.
Rig draw ~700w at the wall (CryptoNotev7) and ~650w at the wall (CryptoNote-Heavy)

[coke15]

hi

ok i will re try with 18.5.1 and old powertable

[issie81]

Hey Guys,

i 1330h considered as good hashrate speed capped at 65c
4x Vega 56 running 6600h

running

P7 1407/875
P3 930/875
Max temp 65
Power Target -22

rock stable @ CN-Heavy

[gameboy366]

Hey Guys,

i 1330h considered as good hashrate speed capped at 65c
4x Vega 56 running 6600h

running

P7 1407/875
P3 930/875
Max temp 65
Power Target -22

rock stable @ CN-Heavy

Yes. This is normal.

[zeef]

Cast XMR - Highspeed CryptoNight (Monero/Aeon/Electroneum/Bytecoin) Miner for Radeon RX Vega GPUs

Update to version 1.0.0 on 2018/04/24

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

Features

- Full support for:

• CryptoNightV7
  • Monero (XMR)
  • Intense (ITNS)
  • Graft (GRFT)
  • Stellite (XTL)
• CryptoNight (Classic)
  • Bytecoin (BCN)
  • DigitalNote (XDN)
  • Electroneum (ETN)
  • LeviarCoin (XLC)
  • Karbo (KRB)
• CryptoNight-Heavy
  • Sumokoin (SUMO)
  • Haven (XHV)
• CryptoNight Lite
  • Aeon (AEON)
• CryptoNightV7 Lite
  • Turtlecoin (TRTL)
• CryptoNightIPBC Lite
  • Interplanetary Broadcast Coin (IPBC)

- Fastest miner for AMD Radeon RX Vega 56/64 GPU series

• more then 2050 CryptoNight Hashes/s
• more then 1420 CryptoNight-Heavy Hashes/s
• more then 4250 CryptoNight-Lite Hashes/s

- Fastest miner for AMD Radeon Vega Frontier Edition GPU

• more then 2100 CryptoNight Hashes/s
• more then 1600 CryptoNight-Heavy Hashes/s

- Optimized cores for Vega and Polaris based GPUs
- Automatic driver version detection and setup recommendations
- Multiple GPU support for upto 8 Vega GPUs
- Monitor temperature and fan speed of each GPU
- Full pool support
- Nicehash support
- Fast Job Switch option to minimize outdated shares
- Remote http access for statistics in JSON format
- 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 Vega Frontier Edition with 16GB RAM
  - or AMD Radeon RX 470/RX 480/RX 570/RX 580 GPU with a least 4GB RAM
  - For about 50% higher hash rates the Radeon Driver 18.3.4 has to be installed

Version History

Cast XMR Version 1.0.0 (2018/4/24)
- Support for Aeon (AEON) CryptoNight Lite variant set --algo=3 to mine
- Support for Turtlecoin (TRTL) CryptoNightV7 Lite variant set --algo=4 to mine
- Support for Interplanetary Broadcast Coin (IPBC) CryptoNight Lite IPBC variation set --algo=5 to mine
- Up to 3% performance improvement with new option --maxmem to allocate the maximum memory of the card. For Vega cards the "HBCC Memory Segment" has to be disabled in the Radeon Settings to use the option. Disadvantage is a higher risk of hash rate drops when the --maxmem option is used.

Cast XMR Version 0.9.6 (2018/04/17)
  - CryptoNight-Heavy fix for very low hash rates when HBCC Memory Segment is enabled
  - HBCC Memory Segment performance hint for Vega64 when mining CryptoNightV7
  - Improvement for 4GB versions of RX 470/480/570/580 when mining CryptoNightV7

Cast XMR Version 0.9.5 (2018/04/14)
  - 0.5% performance improvement for the CryptoNightV7 kernel
  - support for CryptoNight Heavy set --algo=2 to mine:
   - Sumokoin (SUMO)
   - Haven (XHV)

Cast XMR Version 0.9.2 (2018/03/29)
  - Improvements for RX Vegas that achieve 99% the performance of the Blockchain Compute Beta driver with the latest standard Radeon Driver 18.3.4

Cast XMR Version 0.9.1 (2018/03/22)
  - 0.5% overall performance improvement for Vega based GPUs
  - --ratewatchdog experimental option to monitor the hash rate, in case an occasional happening drop of the hash rate is detected the kernel will be resetted to restore the optimal hash rate
  - fully tested CryptoNight variant (CryptoNightV7) for the Monero V7 Network Upgrade PoW Change which is now scheduled for the 6th April.
  - In case you want to mine the Graft coin use the --algo=0 option, an automatic detection of the used CryptoNight variant is not possible for this coin. For all other known CryptoNight coins the hash variant seems to be detected correct
  - In case you are mining with nicehash.com or any other automatic coin switching pool that has the Graft coin in the mix the --algo=0 option is advised to prevent invalid shares on the Graft coin. Be aware to remove the option when the Monero V7 network upgrade is happpening otherwise it then will clash with mining Monero!

Cast XMR Version 0.9.0 (2018/03/08)
  - support for the Monero V7 network upgrade. Read more about it here
  - the Monero PoW switch will be automatically detected, no restart of cast XMR is required. Only make sure to update cast XMR before the network upgrade is happening and that the used Monero pool supports the network upgrade
  - no decrase in hash rate for other currencies was introduced by the change
  - CryptoNightV7 will run at the same hash rate as CryptoNight
  - for any case there is the new --algo option to force which CryptoNight variant to use:
    - -1 = autodetect (default)
    - 0 = CryptoNight
    - 1 = CryptoNightV7 (Monero V7 network upgrade)

Cast XMR Version 0.8.5 (2018/02/07)
  - 1% performance gain for Vega Frontier Edition with Blockchain driver (fastest GPU around)
  - 1% performance improvement with current stock driver (18.1.1) for RX Vega 56/64 (40% to go to reach Blockchain driver performance)
  - fix for random blocking console output
  - GPU now always logs with its device id not the order they are listed in the -G argument
  - --log option to log console output to a file
  - remote access includes CORS support in HTTP header

Cast XMR Version 0.8 (2017/12/14)

  - kernel optimizations result in subtle performance improvements
  - --fastjobswitch option (experimental) to force fast switching to new jobs. When enabled the GPUs will switch to the new job within less then 100ms. This improves the effective hash rate by 1 to 5% as nearly no GPU performance will be wasted on calculating outdated shares anymore. The drawback is a slightly lower displayed hashrate as while switching no hashes are calculated.
  - improved support for more then 8 GPUs
  - support for Radeon RX 470/RX 570 (Polaris) added
  - --forcecompute option to force kernel for compute mode on Polaris (RX470/570/480/580) GPUs. In the Radeon Settings GPU Workload has to be switched to 'Compute'. This option is available in Crimson 17.10.2 (or later) driver and reaches nearly the same performance on Polaris based GPUs as with the Blockchain driver.
  - openCL platform is auto detected if --opencl is not specified
  - --nonicehash option to disable nicehash support
  - nicehash support will automatically disabled if more then 8 GPUs are used. Otherwise search space could be exhausted to early and the GPUs search in overlapping nonce ranges.

Cast XMR Version 0.7 (2017/11/29)

  - network and job status added to current statistics
  - remote access to get current status at http://127.0.0.1:7777 in JSON format (enable with --remoteaccess)
  - command line option to specify number of reconnects to pool (default 100) before giving up (set with --reconnects n)
  - fix for nicehash to support upto 8 GPUs (before only 4 were possible)

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

For more info visit my website www.gandalph3000.com

Download Cast XMR 1.0.0 for Windows (64bit)

SHA256 hash of cast_xmr-vega-win64_100.zip:
fab141ce2b3e3b32636fedfc242e9b91edc21317e108fb361368570694dd338e


A Linux version is nearly finished, but does not reach the same performance as the Windows version, still investigating.

hi glph3k ,

Can you add an feature to your wishlist?

If an gpu or an overclocked failed, when miner is working, make the pc restart, sometimes one gpu doesn t power on .
When this happen the -- gpu number syntax.. should bypass that gpu and allow the cast to start anyway.

Make sense?

Regards

[coke15]

hi

it would be great:)
bored of it ,when it hang /stop hashing and no "reboot" itself

[issie81]

Defo i have a few times miner hangs, not Windows so would be great if there is a auto-correct failover.

[Skyzer0]

This miner is still trash, every single day, miners keeps mining but its frozen and has to be restarted, so its using power and still loading the gpu's without mining.

Specially on a rig with rx580 and rx vega it freezes all the time if i use both in one miner, or 2 separate ones.

[SpceGhst]

Defo i have a few times miner hangs, not Windows so would be great if there is a auto-correct failover.

This miner is still trash, every single day, miners keeps mining but its frozen and has to be restarted, so its using power and still loading the gpu's without mining.

Specially on a rig with rx580 and rx vega it freezes all the time if i use both in one miner, or 2 separate ones.

hi

it would be great:)
bored of it ,when it hang /stop hashing and no "reboot" itself

If the miner is freezing but Windows is still working, you probably have one or more of your cards clocked too high.  Mine hung a couple of times over a 3 day period... reduced the mem clock by 25 on all of them, and it’s been running solid ever since.

[Germini]

Hi dear mates, I've been using my 7 vegas56 with power tables. Now I wanted to not use them, then I used WattMan to do it but after crashing, I lost my personalized profile so I tested OverdriveNTool v0.2.6. and got it to work fine using a dummy profile (different values) so then profile with correct values will work fine lowering power consumption all good.  I'm using win10 with 18.4.1 drivers

I leave this information for anyone new to Vega cards no need for soft power tables nor blockchain drivers
for example script at shell:startup

Code:

:overclocking
echo Applying overclocking...

start OverdriveNTool.exe -p1Vega56dummy
start OverdriveNTool.exe -p2Vega56dummy
start OverdriveNTool.exe -p3Vega56dummy
start OverdriveNTool.exe -p4Vega56dummy
start OverdriveNTool.exe -p5Vega56dummy
start OverdriveNTool.exe -p6Vega56dummy
start OverdriveNTool.exe -p7Vega56dummy

start OverdriveNTool.exe -p1Vega56
start OverdriveNTool.exe -p2Vega56
start OverdriveNTool.exe -p3Vega56
start OverdriveNTool.exe -p4Vega56
start OverdriveNTool.exe -p5Vega56
start OverdriveNTool.exe -p6Vega56
start OverdriveNTool.exe -p7Vega56

echo Starting miner...
start /MAX cast_xmr_monero.bat

[treanski]

Hey Guys,

i 1330h considered as good hashrate speed capped at 65c
4x Vega 56 running 6600h

running

P7 1407/875
P3 930/875
Max temp 65
Power Target -22

rock stable @ CN-Heavy

4 x 1330 = 5320h...
so how you come to 6600?

[oarsman]

Hello guys, my miner hangs at the beginning " initializing gpu, loading kernel... " . Claymore does the same thing. Any ideas please?


https://ibb.co/mi5yiJ

[SpceGhst]

Hello guys, my miner hangs at the beginning " initializing gpu, loading kernel... " . Claymore does the same thing. Any ideas please?

Odds are bad card.  Did you recently add one?  I’ve got 2 cards that work fine just in Windows, but try to run a mining program and it just hangs like that.

[angelbbs]

castxmr supports failover pools?

[AlexanderDumas]

castxmr supports failover pools?

Yes.

[BroganBloodstone]

Dev must have went on a holiday after releasing 1.0 

Hopefully we can get a new updated version soon.

[KolordZ]

Hi guys ! 

I'm using this miner too and I would like to know something about it. I have 2x Sapphire RX Vega 64 Nitro+ and i'm using Cast XMR 1.0.0 with options : fast job switching mode enable and max card memory option enable. My driver version for my cards is 18.5.1. Windows 10 Pro x64 1803.

In Wattman I'm using this options :

Core Frequency: -10%
Memory Clock: 1105 MHz
Power Limit: +20%

I've got 3115 H/s. I think it's bad because I have RX Vega 64 Nitro+ and I'm pretty sure i can get more with this card.. Someone here using this cards too ? Should I change something in my config to get a better hashrate ? I don't find any informations on google..

Thanks for your help !

P. S : I don' tknow how to turn off the blue led on my cards, if anybody knows let me know please ! 

[6950TO7950]

Hi guys ! 

I'm using this miner too and I would like to know something about it. I have 2x Sapphire RX Vega 64 Nitro+ and i'm using Cast XMR 1.0.0 with options : fast job switching mode enable and max card memory option enable. My driver version for my cards is 18.5.1. Windows 10 Pro x64 1803.

In Wattman I'm using this options :

Core Frequency: -10%
Memory Clock: 1105 MHz
Power Limit: +20%

I've got 3115 H/s. I think it's bad because I have RX Vega 64 Nitro+ and I'm pretty sure i can get more with this card.. Someone here using this cards too ? Should I change something in my config to get a better hashrate ? I don't find any informations on google..

Thanks for your help !

P. S : I don' tknow how to turn off the blue led on my cards, if anybody knows let me know please ! 

You surely need to do the opposite from what settings you have, iow up the frequency close to 1400MHz for the core and 1100MHz for the memory and lower the power limit at least at -20% (maybe -30%) and lower the voltage also to 0.9V for both core and memory.

[KolordZ]

Hi guys ! 

I'm using this miner too and I would like to know something about it. I have 2x Sapphire RX Vega 64 Nitro+ and i'm using Cast XMR 1.0.0 with options : fast job switching mode enable and max card memory option enable. My driver version for my cards is 18.5.1. Windows 10 Pro x64 1803.

In Wattman I'm using this options :

Core Frequency: -10%
Memory Clock: 1105 MHz
Power Limit: +20%

I've got 3115 H/s. I think it's bad because I have RX Vega 64 Nitro+ and I'm pretty sure i can get more with this card.. Someone here using this cards too ? Should I change something in my config to get a better hashrate ? I don't find any informations on google..

Thanks for your help !

P. S : I don' tknow how to turn off the blue led on my cards, if anybody knows let me know please ! 

You surely need to do the opposite from what settings you have, iow up the frequency close to 1400MHz for the core and 1100MHz for the memory and lower the power limit at least at -20% (maybe -30%) and lower the voltage also to 0.9V for both core and memory.

Hi !

Thanks for your help

What do you mean about "lower the voltage also to 0.9V" ? I can only change GPU Voltage to + or - in mV