GUIDE: How to unlock the 1107mhz HBM2 cap on Vega64

[bur1x]

Vega 64 is currently hardcapped at 1107mhz HBM2 memory, some lucky ones get up to 1150mhz before crashing.
The reason for this is the SoC Clockspeed which is currently preventing higher Clockspeeds on the HBM2 Packages which we're gonna unlock today.
The HBM2 Memory Controller was actually build to handle up to 1200mhz on the Package so I don't know why AMD locked it in the first place.

I was able to edit the Hex values of the SoC clock and oc it to 1200mhz which enables the HBM2 Package to achive 1200mhz aswell.


Important: This may not work on all Vega64s. If yours crashes no matter which HBM2 mhz and Voltage you put on, chances are that
your card can't handle the SoC Clock and you're gonna need to go back to your initial .regfile mod.


I was able to achive Hashrates over 2200h/s stable with 100% valid shares and little more power consumption over the current Powertable .regfile mod
that's been going around lately.

I believe there's still more room for Hashrate improvements once i spent more time with this GPU.
Up to 1150mhz was easy achievable with no mV increase while 1200mhz was stable but needed a bit more juice.

Whatever you're gonna do with this, each Silicon behaves different so i can't tell you what exact values your GPU is gonna run stable at.
You're gonna have to take a few hours to find your new sweetspot until you settle on a stable mhz/mV rate with 100% valid shares.
I used the Current 1100mhz .regfile Powertable mod as a Baseline so in case you're using this already ( and you should ) on your current Vega64,
then all your Powertables will stay the same but with the unlocked SoC clock.

You will however need to edit the 0000-000X ending within the .reg file like you are already used to, otherwise you may cause damage!!!
If you're not familiar with the standard powertable mod yet, you're gonna have to do your research elsewhere and then come back to this guide.

Once you've done all this i strongly advice using OverdriveNTool and not going through Wattman for tweaking your Clocks and Voltages.
Wattman is buggy af and may cause instabilty.

Download: Unlocked SoC .reg including Powertables





If you find the Information shared any useful and feel generous enough to Donate, you can do so using the provided Wallets.

XMR: 4GdoN7NCTi8a5gZug7PrwZNKjvHFmKeV11L6pNJPgj5QNEHsN6eeX3DaAQFwZ1ufD4LYCZKArktt113 W7QjWvQ7CW7xJqC3LVM2Ah259sF

ETN: etnkHzwzSyb4fEVQpfP55GCLVWMnijQpHUAyLMttnMC3Soyi4arvFFZgh2HeHqEM5xfoEW6S7ZouYc3 nVbvqSNyw4KWsz9EpxN

BTC: 33mwED631BJac95JYtdAvP4uALKWsGdtRx

[1715387707]

1715387707

[1715387707]

1715387707

[xTommYx]

Can you post something like this for Vega FE with 16gb hbm?

[c0ld_snack]

Could you share what hex values you changed to bump the SoC limit? And any other changes you made ontop of the orig ref file would be awesome! Prefer to manually update my currently working regs

[cod3gen]

Can verify that this change does raise GPU SoC. According to HwInfo its now at 1199 MHz. Compared the files to see the changes as i have other settings in my files;






Anyone who have found values for fanspeed and target temperature in registry?

[c0ld_snack]

Can verify that this change does raise GPU SoC. According to HwInfo its now at 1199 MHz. Compared the files to see the changes as i have other settings in my files;

https://i.imgur.com/9ZrZx2S.png
https://image.ibb.co/feUQLG/So_C_unlockspeed.png



Anyone who have found values for fanspeed and target temperature in registry?

You're the man. Updated and rock solid. I noticed that on a few of my bios versions (LC for example), the location of the change is different. An easy search and replace (on the ones closest to the location you describe) was all it took. 2050 h/s

[c0ld_snack]

Anyone who have found values for fanspeed and target temperature in registry?

Regarding this question, I use OverclockNTool and the CLI to automate settings update prior to running the miner.

IIRC: OverdriveNTool.exe -p1"Setting1"

[eranglr]

That is awesome!
Can you please tell which type of Vega64 you tried that with?

[Michael20]

Someone tested von Vega56 with 64bios?

[Melandroscz]

for vega 56 flashed to 64 working tooo Thanx man, thats what i need

i have Gigabyte cards

[zlatkomajstor]

What are the OverdriveNTool settings in order to get those hash rates?

[cod3gen]

Anyone who have found values for fanspeed and target temperature in registry?

Regarding this question, I use OverclockNTool and the CLI to automate settings update prior to running the miner.

IIRC: OverdriveNTool.exe -p1"Setting1"

Yes, i currently use OverdriveNTool, however it would be both easier and better to just have it all in the powerplay tables ;-)

[Michael20]

Whats your mv for 1100 or 1150mhz hbm2?

[RIGED]

run the 1200 reg mod

started CAST miner and my 6 Vega 64 incl mobo and screen are pulling 2000W from 1300W for an added 100H on total
obviously not a winner, as suggested by OP each to his own sweet spot, i must fiddle a little with the values
or
i just settle with 10% less at 1989h/s/vega64 which is what im mining ETN with at the mo.
then again
Total 12 x VEGA64 @23987 (@2600W) +10%(with above hex table)= +2400H/s = +1.1Vega64
hmmmmmmmm

 

[RIGED]

been fiddling around a bit but cant get it to work

took cpu to 1448 and mem to 1020 no change on V, on 3 of 6 gpus, it runs with 100h more on tweeked gpus, run for a few minutes, then a screen flicker, change in ntool settings and eventualy bluescreen (which i avoided by stopping and restarting at screen flicker)

thinking maybe the rest of the hardware cant take it
worried to damage hardware

does anybody have settings for this?

[Bakhtra]

run the 1200 reg mod

started CAST miner and my 6 Vega 64 incl mobo and screen are pulling 2000W from 1300W for an added 100H on total
obviously not a winner, as suggested by OP each to his own sweet spot, i must fiddle a little with the values
or
i just settle with 10% less at 1989h/s/vega64 which is what im mining ETN with at the mo.
then again
Total 12 x VEGA64 @23987 (@2600W) +10%(with above hex table)= +2400H/s = +1.1Vega64
hmmmmmmmm

 

How can you run 12 vega64 in 1 rig? What OS and driver?

[teamjk]

run the 1200 reg mod

started CAST miner and my 6 Vega 64 incl mobo and screen are pulling 2000W from 1300W for an added 100H on total
obviously not a winner, as suggested by OP each to his own sweet spot, i must fiddle a little with the values
or
i just settle with 10% less at 1989h/s/vega64 which is what im mining ETN with at the mo.
then again
Total 12 x VEGA64 @23987 (@2600W) +10%(with above hex table)= +2400H/s = +1.1Vega64
hmmmmmmmm

 

How can you run 12 vega64 in 1 rig? What OS and driver?

possibly on 2 seperate rigs?

[R0mi]

Could you share what hex values you changed to bump the SoC limit? And any other changes you made ontop of the orig ref file would be awesome! Prefer to manually update my currently working regs

Go to Overclock.net, search for preliminary view of Vega, look for Gupsterg posts and those of others.  Bumping SOC value (what string to look for, how to go about changing that value) is explained.

[Bakhtra]

run the 1200 reg mod

started CAST miner and my 6 Vega 64 incl mobo and screen are pulling 2000W from 1300W for an added 100H on total
obviously not a winner, as suggested by OP each to his own sweet spot, i must fiddle a little with the values
or
i just settle with 10% less at 1989h/s/vega64 which is what im mining ETN with at the mo.
then again
Total 12 x VEGA64 @23987 (@2600W) +10%(with above hex table)= +2400H/s = +1.1Vega64
hmmmmmmmm

 

How can you run 12 vega64 in 1 rig? What OS and driver?

possibly on 2 seperate rigs?

I see. Cause with blockchain max only 8 and stable for me. Change to another driver, got lower hashrate.

[Sgsg666]

Any news for vega 56? Can you optimize it too?

[m.vina]

Any news for vega 56? Can you optimize it too?

There are lots of guides on how to do the same with a Vega 56. Best if you even flash your 56 with a Vega 64 BIOS.

Although, there are already lots of guides on how to do this online. Do your own research and google first before asking. Spamming in this forum will get you tagged as a spammer.