VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.

[miner1337]

How do you make them mine monero with 4 and something else with the other two?

A friend with 5 found a solution, that is working (at least for him). I am going to try it with the next restart.
After reboot - change virtual ram size. In his case he changed from 90 to 80. But I guess any change would do the trick. And then move sliders and confirm the HBCC size.

For me it worked with 5 once, when I upped the virtual ram from 64 to 80. That info I got from him have not tried yet, as I am very busy today, but will do with the next restart.
In any case, to make 6 work, it seems we need 96 or more virtual ram, and I simply don't have that much space on the SSD. Someone with bigger SSD should try it.

Isolate the two bads cards, launch Claymore with -di flag to only use those two cards.


You need ~8GB per card of virtual memory.  Just launch xmr-stak-amd with 1 GPU and watch your virtual memory usage jump.  It is linear with each card you add.  Also the virtual memory only appears important when launching xmr-stak-amd.  I will try messing with virtual memory settings and restarting my miner when I get a chance to see if that helps.   With 4xVEGA 64 @ 1900H I need 32GB Virtual Memory.  When I add the other two cards (that refuse HBCC settings) my virtual memory needs hit 48GB.  So it appears all cards are indeed requested 8GB extra memory with our intensity settings however 2 of them are stuck at the low 'non-hbcc' hashrate of 1300H.

TLDR; I don't think we need 96GB of Virtual Mem.  I believe it is 8GB per card.

[1713928564]

1713928564

[1713928564]

1713928564

[1713928564]

1713928564

[1713928564]

1713928564

[1713928564]

1713928564

[l1xx]

How do you make them mine monero with 4 and something else with the other two?

A friend with 5 found a solution, that is working (at least for him). I am going to try it with the next restart.
After reboot - change virtual ram size. In his case he changed from 90 to 80. But I guess any change would do the trick. And then move sliders and confirm the HBCC size.

For me it worked with 5 once, when I upped the virtual ram from 64 to 80. That info I got from him have not tried yet, as I am very busy today, but will do with the next restart.
In any case, to make 6 work, it seems we need 96 or more virtual ram, and I simply don't have that much space on the SSD. Someone with bigger SSD should try it.

Isolate the two bads cards, launch Claymore with -di flag to only use those two cards.


You need ~8GB per card of virtual memory.  Just launch xmr-stak-amd with 1 GPU and watch your virtual memory usage jump.  It is linear with each card you add.  Also the virtual memory only appears important when launching xmr-stak-amd.  I will try messing with virtual memory settings and restarting my miner when I get a chance to see if that helps.   With 4xVEGA 64 @ 1900H I need 32GB Virtual Memory.  When I add the other two cards (that refuse HBCC settings) my virtual memory needs hit 48GB.  So it appears all cards are indeed requested 8GB extra memory with our intensity settings however 2 of them are stuck at the low 'non-hbcc' hashrate of 1300H.

TLDR; I don't think we need 96GB of Virtual Mem.  I believe it is 8GB per card.

Well, the 5th card had never worked for me before I set it from 64 to 80 ... So I don't know. You may be right, you may be not
A thing to note - the ONE time it worked for me, I had disabled onboard video, and connected a monitor to one of the cards.
The guy who has these 5 working, told me that he has all of the other 4 connected one to another with HDMI cables, and the 5th to a monitor. Still after restart it worked for him on 3 only. After restart and change to vram size, all 5 came back online at full speed.

Btw - about crossfire - I noticed, that there is a setting for it only when the card is connected to a Monitor.
But I noticed strange thing - the first card had it ON. I disabled it. Then connected another two cards and they had both off. Have not tried on the others after it. Is that normal?

[Cryptopriest]

But I noticed strange thing - the first card had it ON. I disabled it. Then connected another two cards and they had both off. Have not tried on the others after it. Is that normal?

In amd driverland, everything is normal!

Thats why these are called beta drivers.

BTW, anybody tried driver clean reinstall with all cards plugged in?

[B{_}rg1]

Is it better for Vega to use the new 17.9.3 drivers if you have 4 vegas and 2 rx580. It is impossible to get the HBCC working on more than 2 vegas even having 16 Gb RAM + 80Gb virtual mem with the blockchain drivers...

[miner1337]

On blockchain drivers, 8GB of system RAM, 48GB of Virtual mem.  I can enable HBCC on 4/6 Vega 64's without issue.  I can in rare cases after a full clean reinstall get 5/6 cards to work.  RAM and VMEM is not the issue here.  Shot my Virtual mem up to 96GB and my system mem up to 32GB.  Same outcome. 4/6 can HBCC, 2 cannot.

[Truthchanter]

I'm just getting into the vega+cryptonight scene.. So is this issue about only 4 out of 6 vega gpus having low hashrate specific to a few users or ALL windows users currently?

[Zorg33]

probably all. including me too.

I once had 5/6 hashing at around 1800/card, but I couldn't repeat that ever again.
I'm back on normal driver now on ethash, I got fed up with the buggy BC driver.

BTW I could turn on HBCC for all 6 cards, but only 4 of them had the slider.

[FFI2013]

I was thinking about buying some vega 64 or 1080ti how does the vega hash on other algo's

[miner1337]

I'm just getting into the vega+cryptonight scene.. So is this issue about only 4 out of 6 vega gpus having low hashrate specific to a few users or ALL windows users currently?

The issue is 2/6 cards are hashing monero as if HBCC is disabled (so ~1300H).

4/6 cards are hashing proper (~1900H).

At the moment I am just not mining monero with the 2 that hash low due to HBCC not enabling.

This issue appears widespread.  Other forums have other people complaining about the same.  

The best I've had is 5/6 working but only after a full clean install, first reboot after the clean install and I am back to 4/6.

I should probably move to AMD forums and start asking them for help.  The right people might see it and fix it officially.  I am positive it is a driver issue and can be addressed.

[Truthchanter]

anyone know if it's possible with 1 rig to have some amd (vega) gpus mining xmr and also have nvidia gpus mining equihash? thinking of going this route as a bandaid for this HBCC problem

[Trade_BTC]

Good thing when I ordered parts for my new rig I grabbed a 500 GB SSD which I never do. Thanks to all in this thread you may have saved me a headache.

[Trade_BTC]

Ok 8 Vega 56 and even tho it says hbcc is working on 6 it's not. Tested 3 and hashes at 1840 per with 8 they hover around 1350 for all. This is more than likely a combo of amd drivers and perhaps pcie bios settings or lane limitation. Someone more creative than us hopefully figures it out and shares.

[miner1337]

Yeah no luck fixing this so far.  Has nothing to do with Virtual mem or ram at this point.  8GB of ram to enable HBCC.  8GB of Virtual mem per card to run xmr-stak-amd with the intensity settings to hit 1900H.

Now something weird I've noticed.

Roughly every 24 hours of mining the two cards that refuse to enable HBCC and hash at 1300H suddenly hash at 1900H for ~10min then drop back down.

I am going to try to enable to web client for xmr-stak-amd and write a scraper to monitor the hashrate more closely than I can by randomly checking up on it.  Also appears you can have it write the hashrate out to a file, that might be easiest.

[miner1337]

The only correlation I can find for the random gain of +1200H once a day is it appears to time with

Just to be clear with 6xVEGA 64.

4@1900H + 2@1300H (due to HBCC not enabling), total of 10200H.  Randomly every day it jumps to 11500H for a short period.  The only correlation I can find in the system logs is Windows Defender Updates.

Very strange.

[l1xx]

Yeah no luck fixing this so far.  Has nothing to do with Virtual mem or ram at this point.  8GB of ram to enable HBCC.  8GB of Virtual mem per card to run xmr-stak-amd with the intensity settings to hit 1900H.

Now something weird I've noticed.

Roughly every 24 hours of mining the two cards that refuse to enable HBCC and hash at 1300H suddenly hash at 1900H for ~10min then drop back down.

I am going to try to enable to web client for xmr-stak-amd and write a scraper to monitor the hashrate more closely than I can by randomly checking up on it.  Also appears you can have it write the hashrate out to a file, that might be easiest.

I've seen that too, as randomly my max hashrate is 11500 instead of the usual 10000 that I am on. But no idea if that was for a second, minute or more.
The worse thing about this shit is that you cannot combine 4 vegas with other AMD cards, as it still does not work afterwards on all 4. So either 4 vega or you should add nvidia cards, but that does not really sound like a realistic option, as currently nvidia cards are too overpriced.

Or maybe , the whole thing is a visual glitch, and the 5 cards where I see a HBCC slider enabled, are indeed hashing at around 1900 ea. As how can you explain this? http://prntscr.com/gwokm2
I've had such values , over the 10000-10020 that I see on the console the whole time since my last restart 5 days ago. And on top of that I have only 96% good results .

[miner1337]

Yeah no luck fixing this so far.  Has nothing to do with Virtual mem or ram at this point.  8GB of ram to enable HBCC.  8GB of Virtual mem per card to run xmr-stak-amd with the intensity settings to hit 1900H.

Now something weird I've noticed.

Roughly every 24 hours of mining the two cards that refuse to enable HBCC and hash at 1300H suddenly hash at 1900H for ~10min then drop back down.

I am going to try to enable to web client for xmr-stak-amd and write a scraper to monitor the hashrate more closely than I can by randomly checking up on it.  Also appears you can have it write the hashrate out to a file, that might be easiest.

I've seen that too, as randomly my max hashrate is 11500 instead of the usual 10000 that I am on. But no idea if that was for a second, minute or more.
The worse thing about this shit is that you cannot combine 4 vegas with other AMD cards, as it still does not work afterwards on all 4. So either 4 vega or you should add nvidia cards, but that does not really sound like a realistic option, as currently nvidia cards are too overpriced.

Or maybe , the whole thing is a visual glitch, and the 5 cards where I see a HBCC slider enabled, are indeed hashing at around 1900 ea. As how can you explain this? http://prntscr.com/gwokm2
I've had such values , over the 10000-10020 that I see on the console the whole time since my last restart 5 days ago. And on top of that I have only 96% good results .

Same with 96% good result. 

Your screenshot basically mirrors my exact avg hash rates on nanopool, ~10500.  My reported is almost always 10200 but on nanopool it always averages 10500 or higher. 

I imagine we both have the same setup using the soft power table mod.

[l1xx]

check the web stats of the xmr stak using another device on your network, not the rig itself, so you can read the values real time without touching the console to see whats up. I have not done taht yet, as I need to have physical access to the router.

we have a bit different settings for sure, but its all odd ... I have modded 5 cards - 1220/1100. The sixt is manually adjusted with wattman to 1220/1030 , but its showing even better results, drawing probably more power, but it is what it is.
Also, I am at 1800/1600 intensity, as the thing was crashing after a while on 2016/1600, so I moved it a bit under, and its stable for around a week like this.

[bytiges]

Have you tried using some ridiculous amount of VM like 256GB, or say 128GB or real memory ?
Would be interesting to know if it makes a difference.

[teuflor]

do you try the new driver 17.10.2? probl. the problem is gone?

[stueng]

do you try the new driver 17.10.2? probl. the problem is gone?

I have just tried this with the same outcome, 4/6 cards will enable. What I have noticed is that 2/4 of the cards display as "unknown" under the PCI Bus in System whereas 4/6 show as PCI-E v3.0. So the cards/driver cannot read the PCI bus properly?