SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[Amigo9881]

https://imgur.com/a/mkrQKRp


Hi Dok,

Thank you for all the answers you have given me so for all my noob questions.

Currently i am mining bittubev2 algo and my hashrates and overdrive settings are shown in the attached screen shot.

Gpus according to order showing in screen shot:-

1 - Vega56  (sapphire reference card, samsung mem)
2 - Vega FE (sapphire reference card, samsung mem)
3 - Vega56  (sapphire reference card, samsung mem)
4 - Vega64  (sapphire reference card, samsung mem)
5 - Vega64  (sapphire reference card, samsung mem)
6 - Vega64 (sapphire reference card, samsung mem)

I have not been able to achieve the hash rates you are showing, please advise


Intensity 5

[doktor83]

what's the latest working on blockchain ?

Probably 1.6.1, but i don't see any reasons on staying on blockchain except sentimental reasons.

[doktor83]

Hi Dok,

Thank you for all the answers you have given me so for all my noob questions.

Currently i am mining bittubev2 algo and my hashrates and overdrive settings are shown in the attached screen shot.

Gpus according to order showing in screen shot:-

1 - Vega56  (sapphire reference card, samsung mem)
2 - Vega FE (sapphire reference card, samsung mem)
3 - Vega56  (sapphire reference card, samsung mem)
4 - Vega64  (sapphire reference card, samsung mem)
5 - Vega64  (sapphire reference card, samsung mem)
6 - Vega64 (sapphire reference card, samsung mem)

I have not been able to achieve the hash rates you are showing, please advise


Intensity 5

You need to start miner with intensity 60, let it work for a few minutes , then start it with intensity 56. This should get you over 1500+ easily.
Some call this foreplay.
And of course use v1.6.4

[hesido]

I'm using non-blockchain drivers, 18.5.2. On my end, 13 GPU Rx580 rig, 1.6.4 when manual setting intensity, cannot handle the same intensities as 1.6.2, I get crashes, blackouts etc., but 1.6.4 gives higher hashrate with lower intensities so 1.6.4 kind of makes up for it. (I skipped 1.6.3) A 54 intensity fails on 1.6.4 but the default 51 works, and gives similar hasrate to 53 intensity on the previous versions. I had a bad time with Windows build 1803 so I had to revert, that was the only time I worked with the latest AMD drivers and I had 5% lower hashrates after a whole day of downtime trying to find the registry fixes that makes 1803 tick, so I'm not in the mood to even try the new drivers even though I reverted to the older windows build.

If anybody gained by the latest AMD drivers ON the previous windows build, please let us know.

Microns getting 1030 h/s, 1200 core / 2210 mem, Hynix getting 1040, 1210 core / 2075 mem for heavy.

[fellowbeing]

I have Vega FEs, but I assure you "having the latest windows version" is the most irrelevant and overrated comment you see everywhere! I am using a Windows 10 Build 1501 and never had any problems, except for "remote desktop apps that need newer versions of windows" but never had any mining problems.

Edited: It is actually 1511

[hesido]

I have Vega FEs, but I assure you "having the latest windows version" is the most irrelevant and overrated comment you see everywhere! I am using a Windows 10 Build 1501 and never had any problems, except for "remote desktop apps that need newer versions of windows" but never had any mining problems.

Edited: It is actually 1511

The damn thing practically installed itself, even though I had every precaution (disabled update service, turned off a couple of knobs and switches) in place, except making the network connection a "metered" connection (I think it's not possible on wired connections, stupid choice as I can, in theory, perfectly distribute a 3g connection using a modem with wires). Somehow it decided to re-enable the update service at some point, maybe during a driver update that was needed to operate with more than 8 gpu's, not sure, but it did.

[Amigo9881]

https://imgur.com/a/mkrQKRp


Hi Dok,

Thank you for all the answers you have given me so for all my noob questions.

Currently i am mining bittubev2 algo and my hashrates and overdrive settings are shown in the attached screen shot.

Gpus according to order showing in screen shot:-

1 - Vega56  (sapphire reference card, samsung mem)
2 - Vega FE (sapphire reference card, samsung mem)
3 - Vega56  (sapphire reference card, samsung mem)
4 - Vega64  (sapphire reference card, samsung mem)
5 - Vega64  (sapphire reference card, samsung mem)
6 - Vega64 (sapphire reference card, samsung mem)

I have not been able to achieve the hash rates you are showing, please advise


Intensity 5

You need to start miner with intensity 60, let it work for a few minutes , then start it with intensity 56. This should get you over 1500+ easily.
Some call this foreplay.
And of course use v1.6.4

I am using blockchain Aug 23 drivers.. is it fine or should i use latest ?

Thanks

[doktor83]

Hi Dok,

Thank you for all the answers you have given me so for all my noob questions.

Currently i am mining bittubev2 algo and my hashrates and overdrive settings are shown in the attached screen shot.

Gpus according to order showing in screen shot:-

1 - Vega56  (sapphire reference card, samsung mem)
2 - Vega FE (sapphire reference card, samsung mem)
3 - Vega56  (sapphire reference card, samsung mem)
4 - Vega64  (sapphire reference card, samsung mem)
5 - Vega64  (sapphire reference card, samsung mem)
6 - Vega64 (sapphire reference card, samsung mem)

I have not been able to achieve the hash rates you are showing, please advise


Intensity 5

You need to start miner with intensity 60, let it work for a few minutes , then start it with intensity 56. This should get you over 1500+ easily.
Some call this foreplay.
And of course use v1.6.4

I am using blockchain Aug 23 drivers.. is it fine or should i use latest ?

Thanks

18.3.4 , not the latest. It will give you more hash than BC on bittubev2 algo

[rednoW]

Hi Dok,

Thank you for all the answers you have given me so for all my noob questions.

Currently i am mining bittubev2 algo and my hashrates and overdrive settings are shown in the attached screen shot.

Gpus according to order showing in screen shot:-

1 - Vega56  (sapphire reference card, samsung mem)
2 - Vega FE (sapphire reference card, samsung mem)
3 - Vega56  (sapphire reference card, samsung mem)
4 - Vega64  (sapphire reference card, samsung mem)
5 - Vega64  (sapphire reference card, samsung mem)
6 - Vega64 (sapphire reference card, samsung mem)

I have not been able to achieve the hash rates you are showing, please advise


Intensity 5

You need to start miner with intensity 60, let it work for a few minutes , then start it with intensity 56. This should get you over 1500+ easily.
Some call this foreplay.
And of course use v1.6.4

I am using blockchain Aug 23 drivers.. is it fine or should i use latest ?

Thanks

18.3.4 , not the latest. It will give you more hash than BC on bittubev2 algo

Vega is good for v7 and fast cryptonight algos, no need to use it in heavy where 8gb Polaris are at top

[livada]

what's the latest working on blockchain ?

1.6.2 work fine with BC driver.
i not try 1.6.3

1.8.34 driver work fine with al algo
1.8.6.1 ands 1.8.71 work beter than 1.8.34 in V7 algo but not work with Heavy/tube algo

if use only v7 instal 1.8.61 driver and use 1.6.4 srbminer

if use all algo instal 1.8.34+1.6.4miner and all work beter than BC driver

[Raiz83]

Does anyone know which pool the devfee is mining on?

[ZaGunShow]

I'm getting a significant share drop on nanopool since upgrading to 1.6.4 from 1.6.2. Both machines doing the exact same thing

Everything appears normal within SRBMiner. Almost the exact hash numbers as 1.6.2. However, when I missed a payment, I went to investigate and I now realize my shares dropped by about 20-25%

https://www.dropbox.com/s/e76waamhah2dap1/hash%20drop.JPG?dl=0

----
Windows 10, blockchain with a bunch of Vega64's

[dingdongtobias]

I'm getting a significant share drop on nanopool since upgrading to 1.6.4 from 1.6.2. Both machines doing the exact same thing

Everything appears normal within SRBMiner. Almost the exact hash numbers as 1.6.2. However, when I missed a payment, I went to investigate and I now realize my shares dropped by about 20-25%

https://www.dropbox.com/s/e76waamhah2dap1/hash%20drop.JPG?dl=0

----
Windows 10, blockchain with a bunch of Vega64's

I have exactly the opposite, i have a higher hashrate since using 1.6.4 both on pool & miner, using 18.6.1 drivers and the --sendallstales switch.

[doktor83]

I'm getting a significant share drop on nanopool since upgrading to 1.6.4 from 1.6.2. Both machines doing the exact same thing

Everything appears normal within SRBMiner. Almost the exact hash numbers as 1.6.2. However, when I missed a payment, I went to investigate and I now realize my shares dropped by about 20-25%



----
Windows 10, blockchain with a bunch of Vega64's

nah, not possible, it looks like you are not using a gpu or two, i couldnt know but its not the miners fault that is 100%

[ZaGunShow]

I don't know what to tell you.. but this is confirmed. I just went back to 1.6.2 and an immediate jump back to the normal hash on nano pool.

https://www.dropbox.com/s/n39hd08zwhwm85k/hash%20drop%20update%201.JPG?dl=0

SRBMiner in 1.6.2 (for this system, 8 cards)
https://www.dropbox.com/s/66l98fk97tnx41l/1.6.2.jpg?dl=0

SRBMiner in 1.6.4 (for this system, 8 cards)
(looks the same, but its just not getting the same share results)
https://www.dropbox.com/s/uky020294zdpbmz/1.6.4.jpg?dl=0

[doktor83]

I don't know what to tell you.. but this is confirmed. I just went back to 1.6.2 and an immediate jump back to the normal hash on nano pool.

https://www.dropbox.com/s/n39hd08zwhwm85k/hash%20drop%20update%201.JPG?dl=0

SRBMiner in 1.6.2 (for this system, 8 cards)
https://www.dropbox.com/s/66l98fk97tnx41l/1.6.2.jpg?dl=0

SRBMiner in 1.6.4 (for this system, 8 cards)
(looks the same, but its just not getting the same share results)
https://www.dropbox.com/s/uky020294zdpbmz/1.6.4.jpg?dl=0

1.6.4 can produce compute errors on BC drivers, maybe you have a ton of those? That is why i recommend 18.3.4 or18.6.1 on the first page, it works a lot better on those drivers. Maybe if you can try it on one of those?

[rednoW]

1.6.4 can produce compute errors on BC drivers, maybe you have a ton of those? That is why i recommend 18.3.4 or18.6.1 on the first page, it works a lot better on those drivers. Maybe if you can try it on one of those?

I have rather old rig with 4 polaris cards (8gb) and win 8.1. There are no recent amd drivers for win 8.1 so I'm still using August blockchain ones. And when I try to switch to bittube v2 and srbminer 1.6.4 I've got severe share drop (effective hashrate measures for 1 day 3.2 khs. miner still shows good hashrate on its console window, ~4khs)
So I had to switch back to heavy and 1.6.0 version ((

Don't wanna install win10 on this ancient rig ....

[ZaGunShow]

1.6.4 can produce compute errors on BC drivers, maybe you have a ton of those? That is why i recommend 18.3.4 or18.6.1 on the first page, it works a lot better on those drivers. Maybe if you can try it on one of those?

Everything has been rock solid on the blockchain drivers. I'm not going to turn these systems upside down ATM to 'test'. Whatever you have done to try to squeeze more hash out of the cards was not done in testing the Blockchain driver. After a long time SRBMiner user, I guess I'll switch to XMR-Stack if the blockchain drivers are suddenly not being supported?

[doktor83]

1.6.4 can produce compute errors on BC drivers, maybe you have a ton of those? That is why i recommend 18.3.4 or18.6.1 on the first page, it works a lot better on those drivers. Maybe if you can try it on one of those?

Everything has been rock solid on the blockchain drivers. I'm not going to turn these systems upside down ATM to 'test'. Whatever you have done to try to squeeze more hash out of the cards was not done in testing the Blockchain driver. After a long time SRBMiner user, I guess I'll switch to XMR-Stack if the blockchain drivers are suddenly not being supported?

Like windows xp, old things get abandoned after some time in favor of newer. 18.3.4 are great drivers, stable (and not really new also).
Ask livada, he also never wanted to stop using blockchain drivers, and finally when he gave up and tested these two drivers, he said he got more hash, more stable system and lower power consumption.
So i will leave it to you, it's your choice.

[dragonmike]

1.6.4 can produce compute errors on BC drivers, maybe you have a ton of those? That is why i recommend 18.3.4 or18.6.1 on the first page, it works a lot better on those drivers. Maybe if you can try it on one of those?

I have rather old rig with 4 polaris cards (8gb) and win 8.1. There are no recent amd drivers for win 8.1 so I'm still using August blockchain ones. And when I try to switch to bittube v2 and srbminer 1.6.4 I've got severe share drop (effective hashrate measures for 1 day 3.2 khs. miner still shows good hashrate on its console window, ~4khs)
So I had to switch back to heavy and 1.6.0 version ((

Don't wanna install win10 on this ancient rig ....

Have you added --sendallstales to the config/command line?