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

[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.

Anybody else having a similar issue? 5card vega rig, updated drivers, 3 cards running as standard, 2 running at 120 and 300h/s. DDUed several times, crossfire etc disabled, HBCC on or off makes no difference. intensity set to 7... Arrrgh.

[thebluez]

i have error somethink
Ubuntu 16.04 , vega64 (6GPU)

"
Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2679.0)
Driver Version OK.
GPU0: gfx900 (card1) | 64 Compute Units | Memory (MB): 8176 | Intensity: 7 / 10
Error clBuildProgramm -11
"

plz help

[glph3k]

i have error somethink
Ubuntu 16.04 , vega64 (6GPU)

"
Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2679.0)
Driver Version OK.
GPU0: gfx900 (card1) | 64 Compute Units | Memory (MB): 8176 | Intensity: 7 / 10
Error clBuildProgramm -11
"

plz help

Sure you are on the AMD GPU Pro driver not the Rocm version?

Did you install the driver with:

./amdgpu-pro-install -y --opencl=pal

?

[cromsps]

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"

Without the OverdriveNTool, directly on AMD Software,

Vega 56 -> -2 power, -2 core, @950   1860 H/s
Vega 64 -> -3 power -3 core, @1025  1800 H/s

But yes, more power and less H/s, wich means less Profit

[rainbowfcc]

I turned my rig to v8 and getting around %6-8 more "share above target" error with same settings of v7.. is there a way to fix it? anyone having same issue?

(because of high of this error, i changed my rig back to cryptonight heavy for better profit.. i got %100 accepted shares with crypthonight heavy with same settings )

[xADMIRALx]

hello guys,i switched from the old version of cast-xmr to the new 1.5.0, did not change the startup parameters, everything was the same, only the exe file was replaced, and the hashrate decreased from 1900h / s to 800 h / s, help to understand what the problem is? HBCC on

[DgDamis]

Hey Guys,
I managed to process through the network upgrade flawlessly.
After the initial block, I stopped mining CryptoNightV7 and ran an updated bat file.
I use NiceHash and the only thing I needed to do was to change a server address and port.

Overall my hashrate dropped around 5% and power consumption increased up to 25W more for a single card (8% increase).

Adrenalin Driver 18.10.1
HBCC Off
Cast XMR 1.5.0

[GordoLui]

I've also been having issues after the fork. The systems I got working are all hashing around 100-200 sols less than before. And some dont even begin. Been troubleshooting all morning long and slowly making progress. You just got to check everything. Check your drivers, your windows version, and your bat files. Have you guys been trying other drivers? I'm using 18.5.1

I always used the radeon software to configure everything but now i am considering using power table to optimize performance since the gap has gotten a lot bigger.

[cromsps]

I turned my rig to v8 and getting around %6-8 more "share above target" error with same settings of v7.. is there a way to fix it? anyone having same issue?

(because of high of this error, i changed my rig back to cryptonight heavy for better profit.. i got %100 accepted shares with crypthonight heavy with same settings )

I had the same problem when changing to V7, at the time I set the right Algo and got 100% accepted...
This time, I did even try the Autodetect Algo (-1), I put the 10 algo and everything went ok...

[Khaak Ru]

hello guys,i switched from the old version of cast-xmr to the new 1.5.0, did not change the startup parameters, everything was the same, only the exe file was replaced, and the hashrate decreased from 1900h / s to 800 h / s, help to understand what the problem is? HBCC on

same thing

[EscapeV3locity]

hello guys,i switched from the old version of cast-xmr to the new 1.5.0, did not change the startup parameters, everything was the same, only the exe file was replaced, and the hashrate decreased from 1900h / s to 800 h / s, help to understand what the problem is? HBCC on

same thing

I'm in the same boat.

I tried 18.5.1 and 18.6.1 drivers and they both give me around 800 h/s.  I was getting 1850 h/s previously.  I have HBCC=off Large pages=ON. 

I'm sad

[Khaak Ru]

hello guys,i switched from the old version of cast-xmr to the new 1.5.0, did not change the startup parameters, everything was the same, only the exe file was replaced, and the hashrate decreased from 1900h / s to 800 h / s, help to understand what the problem is? HBCC on

same thing

I'm in the same boat.

I tried 18.5.1 and 18.6.1 drivers and they both give me around 800 h/s.  I was getting 1850 h/s previously.  I have HBCC=off Large pages=ON. 

I'm sad

Installed 18.5.1 and now getting 1650 h/s

[Khaak Ru]

hello guys,i switched from the old version of cast-xmr to the new 1.5.0, did not change the startup parameters, everything was the same, only the exe file was replaced, and the hashrate decreased from 1900h / s to 800 h / s, help to understand what the problem is? HBCC on

same thing

I'm in the same boat.

I tried 18.5.1 and 18.6.1 drivers and they both give me around 800 h/s.  I was getting 1850 h/s previously.  I have HBCC=off Large pages=ON. 

I'm sad

Installed 18.5.1 and now getting 1650 h/s

I am at 1850 after some tweaks with ONT

[EscapeV3locity]

hello guys,i switched from the old version of cast-xmr to the new 1.5.0, did not change the startup parameters, everything was the same, only the exe file was replaced, and the hashrate decreased from 1900h / s to 800 h / s, help to understand what the problem is? HBCC on

same thing

I'm in the same boat.

I tried 18.5.1 and 18.6.1 drivers and they both give me around 800 h/s.  I was getting 1850 h/s previously.  I have HBCC=off Large pages=ON. 

I'm sad

Installed 18.5.1 and now getting 1650 h/s

I am at 1850 after some tweaks with ONT

What is ONT?

Can you post a link for everyone so we can look into this ONT.

[side-fish]

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

Thanks a bunch for your continued support. Switching HBCC off worked for me. I was skeptical at first, but you know, I don't quite understand how the inner workings of the miner. Was able to bring my hash from under 900 to under 1800 per Vega 56 with this.

[ntshb]

I am using 18.5.1 and i always encounter the code 43 error after applying the reg mod.

Even if i don't apply the reg mod, the vega 56 runs but the fans don't spin at all and it hangs after a while

[EscapeV3locity]

hello guys,i switched from the old version of cast-xmr to the new 1.5.0, did not change the startup parameters, everything was the same, only the exe file was replaced, and the hashrate decreased from 1900h / s to 800 h / s, help to understand what the problem is? HBCC on

same thing

I'm in the same boat.

I tried 18.5.1 and 18.6.1 drivers and they both give me around 800 h/s.  I was getting 1850 h/s previously.  I have HBCC=off Large pages=ON. 

I'm sad

Installed 18.5.1 and now getting 1650 h/s

I am at 1850 after some tweaks with ONT

I think I know why I may be having these issues, its because I'm using a Vega FE.  Anyone else have hash data on Vega FE?

[linexbee]

Hey Guys,
I managed to process through the network upgrade flawlessly.
After the initial block, I stopped mining CryptoNightV7 and ran an updated bat file.
I use NiceHash and the only thing I needed to do was to change a server address and port.

Overall my hashrate dropped around 5% and power consumption increased up to 25W more for a single card (8% increase).

Adrenalin Driver 18.10.1
HBCC Off
Cast XMR 1.5.0

I'm kinda same
Adrenalin Driver 18.7.1 (not planning to update until i know is stable)
Using soft power tables(not sure if it really helps)
Cast XMR 1.5.0  (algo 10)
HBCC - have no idea, same as it was for V7, didn't touch it for this fork
power: 4 x vega64 liquid cooled ~860W (was 740W on V7)
Hashrate: 7610H/s (was ~7900H/s on V7)

[DobieParty]

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.

Anybody else having a similar issue? 5card vega rig, updated drivers, 3 cards running as standard, 2 running at 120 and 300h/s. DDUed several times, crossfire etc disabled, HBCC on or off makes no difference. intensity set to 7... Arrrgh.

The solution is to run a dummy plug.  When I have a monitor plugged in I have the exact same issue.  Put in an hdmi dummy plug. reboot, and its back to normal

[ntshb]

Do i still need the reg mod even for 18.5.1?