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

[skablast]

But how much is your power consumption at the wall ?
It seem very high to me

[1714909156]

1714909156

[1714909156]

1714909156

[1714909156]

1714909156

[1714909156]

1714909156

[1714909156]

1714909156

[1714909156]

1714909156

[bubaba]

I am having an issue with getting the miner to work at all.

I have two vega 56's and I have done circusdad's instructions (among others) and everything runs fine until I connect to a pool. Once it connects my computer locks up. I have tried sooooo many settings and drivers. I'm at my wits end.

Has anyone else run into this? I can not get these things to mine XMR without my computer immediately freezing up.

Thanks guys!

Have you tried mining other cryptonight coins? If not, that would be a good place to start, just to ensure that the issue is not with the miner. Make sure you have installed the latest AMD drivers for your graphics card, and ensure that they are not OC'd to begin with. Try a different XMR pool if possible, i use dwarf, and have had no issues with them so far. Thermal issues seem to be the likely issue here.

I have tried different pools and different coins. Some other algo's work but I can't get cryptonight to work at all.

I have stock settings and have tried blockchain, older and latest drivers. I used DDU to uninstall in between too. Sooo frustrating

Where is your Screen plugged in?
DDU using in safeMode ?
Not applying 64 tables instead of 56 tables?
Your cards are detected in OverdriveNtool?
PSU has enough Power?
Tested each cards individually?

[AlexanderDumas]

But how much is your power consumption at the wall ?
It seem very high to me

at 1950Hs it should be around 140/150W per card + 80/90W for MB, CPU, Mem etc...
at least that is what i get.

[glph3k]

Hi,

an Cast XMR update is available.

The main reason for the update is the integration of the PoW changes to CryptoNight for the Monero V7 network upgrade which are documented here:

https://github.com/monero-project/monero/pull/3253

The Monero V7 network upgrade is planned to be end of march, an exact and final block height is not set yet. So stay up to date!

Regards,
glph3k


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 decrease 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)


Download Cast XMR 0.9.0 for Windows (64bit)

cast_xmr-vega-win64_090.zip SHA256 fingerprint:
49fe7e231cf5d4434c5d0fcb69af261a6e4e7340441d4d6ad9f4022854e38027

[Bhaal1]

Hi,

an Cast XMR update is available.

The main reason for the update is the integration of the PoW changes to CryptoNight for the Monero V7 network upgrade which are documented here:

https://github.com/monero-project/monero/pull/3253

The Monero V7 network upgrade is planned to be end of march, an exact and final block height is not set yet. So stay up to date!

Regards,
glph3k


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 decrease 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)


Download Cast XMR 0.9.0 for Windows (64bit)

cast_xmr-vega-win64_090.zip SHA256 fingerprint:
49fe7e231cf5d4434c5d0fcb69af261a6e4e7340441d4d6ad9f4022854e38027

Thanks!

[dudee]

my result with Asus RX580 8GB 1350/2020
speed 1050-1080 H/s   bit better then claymore.

[dlezama]

There is some trouble with version 0.9.0 and Nicehash. It goes back and forth between working fine and all shares being rejected. I rolled back to 0.8.5, but I'm concerned as the date for the Monero V7 hard-fork approaches.

[glph3k]

There is some trouble with version 0.9.0 and Nicehash. It goes back and forth between working fine and all shares being rejected. I rolled back to 0.8.5, but I'm concerned as the date for the Monero V7 hard-fork approaches.

Using Nicehash all the time, no problems.

With which error messages are they rejected?

How many GPUs?

Which pool?

[BogdanCo]

There is some trouble with version 0.9.0 and Nicehash. It goes back and forth between working fine and all shares being rejected. I rolled back to 0.8.5, but I'm concerned as the date for the Monero V7 hard-fork approaches.

I'm using 0.9.0 and Nicehash and until now no issues.

[dlezama]

There is some trouble with version 0.9.0 and Nicehash. It goes back and forth between working fine and all shares being rejected. I rolled back to 0.8.5, but I'm concerned as the date for the Monero V7 hard-fork approaches.

Using Nicehash all the time, no problems.

With which error messages are they rejected?

How many GPUs?

Which pool?

Unfortunately I didn't capture the output and I don't remember the error. I do remember reading "New Job received (CryptoNight V7)". I thought that was odd, since V7 hasn't been deployed yet right? The rig is a 6 x RX Vega 56.

I switched back to 0.9.0 and so far it has been working fine. I'll keep an eye and report back if it fails again.

[dlezama]

There is some trouble with version 0.9.0 and Nicehash. It goes back and forth between working fine and all shares being rejected. I rolled back to 0.8.5, but I'm concerned as the date for the Monero V7 hard-fork approaches.

Using Nicehash all the time, no problems.

With which error messages are they rejected?

How many GPUs?

Which pool?

Unfortunately I didn't capture the output and I don't remember the error. I do remember reading "New Job received (CryptoNight V7)". I thought that was odd, since V7 hasn't been deployed yet right? The rig is a 6 x RX Vega 56.

I switched back to 0.9.0 and so far it has been working fine. I'll keep an eye and report back if it fails again.

It happened again, definitely a problem with V7 jobs. In the fragment below you see the miner reconnecting, but I looked through the log and other times it started working when I received a non-V7 job, without the connection dropping.

Code:

[18:53:46] New Job received (CryptoNight). Avg Job Time: 79.2 sec
[18:54:26] GPU2 Found Nonce, submitting...
[18:54:26] Share Accepted -> +1
[18:54:26] Shares: 455 Accepted, 0 Errors | Hash Rate Avg: 11498.9 H/s | Avg Search Time: 38.7 sec
[18:55:35] New Job received (CryptoNight). Avg Job Time: 79.3 sec
[18:55:56] New Job received (CryptoNight). Avg Job Time: 79.1 sec
[18:57:21] New Job received (CryptoNight). Avg Job Time: 79.1 sec
[18:58:23] New Job received (CryptoNightV7). Avg Job Time: 79.0 sec
[18:58:23] Difficulty changed. Now: 400015.
[18:58:33] GPU5 Found Nonce, submitting...
[18:58:33] !Rejected by pool! Reason: Share above target.
[18:58:33] Shares: 455 Accepted, 1 Errors | Hash Rate Avg: 11499.1 H/s | Avg Search Time: 39.3 sec
[18:59:16] New Job received (CryptoNightV7). Avg Job Time: 78.9 sec
[18:59:28] GPU1 Found Nonce, submitting...
[18:59:28] !Rejected by pool! Reason: Share above target.
[18:59:28] Shares: 455 Accepted, 2 Errors | Hash Rate Avg: 11499.3 H/s | Avg Search Time: 39.4 sec
[19:00:08] GPU5 Found Nonce, submitting...
[19:00:08] !Rejected by pool! Reason: Share above target.
[19:00:08] Shares: 455 Accepted, 3 Errors | Hash Rate Avg: 11499.2 H/s | Avg Search Time: 39.5 sec
[19:00:33] GPU4 Found Nonce, submitting...
[19:00:33] !Rejected by pool! Reason: Share above target.
[19:00:33] Shares: 455 Accepted, 4 Errors | Hash Rate Avg: 11499.2 H/s | Avg Search Time: 39.5 sec
[19:00:41] SOCKET ERROR - RECEIVE error: socket closed
[19:00:41] Connecting to Pool failed. Retrying in 20 secs ...
[19:01:02] Connecting to cryptonight.usa.nicehash.com:3355 ...
[19:01:02] Connected to pool.
[19:01:02] New Job received (CryptoNight).
[19:01:02] Difficulty changed. Now: 200007.
[19:01:08] GPU2 Found Nonce, submitting...
[19:01:08] Share Accepted -> +1
[19:01:08] Shares: 456 Accepted, 4 Errors | Hash Rate Avg: 11611.3 H/s | Avg Search Time: 39.5 sec

[Rabinovitch]

Damn! Why does my 2 Vegas 56 are starting to mine at 1900, but then (after 15-20 minutes) the hashrate is falling to 1650-1660 H/s? Right after miner restart (without any additional moves like disabling/enabling the GPUs) it becomes 1900 again. May be it's a well-known issue and it can be fixed in several seconds? 

[glph3k]

It happened again, definitely a problem with V7 jobs. In the fragment below you see the miner reconnecting, but I looked through the log and other times it started working when I received a non-V7 job, without the connection dropping.

Code:

[18:53:46] New Job received (CryptoNight). Avg Job Time: 79.2 sec
[18:54:26] GPU2 Found Nonce, submitting...
[18:54:26] Share Accepted -> +1
[18:57:21] New Job received (CryptoNight). Avg Job Time: 79.1 sec
[18:58:23] New Job received (CryptoNightV7). Avg Job Time: 79.0 sec
[18:58:23] Difficulty changed. Now: 400015.
[18:58:33] GPU5 Found Nonce, submitting...
[18:58:33] !Rejected by pool! Reason: Share above target.

Hi,

thanks, that is indeed interesting.

There seem to be CryptoNote currencies around and in the mix of nicehash.com that already use the version 7 flags.

The version 7 flag is used in Monero for switching to the new PoW hash, which then clashes with other currencies that have also a version 7 but uses classic CrypthoNight.

Will have to find out which currencies that is/are.

The problem is not only cast XMR related, but a general problem of nicehash.com and/or CryptoNight hashing.

Sorry, bleeding edge, probably one of the first to encounter. Will report on the Monero forums.

To fix the current issue with cast XMR when using nicehash.com is to use the "--algo=0" flag, to force the current CryptoNight PoW.


Regards,
glph3k

[glph3k]

Damn! Why does my 2 Vegas 56 are starting to mine at 1900, but then (after 15-20 minutes) the hashrate is falling to 1650-1660 H/s? Right after miner restart (without any additional moves like disabling/enabling the GPUs) it becomes 1900 again. May be it's a well-known issue and it can be fixed in several seconds? 

It is a know issue. Maybe related to heating or some internal driver problem. A fix is to use a mining monitor like:

https://github.com/anadventureisu/cast-xmr-ui

It will automatically detect the drop and restart cast XMR.

[glph3k]

Hi,

found the coin that has problems with CryptoNightV7: GRAFT

https://www.graft.network/

It reports that it is CryptoNote V7, but relies on the classic CryptoNight hash.

Unfortunatly nicehash.com has Graft in its CryptoNight mix.

So in case you want to mine successful Graft or are using nicehash.com, please use the --algo=0 switch for cast XMR 0.9.0.

Will try to sort it out in the next update.

regards,
Glph3k

It happened again, definitely a problem with V7 jobs. In the fragment below you see the miner reconnecting, but I looked through the log and other times it started working when I received a non-V7 job, without the connection dropping.

Code:

[18:53:46] New Job received (CryptoNight). Avg Job Time: 79.2 sec
[18:54:26] GPU2 Found Nonce, submitting...
[18:54:26] Share Accepted -> +1
[18:57:21] New Job received (CryptoNight). Avg Job Time: 79.1 sec
[18:58:23] New Job received (CryptoNightV7). Avg Job Time: 79.0 sec
[18:58:23] Difficulty changed. Now: 400015.
[18:58:33] GPU5 Found Nonce, submitting...
[18:58:33] !Rejected by pool! Reason: Share above target.

Hi,

thanks, that is indeed interesting.

There seem to be CryptoNote currencies around and in the mix of nicehash.com that already use the version 7 flags.

The version 7 flag is used in Monero for switching to the new PoW hash, which then clashes with other currencies that have also a version 7 but uses classic CrypthoNight.

Will have to find out which currencies that is/are.

The problem is not only cast XMR related, but a general problem of nicehash.com and/or CryptoNight hashing.

Sorry, bleeding edge, probably one of the first to encounter. Will report on the Monero forums.

To fix the current issue with cast XMR when using nicehash.com is to use the "--algo=0" flag, to force the current CryptoNight PoW.


Regards,
glph3k

[Eisenkopf89]

Damn! Why does my 2 Vegas 56 are starting to mine at 1900, but then (after 15-20 minutes) the hashrate is falling to 1650-1660 H/s? Right after miner restart (without any additional moves like disabling/enabling the GPUs) it becomes 1900 again. May be it's a well-known issue and it can be fixed in several seconds? 

The heat from the HBM2 is the problem. Try to run the Fans between 80-100% when  you have the referenz cooler. Otherwise 60% in other cards like Nitro+ cards vor red devil...

[AlexanderDumas]

my result with Asus RX580 8GB 1350/2020
speed 1050-1080 H/s   bit better then claymore.

RX580 with Samsung memory I guess....?
Mines cannot get over 890/910hs, so they are pointed to Ethereum...

[dlezama]

Hi,

found the coin that has problems with CryptoNightV7: GRAFT

https://www.graft.network/

It reports that it is CryptoNote V7, but relies on the classic CryptoNight hash.

Unfortunatly nicehash.com has Graft in its CryptoNight mix.

So in case you want to mine successful Graft or are using nicehash.com, please use the --algo=0 switch for cast XMR 0.9.0.

Will try to sort it out in the next update.

regards,
Glph3k

Looks like I hit a real unknown issue, exciting actually I'll use --algo=0 for now.

[visten]

I am not into the advantages of the Vega 56 card, but did I get it right that it can hash with an updated 64 BIOS that it can mine regulary 2000 Hash/s?
It seems that mining monero with the Vega 56 is much more profitable than anything else or do I get something wrong ?

I need to decide if I should add some 1070 cards for 480 Euro per piece or rx Vega 56 cards for 670 Euro per piece to my rig?? What are you guys suggesting?

[Rabinovitch]

The heat from the HBM2 is the problem. Try to run the Fans between 80-100% when  you have the referenz cooler. Otherwise 60% in other cards like Nitro+ cards vor red devil...

The fans are spinning at ~90% already (reference design)...