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

[ingyenfrag]

Hashrate on cnv8 has cratered. Vega 64s/blockchain drivers/HBCC enabled. intensity 7. hashing at under 1k...

This is a known problem with the blockchain drivers. Update to 18.5.1, they are more stable and don't need the hardware reset trick and will fix performance with V8. HBCC should be turned off. Vega64 can go with intensity 9 if used headless (no desktop running on it),

18.5.1 exactly or any newer one?

Can recommend 18.5.1 .

Later ones (including 18.10.1) only run with lower intensity settings if a desktop is running on the card. But try for yourself.

I believe you.
Until today I used the blockchain. A few month ago I've tried the 18.7.1 but it was a little bit slower but at least the consumption was a little bit better.

[Yerba]

Hashrate on cnv8 has cratered. Vega 64s/blockchain drivers/HBCC enabled. intensity 7. hashing at under 1k...

This is a known problem with the blockchain drivers. Update to 18.5.1, they are more stable and don't need the hardware reset trick and will fix performance with V8. HBCC should be turned off. Vega64 can go with intensity 9 if used headless (no desktop running on it),

18.5.1 exactly or any newer one?

Can recommend 18.5.1 .

Later ones (including 18.10.1) only run with lower intensity settings if a desktop is running on the card. But try for yourself.

Any real information, that with 18.5.1 hashrate drops only 10%, not from 2000 to 600?

[huntingthesnark]

Hashrate on cnv8 has cratered. Vega 64s/blockchain drivers/HBCC enabled. intensity 7. hashing at under 1k...

This is a known problem with the blockchain drivers. Update to 18.5.1, they are more stable and don't need the hardware reset trick and will fix performance with V8. HBCC should be turned off. Vega64 can go with intensity 9 if used headless (no desktop running on it),

Hmmm. That seems to have worked for all but two of the gpus, which are still hashing in the low hundreds. I did DDU, and device manager says all vegas are using hte same driver...

[carlosmonaco]

Hello,
All my Vega are now around 650h/s instead of 2000h/s , I tried to lower intensity but no effect. How to achieve 1800h/s and above on V8 ?

[ingyenfrag]

Hashrate on cnv8 has cratered. Vega 64s/blockchain drivers/HBCC enabled. intensity 7. hashing at under 1k...

This is a known problem with the blockchain drivers. Update to 18.5.1, they are more stable and don't need the hardware reset trick and will fix performance with V8. HBCC should be turned off. Vega64 can go with intensity 9 if used headless (no desktop running on it),

18.5.1 exactly or any newer one?

Can recommend 18.5.1 .

Later ones (including 18.10.1) only run with lower intensity settings if a desktop is running on the card. But try for yourself.

Any real information, that with 18.5.1 hashrate drops only 10%, not from 2000 to 600?

It works, but when i want to set the core clock to 1408 MHz in OverdriveNTool it only runs at around 1330MHz and it gives ~1600 H/s per GPU.
If I set the core clock to 1450MHz it runs at 1380MHz anf makes ~1700 H/s per GPU.

--intensity=7  results ~1830 H/s --> "If I set the core clock to 1450MHz it runs at 1380MHz"
--intensity=6  results ~1770 H/s --> "If I set the core clock to 1450MHz it runs at 1380MHz"
--intensity=8  results ~1750 H/s --> "If I set the core clock to 1450MHz it runs at 1380MHz"

[HansHagberg]

Just ran into the problems with hashrate/V8/blockchain driver

So we need to finally update drivers. For a Vega owner, that may result in endless pain and lifelong suffering but ok...

Do the new drivers work with powerplay tables and other tricks we are used to?

[huntingthesnark]

Just ran into the problems with hashrate/V8/blockchain driver

So we need to finally update drivers. For a Vega owner, that may result in endless pain and lifelong suffering but ok...

Do the new drivers work with powerplay tables and other tricks we are used to?

I know. It's all very well saying 'update your drivers' but as we all know, with Vegas that's just the beginning of a cosmic battle.

[Dscha]

RX580s (Samsung) lowered from 948 to 908 and Power Usage went up from 610W to 710W (Core: 1250/900 | Mem: 1950/850)... I guess, it's time to tinker around again.

(Win10 / 18.5.1 Driver / CastXMR 1.5.0 / using OverdriveNTool)

[huntingthesnark]

Hashrate on cnv8 has cratered. Vega 64s/blockchain drivers/HBCC enabled. intensity 7. hashing at under 1k...

This is a known problem with the blockchain drivers. Update to 18.5.1, they are more stable and don't need the hardware reset trick and will fix performance with V8. HBCC should be turned off. Vega64 can go with intensity 9 if used headless (no desktop running on it),

Hmmm. That seems to have worked for all but two of the gpus, which are still hashing in the low hundreds. I did DDU, and device manager says all vegas are using hte same driver...

Like a bad nightmare, 'disable crossfire, disable upls' has floated into my head... Which hasn't worked. Bastard Vegas.

[ntshb]

Hashrate on cnv8 has cratered. Vega 64s/blockchain drivers/HBCC enabled. intensity 7. hashing at under 1k...

This is a known problem with the blockchain drivers. Update to 18.5.1, they are more stable and don't need the hardware reset trick and will fix performance with V8. HBCC should be turned off. Vega64 can go with intensity 9 if used headless (no desktop running on it),

i've set the switch-radeon-gpu --hbcc=off  but cast xmr still says hbcc is on

[kristikun]

Just ran into the problems with hashrate/V8/blockchain driver

So we need to finally update drivers. For a Vega owner, that may result in endless pain and lifelong suffering but ok...

Do the new drivers work with powerplay tables and other tricks we are used to?

I have vegas 56 biosed to 64... 5x and 1x 64 watercooled
So i already updated the drivers did the registry power play thingy , didn´t  even neeed to disable crossfire , tested V8 had 1600h on each 56vega  got the intensity to 7 and 1820-1870 on each vega (180W) was used to 1940-1960 with this powerplay  ,  Did the same thing for my Watercooled 64  without powerplay  1790-1860 ( intensity 9 , diff intensity 1600-1700 )

[cromsps]

Well my Vegas are running @ ~900Khs lool

And when I run cast xmr (last version) it says Gfx900(?) , can anyone confirm this ? it was supposed to say Gfx901(?)

[glph3k]

Hashrate on cnv8 has cratered. Vega 64s/blockchain drivers/HBCC enabled. intensity 7. hashing at under 1k...

This is a known problem with the blockchain drivers. Update to 18.5.1, they are more stable and don't need the hardware reset trick and will fix performance with V8. HBCC should be turned off. Vega64 can go with intensity 9 if used headless (no desktop running on it),

i've set the switch-radeon-gpu --hbcc=off  but cast xmr still says hbcc is on

Did you add a restart or autorestart command to switch-radeon-gpu?

It should be  "switch-radeon-gpu --hbcc=off autorestart" to also reset the device? If yes and the device is not resetting try a reboot.

[glph3k]

Well my Vegas are running @ ~900Khs lool

And when I run cast xmr (last version) it says Gfx900(?) , can anyone confirm this ? it was supposed to say Gfx901(?)

A Vega lists as

gfx901 when HBCC is on

gfx900 when HBCC is off

[cromsps]

A Vega lists as

gfx901 when HBCC is on

gfx900 when HBCC is off

Thanks, I did not know that :-)

I am going to update the drivers (I have the Blockchain) and test it like we're talking about here :-)

Thanks once more,

[moskillo]

i have a vega56 rig, and i tried to setup cast-xmr-vega with nicehash:

Code:

cast_xmr-vega -S cryptonight.usa.nicehash.com:3355 -u Wallet.Worker  -p "" -G 0,1,2

works (1,83 kh/s), but in nicehash web the worker show active but speed=0..... its working or not?

[ingyenfrag]

For me the same settings consumes more power with the new CNv8. 1175W-->1260W. It's more than 7% increase (for a 6 card rig with bad ASIC quality GPU-s).
Anyone experiencing similar changes?

[sympatiq]

For me the same settings consumes more power with the new CNv8. 1175W-->1260W. It's more than 7% increase (for a 6 card rig with bad ASIC quality GPU-s).
Anyone experiencing similar changes?

Same for me 1500 W to 1740W 8 card vega rig.From what i see the profitability is about the same with V7.

[cromsps]

i have a vega56 rig, and i tried to setup cast-xmr-vega with nicehash:

Code:

cast_xmr-vega -S cryptonight.usa.nicehash.com:3355 -u Wallet.Worker  -p "" -G 0,1,2

works (1,83 kh/s), but in nicehash web the worker show active but speed=0..... its working or not?

Hello,

Nicehash wiil give you the speed only when accepting shares... did you wait a little before post ?

Second, if you are trying to use V8, your server and port is not right... search on their website for the right server and port :-)

[ntshb]

Hashrate on cnv8 has cratered. Vega 64s/blockchain drivers/HBCC enabled. intensity 7. hashing at under 1k...

This is a known problem with the blockchain drivers. Update to 18.5.1, they are more stable and don't need the hardware reset trick and will fix performance with V8. HBCC should be turned off. Vega64 can go with intensity 9 if used headless (no desktop running on it),

i've set the switch-radeon-gpu --hbcc=off  but cast xmr still says hbcc is on

Did you add a restart or autorestart command to switch-radeon-gpu?

It should be  "switch-radeon-gpu --hbcc=off autorestart" to also reset the device? If yes and the device is not resetting try a reboot.

yes i did

this is my run.bat
switch-radeon-gpu --hbcc=off autorestart
cast_xmr-vega --algo=-1 -S xmr-us-east1.nanopool.org:14444 --intensity 7 -G 0,1,2,3,4,5 -u worker.name --fastjobswitch           


I typed the same thing in the jj reset and run because I need it to set the fan profile and speed in ODNT (im using the older reg mod)