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

[btrot1985]

Hello all I've started using SRBMiner exclusively, mining Monero, I get flawless performance on my Vega 56 at tweak profile 9 approx. 2020 H/S for approx. 36-48 Hrs with no invalid/bad shares, somewhere between that time it starts spitting all invalid/bad shares, any recommendations or ideas as to what may be causing this.  Is there a way to configure the miner to automatically restart when it does start submitting invalid shares?

[safart01]

Hi all,

There is a spreadsheet in the url below, to register the Hash and Miner Settings, who can collaborate to help other people. This is a great initiative.

https://docs.google.com/spreadsheets/d/1pH326fwnYWC5Jef2FdF4KnJ4CLj0cwDDtGjrlgekk1A/edit#gid=514064850

thank you

[stzzzz]

Hello all I've started using SRBMiner exclusively, mining Monero, I get flawless performance on my Vega 56 at tweak profile 9 approx. 2020 H/S for approx. 36-48 Hrs with no invalid/bad shares, somewhere between that time it starts spitting all invalid/bad shares, any recommendations or ideas as to what may be causing this.  Is there a way to configure the miner to automatically restart when it does start submitting invalid shares?

exactly the same  on 1.9 with lower gpus and even WITH NO TWEAKS. 1.87 is also not perfect but works at least.
restart on invalid shares is good idea as they go after few hours
--gpuerrorrestart needed

[Bllacky]

Hello all I've started using SRBMiner exclusively, mining Monero, I get flawless performance on my Vega 56 at tweak profile 9 approx. 2020 H/S for approx. 36-48 Hrs with no invalid/bad shares, somewhere between that time it starts spitting all invalid/bad shares, any recommendations or ideas as to what may be causing this.  Is there a way to configure the miner to automatically restart when it does start submitting invalid shares?

exactly the same  on 1.9 with lower gpus and even WITH NO TWEAKS. 1.87 is also not perfect but works at least.
restart on invalid shares is good idea as they go after few hours
--gpuerrorrestart needed

I have a similar issue. Everything works fine, and then after 16-20 hours I only get rejected shares.

[doktor83]

Hello all I've started using SRBMiner exclusively, mining Monero, I get flawless performance on my Vega 56 at tweak profile 9 approx. 2020 H/S for approx. 36-48 Hrs with no invalid/bad shares, somewhere between that time it starts spitting all invalid/bad shares, any recommendations or ideas as to what may be causing this.  Is there a way to configure the miner to automatically restart when it does start submitting invalid shares?

exactly the same  on 1.9 with lower gpus and even WITH NO TWEAKS. 1.87 is also not perfect but works at least.
restart on invalid shares is good idea as they go after few hours
--gpuerrorrestart needed

I have a similar issue. Everything works fine, and then after 16-20 hours I only get rejected shares.

Interesting. So is this only on 1.9.0 or 188, 189 too ?
Can some of you upload a log file somewhere for me to inspect?
Also which pool are you guys using?

[stsocrat]

start
about 1-10 hours all are ok
and then

[2019-07-03 18:02:41] JOB error: Last and current jobs have same job_id
[2019-07-03 18:02:41] Reconnecting to pool.hashvault.pro:3333 in 15 seconds
[2019-07-03 18:02:56] Connected to pool.hashvault.pro:3333
[2019-07-03 18:02:56] Pool difficulty: 20000
[2019-07-03 18:02:56] Job received, block height 1870497 [ID: b89226cb-e47f-4285-80ca-bbb357dc1454]
[2019-07-03 18:02:58] JOB error: Last and current jobs have same job_id

and again, and again...

What's that?

[doktor83]

start
about 1-10 hours all are ok
and then

[2019-07-03 18:02:41] JOB error: Last and current jobs have same job_id
[2019-07-03 18:02:41] Reconnecting to pool.hashvault.pro:3333 in 15 seconds
[2019-07-03 18:02:56] Connected to pool.hashvault.pro:3333
[2019-07-03 18:02:56] Pool difficulty: 20000
[2019-07-03 18:02:56] Job received, block height 1870497 [ID: b89226cb-e47f-4285-80ca-bbb357dc1454]
[2019-07-03 18:02:58] JOB error: Last and current jobs have same job_id

and again, and again...

What's that?

A nasty bug i should fix  
Could you please send me the log file in PM so i can get more info on what's happening?
Thanks for reporting

[stsocrat]

Ok, i'll collect them.
(Logging was switched off)

[SmartOdissey]

Interesting. So is this only on 1.9.0 or 188, 189 too ?
Can some of you upload a log file somewhere for me to inspect?
Also which pool are you guys using?

same shit
on 1.8.0 - work perfect
on 1.9.0  -random "invalid/bad shares",  but +150 h/s, using https://mining.bit.tube/

[doktor83]

Interesting. So is this only on 1.9.0 or 188, 189 too ?
Can some of you upload a log file somewhere for me to inspect?
Also which pool are you guys using?

same shit
on 1.8.0 - work perfect
on 1.9.0  -random "invalid/bad shares",  but +150 h/s, using https://mining.bit.tube/

i think it's not the same issue, because those guys have problem with CN/R and precompilation, not Tube.

https://bitcointalk.org/index.php?topic=3167363.msg50571884#msg50571884

heavy_mode default value is now 3, before it was 1.
Mode 3 is faster but can produce more compute errors.

also it can happen that after a pool disconnect/reconnect shares get sent to the pool , those will automatically be flagged as invalid shares.
I will make some changes regarding this, so it shouldnt happen.

[SmartOdissey]

how to automatically restart miner after this?

[lpadua]

Hi all,

I tried started mining with SRB, the last version 1.9, configured all but I can´t connect to the pool that I´m used to connect, xmr.pool.minergate.com.
 
Is there some incompatibility with the pool or similar?  I reviewed N tutorials from the videos that are available and is correctly configured.


By the way, is advised to use Radeon Adrenalin Edition 18.5.1, Radeon Adrenalin Edition 18.5.2 or Radeon Adrenalin Edition 18.6.1 but the Radeon VII is not detected by them, I had to use the last ones.


If someone help me I will appreciate it!

Thanks!

[doktor83]

Hi all,

I tried started mining with SRB, the last version 1.9, configured all but I can´t connect to the pool that I´m used to connect, xmr.pool.minergate.com.
 
Is there some incompatibility with the pool or similar?  I reviewed N tutorials from the videos that are available and is correctly configured.


By the way, is advised to use Radeon Adrenalin Edition 18.5.1, Radeon Adrenalin Edition 18.5.2 or Radeon Adrenalin Edition 18.6.1 but the Radeon VII is not detected by them, I had to use the last ones.


If someone help me I will appreciate it!

Thanks!

Just tried and it works with Minergate :

Code:

{
"pools" :
[
	{
		"pool" : "xmr.pool.minergate.com:45700", 
		"wallet" : "your-email-address", 
		"password" : "x",
	}
]
}

Show your configs, so i can help you.

[AnotherMinerDummy]

Miner works fine with one vc (vega56 2000 H/s).
But with 2 plugged it shows only half hashrate https://i.imgur.com/HZnT1Gw.png.
8GB ram, 60GB ssd swap, intel g4400, ASUS H110M-K D3
What could it be?

[doktor83]

Miner works fine with one vc (vega56 2000 H/s).
But with 2 plugged it shows only half hashrate.
8GB ram, 60GB ssd swap, intel g4400, ASUS H110M-K D3
What could it be?

--setcomputemode as admin once, and add --resetvega to start.bat

[AnotherMinerDummy]

Thanks for help, but did both, and still have low hashrate with 2 vc. normal with one.
Also tryed Adrenalin 18.6.1 instead of newest, updating mobo bios, putting vc in diff slots (both plugged via razers).

[doktor83]

Thanks for help, but did both, and still have low hashrate with 2 vc. normal with one.
Also tryed Adrenalin 18.6.1 instead of newest, updating mobo bios, putting vc in diff slots (both plugged via razers).

Can you paste your config file here ?

btw. that's almost the same hashrate i get on my Vega56 Hynix sometimes when the --resetvega isn't applied..

[AnotherMinerDummy]

https://pastebin.com/KA7jTCF5

[AnotherMinerDummy]

upd
changed mobo(to ga 970a ds3p) and now it works fine, ~4k
could it be PCI bus thing?

upd2
if one of vc is in PCI ex1 slot both cards shows low hashrate and if both in PCI ex4-16 then both works fine.

[doktor83]

upd
changed mobo(to ga 970a ds3p) and now it works fine, ~4k
could it be PCI bus thing?

upd2
if one of vc is in PCI ex1 slot both cards shows low hashrate and if both in PCI ex4-16 then both works fine.

Great, im glad you found the solution