SRBMiner-MULTI AMD & NVIDIA & INTEL & CPU miner

[SCF0]

Hi, sorry i missed your message.
1.9.4 is just a quick patch for Haven, and yes i probably screw up some things.. Im not maintaining the CN version anymore, just wanted to give an option for XHV miners who want to continue using SRBMiner.
For all the rest algorithms just use 1.9.3 version.

No worries.

That's what I assumed as well. The question is, since it was just a quick patch, how much work would it be for you to get it working on those older GCN cards again? Some of them would still be viable in XHV, especially with cheap power.

[1713560252]

1713560252

[1713560252]

1713560252

[doktor83]

V0.5.0

+ Now supporting real MULTI ALGORITHM mining, you can mine up to 4 algorithms at the same time
+ Changed API and WEB stats to be compatible with the new multi algorithm mining functionality
+ Added GPU auto tune functionality
+ A lot of changes in configuration parameters and the way you define them (check Help folder)
+ Updated algorithm 'defyx' to 'panthera'
+ Updated algorithm 'tellor' to work on tellorpool.org, and removed devfee
+ Added algorithm 'cryptonight_ccx'
+ Added algorithm 'cryptonight_xhv'
+ Added algorithm 'cryptonight_gpu'
+ Added algorithm 'cryptonight_upx'
+ Added algorithm 'cryptonight_heavyx'
+ Added algorithm 'verushash'
+ Added new parameters '--gpu-auto-tune', '--multi-algorithm-job-mode', '--cpu-threads-intensity', '--gpu-auto-intensity', '--gpu-cn-mode'
+ Parameter '--gpu-ethash-mode' now has a new mode : 3
+ A lot of bug fixes

You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!

Total reorganisation, new features etc.. Hope a lot of you find it useful
I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature.

Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature.

Also for you guys that mine Ethash with 4GB gpu's, i added --gpu-ethash-mode 3 (it should be auto used if possible), which needs you to have 1 8GB AMD gpu and at least 5GB of system RAM.

[alucard20724]

V0.5.0


You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!

Total reorganisation, new features etc.. Hope a lot of you find it useful
I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature.

Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature.

does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now.   

[doktor83]

V0.5.0


You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!

Total reorganisation, new features etc.. Hope a lot of you find it useful
I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature.

Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature.

does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now.   

Yes, it's ! now, check the examples folder it contains a bunch of good examples

[alucard20724]

V0.5.0


You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!

Total reorganisation, new features etc.. Hope a lot of you find it useful
I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature.

Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature.

does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now.  

Yes, it's ! now, check the examples folder it contains a bunch of good examples

Is there a chance to add the "," back?   it's just the "!" is non-standard and not used in any other miners... that i know of.    the "!" makes it more difficult for multi-miners that used multiple programs.

Also, do you now support NAVI on all gpu algo?

[doktor83]

V0.5.0


You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!

Total reorganisation, new features etc.. Hope a lot of you find it useful
I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature.

Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature.

does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now.  

Yes, it's ! now, check the examples folder it contains a bunch of good examples

Is there a chance to add the "," back?   it's just the "!" is non-standard and not used in any other miners... that i know of.    the "!" makes it more difficult for multi-miners that used multiple programs.

Also, do you now support NAVI on all gpu algo?

I had to use a 'non standard' character because of the password field for example, which is used on a lot of pools to pass additional data, and they are comma separated.
That's why i chose ; and ! because those are not used (probably) in wallet address, pool url, password field etc..
Also wanted it to be same for every parameter and not leave comma for gpu-id for example but use ! on others..

Hopefully software that uses SRB will adapt to the new format.

[BoozyTalking]

Thank you for dual mining!

Can you please add ProgPowEpic for dual mining?

[doktor83]

Thank you for dual mining!

Can you please add ProgPowEpic for dual mining?

Sorry but no, not worth my time.

[BoozyTalking]

Ok i see, maybe you will change your mind in time. PPOWEpic+Argon2d(NIMIQ) would be great.

[BoozyTalking]

Got error with dual mining:
https://i.imgur.com/6ZOzrcE.png

[doktor83]

Got error with dual mining:

Did you run it as admin or normal user?

[BoozyTalking]

admin

[doktor83]

does it also crash when running 1 algorithm ? (epic)

[BoozyTalking]

Didn't try single algo on this version, 0.4.7 work fine.

Got same error without crash:

Code:

[2020-09-07 19:46:54] New job received [0], block height 596233[0]
[2020-09-07 19:47:12] Socket error : 10054[1]
[2020-09-07 19:47:12] Reconnecting to yespower.eu.mine.zergpool.com:6533 in 15 seconds[1]
[2020-09-07 19:47:24] New job received [1], block height 596233[0]
[2020-09-07 19:47:28] Connected to yespower.eu.mine.zergpool.com:6533[1]

and got new error:

Code:

[2020-09-07 19:50:05] PARSE error: Invalid difficulty received[0]
[2020-09-07 19:50:05] Redirecting jobs from algorithm 1 to algorithm 0 workers [a]
[2020-09-07 19:50:05] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]

[doktor83]

Didn't try single algo on this version, 0.4.7 work fine.

Got same error without crash:

Code:

[2020-09-07 19:46:54] New job received [0], block height 596233[0]
[2020-09-07 19:47:12] Socket error : 10054[1]
[2020-09-07 19:47:12] Reconnecting to yespower.eu.mine.zergpool.com:6533 in 15 seconds[1]
[2020-09-07 19:47:24] New job received [1], block height 596233[0]
[2020-09-07 19:47:28] Connected to yespower.eu.mine.zergpool.com:6533[1]

and got new error:

Code:

[2020-09-07 19:50:05] PARSE error: Invalid difficulty received[0]
[2020-09-07 19:50:05] Redirecting jobs from algorithm 1 to algorithm 0 workers [a]
[2020-09-07 19:50:05] Reconnecting to epic.icemining.ca:4000 in 15 seconds[0]

Socket error 10054 is normal , means pool forcibly closed the connection. The crash now, that ain't normal

Invalid difficulty received is also normal with Epic, its a bug in their node. Sometimes it just sends diff 0, and in that case miner disconnects and tries to reconnect.
It would be good to find out the crash reason.

can you dig the error from windows error reporting? i bet its 0xC0000005

[BoozyTalking]

Google translate for you  So sorry about typos:

Code:

Log name: Application
Source: Application Error
Date: 09/08/2020 1:18:16 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
Description:
Faulting Application Name: SRBMiner-MULTI.exe, Version: 0.5.0.0, Timestamp: 0x5f54d0dd
Faulting module name: SRBMiner-MULTI.exe, version: 0.5.0.0, timestamp: 0x5f54d0dd
Exception code: 0xc0000005
Error offset: 0x000000000041a80e
Faulting Process ID: 0x11d4
Faulting application start time: 0x01d6854015a01e12
Report ID: 9d73e510-a973-44e4-b2b1-136933c49a16
Bad package full name:
Application code associated with the failing package:
Xml events:
<Event xmlns = "http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name = "Application Error" />
    <EventID Qualifiers = "0"> 1000 </EventID>
    <Level> 2 </Level>
    <Task> 100 </Task>
    <Keywords> 0x80000000000000 </Keywords>
    <TimeCreated SystemTime = "2020-09-07T22: 18: 16.063963500Z" />
    <EventRecordID> 14228 </EventRecordID>
    <Channel> Application </Channel>
    <Computer> Computer </Computer>
    <Security />
  </System>
  <EventData>
    <Data> SRBMiner-MULTI.exe </Data>
    <Data> 0.5.0.0 </Data>
    <Data> 5f54d0dd </Data>
    <Data> SRBMiner-MULTI.exe </Data>
    <Data> 0.5.0.0 </Data>
    <Data> 5f54d0dd </Data>
    <Data> c0000005 </Data>
    <Data> 000000000041a80e </Data>
    <Data> 11d4 </Data>
    <Data> 01d6854015a01e12 </Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

[doktor83]

Google translate for you   So sorry about typos:

Code:

Log name: Application
Source: Application Error
Date: 09/08/2020 1:18:16 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
Description:
Faulting Application Name: SRBMiner-MULTI.exe, Version: 0.5.0.0, Timestamp: 0x5f54d0dd
Faulting module name: SRBMiner-MULTI.exe, version: 0.5.0.0, timestamp: 0x5f54d0dd
Exception code: 0xc0000005
Error offset: 0x000000000041a80e
Faulting Process ID: 0x11d4
Faulting application start time: 0x01d6854015a01e12
Report ID: 9d73e510-a973-44e4-b2b1-136933c49a16
Bad package full name:
Application code associated with the failing package:
Xml events:
<Event xmlns = "http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name = "Application Error" />
    <EventID Qualifiers = "0"> 1000 </EventID>
    <Level> 2 </Level>
    <Task> 100 </Task>
    <Keywords> 0x80000000000000 </Keywords>
    <TimeCreated SystemTime = "2020-09-07T22: 18: 16.063963500Z" />
    <EventRecordID> 14228 </EventRecordID>
    <Channel> Application </Channel>
    <Computer> Computer </Computer>
    <Security />
  </System>
  <EventData>
    <Data> SRBMiner-MULTI.exe </Data>
    <Data> 0.5.0.0 </Data>
    <Data> 5f54d0dd </Data>
    <Data> SRBMiner-MULTI.exe </Data>
    <Data> 0.5.0.0 </Data>
    <Data> 5f54d0dd </Data>
    <Data> c0000005 </Data>
    <Data> 000000000041a80e </Data>
    <Data> 11d4 </Data>
    <Data> 01d6854015a01e12 </Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Exception code: 0xc0000005

I need to find where this access violation occurs.

[alucard20724]

V0.5.0


You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!

Total reorganisation, new features etc.. Hope a lot of you find it useful
I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature.

Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature.

does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now.  

Yes, it's ! now, check the examples folder it contains a bunch of good examples

Is there a chance to add the "," back?   it's just the "!" is non-standard and not used in any other miners... that i know of.    the "!" makes it more difficult for multi-miners that used multiple programs.

Also, do you now support NAVI on all gpu algo?

I had to use a 'non standard' character because of the password field for example, which is used on a lot of pools to pass additional data, and they are comma separated.
That's why i chose ; and ! because those are not used (probably) in wallet address, pool url, password field etc..
Also wanted it to be same for every parameter and not leave comma for gpu-id for example but use ! on others..

Hopefully software that uses SRB will adapt to the new format.

Never got an answer on whether you support all algos on Navi now.

[doktor83]

V0.5.0


You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!

Total reorganisation, new features etc.. Hope a lot of you find it useful
I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature.

Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature.

does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now.  

Yes, it's ! now, check the examples folder it contains a bunch of good examples

Is there a chance to add the "," back?   it's just the "!" is non-standard and not used in any other miners... that i know of.    the "!" makes it more difficult for multi-miners that used multiple programs.

Also, do you now support NAVI on all gpu algo?

I had to use a 'non standard' character because of the password field for example, which is used on a lot of pools to pass additional data, and they are comma separated.
That's why i chose ; and ! because those are not used (probably) in wallet address, pool url, password field etc..
Also wanted it to be same for every parameter and not leave comma for gpu-id for example but use ! on others..

Hopefully software that uses SRB will adapt to the new format.

Never got an answer on whether you support all algos on Navi now.

Maybe you could try it ?
I compiled all algorithms except MTP for Navi, but i did not test because i dont have a card. You could try and report back.

[BoozyTalking]

Hi, Doktor. Your last cmd line option for exceptions help with miner crushes, but after 8-10 hours of mining miner just stop mining,
program continue to work, accept works from pools, but not generate hashes.