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

[JuanHungLo]

V1.4.5
- Added check of already sent result, so possibly no more duplicate shares should be sent to the pool
- Added GPU core clock & memory display (ADL OverdriveN supported cards)

Also added an experiimental kernel (4) , so if you guys with old gpu's could check it that would be great

Dok,
CC displays for me, but not MC

Sapphire RX 470 8GB Nitro+ (Samsung), Win7-64, Robinhood AMD driver hack (22.19.659.1)

yup just realised that myself, i tested on 570 & 580 before i uploaded the new v.
After that tried on 480 and no mem clk, so in next version that will be fixed )

I was in a hurry to give you a new version with the duplicates check, so i hope no more bans.

I will update all rigs now and let you know if dups aren't fixed.

[zot57]

try to flash this timings:
777000000000000022C39C00AC595A3D90550F12B84C8408004006007E0514206A8900A00200312 0100F292F94273116

or this

999000000000000022C39C00AC595A3D90550F123CCF530C004006007E0514206A8900A00200312 0100F292F94273116

Where to insert those from which strap?

[doktor83]

V1.4.5
- Added check of already sent result, so possibly no more duplicate shares should be sent to the pool
- Added GPU core clock & memory display (ADL OverdriveN supported cards)

Also added an experiimental kernel (4) , so if you guys with old gpu's could check it that would be great

Dok,
CC displays for me, but not MC

Sapphire RX 470 8GB Nitro+ (Samsung), Win7-64, Robinhood AMD driver hack (22.19.659.1)

yup just realised that myself, i tested on 570 & 580 before i uploaded the new v.
After that tried on 480 and no mem clk, so in next version that will be fixed )

I was in a hurry to give you a new version with the duplicates check, so i hope no more bans.

I will update all rigs now and let you know if dups aren't fixed.

the critical moment could be after 2hrs when the devfee switches back to the user mining, as someone wrote

[Larvitar]

It is hynix 1170/2150  modded bios  , they make 30 on eth that way and 940 on sumo

for cryptonight algo big metter only gpu core clock, if your gpu can do 1250-1300mhz - you will see ~1000h/s per card.
Just overclock gpu to 1300mhz and clock down memmory to 2050mhz

Well after 1400/2100 the hashrate got lower from 830-50 to 790 . So this is not a good decision or I am doing something wrong?

1. try to downclock memory more, to 2000 or 2050
2. have you downvolt the core?
3. may be you should try different timings for you memory, in my cases (over 20 gpus) this work for cpyptonight like a charm. All of my cards have hynix memory and to all of them i flashed identical timings, if you want to i can post it here so you can try

I have also hynix and got also lower hashrate to 780. i have sapphire rx580 8gb hynix. I used oneclick in polaris but obviously didn't work.
i have gpu at 1300mhz and 950mV and memory at 2050 and 875mV. Let me know what to do to get 1.000.

try to flash this timings:
777000000000000022C39C00AC595A3D90550F12B84C8408004006007E0514206A8900A00200312 0100F292F94273116

or this

999000000000000022C39C00AC595A3D90550F123CCF530C004006007E0514206A8900A00200312 0100F292F94273116

I think these timings are for Hynix 4GB, not the 8GB ones.

I suggest to use the SRBPolaris's PimpMyStraps or One-click straps from PolarisBiosEditor. It's safe and improve performance. Oh PM me if you wanna more performance.

If you already have a biosmoded GPU, maybe you need to deal with the intensity.

[JuanHungLo]

V1.4.5
- Added check of already sent result, so possibly no more duplicate shares should be sent to the pool
- Added GPU core clock & memory display (ADL OverdriveN supported cards)

Also added an experiimental kernel (4) , so if you guys with old gpu's could check it that would be great

Dok,
CC displays for me, but not MC

Sapphire RX 470 8GB Nitro+ (Samsung), Win7-64, Robinhood AMD driver hack (22.19.659.1)

yup just realised that myself, i tested on 570 & 580 before i uploaded the new v.
After that tried on 480 and no mem clk, so in next version that will be fixed )

I was in a hurry to give you a new version with the duplicates check, so i hope no more bans.

I will update all rigs now and let you know if dups aren't fixed.

the critical moment could be after 2hrs when the devfee switches back to the user mining, as someone wrote

Unfortunately, we still have a problem.

[doktor83]

V1.4.6-fix-fixes
- Fixed duplicate share sending fix
- Fixed GPU core clock & memory display fix

Ok, try this now it should all be good.
i shouldn't rush so much, then this wouldnt happen. sorry folks.

now when a duplicate share sending occures, there is info about it in the log :

[2018-04-19 18:32:22] miner_result: Duplicate share protection kicked in!

[alivanich]

1.4.4.
One my rig always failed on devfee:

[2018-04-19 17:16:29] Connecting to xmr-eu1.nanopool.org:14444
[2018-04-19 17:16:30] Connected!
[2018-04-19 17:16:30] Pool difficulty: 120001
[2018-04-19 17:16:30] Pool sent a new job (ID: 17013)
[2018-04-19 17:16:34] Pool sent a new job (ID: 17014)
[2018-04-19 17:16:34] Pool accepted result 0x00005926
[2018-04-19 17:16:38] Pool accepted result 0x000037CC
[2018-04-19 17:16:42] Pool accepted result 0x0000849B
[2018-04-19 17:17:05] Pool accepted result 0x00007510
[2018-04-19 17:17:17] Pool accepted result 0x000060FA
[2018-04-19 19:13:29] Connected to devfee pool
[2018-04-19 19:14:34] Disconnected from devfee pool
[2018-04-19 19:14:34] Now mining for user

Ahter last string nothing happens.

[doktor83]

 can i get the part of log from devfee start and a little after devfee should end?

[ZaGunShow]

Ok still on 1.4.1 Yes I need to update, but via the changelog, I don't see any changes address this issue.

When I had the test Rig on 5 cards (Vega64) the 'reboot_script' system would kick in and reboot windows (10, 64b). All was good with the world. However I recently went to 8 cards in the system, now I'm getting a daily hang or 2 that does not restart. It just hangs and stays there. Something about the additional overhead not allowing it to advance realize its offline? I'm not sure..

I'm not sure what setting could be tweaked to make this more bulletproof.... Or what additional info I could provide you @doktor83?

Thanks

[alivanich]

can i get the part of log from devfee start and a little after devfee should end?

I started without a log file before
Now i turn on log, but rig working fine (after reduce intensity, memclock and coreclock)

[Lunga Chung]

try to flash this timings:
777000000000000022C39C00AC595A3D90550F12B84C8408004006007E0514206A8900A00200312 0100F292F94273116

or this

999000000000000022C39C00AC595A3D90550F123CCF530C004006007E0514206A8900A00200312 0100F292F94273116


I think these timings are for Hynix 4GB, not the 8GB ones.

I suggest to use the SRBPolaris's PimpMyStraps or One-click straps from PolarisBiosEditor. It's safe and improve performance. Oh PM me if you wanna more performance.

If you already have a biosmoded GPU, maybe you need to deal with the intensity.

Any difference between PimpMyStraps or One-click straps or is it just a name?

Not sure if this a re 4Gb versions, but ill give it a try, from 1750?

[doktor83]

try to flash this timings:
777000000000000022C39C00AC595A3D90550F12B84C8408004006007E0514206A8900A00200312 0100F292F94273116

or this

999000000000000022C39C00AC595A3D90550F123CCF530C004006007E0514206A8900A00200312 0100F292F94273116


I think these timings are for Hynix 4GB, not the 8GB ones.

I suggest to use the SRBPolaris's PimpMyStraps or One-click straps from PolarisBiosEditor. It's safe and improve performance. Oh PM me if you wanna more performance.

If you already have a biosmoded GPU, maybe you need to deal with the intensity.

Any difference between PimpMyStraps or One-click straps or is it just a name?

Not sure if this a re 4Gb versions, but ill give it a try, from 1750?

not the same straps, schnack took straps from the net. i didn't.

[Lunga Chung]

not the same straps, schnack took straps from the net. i didn't.

thx, sent you a PM

[deathlire]

Hi there, I've had a problem with every miner around since the monero pow change, since the only miner I was able to use was Claymore 9.7beta without it crashing my display drivers.
I've tried xmr-stak, xmrig-amd, newer claymore's (No ASM bin found for my old card.) and about anything else that is supposed to work, I've compiled all the ones available and tried
with stock binaries on windows..

Display drivers crash no matter which version I try.. 14.4 15.7, 15.11-beta (for some reason this one is tricky to find.) Even tried the crimson edition beta which I've found out doesn't
actually include any assembler/disassembly tools for openCL.. Anywho..

Display card: AMD Ati Radeon 6530D (Evergeen or BeaverCreek as it picks it up everywhere.)
Cpu: AMD A6-3620 APU w/ the onboard 6530D

I've tried all 4 kernels out, all kill display, and of course can't get ADL to work, but I'd be highly surprised if that could even work at all anyways on this gpu.

All in all I really don't know what to do, or even try anymore.. I'd lend a hand if I could for getting what is needed to make these A-Series APUs to work.  I haven't really seen anything in
the code for the other miners like xmrig/xmr-stak that would be a problem.. But I noted for some reason Claymore is posting exact driver versions for all of their releases, and wondering
how they are able to compile against them specifically, or if that just happens to be what they were using when compiling...

Any help is appreciated, and I'd love to get back to mining on my gpu, had a ton more shares and efficiency even at 42H/s and that's better than 0 since it's on 24/7 anyways.

Here are a couple screenshots for how it's acting and what it catches, and second is showing when display was killed and came back.
https://imgur.com/a/mBtohkv

Thanks, you really are saving miner's lives with this miner and I hope you keep at it.. So I tip my hat to you Doc.

[cryptosize]

Hi there, I've had a problem with every miner around since the monero pow change, since the only miner I was able to use was Claymore 9.7beta without it crashing my display drivers.
I've tried xmr-stak, xmrig-amd, newer claymore's (No ASM bin found for my old card.) and about anything else that is supposed to work, I've compiled all the ones available and tried
with stock binaries on windows..

Display drivers crash no matter which version I try.. 14.4 15.7, 15.11-beta (for some reason this one is tricky to find.) Even tried the crimson edition beta which I've found out doesn't
actually include any assembler/disassembly tools for openCL.. Anywho..

Display card: AMD Ati Radeon 6530D (Evergeen or BeaverCreek as it picks it up everywhere.)
Cpu: AMD A6-3620 APU w/ the onboard 6530D

I've tried all 4 kernels out, all kill display, and of course can't get ADL to work, but I'd be highly surprised if that could even work at all anyways on this gpu.

All in all I really don't know what to do, or even try anymore.. I'd lend a hand if I could for getting what is needed to make these A-Series APUs to work.  I haven't really seen anything in
the code for the other miners like xmrig/xmr-stak that would be a problem.. But I noted for some reason Claymore is posting exact driver versions for all of their releases, and wondering
how they are able to compile against them specifically, or if that just happens to be what they were using when compiling...

Any help is appreciated, and I'd love to get back to mining on my gpu, had a ton more shares and efficiency even at 42H/s and that's better than 0 since it's on 24/7 anyways.

Here are a couple screenshots for how it's acting and what it catches, and second is showing when display was killed and came back.
https://imgur.com/a/mBtohkv

Thanks, you really are saving miner's lives with this miner and I hope you keep at it.. So I tip my hat to you Doc.

I also have an Evergreen GPU (Radeon 5770) and even went back to 14.4 drivers from 15.7.1.

No miner works properly, except Claymore v9.7. I even noticed that my PC hangs with non-Claymore miners.

What kind of sorcery is this?!

[dannyprats]

V1.4.6-fix-fixes
- Fixed duplicate share sending fix
- Fixed GPU core clock & memory display fix

Ok, try this now it should all be good.
i shouldn't rush so much, then this wouldnt happen. sorry folks.

now when a duplicate share sending occures, there is info about it in the log :

[2018-04-19 18:32:22] miner_result: Duplicate share protection kicked in!

I still getting "Your IP is banned" with v1.4.6   ..

https://imgur.com/a/xwTOWxX

[JuanHungLo]

V1.4.6-fix-fixes
- Fixed duplicate share sending fix
- Fixed GPU core clock & memory display fix

Ok, try this now it should all be good.
i shouldn't rush so much, then this wouldnt happen. sorry folks.

now when a duplicate share sending occures, there is info about it in the log :

[2018-04-19 18:32:22] miner_result: Duplicate share protection kicked in!

I still get "Your IP is banned" with v1.4.6   ..

https://imgur.com/a/xwTOWxX

Interesting.  I haven't yet.  Still monitoring.

[deathlire]

I also have an Evergreen GPU (Radeon 5770) and even went back to 14.4 drivers from 15.7.1.

No miner works properly, except Claymore v9.7. I even noticed that my PC hangs with non-Claymore miners.

What kind of sorcery is this?!

Not quite sure, but I did have that happen with a full on crash when it came to I'm thinking was xmr-stak on some of the odd drivers..
Most of the time though just a flash and display drivers pop back up and no hashes ever as soon as it gets a job and tries to work.
Also claymore is pretty much dead now.. would be nice if they released the code to it, would help out about all branches of miners
for video instability and such.

I still getting "Your IP is banned" with v1.4.6   ..

https://imgur.com/a/xwTOWxX

That pool might have a much longer threshold on banning time.. instead of the usual 10 or 30 minutes, it might be much higher.
Might want to check with the pool to make sure about that.. Some actually do 24 hours.

[cryptosize]

Also claymore is pretty much dead now.. would be nice if they released the code to it, would help out about all branches of miners

Claymore doesn't even accept BTC/ETH donations to release the source code to the community.

Go figure...

[dannyprats]

after entering in "failover pool"..

How can I set the number of seconds to wait for check the first pool again?