Guide to reaching 2k+ (2020 H/s) on Cryptonight v8 on a Vega 64

[진세]

https://www.reddit.com/r/MoneroMining/comments/9pwedo/guide_to_reaching_2k_2020_hs_on_cryptonight_v8_on/

Guide to reaching 2k+ (2020 H/s) on Cryptonight v8 on a Vega 64

Target:

• Hashrate : 2020 H/s

• Pool Reported Hashrate : 2000 H/s (Since SRBMiner fee is 0.85% : 2020*(1-0.0085))

• HWinfo Watt : 139.5 Watt (NOT WALL, taken from 12hours avg run of 6 vega 64s via HWinfo)

• GPU Temp : 62-64 C (Air-cooled)

• HBM Temp : 73-75 C (Air-cooled)

Please use this guide with a grain of salt, these are my personal setting and may not work for all !!

Edit 3 : The SAME can also be achived with the Soft PowerPlayTables, these settings are separate, do not mix both configs : GPU WILL CRASH

Edit 4 : Actual consumption and performance analysis by u/vmozara !! Thx a ton !

Required:

• Windows 10 1803 build

• Adrenaline driver 18.5.1(No wattman)(No SoftPowerPlay Tables)

• Overdriven Tool

• SRBMiner 1.6.8 Bitcointalk Thread of SRBMiner

• None of the above are mine !! lul !!

Windows Setup:

• Enable large page file locking via Group Policy Follow the step, just assign it to your user account in the last step

• Set Large page file size to 10GB per card Follow steps for windows 10, but use size i've given

• A folder which is excluded from windows defender/antivirus scanning

Vega 64 Setup:

• Extract the SRBminer to the above folder

• Uninstall existing driver and install 18.5.1 drivers afresh (Only drivers)

• Reboot

• Open command prompt as administator

• Navigate to SRBminer folder

• Run : SRBMiner-CN.exe --setcomputemode

• This diables crossfire and enables the compute mode of vega

• Reboot

OverdrivenTool Config:

• Extract overdriven tool(ODT) inside the SRBMiner folder

• Open ODT and check if all your cards are showing up, if not retry the Vega setup steps

• Click "New", assign a name, eg: CN8

• Close ODT

• Now open the "OverdriveNTool.ini" that was created in the same folder with notepad

• In the lines "GPU_P0" to "GPU_P6" add ;0 to the end of the line

• In the lines "Mem_P0" to "Mem_P2" add ;0 to the end of the line

• Save and close the file

• Open ODT, now u should see that except GPU P7 and Mem P3 other states will be non modifiable

• Set GPU P7 to 1552, 840

  • Edit 3 : If you have a PPT(1100mhz mod) installed : Set GPU P7 to 1408, 840

• Set Mem P3 to 1100, 875

• Min RPM to 3500, Target Temp to 65 C, Max Temp to 75 C, Power Limit to 0

• Select CN8 profile and click Save and close (no need to apply)

• Edit 2 : Open notepad and type Line 1 : Devcon\devcon.exe enable @PCI\ven_1002"&"dev_687*

• Edit 2 : Line 2 : Devcon\devcon.exe restart @PCI\ven_1002"&"dev_687*

• Line 3 : OverdriveNTool.exe -p1"CN8" -p2"CN8"

• Note: In -p1"CN8" , 1 stands for the Vega 64 card as per the ODT dropdown list as per Step 2, add as many vega cards u want to set their clock speeds

• Edit 2 : Line 4 : Devcon\devcon.exe restart @PCI\ven_1002"&"dev_687*

• Save the file as "SetClocks.bat" in the same folder as SRBminer

SRBMiner Config:

• Go to the BinaryKernels folder and rename the normalv8 folder to normalv8-backup

• Go to the Config folder and open config-normalv8.txt

• Replace contents with these:

{
"cryptonight_type" : "normalv8",
"intensity" : 124,
"worksize" : 16,
"double_threads" : true
}

• Save and close

• Config the pools.txt as u see fit

• Open start.bat in Notepad

• Replace the last line with this:

• SRBMiner-CN.exe --config Config\config-normalv8.txt --pools pools.txt --logfile Log\%LOGTIME% --disablegpuwatchdog --startupscript SetClocks.bat

• In the next line type pause

• Save and close

Happy Mining !!

• Edit 2 : Open command prompt as administator

• Edit 2 : Navigate to SRBminer folder

• Edit 2 : Run start.bat

• This should, if all is set properly automatically reset yout vega and set the vega clock speed and fan speeds and start mining on its own!!

Note :

• If you are getting a high amount of COMPUTE ERRORS*, drop the Memory clock from 1100 to 1060 for that particular card, though this will reduce the HR of that card by 30H/s. Check my screenshot 5/6 cards run @ 1100, one card runs @ 1060*

• SRBMiner show Accepted(stales) shares, these are not rejected shares

The Proof - Screenshot After a 12 Hour run:

• 6 Sapphire Vega 64 : Air Cooled : Reference Cards

• SRBMiner

• OverdriveNTool(No PPT)

• HWinfo - Check the timer and averages

Edit : I know the miner and ODT show clock as 1552, but the HWinfo shows 13xx, I have no clue y that is but setting ODT to 13xx, causes a massive drop in HR and is unstable at 840mV.

Edit 2 : Added Devcon.exe restart to help power settings stick

Edit 3 : Added PPT info and GPU clock speed for PPT(1100mhz) users

Edit 4 : Added Actual consumption data and performance analsis by u/vmozara

This is after a 12 hour run see the HWinfo clock and the averages

71 Comments

Share

Save

86% Upvoted

What are your thoughts? Log in or Sign upLOG INSIGN UP

SORT BY

BEST

level 1

Dashes91

5 points·4 days ago

Hi @GKumaran..

i test your guide on srb and it crash all my vega64 with those settings. and they get 1220 watt on 4 gpu..

i have a guide too on xmrig-amd , i get 7830 hash on 4 vega with 180 watt each.. 1930 h something over

this is my link https://forum.hashvault.pro/topic/240-cryptonight-v2monero-v8-v9-vega-64-settings/

HAve a nice day .. and thank for u're effort.

Reply

Share

ReportSave

level 2

GKumaran

1 point·4 days ago

Will check out the guide mate, more hash is always more fun

P.s: try my settings with devcon restarts and without pp tables

Reply

Share

ReportSave

level 2

rohitram43

1 point·4 days ago

Agree on the power consumption...it increases dramatically.. i am back to using pp tables

Reply

Share

ReportSave

level 3

Shakhburz

1 point·2 days ago

The new PoW v8 requires more energy hence the consumption is higher and I believe there is nothing that can be done.

Did you manage to optimize power (measured at wall) by using pp tables?

Reply

Share

ReportSave

level 4

rohitram43

2 points·2 days ago

Yes.. but there is so much optimization you can do.. the power consumption per vega has gone up by around 30-35 w to maintain the same hash rates as v7

Reply

Share

ReportSave

level 5

Shakhburz

1 point·2 days ago

Could you provide the ppt and/or ODN values, H/s and wattage at wall?

My 2 x Vega64 rig was set up using OP guide and does 4074 H/s and draws 455 W at wall right now, measured by TP-Link HS110. When idle it draws 100 W. Probably half of that are the cards themselves idling.

Reply

Share

ReportSave

level 1

vmozara

5 points·4 days ago

I tested OP method on 7x Vega 64 metered rig.

My original V7 settings GPU 1408 Memory 1100 MHZ Consumption ~1300W - 14900H/s JCE Miner

My V8 settings GPU 1200MHZ Memory 1100 MHZ Consumption ~1350W - 13200H/s SRBMINER

OP V8 configuration GPU 1520 MHZ Memory 1100MHZ Consumption 1550W - Hashrate 14350

OP V8 configuration with reduced clocks: GPU 1200MHZ Memory 1100MHz Consumption 1350W - Hashrate 13200H/s

Conclusion: OP method yield same results as using adrenalin+power table. Extra hashes come from increased GPU core however it comes at the cost of 28W extra per card compared to 1200MHz (this core results in same consumption v8 as 1400MHZ v7). HWinfo consumption is not relevant, while it can be used simply to check if the card is consuming more or less than previous settings, it can not be used to compare different cards or real life consumption.

Let's hope AMD will save us with new driversm hopefully they can make then more efficient in this algo, as they did long time ago with blockchain. Also, can't wait for JCE miner implementation, as his V7 version was fastest Vega miner around, hopefully he can repeat the magic with V8.

Cheers

Reply

Share

ReportSave

level 2

GKumaran

1 point·4 days ago·edited 4 days ago

My man !!! :D :D

Thx so much for the analysis and the real world consumption data. Will help me fine tune my rig better !!

Adding this to the post so others are also benefited, Thx a ton !! :D

Reply

Share

ReportSave

level 2

phoneco

1 point·2 hours ago

You have not set SRB well . Vega64 on V7 go 2100+ even some 2200+ if know how to set.

Reply

Share

ReportSave

level 1

thelastasdf

4 points·5 days ago

Wow mate, you made the vega definitive guide obsolete in a very short post 😁. Thanks for sharing!

Reply

Share

ReportSave

level 1

rohitram43

2 points·5 days ago

Any idea if the stale shares is similar with stak as well? How do I check in stak and srbminer?

Btw I used the same pp tables as stak and am getting same hashrates as v7 when using srbminer... thanks!!

Reply

Share

ReportSave

level 1

Shakhburz

2 points·4 days ago·edited 4 days ago

Thanks for this!

I never tried SRBMiner so I thought this would be a good time to try it.

I'm getting constant 2027 H/s in a virtual machine under Ubuntu while xmr-stak gets 1975 on the same machine. Using Adrenalin 18.6.1 drivers.

I'm confused how your rig only takes ~139,5 W/GPU Chip. My HWInfo reports GPU Chip Power around 200W with the same OverdriveNTool clocks/voltages. However, the readings might be off because it's running in a VM. Tomorrow I'll move the miners in my 1st dedicated rig and I'll see. Time to relieve my home server of mining :)

Edit: GPU is Gigabyte Radeon RX Vega64 Gaming OC 8G.

Much later edit:

The performance is really good and the pool agrees too. I'll take it :) Thanks!

One thing that annoyed me was sometimes losing about 200 H/s after a reboot of the VM. After a couple of hours of checking everything I found that this is solved by deleting the OpenCL cache in the SRBMiner/Cache folder. As to why it would differ, I don't have a clue but I suspect the GPU being passed through to the VM could be the culprit.

-------------------------STATS-------------------------

Miner version:  1.6.8
Driver version: 24.20.11021.1000
Mining time:    0 days, 10 hours, 51 minutes, 49 seconds

Algo: normalv8

Pool: xmrpool.eu:7777
Connected since: 2018-10-21 19:58:18
Pool Difficulty: 50000
Pool latency: ~42 ms
Last job received: 212 seconds ago


Accepted(Stale)/Total shares: 1513(40)/1513 (100.0%)
Average time to find share: 25 seconds
1 min. average speed:   2031 H/s
5 min. average speed:   2032 H/s
30 min. average speed:  2032 H/s
Max. speed:             2054 H/s

Compute Errors:
BUS_ID_0: 1

-------------------------------------------------------

Reply

Share

ReportSave

level 1

rohitram43

2 points·4 days ago

My vegas are pulling 25-30w extra each (wall draw) when i use the method described by OP.. i am back to using the PP tables..

But kudos to srb miner.. power consumption is the same.. but hashes like v7 😀

Reply

Share

ReportSave

level 2

robodan918

1 point·4 days ago

I have pp tables + newest drivers on my vegas and using srb miner stock, getting 1980h/s+ on V64, 1880h/s+ on V56

Don't need so many mods

Reply

Share

ReportSave

level 3

metinbeycigim

0 points·3 days ago

can you post ppts for vega 64 and 56 and what is your driver version?

Reply

Share

ReportSave

level 4

robodan918

1 point·3 days ago

stock ppt tables from the vega mining guide

Reply

Share

ReportSave

level 1

CleaverHans

2 points·1 day ago

Thanks heaps - Such a great guide. Took a little bit of tweaking on my Vega 56s but getting solid H/s again.

SRB Miner for Lyfe

Cheers

Reply

Share

ReportSave

level 1

tkoucinauci

2 points·5 days ago

hmm, that is tooo low mV for GPU and Mem for most of the people. My reference Vega 56 give BSOD with 950 mV...

• Set GPU P7 to 1552, 840

• Set Mem P3 to 1100, 875

Reply

Share

ReportSave

level 2

heavyarms1912

2 points·5 days ago

those values aren't the actual ones anyway. You can even set 800 in ODN. Check using HWInfo64 for actual core voltage. that would be between 875-925mV HBM2 anyways works at 1.35V for Vega 64 and 1.25V for Vega 56.

Reply

Share

ReportSave

level 3

GKumaran

0 points·5 days ago

Did you see the screenshot ive posted showing the hwinfo monitor? 😅

Reply

Share

ReportSave

level 4

heavyarms1912

2 points·5 days ago

No but that screenshot is just analogous to what I suggested. The voltage isn't what you've set also the clocks are at 13xx Mhz. you don't need to set 1552 on core. I never said your hashrate is fake :)

TL;DR if you're far off from required clocks/volts the driver or something else has some sort of guard that controls.

p.s. Not trying to demean any of the work that you did. In fact upvoted the post.

Reply

Share

ReportSave

level 5

mmarkomarko

2 points·4 days ago

TL;DR if you're far off from required clocks/volts the driver or something else has some sort of guard that controls.

what may be happening is that he is not really running in the gpu power state 7 but keeps dropping to power state 6 (or below) which brings the clocks and voltages back to defaults. If it's a refernce card - do the red lights on the card keep flashing from 6 to 7 (i.e. the 7th light flashing)?

This is what was happening to me before using PPT editor to edit voltages in ALL power states... (which you can't do without it)

Reply

Share

ReportSave

level 6

GKumaran

2 points·4 days ago

Thanx for the tip mate, i checked on my cards. All 6 cards have 8 red lights on, all are solid, no flashing. P0 - P7, 8 p states, 8 leds

Reply

Share

ReportSave

level 5

GKumaran

1 point·5 days ago

Yeah i know, but if i set my ODT to the clocks shown in hwinfo, then actual goes lower than that !! Its like there is a hidden offset for the cards, and i have no clue how it works !!

As long as it works y bother !! lul !!

P.S: my objective was to reach 2000h/s on the pool side at the lowest consumption

Reply

Share

ReportSave

level 6

heavyarms1912

1 point·5 days ago

That's what has been since 18.3 drivers iirc. Set 1442 and it should be 1400+ actuals. 906 core p7 and 900 p3.

Reply

Share

ReportSave

level 5

mmarkomarko

1 point·4 days ago

demean

what may be happening is that he is not really running in the gpu power state 7 but keeps dropping to power state 6 (or below) which brings the clocks and voltages back to defaults. If it's a refernce card - do the red lights on the card keep flashing from 6 to 7 (i.e. the 7th light flashing)?

This is what was happening to me before using PPT editor to edit voltages in ALL power states... (which you can't do without it)

Reply

Share

ReportSave

level 2

GKumaran

1 point·5 days ago

I too thought the same until i tried it and it works !! Stable on my 6 cards check screenshot !!

The trick is to take the leap of faith !!

Actually first found these setting in a Ethereum mining reddit for Vega 64:

https://www.reddit.com/r/Amd/comments/6xqpot/vega_64_435_mhs_130w/

Tweaked these over the months for Monero.

Reply

Share

ReportSave

level 1

Tidsdilatation

2 points·5 days ago

Thank you very much for writing this, you literally just handed me 400 more hashes.

Reply

Share

ReportSave

level 2

GKumaran

2 points·5 days ago

Cool ! Have fun !~!

Reply

Share

ReportSave

level 3

Tidsdilatation

2 points·5 days ago

You dont know any good OverdriveNtool settings for rx580 8gb? I got a mixed rig, half vega 64 and other half rx580 :D Now i think i can get alot more than 600h/s out of my rx580 when you opened my eyes :D

Reply

Share

ReportSave

level 4

GKumaran

1 point·5 days ago

No bro, unfortunately i own only vega 64s !!

Reply

Share

ReportSave

level 4

GKumaran

1 point·4 days ago

Some people report 850-900 H/s on rx580, check it out

https://bitcointalk.org/index.php?topic=3167363.msg47082609#msg47082609

Reply

Share

ReportSave

level 4

CommonMisspellingBot

1 point·5 days ago

Hey, Tidsdilatation, just a quick heads-up:
alot is actually spelled a lot. You can remember it by it is one lot, 'a lot'.
Have a nice day!

The parent commenter can reply with 'delete' to delete this comment.

Reply

Share

ReportSave

level 5

BooCMB

3 points·5 days ago

Hey CommonMisspellingBot, just a quick heads up:
Your spelling hints are really shitty because they're all essentially "remember the fucking spelling of the fucking word".

You're useless.

Have a nice day!

Reply

Share

ReportSave

level 1

KIM_LONG_VIX

1 point·5 days ago

Unfortunately with this or xmr-stak i'm getting "application has been blocked from accessing graphics hardware", across all various driver versions 5.2, 5.1, 6.1. Anyone have any clue what I can do :(

Reply

Share

ReportSave

level 2

GKumaran

1 point·5 days ago

application has been blocked from accessing graphics hardware

Give this a try, the comments section also.

https://www.drivereasy.com/knowledge/application-blocked-accessing-graphics-hardware-error-windows-10-solved/

Reply

Share

ReportSave

level 3

KIM_LONG_VIX

1 point·5 days ago

I've tried those steps on both of my rigs, and they don't seem to fix the issue. I'm thinking I might just do a full reinstall of the latest Windows and build from scratch with this guide -- I was using registry files to mess with the power, but seems like now OverdriveNTool can do that without registry edits...is that accurate?

Reply

Share

ReportSave

level 4

GKumaran

1 point·5 days ago

Yep, that was the idea. Simple mining no PPT , registy etc !!

Do share the outcome!!

Reply

Share

ReportSave

level 5

KIM_LONG_VIX

1 point·5 days ago

Okay I will. I'll probably be back there tomorrow. Another post said it might be best to shut down, unplug all cards, boot into safe mode, DDU & shut down again, and then & only then plug the cards back in, boot, and install 18.5.1. So i will probably do that first, try your guide in a fresh folder, and measure in HWMon.

I did also try to use OverdriveNTool on my current setup and it had errors setting the power, but I'm thinking it has to be driver silliness. So going to try those steps first.

Reply

Share

ReportSave

level 5

KIM_LONG_VIX

1 point·5 days ago

Tried with the OverdriveNTool and it didn't respect power settings, leading to a crash. Going to try this guide but with power tables now.

Reply

Share

ReportSave

level 6

GKumaran

1 point·5 days ago·edited 5 days ago

Add these line to the setclock.bat file to ensure the power setting are set clean:

Line 1 : Devcon\devcon.exe enable @PCI\ven_1002"&"dev_687*

Line 2 : Devcon\devcon.exe restart @PCI\ven_1002"&"dev_687*

Line 3 : Overdriven settings

Line 4 : Devcon\devcon.exe restart @PCI\ven_1002"&"dev_687*

That tool is bundled with srbminer in the devcon folder.

Also start.bat is to be run as admin(run cmd as admin and navigate to start.bat)

Reply

Share

ReportSave

level 7

KIM_LONG_VIX

1 point·5 days ago

Ah okay, so you still have to restart the devices, you just don't need to use power tables. Thank you for the tip. I will be going to do a fresh install tomorrow, and I"ll let you know how it goes.

If it works well, I'll add any troubles I had to your guide and share it with you

Thank you very much for your replies and help

Reply

Share

ReportSave

level 7

KIM_LONG_VIX

1 point·4 days ago

Hello. I have attempted again tonight and to no avail. I tried your full guide. The power settings work, the overclock works, but it eventually goes from 2k hashrate to peanuts, then blocks graphics access to SRB Miner (same error).

Any other thoughts? I'm at a total loss here.

Reply

Share

ReportSave

level 8

KIM_LONG_VIX

1 point·4 days ago

Tried again with a full fresh install of windows and still same issue. Totally insane.

Reply

Share

ReportSave

level 7

KIM_LONG_VIX

1 point·3 days ago

Here is a screenshot of the issue: https://image.ibb.co/kFharV/Untitled.png

Everything works perfectly at first. Power is right, overclocking right, hashrate good. Then, the lights on card go from 8 to 1, power tables drop, and hashing (eventually) goes to 0.

Please help in any way you can. Thanks

Reply

Share

ReportSave

level 8

KIM_LONG_VIX

1 point·3 days ago·edited 3 days ago

This happens even when I only have one card plugged in.

Edit: It really seems to happen when the difficulty is ramped up from 26k to 42k...any idea if it could be a pool thing? I sincerely am at a loss now. I have several rigs, each with this exact problem, that only work on blockchain drivers (with real shit hashrate)

Edit again: I noticed this in your guide reading it very closely: "install 18.5.1 drivers afresh (Only drivers)" Does this mean to not install AMD Settings? How can I install just drivers? Maybe this is my problem...?

Edit x3: Another guide mentions "Install only the driver package without amd settings". So I'm going to do a custom install, and only do drivers, and hope to Jesus himself this is the fucking fix.

Reply

Share

ReportSave

level 8

GKumaran

1 point·3 days ago

Set minimum fan speed in overdriven tool to 3500 rpm and try again. You temp and fan speed are so not good

Reply

Share

ReportSave

level 9

KIM_LONG_VIX

2 points·3 days ago

My min fan was 5k, max 5k, acoustic 5k.

I changed to min 3.5k, max 5k, and acoustic 4k as in your config.

It fucking worked.

It somehow fucking worked.

I'm going to run this for 24h.

I am going to build upon your guide with screenshots and premade files as a thank-you for your help - it will probably take me a week or 2. But dude. I'm back online. I can't thank you enough.

And as a bonus, no more power tables or registry bullshit! WHAT A RELIEF!

Reply

Share

ReportSave

level 2

SiliconNerd

1 point·3 days ago

This is due to windows defender marking the .exe file as a virus and blocking it! You need to add the file (.exe) or the unzipped miner folder as an exclusion in the 'Virus & threat protection' settings.

Reply

Share

ReportSave

level 3

KIM_LONG_VIX

1 point·3 days ago

Thank you! I will try setting the defender again. I think I may have moved the miner folder around and not whitelisted the new folder. I'm gonna go ahead and whitelist the folder, executables, and batch files. I'll let you know how it goes.

If I get this working, I'm going to post a full guide along with the troubles I've had to try and help others. You guys rock.

Reply

Share

ReportSave

level 3

KIM_LONG_VIX

1 point·3 days ago

Unfortunately it looks like this did not work either. Same issue -- I start around 2k, then you can see it gap the power down and my hashes go to total crap.

So now I've done the Defender fix too for sure...any other thoughts? Sorry I'm such a bother, but folks are getting this working so there must be a way...

Reply

Share

ReportSave

level 1

minerjed

1 point·5 days ago