Search content
Sort by
Showing 20 of 36 results by miner1337
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
Even better, a true community hero here:
https://bitcointalk.org/index.php?topic=2002025.msg23619746#msg23619746
Official Blockchain Linux Drivers? Appear to be based on 17.40 where the Windows blockchain drivers are 17.30.
http://support.amd.com/en-us/kb-articles/Pages/AMDGPU-Pro-Beta-Mining-Driver-for-Linux-Release-Notes.aspx
http://support.amd.com/en-us/kb-articles/Pages/AMDGPU-Pro-Beta-Mining-Driver-for-Linux-Release-Notes.aspx
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
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.
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.
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
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.
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.
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
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.
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.
6x VEGA 64
Using https://github.com/halsafar/Vega64SoftPowerTableEditor
Modify registry:
- 1408mhz for P5,6,7.
- 1050mhz for mem
- 950 for core voltages
HBCC only works for 4/6 cards so I am short ~1000H.
Getting 10500H @ 1150W (total draw at the wall).
Total draw at the wall when idle is 250W.
So that is ~150W per card.
Stable for 72 hours. 99% submission rate on nano pool. My average on the pool is expected, 10500.
This is huge given if I try the same setup using stock settings the total draw is ~2000W.
950mV is to much for monero 1408/1050.Using https://github.com/halsafar/Vega64SoftPowerTableEditor
Modify registry:
- 1408mhz for P5,6,7.
- 1050mhz for mem
- 950 for core voltages
HBCC only works for 4/6 cards so I am short ~1000H.
Getting 10500H @ 1150W (total draw at the wall).
Total draw at the wall when idle is 250W.
So that is ~150W per card.
Stable for 72 hours. 99% submission rate on nano pool. My average on the pool is expected, 10500.
This is huge given if I try the same setup using stock settings the total draw is ~2000W.
My cards are 1408/1100(some cards need 1080mem) with 905mV in registry (and OverdriveNTool) and 875mV in Hwinfo64 ... seems stable ...
Fan settings are important btw. With my settings the cards only hit ~56C while HBM2 mem is 70+. Manual fan settings required. I use 3100 RPM.
Yeah I am positive I can go a bit lower. I wanted a stable base before I shot for the moon. Next iteration on the rig now that I know these settings are stable I was thinking of 910mv.
I had my mem running at 1100 but for an extra like 10H per card I felt it wasnt necessary given the extra heat. I'll be plotting results and optimizing this once I have more data.
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
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.
6x VEGA 64
Using https://github.com/halsafar/Vega64SoftPowerTableEditor
Modify registry:
- 1408mhz for P5,6,7.
- 1050mhz for mem
- 950 for core voltages
HBCC only works for 4/6 cards so I am short ~1000H.
Getting 10500H @ 1150W (total draw at the wall).
Total draw at the wall when idle is 250W.
So that is ~150W per card.
Stable for 72 hours. 99% submission rate on nano pool. My average on the pool is expected, 10500.
This is huge given if I try the same setup using stock settings the total draw is ~2000W.
Using https://github.com/halsafar/Vega64SoftPowerTableEditor
Modify registry:
- 1408mhz for P5,6,7.
- 1050mhz for mem
- 950 for core voltages
HBCC only works for 4/6 cards so I am short ~1000H.
Getting 10500H @ 1150W (total draw at the wall).
Total draw at the wall when idle is 250W.
So that is ~150W per card.
Stable for 72 hours. 99% submission rate on nano pool. My average on the pool is expected, 10500.
This is huge given if I try the same setup using stock settings the total draw is ~2000W.
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
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.
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
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.
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.
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
I have been unable to locate a solution.
More info though. If I do a completely clean install with 1 GPU connected. Then boot with all 6. Disable crossfire. I can enable HBCC on 5/6 cards before reboot. Reboot once and it is 4/6 cards forever. Given we have to reboot to install the soft power tables I don't even consider this a half a solution.
I am sure the problem is addressable by AMD.
For now mine monero with four and mine something else with the other two.
More info though. If I do a completely clean install with 1 GPU connected. Then boot with all 6. Disable crossfire. I can enable HBCC on 5/6 cards before reboot. Reboot once and it is 4/6 cards forever. Given we have to reboot to install the soft power tables I don't even consider this a half a solution.
I am sure the problem is addressable by AMD.
For now mine monero with four and mine something else with the other two.
Someone is paying attention:
https://github.com/halsafar/Vega64SoftPowerTableEditor
Looks like it is in early stages but the basics are done. I will give it a test, compare the output to see if it matches our custom known mods to the soft power table.
https://github.com/halsafar/Vega64SoftPowerTableEditor
Looks like it is in early stages but the basics are done. I will give it a test, compare the output to see if it matches our custom known mods to the soft power table.
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
Does anyone know of a way to compare the PCIE lane setup across GPU's or at least how Windows sees it?
According to GPU-Z they are all PCIE 3.0 16x. I need more details than that.
According to GPU-Z they are all PCIE 3.0 16x. I need more details than that.
The madness continues ...
HWInfo broke my system, had to reinstall the drivers and to apply mods again.
How are we supposed to do any monitoring with these s*** drivers? Any click anywhere outside the console breaks things, random timed out session of Team Viewer breaks things. This is very very f** up.
I really want to see how the hot card is working, but can't really do that with XMR STAK, as everything breaks too easy.
Anyway, I've seen ppl having issues with HBCC. I seem to have one too. Two of the cards are hashing at ~700 & 650. They had HBCC enabled before, now after the driver reinstall I can't even enable the thing.
But even enabled, I still had these 650-700 H/s on these threads, so I don't think it was actually working.
Rest seems to be OK (right now all of that is at 1800/1600). The change from 1600/1600 was a cosmetic +50-100 H/s total, so I see no point in pushing it more.
Can anyone help me solving that issue?
I have 8GB Ram, 64GB Virtual Memory, 6x RX VEGA 64 (Air).
Is 16 GB RAM going to solve this? My HBCC Slider says ~ 11666 MB. Is that the same number for you guys?
https://prnt.sc/gqyzlr
HWInfo broke my system, had to reinstall the drivers and to apply mods again.
How are we supposed to do any monitoring with these s*** drivers? Any click anywhere outside the console breaks things, random timed out session of Team Viewer breaks things. This is very very f** up.
I really want to see how the hot card is working, but can't really do that with XMR STAK, as everything breaks too easy.
Anyway, I've seen ppl having issues with HBCC. I seem to have one too. Two of the cards are hashing at ~700 & 650. They had HBCC enabled before, now after the driver reinstall I can't even enable the thing.
But even enabled, I still had these 650-700 H/s on these threads, so I don't think it was actually working.
Rest seems to be OK (right now all of that is at 1800/1600). The change from 1600/1600 was a cosmetic +50-100 H/s total, so I see no point in pushing it more.
Can anyone help me solving that issue?
I have 8GB Ram, 64GB Virtual Memory, 6x RX VEGA 64 (Air).
Is 16 GB RAM going to solve this? My HBCC Slider says ~ 11666 MB. Is that the same number for you guys?
https://prnt.sc/gqyzlr
I managed to only get 4 cards with HBCC actually working. They sliders show up for the other 2 cards but changing any settings has no effect on the slider and the hashrate reflects HBCC is not working. I even added other AMD cards like an R9 290 and RX 570 later on and it dropped it to only 3 cards with HBCC working
Same with 4 cards only working with HBCC. The other 2 do not listen to their HBCC settings. See https://bitcointalk.org/index.php?topic=2201970 for as much details as I can provide.
The worst is that 2 cards also ignore Soft Power Table settings in the registry. Also a major clue I am sure as to why this is happening.
FYI it seems you need 8GB Virtual Mem per card. My rig only has 8GB of RAM but I tried with 16 and 32 and it did not change anything regarding the HBCC issue on more than 4 GPU.
A major clue recently was that plugging in a dummy hdmi connector to one of the problematic cards while running xmr-stak-amd miner caused the hash rate to spike up for ~10s before it dropped back down.
I have yet to do a clean install of Windows as I would like to confirm why this is happening first so I can save others the trouble. If I clean install Windows and it works then I lost my chance to debug it.
With that said I plan a methodical re-install of Windows to hopefully fix it.
How much MB do you see next to the HBCC slider with your setup? Try changing to more VRam than 64 if u have larger SSD.
I notice, that when I enable the HBCC, the system thinks for a second before closing the AMD Settings, and their fans change speed for a second, so it actually hear that this is being applied. On the other two , the settings just insta close.
Exact same issue regarding how Wattman reacts.
4/6 cards when I modify the HBCC slider at all and hit apply cause the screen to flicker a bit, Wattman closes, you can hear the card "re init" as its fan spins up for a second then comes back to normal.
2/6 cards when I modify HBCC Wattman just closes. Nothing else happens.
The madness continues ...
HWInfo broke my system, had to reinstall the drivers and to apply mods again.
How are we supposed to do any monitoring with these s*** drivers? Any click anywhere outside the console breaks things, random timed out session of Team Viewer breaks things. This is very very f** up.
I really want to see how the hot card is working, but can't really do that with XMR STAK, as everything breaks too easy.
Anyway, I've seen ppl having issues with HBCC. I seem to have one too. Two of the cards are hashing at ~700 & 650. They had HBCC enabled before, now after the driver reinstall I can't even enable the thing.
But even enabled, I still had these 650-700 H/s on these threads, so I don't think it was actually working.
Rest seems to be OK (right now all of that is at 1800/1600). The change from 1600/1600 was a cosmetic +50-100 H/s total, so I see no point in pushing it more.
Can anyone help me solving that issue?
I have 8GB Ram, 64GB Virtual Memory, 6x RX VEGA 64 (Air).
Is 16 GB RAM going to solve this? My HBCC Slider says ~ 11666 MB. Is that the same number for you guys?
https://prnt.sc/gqyzlr
HWInfo broke my system, had to reinstall the drivers and to apply mods again.
How are we supposed to do any monitoring with these s*** drivers? Any click anywhere outside the console breaks things, random timed out session of Team Viewer breaks things. This is very very f** up.
I really want to see how the hot card is working, but can't really do that with XMR STAK, as everything breaks too easy.
Anyway, I've seen ppl having issues with HBCC. I seem to have one too. Two of the cards are hashing at ~700 & 650. They had HBCC enabled before, now after the driver reinstall I can't even enable the thing.
But even enabled, I still had these 650-700 H/s on these threads, so I don't think it was actually working.
Rest seems to be OK (right now all of that is at 1800/1600). The change from 1600/1600 was a cosmetic +50-100 H/s total, so I see no point in pushing it more.
Can anyone help me solving that issue?
I have 8GB Ram, 64GB Virtual Memory, 6x RX VEGA 64 (Air).
Is 16 GB RAM going to solve this? My HBCC Slider says ~ 11666 MB. Is that the same number for you guys?
https://prnt.sc/gqyzlr
I managed to only get 4 cards with HBCC actually working. They sliders show up for the other 2 cards but changing any settings has no effect on the slider and the hashrate reflects HBCC is not working. I even added other AMD cards like an R9 290 and RX 570 later on and it dropped it to only 3 cards with HBCC working
Same with 4 cards only working with HBCC. The other 2 do not listen to their HBCC settings. See https://bitcointalk.org/index.php?topic=2201970 for as much details as I can provide.
The worst is that 2 cards also ignore Soft Power Table settings in the registry. Also a major clue I am sure as to why this is happening.
FYI it seems you need 8GB Virtual Mem per card. My rig only has 8GB of RAM but I tried with 16 and 32 and it did not change anything regarding the HBCC issue on more than 4 GPU.
A major clue recently was that plugging in a dummy hdmi connector to one of the problematic cards while running xmr-stak-amd miner caused the hash rate to spike up for ~10s before it dropped back down.
I have yet to do a clean install of Windows as I would like to confirm why this is happening first so I can save others the trouble. If I clean install Windows and it works then I lost my chance to debug it.
With that said I plan a methodical re-install of Windows to hopefully fix it.
I have a feeling that you cannot enable or disable HBCC with blockchain drivers. It is enabled or disabled automatically depending on driver or motherboard/cpu settings.
When you play with HBCC slider (switch) you just reboot some driver logic that causes the speed back to normal (high) if it went slow before for some reason ))). Hope you catch what I'm trying to say ))
Just look to release notes for more fresh 17.8.2 driver ))
http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-17.8.2-Release-Notes.aspx
When you play with HBCC slider (switch) you just reboot some driver logic that causes the speed back to normal (high) if it went slow before for some reason ))). Hope you catch what I'm trying to say ))
Just look to release notes for more fresh 17.8.2 driver ))
Code:
Fixed Issues
- The "Reset" option in Radeon Settings Gaming tab may enable the "HBCC Memory Segment" feature instead of setting it to the default disabled state.
- Radeon WattMan may not reach applied overclock states on Radeon RX Vega series graphics.
- The "Reset" option in Radeon Settings Gaming tab may enable the "HBCC Memory Segment" feature instead of setting it to the default disabled state.
- Radeon WattMan may not reach applied overclock states on Radeon RX Vega series graphics.
http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-17.8.2-Release-Notes.aspx
I don't quite catch what you are trying to say. If you could be clear that would be great, be a champion of information.
If anyone knows of a way to compare the PCI-E lanes windows assigned to each GPU that would be great.
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
More info.
I got a dummy hdmi plug. So far my VEGA 64s have not needed one. They always run fine monitor or not.
While xmr-stak-amd was mining I plugged a dummy plug into one of the two problematic cards. Everything froze, screen went black, flickered a bit, then came back. xmr-stak-amd looked stalled but eventually came back to life.
Check hash rates. The one card I plugged the dummy plug into was hashing at 1900H but only for ~10sec!! Then it dropped back down.
So, I figure lets reboot with the hdmi dummy plug connected from the start. If I do this, I cannot enable HBCC on any card as the machine always crashes.
So the best I can get now is to get everything all setup for 1900H (clock speeds, HBCC toggled). Then once xmr-stak is running I can shove a dummy plug into a card hashing low and get ~10s of 1900H before it drops down to 1300H.
I got a dummy hdmi plug. So far my VEGA 64s have not needed one. They always run fine monitor or not.
While xmr-stak-amd was mining I plugged a dummy plug into one of the two problematic cards. Everything froze, screen went black, flickered a bit, then came back. xmr-stak-amd looked stalled but eventually came back to life.
Check hash rates. The one card I plugged the dummy plug into was hashing at 1900H but only for ~10sec!! Then it dropped back down.
So, I figure lets reboot with the hdmi dummy plug connected from the start. If I do this, I cannot enable HBCC on any card as the machine always crashes.
So the best I can get now is to get everything all setup for 1900H (clock speeds, HBCC toggled). Then once xmr-stak is running I can shove a dummy plug into a card hashing low and get ~10s of 1900H before it drops down to 1300H.
Thanks for this. I've been playing with the power settings with a Sapphire RX Vega 64 Liquid Cooled and got 1990.7 H/s stable @ 0.875 VDDC. Couldn't get power draw at the wall because I need a kill-a-watt thing.
https://i.imgur.com/DvDAIpS.png
About 145W. More details in the next video this weekend.
Highly doubt if it is stable.
One of my cards needs 910mV voltage (gpu-z) to run 1408/1100 stable, other can handle 900mV. If yours is stable - you are the silicon lottery winner ))
I assume you use the soft power tables to make your adjustments. Curious which P states you set for core. Just P6 and P7? All? Is it the same as OldComer's where he adjusts 4,5,6,7 to be nearly the same. How about for mem p states? Just the last one? OldComer doesn't appear to adjust voltages after reviewing his registry file. Just P4,5,6,7 and Mem clock. At least comparing the default soft pp for vega 64 with his.
Re: VEGA 64 - Cannot Enable HBCC on 2/6 cards in rig after reboot.
The effect on xmr-stak-amd is 1300H/S vs 1900H/S, big deal.. 
Yup, exactly that. I am losing 1200H because 2 cards won't enable HBCC. I mean not the end of the world but I hate having problems I cannot solve.
My next move is likely a clean install of Windows.
Given I tried OLDComer's power table mod and it took perfectly on 4/6 cards. The same 2 cards that I cannot enable HBCC on simply ignore it. The registry section for those 2 cards has the soft power table entry and it is correct. Yet those 2 cards just reset to AMD Stock settings when I hit reset in Wattman while the other 4 jump to OLDComer's settings.
Clearly this is a clue or related to the same HBCC problem (or an annoying coincidence).
So I am thinking this problem is solvable. I am thinking Windows has done something wrong with the card.
Hello guys, building a 6xVega XMR mining rig, need some advice.
Parts:
Asrock H81 Pro BTC R2.0
Intel Celeron G1840 (can't get cheaper CPU)
16GB DDR3 RAM, I already have this
250GB SSD
My problem is Vega 64 and 56 are the same price (600 euros). Should I buy 64s or 56s?
Is there any point in buying a Ryzen CPU instead and have it mine as well?
Thanks in advance.
I wouldn't go with 6 Vega now, to many problems can be. 4 Vega+something else (Nvidia for example) should be fineParts:
Asrock H81 Pro BTC R2.0
Intel Celeron G1840 (can't get cheaper CPU)
16GB DDR3 RAM, I already have this
250GB SSD
My problem is Vega 64 and 56 are the same price (600 euros). Should I buy 64s or 56s?
Is there any point in buying a Ryzen CPU instead and have it mine as well?
Thanks in advance.
What kind of problems?
See (https://bitcointalk.org/index.php?topic=2201970.0). In short, it seems we cannot easily enable HBCC on more than 4 cards. I had it working on all 6 at once point, rebooted, never been able to get back. Read the first post, I've tried everything short of nuking Windows entirely. Others are reporting the same issues.
What I wouldn't do for some trick to avoid having to disable/enable HBCC on every card after reboot to get 1900+H XMR.
Also, regarding the power table mods. OLDComer's mod works on 4/6 Vega64's I have. The same two cards I cannot enable HBCC on also seem to ignore the power table registry settings entirely. Likely a clue there but I am not sure what.