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

[MaxMidnite]

Using latest version, thank you for stellitev4 support.
HashRate is also very nice, one thing I get alot of
Pool rejected result 0x0001704C (low difficulty share)
Other miners do not show me this message, what it mean?
Anything to worry about?

[doktor83]

Using latest version, thank you for stellitev4 support.
HashRate is also very nice, one thing I get alot of
Pool rejected result 0x0001704C (low difficulty share)
Other miners do not show me this message, what it mean?
Anything to worry about?

it means you are using wrong algorithm. What are you trying to mine?

[MaxMidnite]

Using latest version, thank you for stellitev4 support.
HashRate is also very nice, one thing I get alot of
Pool rejected result 0x0001704C (low difficulty share)
Other miners do not show me this message, what it mean?
Anything to worry about?

it means you are using wrong algorithm. What are you trying to mine?

StelliteV4, I set it to this and stellite pool?
Maybe pool no ready yet?

[doktor83]

Using latest version, thank you for stellitev4 support.
HashRate is also very nice, one thing I get alot of
Pool rejected result 0x0001704C (low difficulty share)
Other miners do not show me this message, what it mean?
Anything to worry about?

it means you are using wrong algorithm. What are you trying to mine?

StelliteV4, I set it to this and stellite pool?
Maybe pool no ready yet?

nooo, they will fork next week, probably friday
So it's not that algo , yet.

[MaxMidnite]

Using latest version, thank you for stellitev4 support.
HashRate is also very nice, one thing I get alot of
Pool rejected result 0x0001704C (low difficulty share)
Other miners do not show me this message, what it mean?
Anything to worry about?

it means you are using wrong algorithm. What are you trying to mine?

Also where do I add the "Kernel" can you give example as I added:

/* Intensity 0-> auto intensity, or value from 1-300  */
"intensity" : 0,
"kernel" : 4,

Tried each Kernel and made no difference in hash, so thinking put it in wrong place?

Thanks man

[MaxMidnite]

Using latest version, thank you for stellitev4 support.
HashRate is also very nice, one thing I get alot of
Pool rejected result 0x0001704C (low difficulty share)
Other miners do not show me this message, what it mean?
Anything to worry about?

it means you are using wrong algorithm. What are you trying to mine?

StelliteV4, I set it to this and stellite pool?
Maybe pool no ready yet?

nooo, they will fork next week, probably friday
So it's not that algo , yet.

Thanks man, got it, my bad. :-)

[doktor83]

Using latest version, thank you for stellitev4 support.
HashRate is also very nice, one thing I get alot of
Pool rejected result 0x0001704C (low difficulty share)
Other miners do not show me this message, what it mean?
Anything to worry about?

it means you are using wrong algorithm. What are you trying to mine?

Also where do I add the "Kernel" can you give example as I added:

/* Intensity 0-> auto intensity, or value from 1-300  */
"intensity" : 0,
"kernel" : 4,

Tried each Kernel and made no difference in hash, so thinking put it in wrong place?

Thanks man

Not there, you put it in gpu_conf :


"gpu_conf" :
[
   { "id" : 0, "intensity" : 80, "worksize" : 8, "threads" : 1, "kernel" : 1},
   { "id" : 1, "intensity" : 40, "worksize" : 8, "threads" : 2, "kernel" : 2},
   { "id" : 3, "intensity" : 30, "worksize" : 8, "threads" : 2, "kernel" : 3},
   { "id" : 4, "intensity" : 90, "worksize" : 8, "threads" : 1, "kernel" : 4}
]

What GPU's do you have?

[Iamtutut]

Doctor, is there a kernel recommandation for RX 570s ?

Thanks.

[doktor83]

Doctor, is there a kernel recommandation for RX 570s ?

Thanks.

Kernel 1, that's for newer cards.
Also if you dont set it , it will be automatically set to 1.

[Iamtutut]

Thanks for your reply, then I don't have anything to change.

[trifo]

Version 1.5.7 deleted by antivirus...

[doktor83]

Version 1.5.7 deleted by antivirus...

also version 1.5.6, 1.5.5 and so on

[trifo]

No, only 1.5.7 version... Tested...

[doktor83]

No, only 1.5.7 version... Tested...

yes i decided finally to put a virus into it, now is time to steal all your pictures from my documents

[trifo]

Observation and info for you only... Windows Defender delete version 1.5.7 previous versions no...

[Sgsg666]

Observation and info for you only... Windows Defender delete version 1.5.7 previous versions no...

dude previous versions does gets deleted too if i tried to run miner without windows defender exclusion.

[UnclWish]

No, only 1.5.7 version... Tested...

yes i decided finally to put a virus into it, now is time to steal all your pictures from my documents

I don't think you will be glad to see them )))))))

[dingdongtobias]

Really? Some people still so retarded that they have an urge to share with the community if a well known miner was reported as virus?
Thank you for saving us from the evil!

[istr]

Hi Doc!

A strange behavior!
I've noticed that a long time ago but now I've decided to tell you.
It may help you debugging the code.

I've automated startup procedure for the miner whenever windows starts.
Let's take for example one of my rigs with 6 cards.
Windows boots and after a while miner starts.
After some time of stabilization watching memory usage in task manager I see it stable at  ~286 - 290 M.
If I kill the miner process and start it again giving it time to stabilize it stays at  ~560 - 570 M.
That's why I was saying all the time about "memory management".
I don't know but this is the behavior.
It may help.

Greetings!

ps:  in heavy algo.

well if you would follow this thread regulary you would know that this is very well known, and can be fixed by just fireing up GPU-Z

You know something Doc, you didn't understand me.
I'm not talking about the known hashrate drop problem which I first introduced to the community the temporary solution with GPU-Z
but about different seized memory (MB) into 2 different runs of miner which of course may related.
No hard feelings!

No hard feelings, we did not understand eachother.
Also i don't take notes who said/wrote what and when , so i couldn't know you found this nice 'fix'.

Is this behaviour you are referring to happening every time (like first run always less mem used, second run always ok) ?
I see other miners have this 'problem' too on heavy.

Yes, happening all the time.
Miner uses about half the mem every time machine reboots and for every next run about double of that.

Also what means compute errors?
I've installed a new Gigabyte rx580 8gb card.
I have no memory errors, no hang ups, working fine but only this new card reports 1 or 2 compute errors in stats in a day!

[hesido]

Also what means compute errors?
I've installed a new Gigabyte rx580 8gb card.
I have no memory errors, no hang ups, working fine but only this new card reports 1 or 2 compute errors in stats in a day!

It means there are uncaught memory errors which produced a bad share, which got caught by SRBminer and was not submitted. Some of my microns exhibit memory errors but almost never produce a bad share (but a memory error reported is an error caught and "fixed", the mem errors which don't get caught are the problem), but my Hynix ones never display a mem error in monitoring software yet they produce bad shares once in a while. If bad shares by a specific card is above 0.5% (compared to what it produces on its own), you may reduce mem freq by 10mhz or up the voltage. Just 10mhz may work wonders.