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

That's exactly what it does now, it works without a hitch (Although the switch is manual)


You mean algo switch? That sound superb!

Although now I'm a victim of the win 1803 update, it updated no matter what I did to avoid it, apparently it was not enough.. Now mining above 9500 total hashes (I used to be able to do 13500) hangs the system, so back to Eth mining until I figure this out :\

CL_INVALID_BUFFER_SIZE errors means you're running out of GPU mem.  Reduce your intensity.

Thanks you for the miner, it work well but on one of my rig with 8xRX570 - 4g.

It only see/work with one GPU, (using awesome miner).

Do you know why ?

Can you add Worktips coin under litev7.....

I Have Tested The Miner Vs Claymore 11.3

Hash Speed With Claymore 11.3
RX580 8GB MSI =   968 hashes 1200/2000
RX580 8GB GTS = 1024 hashes overclocked core to 1315 mem 2100 
RX570 8GB MSI =   974 hashes 1200/2000
RX580 4GB GTS =   825 hashes 1200/1950

Hash Speed With SRBMiner v1.5.9
RX580 8GB MSI =  994 hashes core 1200/2000
RX580 8GB GTS =  998 hashes core 1200/2000
RX570 8GB MSI =  995 hashes core 1200/2000
RX580 4GB GTS =  955 hashes core 1250/1950

I do have my own custom bios For all cards so results may not be the same for everyone but these are the best i could get

in my comparison the two miners or the best but SRBminer with a 4 card gpu rig hases at 3980 hashes compared to 3860 hashes with claymore 11.3

now all we need is a linux version of this miner so i can run it on my SMOS rigs

so untill that happens im stuck with Claymore 11.3 and SRBminer on my 2 Windows Rigs

so as far as the fastest miner goes SRBminer Hands Down Is the King in my book

How much is your virtual memory set to?  Make it at least  sum of VRAM of each GPU.
Also in order to hash higher increase core clocks to 1250 range (voltages 875-925mV core, 900mV mem)

Also I don't have  "kernel" : 0, in my GPU config settings.  Not sure how that changes things.

Use 54 intensity (CN HEAVY) ABOVE THAT it will lower Hashes on rx580


{
  "cryptonight_type": "heavy",
  "intensity": 54,
  "double_threads": true,
  "api_enabled": true,
  "api_port": 4028
}

Open Config.txt file delete all and copy that

JUST use it and try....

@dingdongtobias use also on my Rig 5x  Rx580 Aorus and 1x Rx480 Nitro+ i can push 6.3k

These people here think they just throw a number and voila.

112 is the best for me on CNv7

Maybe wanting to report a bug... 

I'm mining Monero, SRB reports 2580 H/s, Nanopool 2 hour SMA flutuates slightly from 2520 to 2677 H/s.

Seems more than fine to me.

Perhaps a strong downvolt, or a shortage of power supply, a poor riser. There are many reasons. My 588 runs 900mv / 850mv 1150 / 2100-2150 (depending on memory and algorithm) 24/7. I advise you to monitor the memory errors in the HWINFO. Ideally, they should always be 0, and do not run any garbage programs like msiab, they affect the stability. Also, the temperature of 74 degrees on one of the cards is super-high for me. I think this can also cause instability.
I advise you to set the parameter --gpureorder, this will simplify the setting and monitoring (Bus_id) of the cards using odnttool and gpuz

I'm using 110 with mine - seemed to give best results with my overclock but i think it might be PoW dependant so YMMW

Huum its like little difference but more stability.


"gpu_conf" :
[
   { "id" : 0, "intensity" : 72, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 1, "intensity" : 72, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 2, "intensity" : 72, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 3, "intensity" : 72, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 4, "intensity" : 72, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 5, "intensity" : 72, "worksize" : 8, "threads" : 2, "kernel" : 0}
]
}

[2018-06-08 15:38:53] GPU0:    920 H/s [T: 59c, RPM: 2187, CC: 1150 MHz, MC: 2175 MHz][BUS:5]
[2018-06-08 15:38:53] GPU1:    704 H/s [T: 74c, RPM: 2124, CC: 1150 MHz, MC: 2175 MHz][BUS:1]
[2018-06-08 15:38:53] GPU2:    872 H/s [T: 63c, RPM: 2027, CC: 1150 MHz, MC: 2175 MHz][BUS:4]
[2018-06-08 15:38:53] GPU3:    850 H/s [T: 67c, RPM: 2152, CC: 1150 MHz, MC: 2175 MHz][BUS:3]
[2018-06-08 15:38:53] GPU4:    920 H/s [T: 57c, RPM: 2901, CC: 1150 MHz, MC: 2175 MHz][BUS:2]
[2018-06-08 15:38:53] GPU5:    920 H/s [T: 45c, RPM: 3037, CC: 1150 MHz, MC: 2175 MHz][BUS:6]
[2018-06-08 15:38:53] Total:   5186 H/s

Not sure why some of the GPU produce different results, all are same really

Set the intensity 72, it is the best for v7 at 588, decreasing temporarily the memory frequency for the test.
588 with such settings should produce about 950-970 hashes v7

Hi man + others

Thanks for the info, these are my new set of results; (double threads = true)

I cannot push this over 86 with 80 being most stable (5200+ hash)

ALL CARDS ARE 8GB

"gpu_conf" :
[
   { "id" : 0, "intensity" : 86, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 1, "intensity" : 86, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 2, "intensity" : 86, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 3, "intensity" : 86, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 4, "intensity" : 86, "worksize" : 8, "threads" : 2, "kernel" : 0},
   { "id" : 5, "intensity" : 86, "worksize" : 8, "threads" : 2, "kernel" : 0}
]
}

[2018-06-08 15:09:52] GPU0:    896 H/s [T: 57c, RPM: 2187, CC: 1150 MHz, MC: 2175 MHz][BUS:5]
[2018-06-08 15:09:52] GPU1:    842 H/s [T: 72c, RPM: 2128, CC: 1150 MHz, MC: 2175 MHz][BUS:1]
[2018-06-08 15:09:52] GPU2:    848 H/s [T: 60c, RPM: 2031, CC: 1150 MHz, MC: 2175 MHz][BUS:4]
[2018-06-08 15:09:52] GPU3:    852 H/s [T: 63c, RPM: 2127, CC: 1150 MHz, MC: 2175 MHz][BUS:3]
[2018-06-08 15:09:52] GPU4:    893 H/s [T: 54c, RPM: 2918, CC: 1150 MHz, MC: 2175 MHz][BUS:2]
[2018-06-08 15:09:52] GPU5:    893 H/s [T: 44c, RPM: 3036, CC: 1150 MHz, MC: 2175 MHz][BUS:6]
[2018-06-08 15:09:52] Total:   5224 H/s


If I do I get this error:
 Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 0 for DeviceID 1 (Thread 3)

Yes, I will obey your advice about 24 hours and the change of the miner, thx. You do not steal a hash, since all the shares that the miner finds reach the pool. But the hasht at this point is actually lower than the miner draws. Why this happens, I do not know. I came here for help, because I did not have enough of my knowledge. But if you do not know, then I do not have anyone else to turn to ...

For RX570/RX580
If 4gb cards.  59 intensity, wksize 8, dual threads
If 8gb cards   114-120, wksize 8, dual threads

Try this :

{
"cryptonight_type" : "normalv7",
"intensity" : 54,
"double_threads" : true
}


DOKTOR, i am with you i know you are not stealing our hash. Just keep up the good work and ignore smartboys 

Thanks for the reply.

Yes its V7 algro, I always used auto setting.
Do you have recommended Intensity setting? not sure if you have similar setup?

If you're compare with Claymore - you use v7 algo. Isn't it?
You must set right intensity in SRB for your cards, not auto. On Claymore you also not got max speed...

I know there more juice to this miner!

I'm using the latest 1.5.9 with 6x RX580s.
On Claymore 11.3 DevFree I get about 5200 H/S
On this one I get about 4890 H/S if lucky.
Something is not right, I think the kernel settings need tweaking or not working correctly.

Not sure why lower hash on some of the cards with same settings?

[2018-06-08 14:11:25] GPU0:    843 H/s [T: 56c, RPM: 2179, CC: 1150 MHz, MC: 2175 MHz][BUS:5]
[2018-06-08 14:11:25] GPU1:    773 H/s [T: 65c, RPM: 2124, CC: 1150 MHz, MC: 2175 MHz][BUS:1]
[2018-06-08 14:11:25] GPU2:    804 H/s [T: 60c, RPM: 2020, CC: 1150 MHz, MC: 2175 MHz][BUS:4]
[2018-06-08 14:11:25] GPU3:    784 H/s [T: 64c, RPM: 2132, CC: 1150 MHz, MC: 2175 MHz][BUS:3]
[2018-06-08 14:11:25] GPU4:    843 H/s [T: 53c, RPM: 2883, CC: 1150 MHz, MC: 2175 MHz][BUS:2]
[2018-06-08 14:11:25] GPU5:    843 H/s [T: 43c, RPM: 2992, CC: 1150 MHz, MC: 2175 MHz][BUS:6]