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

[3MEHDI]

V1.8.1
- Fixed a bug that could crash miner if using CNV4 (R) algo
- Fixed a bug that crashed miner if doing fast algo switching from CNV4 to any algo
- Stales are not displayed anymore by default, added parameter --showstales which turns back on the display of stale shares
- Changed --maxnosharesent default value from 15 minutes to 30
- Logging is now disabled by default in the example start.bat
- Added parameter --preparedata, which could pontentially make a small speed increase on weak GPU's, but also could make it worse. All algos except webchain


+ If you are having ocassional crashes out of nowhere while mining the new V4 (R) algo, please update to version 1.8.1 as this issue is now (hopefully) fixed

+ The info miner displays and is called 'stale shares' is not displayed by default anymore, so if you miss it, and know what is it (it only displays the number of shares sent after a new job was received, it's not the real number of stale shares - that's something only the pool knows), then you can turn it back on by adding --showstales in start.bat

+ A new experimental (beta) parameter --preparedata added, and when enabled CPU will prepare some stuff for the GPU before it begins to work, so this *could* potentially lead to a small increase in hashrate on weaker, older GPU's. I tested on Vega56 and Rx58x series, and there was no gain, but i would like someone to test on weak cards that i don't have, older gcn1,2 series.


Please all of you having crashes on 1.7.9 and 1.8.0 on V4 algo , try out 1.8.1 as this issue should be fixed now.

Hi dear
i install version 1.8.1
After 8 to 9 hours, the temperature of my Gpu increases without reason.
Up to 80 ° C
I will have to re-run the Meining software
Again 8 to 9 hours later this happens
The problem is not the cooling system

3x sapphire  orginal  pack vega 56 upgrade bios to vega 64  samsung chip

[1714820983]

1714820983

[1714820983]

1714820983

[Piradoxlanieve]

Since the last versions, the SRBMiner-CN.exe stopped working, I have to close and re-run manually, the executable does not restart itself, I'm mining bittube, my rig is 6 rx480, 1 rx580 and 1 gtx1070, before it did not happen but now it happens 2 times or 3 a day.

Sorry my bad english.

Windows error report

Nombre de la aplicación con errores: SRBMiner-CN.exe, versión: 1.8.1.0, marca de tiempo: 0x00000000
Nombre del módulo con errores: SRBMiner-CN.exe, versión: 1.8.1.0, marca de tiempo: 0x00000000
Código de excepción: 0xc0000005
Desplazamiento de errores: 0x0000000000085db8
Identificador del proceso con errores: 0x165c
Hora de inicio de la aplicación con errores: 0x01d4e1f818cc07ae
Ruta de acceso de la aplicación con errores: C:\Users\RX480\Desktop\SRBMiner-CN\SRBMiner-CN.exe
Ruta de acceso del módulo con errores: C:\Users\RX480\Desktop\SRBMiner-CN\SRBMiner-CN.exe
Identificador del informe: 473c3244-8f9e-40f4-8ea6-5ed4271bbe3f
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:

[ikicha]

V1.8.1
- Fixed a bug that could crash miner if using CNV4 (R) algo
- Fixed a bug that crashed miner if doing fast algo switching from CNV4 to any algo
- Stales are not displayed anymore by default, added parameter --showstales which turns back on the display of stale shares
- Changed --maxnosharesent default value from 15 minutes to 30
- Logging is now disabled by default in the example start.bat
- Added parameter --preparedata, which could pontentially make a small speed increase on weak GPU's, but also could make it worse. All algos except webchain


+ If you are having ocassional crashes out of nowhere while mining the new V4 (R) algo, please update to version 1.8.1 as this issue is now (hopefully) fixed

+ The info miner displays and is called 'stale shares' is not displayed by default anymore, so if you miss it, and know what is it (it only displays the number of shares sent after a new job was received, it's not the real number of stale shares - that's something only the pool knows), then you can turn it back on by adding --showstales in start.bat

+ A new experimental (beta) parameter --preparedata added, and when enabled CPU will prepare some stuff for the GPU before it begins to work, so this *could* potentially lead to a small increase in hashrate on weaker, older GPU's. I tested on Vega56 and Rx58x series, and there was no gain, but i would like someone to test on weak cards that i don't have, older gcn1,2 series.


Please all of you having crashes on 1.7.9 and 1.8.0 on V4 algo , try out 1.8.1 as this issue should be fixed now.

Hi dear
i install version 1.8.1
After 8 to 9 hours, the temperature of my Gpu increases without reason.
Up to 80 ° C
I will have to re-run the Meining software
Again 8 to 9 hours later this happens
The problem is not the cooling system

3x sapphire  orginal  pack vega 56 upgrade bios to vega 64  samsung chip

Try to disable automatic temp configuration or try extra conf :

"target_temperature" : 70,
"shutdown_temperature" : 80,

Goodluck

[babkaVkedax]

SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem
All drivers, except
Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23
hash rate is 2 times lower than it should be
eg:
haven 750/780 --- 340/350
How to solve a problem?
Thank.

[iRonNuke]

SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem
All drivers, except
Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23
hash rate is 2 times lower than it should be
eg:
haven 750/780 --- 340/350
How to solve a problem?
Thank.

Why are you using a soon 2 year old driver? Maybe that's the issue, don't know. But try atleast 1.8.6.1 or any newer and enable compute mode.

[doktor83]

SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem
All drivers, except
Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23
hash rate is 2 times lower than it should be
eg:
haven 750/780 --- 340/350
How to solve a problem?
Thank.

Compute mode. Enable compute mode.

https://www.srbminer.com/start.html

[babkaVkedax]

SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem
All drivers, except
Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23
hash rate is 2 times lower than it should be
eg:
haven 750/780 --- 340/350
How to solve a problem?
Thank.

Compute mode. Enable compute mode.

https://www.srbminer.com/start.html

Thank you very much.

[babkaVkedax]

SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem
All drivers, except
Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23
hash rate is 2 times lower than it should be
eg:
haven 750/780 --- 340/350
How to solve a problem?
Thank.

Why are you using a soon 2 year old driver? Maybe that's the issue, don't know. But try atleast 1.8.6.1 or any newer and enable compute mode.

Oddly enough, but all video cards with 4GB of Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 show a higher hash rate!
Thanks for the answer.

[doktor83]

SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem
All drivers, except
Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23
hash rate is 2 times lower than it should be
eg:
haven 750/780 --- 340/350
How to solve a problem?
Thank.

Why are you using a soon 2 year old driver? Maybe that's the issue, don't know. But try atleast 1.8.6.1 or any newer and enable compute mode.

Oddly enough, but all video cards with 4GB of Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 show a higher hash rate!
Thanks for the answer.

Well if you don't have problems with the blockchain driver + you have better hashrate, why don't you stay on it ?

[babkaVkedax]

SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem
All drivers, except
Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23
hash rate is 2 times lower than it should be
eg:
haven 750/780 --- 340/350
How to solve a problem?
Thank.

Why are you using a soon 2 year old driver? Maybe that's the issue, don't know. But try atleast 1.8.6.1 or any newer and enable compute mode.

Oddly enough, but all video cards with 4GB of Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 show a higher hash rate!
Thanks for the answer.

Well if you don't have problems with the blockchain driver + you have better hashrate, why don't you stay on it ?

On one computer I put video cards on 8GB and 4GB.
There is a problem with 4GB.
Now the problem is solved.
Thank.

[smeads]

Hi....I have 8 rigs, this is the only one that will not run the newest version.

Any suggestions?

Here's the log:

https://i.ibb.co/WKg4tPm/Greenshot-2019-03-24-15-44-04.png

[doktor83]

Hi....I have 8 rigs, this is the only one that will not run the newest version.

Any suggestions?

Here's the log:

for marketcash use an earlier version, this bug will be fixed in the next version

[ledgerdary]

In the top post, it is suggested to use Driver 19.3.2 for Cryptonight V4. I'm running a Vega 56 on 1.8.1, but since I updated my drivers from 18.6.1 to 19.3.2, I get low difficulty shares that get rejected by the pool every now and then. Any suggestions on how to solve this? And is anyone else running 56s in a similar manner? Is CC 1400/950, MC 950/900 optimal? Thanks in advance!

[smeads]

Hi....I have 8 rigs, this is the only one that will not run the newest version.

Any suggestions?

Here's the log:

https://i.ibb.co/WKg4tPm/Greenshot-2019-03-24-15-44-04.png

for marketcash use an earlier version, this bug will be fixed in the next version

When will the new version w/ the fixes for MKT be released? You should have mentioned this in the current release, I would not have released an update of my software with your newest mining software. Please push out the fix soon.

[doktor83]

When will the new version w/ the fixes for MKT be released? You should have mentioned this in the current release, I would not have released an update of my software with your newest mining software. Please push out the fix soon.

I plan on releasing the new version today, i couldn't mention that MKT isn't working because i did not know until i saw your screenshot

[smeads]

When will the new version w/ the fixes for MKT be released? You should have mentioned this in the current release, I would not have released an update of my software with your newest mining software. Please push out the fix soon.

I plan on releasing the new version today, i couldn't mention that MKT isn't working because i did not know until i saw your screenshot

LOL.... fair enough... please ping me when you have it up. I own and wrote www.profitbotpro.com ... I want to make sure I get your updated files out as quickly as you release them. All my rigs cannot currently mine MKT....I was eager to switch to the new version which stopped my rigs from crashing daily on the new algo's. They were running solid for many many months without reboots, previously. I leave your dev fee in there, btw... so you guys get some $$ from the people using my software.

Randy/smeads/bearlyhealz

[doktor83]

In the top post, it is suggested to use Driver 19.3.2 for Cryptonight V4. I'm running a Vega 56 on 1.8.1, but since I updated my drivers from 18.6.1 to 19.3.2, I get low difficulty shares that get rejected by the pool every now and then. Any suggestions on how to solve this? And is anyone else running 56s in a similar manner? Is CC 1400/950, MC 950/900 optimal? Thanks in advance!

The 19.3.2 are recommended if you have miner crashes, but if everything works OK for you on 18.6.1 then stay with it.

[doktor83]

V1.8.2
- Upx and litev7 algos on auto settings now have more hashrate or lower power consumption, or both
- Reworked networking code, so probably get rid of a bug or two
- Another try to fix V4 algo crashing
- Maxnosharesent parameter default value is now 45 minutes
- Fixed MarketCash , it was broken in 1.8.1

+ Got some speedup on litev7 and upx algos if you use auto setup, mainly on Vegas and weak Rx550 - 560 cards, also power consumption dropped.

+ Another try to fix/postpone the crash that is happening on V4 algos. I would suggest to create/compile the kernel on 18.6.1 driver, then move to Adrenaline 2019 driver (19.3.2 for example).
Some users reported none/less crashes on newer drivers.

+ Fully rewrote the networking code so now :
- You will get 'Block expired' errors from some pools
- Lot's of rejects on Webchain algo

To explain : Some pools like Nicehash or Nanopool, do not accept stale shares (shares sent after a new job was dispatched). In earlier versions of SRB miner did not send these shares to the pool when it detected that a new job arrived in the mean time. Now these are sent too. I made this decision because i saw some discussions where people say that SRB displays higher hashrates than they really are, or steals hashrate ( ). This way user can see all shares - accepted and rejected, and can have a clearer picture of his real speed.

Webchain is a similar story, it rejects stale shares. And oh, there are a lot of those, because it has a short blocktime so new jobs just bam bam bam keep coming.
That's why you have 30% lower hashrate poolside than in miner. Yes i know Loud miner does not have this 'problem' so please use it instead if you have better results.

[smeads]

V1.8.2
- Upx and litev7 algos on auto settings now have more hashrate or lower power consumption, or both
- Reworked networking code, so probably get rid of a bug or two
- Another try to fix V4 algo crashing
- Maxnosharesent parameter default value is now 45 minutes
- Fixed MarketCash , it was broken in 1.8.1

+ Got some speedup on litev7 and upx algos if you use auto setup, mainly on Vegas and weak Rx550 - 560 cards, also power consumption dropped.

+ Another try to fix/postpone the crash that is happening on V4 algos. I would suggest to create/compile the kernel on 18.6.1 driver, then move to Adrenaline 2019 driver (19.3.2 for example).
Some users reported none/less crashes on newer drivers.

+ Fully rewrote the networking code so now :
- You will get 'Block expired' errors from some pools
- Lot's of rejects on Webchain algo

To explain : Some pools like Nicehash or Nanopool, do not accept stale shares (shares sent after a new job was dispatched). In earlier versions of SRB miner did not send these shares to the pool when it detected that a new job arrived in the mean time. Now these are sent too. I made this decision because i saw some discussions where people say that SRB displays higher hashrates than they really are, or steals hashrate ( ). This way user can see all shares - accepted and rejected, and can have a clearer picture of his real speed.

Webchain is a similar story, it rejects stale shares. And oh, there are a lot of those, because it has a short blocktime so new jobs just bam bam bam keep coming.
That's why you have 30% lower hashrate poolside than in miner. Yes i know Loud miner does not have this 'problem' so please use it instead if you have better results.

Awesome!! Thank you. I can confirm MKT works perfectly on all my rigs.

[GKumaran]

Hey doc, it's only nicehash and nanopool that are so Hard on rejects, the miner still will send the stales right?? Cause major pools like supportxmr still use the shares for last job unless a new block is found.

This does give better hashrate for the miner. I know most people say fake hashrate, but those who understand it appreciate it 😃😃