Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 190. (Read 237263 times)

Does anyone know which pool the devfee is mining on?

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

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

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

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

Thanks

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.

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

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.

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

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

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

what's the latest working on blockchain ?

Its time to change the good old blockchain drivers to 18.3.4 or 18.6.1

With SRB Miner 1.6.4, my Vega FE rig is currently doing a stable 11060 H/s. Each Vega FE gives a minimum 2205 H/s and a maximum of 2222 H/s, each card is slightly different as you know. Now the temperatures are between 58 and 60 C, only one card rarely goes to 61 C and then gets back! So I think this is pretty cool. I set memory clock of 1100 MHz and memory voltage of 810 mV for all of them. I set slightly varying core clocks however as each one behaves slightly different but generally it is in the range of 1502-1552 MHz and core voltage of 950-1000 mV.

Using OverDrive when I had Blockchain drivers, I could set core clock to 1600 MHz and core voltage to 890 mV which is weird, memory was 1100 MHz along with 880 mV, this would get me 10910 H/s (even with SRB Miner 1.4. with slightly higher (extra ~5 C) temperatures. So I'm not sure if the rig is consuming more power now than before, but extra 160 H/s must be mostly related to SRB Miner 1.6.4 and the new drivers.

I also noticed fan readings are jumpy at times both in the WattMan and the SRB Miner so this must be sensor readings from the driver or maybe really the fans are aging already. These hashrates that I've mentioned are for CN7 only.

Thanks for the great Miner! I think some extra features may be handy and will dig it later.

[2018-07-19 10:23:01] Starting init of mining threads
[2018-07-19 10:23:01] Error CL_OUT_OF_HOST_MEMORY when creating clCreateCommandQueue for DeviceID 0 (Thread 0)
[2018-07-19 10:23:01] Error initing GPU's. Stopping miner process
[2018-07-19 10:23:01] Stopping miner process



guilty
"restart_devices_on_startup" : true,
"restart_devices_on_startup_script" : "restart_devices_on_startup_script.bat",


restart_devices_on_startup_script.bat
OverdriveNTool.exe -r1 -r2 -r3 -r4 -r5 -r6 -p1Vega56 -p2Vega56 -p3Vega56 -p4Vega56 -p5Vega56 -p6Vega56

?



1.6.4
[2018-07-19 09:48:11] stats: HW error: BUS_ID_16: 1
[2018-07-19 09:48:11] stats: HW error: BUS_ID_13: 1
?

1,4,9 ok




1.4.9 more issues than 1.6.4
11700                     11556 H/s



1.6.4 pours errors

[2018-07-19 09:58:16] stats: Average time to find share: 8 seconds
[2018-07-19 09:58:16] stats: HW error: BUS_ID_16: 2
[2018-07-19 09:58:16] stats: HW error: BUS_ID_7: 1
[2018-07-19 09:58:16] stats: HW error: BUS_ID_10: 1
[2018-07-19 09:58:16] stats: HW error: BUS_ID_3: 2



1,6,4
-------------------------------------------------------
[2018-07-19 10:00:41] GPU0 :    1923 H/s [T: 62c, RPM: 3674, CC: 1212 MHz, MC: 905 MHz][BUS:19]
[2018-07-19 10:00:41] GPU1 :    1925 H/s [T: 65c, RPM: 3678, CC: 1212 MHz, MC: 905 MHz][BUS:10]
[2018-07-19 10:00:41] GPU2 :    1908 H/s [T: 60c, RPM: 3668, CC: 1212 MHz, MC: 905 MHz][BUS:13]
[2018-07-19 10:00:41] GPU3 :    1936 H/s [T: 65c, RPM: 3677, CC: 1212 MHz, MC: 905 MHz][BUS:7]
[2018-07-19 10:00:41] GPU4 :    1917 H/s [T: 64c, RPM: 3676, CC: 1212 MHz, MC: 905 MHz][BUS:16]
[2018-07-19 10:00:41] GPU5 :    1919 H/s [T: 57c, RPM: 3547, CC: 1212 MHz, MC: 905 MHz][BUS:3]
[2018-07-19 10:00:41] Total:    11528 H/s

1,4,9
[2018-07-19 10:03:12] GPU0:    1951.0 H/S [T: 56c, RPM: 4529, CC: 1212 MHz, MC: 905 MHz]
[2018-07-19 10:03:12] GPU1:    1950.0 H/S [T: 58c, RPM: 4754, CC: 1212 MHz, MC: 905 MHz]
[2018-07-19 10:03:12] GPU2:    1932.0 H/S [T: 56c, RPM: 4475, CC: 1212 MHz, MC: 905 MHz]
[2018-07-19 10:03:12] GPU3:    1961.0 H/S [T: 59c, RPM: 4571, CC: 1212 MHz, MC: 905 MHz]
[2018-07-19 10:03:12] GPU4:    1945.0 H/S [T: 59c, RPM: 4557, CC: 1212 MHz, MC: 905 MHz]
[2018-07-19 10:03:12] GPU5:    1945.0 H/S [T: 53c, RPM: 4434, CC: 1212 MHz, MC: 905 MHz]
[2018-07-19 10:03:12] Total:   11684.0 H/S

Hoho, v1.6.5 is coming !?

Just testing an RX460 2GB
Cores unlocked
Samsung memory
Core @1180
Mem @2000
Drivers 18.3.2

v7:
1T=130
2T=360

Heavy:
1T=220
2T=244

TUBE:
1T=217
2T=240

FAST:
1T=320
2T=970

Seems to be correct values ?

Those look like nice results to me, both on BitTube and Cryptonight V7. Thanks for sharing the screenshots of OverdriveNTool too, that has become our go to software for editing AMD GPU configurations.

Some results & settings on Vega56 8G Hynix mem

Bittubev2




Cnv7

if you want to mine Heavy algos, use Adrenaline 18.3.4