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

[ManDoneKTM]

New version seems to be a little bit faster , but i want to mine Wtips , wich algo should i use ? The coin need PICO algo ... i cant find it in setup guide . Thanks .

[1714097826]

1714097826

[1714097826]

1714097826

[1714097826]

1714097826

[1714097826]

1714097826

[1714097826]

1714097826

[doktor83]

New version seems to be a little bit faster , but i want to mine Wtips , wich algo should i use ? The coin need PICO algo ... i cant find it in setup guide . Thanks .

turtle

[doktor83]

tweak work only on vegas?
4xx 5xx dont work?

Polaris cards can be modded and yours probably are, if you are mining.
If not, i recommend you SRBPolaris and pimp my straps feature.

That said, messing with an already tweaked bios is the right way to freeze/bsod/crash.
There would be sense in tweaking an unmodded gpu, but i believe there are not many of those in the mining world 

[kibatronic]

On my two rigs the WinIO64.sys blocked usage of WinAMDTweak.exe by blocking the loading of EIO.dll. This persisted even after rebooting. The only way of deleting the file was by booting into safe mode and deleting the SRB 1.8.4 folder.

Winio gets started/loaded on demand when miner starts. When miner is closed Winio gets unloaded but it wont get disabled until windows restart. After restart it won't be active so you probably ran miner again after restart, that's why you could not delete it.

Tested again and you are correct. If I restart and do not start the miner it is possible to delete the file. Sorry for your trouble.

[Mashy81]

Nice work.
UPX algo nice increase.
haven't tried the other algo's yet.

UPX V64 9800hs  V56 9400hs

[lncm]

It doesn't really work for me.

Vega 56 with Samsung Memory, conservative power settings, cvddc and mvddc 900, cclock 1200, mclock 940.

Perfectly stable for days with 1.8.1, ~1800 H/s.

With tweak settings, HBB goes boom and starts hashing @ 1100 H/s.
Reduced memory clock to 900 and set voltage to 950 mv. Can go up to 3, just as fast as 940 Mhz memory with 1.8.1 and no tweak (obviously).

Tweak setting 4 gave imediate screen corruption.

Should I test it with default memory clock?

[doktor83]

It doesn't really work for me.

Vega 56 with Samsung Memory, conservative power settings, cvddc and mvddc 900, cclock 1200, mclock 940.

Perfectly stable for days with 1.8.1, ~1800 H/s.

With tweak settings, HBB goes boom and starts hashing @ 1100 H/s.
Reduced memory clock to 900 and set voltage to 950 mv. Can go up to 3, just as fast as 940 Mhz memory with 1.8.1 and no tweak (obviously).

Tweak setting 4 gave imediate screen corruption.

Should I test it with default memory clock?

Even at profile 1 you should have a minimum 5% increase.
Clocks are ok, vddc is ok, so i don't really get it why you get lower hash.

Did you just use + - , or set the profile in the config file ?
If only + -, there's a bug i fixed, it will be released in a day.

[BestBitcoinOdds]

Mining ETN at nanopool with RX580 8GB , intensity 60 on each card 890h/s! Is there anyway I can further tweak it or that's the maximum? Do you guys have some BIOS mods for RX580 Sapphire Nitro+ Special Edition's with Micron memory for cryptonight algorithm? I am currently mining it with my ETH, which may be causing this not optimal speed.

[akvilon888]

Mining ETN at nanopool with RX580 8GB , intensity 60 on each card 890h/s! Is there anyway I can further tweak it or that's the maximum? Do you guys have some BIOS mods for RX580 Sapphire Nitro+ Special Edition's with Micron memory for cryptonight algorithm? I am currently mining it with my ETH, which may be causing this not optimal speed.

you can use polaris bios editor, it has auto timing option, so you can mod your bios and then get some more h/s. i have some old cards rx 480 with 8gb, and they both does ~1000h/s on cnr and ~30mhs on eth, both with bios with moded timings by PBE.

[lncm]

It doesn't really work for me.

Vega 56 with Samsung Memory, conservative power settings, cvddc and mvddc 900, cclock 1200, mclock 940.

Perfectly stable for days with 1.8.1, ~1800 H/s.

With tweak settings, HBB goes boom and starts hashing @ 1100 H/s.
Reduced memory clock to 900 and set voltage to 950 mv. Can go up to 3, just as fast as 940 Mhz memory with 1.8.1 and no tweak (obviously).

Tweak setting 4 gave imediate screen corruption.

Should I test it with default memory clock?

Even at profile 1 you should have a minimum 5% increase.
Clocks are ok, vddc is ok, so i don't really get it why you get lower hash.

Did you just use + - , or set the profile in the config file ?
If only + -, there's a bug i fixed, it will be released in a day.

No, I set the profile in config, and setup 1.8.4 from scratch.

Maybe because of Samsung memory? (Reported by GPU-Z)

Some Vegas are a bit finecky with memory overclock and disable HBM, starting to hash at much lower speeds. You have to reset the card to get it working again. I got it from too much memory overclock, and lowered it to 940 until it fully stabilize. No problems now, still haven't upgraded from 1.8.1 because it's really stable with my 480/580/Vega 56 rig.

[doktor83]

It doesn't really work for me.

Vega 56 with Samsung Memory, conservative power settings, cvddc and mvddc 900, cclock 1200, mclock 940.

Perfectly stable for days with 1.8.1, ~1800 H/s.

With tweak settings, HBB goes boom and starts hashing @ 1100 H/s.
Reduced memory clock to 900 and set voltage to 950 mv. Can go up to 3, just as fast as 940 Mhz memory with 1.8.1 and no tweak (obviously).

Tweak setting 4 gave imediate screen corruption.

Should I test it with default memory clock?

Even at profile 1 you should have a minimum 5% increase.
Clocks are ok, vddc is ok, so i don't really get it why you get lower hash.

Did you just use + - , or set the profile in the config file ?
If only + -, there's a bug i fixed, it will be released in a day.

No, I set the profile in config, and setup 1.8.4 from scratch.

Maybe because of Samsung memory? (Reported by GPU-Z)

Some Vegas are a bit finecky with memory overclock and disable HBM, starting to hash at much lower speeds. You have to reset the card to get it working again. I got it from too much memory overclock, and lowered it to 940 until it fully stabilize. No problems now, still haven't upgraded from 1.8.1 because it's really stable with my 480/580/Vega 56 rig.

Samsung is ok, you should use the --resetvega switch, which is mega recommended if you have Vegas.. It disables/enables the gpu before mining.

[doktor83]

V1.8.5
- Fixed the 'tweak_profile' changing with + - on keyboard
- Tweaking is now auto disabled if no supported devices found

This release is a quick fix

+ There was a bug with using + - while mining to switch tweak_profiles. Miner reported 0 hash after switch and restarted itself. This should now be fixed.

+ If no tweak supported devices found, tweaking is auto disabled so no unneccessary resources are used

[livada]

V1.8.5
- Fixed the 'tweak_profile' changing with + - on keyboard
- Tweaking is now auto disabled if no supported devices found

This release is a quick fix

+ There was a bug with using + - while mining to switch tweak_profiles. Miner reported 0 hash after switch and restarted itself. This should now be fixed.

+ If no tweak supported devices found, tweaking is auto disabled so no unneccessary resources are used

SRBMINER block AMD MEM TWEAK

Failed to load EIO.dll

after srb 1.8.4 start amd tweak stop work.


wtf?

use other option. iff user not use + for tweak not block amd mem tweek . if use block tweak.

i use srbminer but i wont use beter tweak (amd mem tweek) not srb miner tweak.

problem is : when i go out and use other miner amd tweek not work. srb block and not work after exit. only restart unblock amd tweek. this is problem.

[doktor83]

V1.8.5
- Fixed the 'tweak_profile' changing with + - on keyboard
- Tweaking is now auto disabled if no supported devices found

This release is a quick fix

+ There was a bug with using + - while mining to switch tweak_profiles. Miner reported 0 hash after switch and restarted itself. This should now be fixed.

+ If no tweak supported devices found, tweaking is auto disabled so no unneccessary resources are used

SRBMINER block AMD MEM TWEAK

Failed to load EIO.dll

after srb 1.8.4 start amd tweak stop work.


wtf?

use other option. iff user not use + for tweak not block amd mem tweek . if use block tweak.

i use srbminer but i wont use beter tweak (amd mem tweek) not srb miner tweak.

Use the --disabletweaking parameter if you are going to use an external software to change timings on the fly.

[livada]

V1.8.5
- Fixed the 'tweak_profile' changing with + - on keyboard
- Tweaking is now auto disabled if no supported devices found

This release is a quick fix

+ There was a bug with using + - while mining to switch tweak_profiles. Miner reported 0 hash after switch and restarted itself. This should now be fixed.

+ If no tweak supported devices found, tweaking is auto disabled so no unneccessary resources are used

SRBMINER block AMD MEM TWEAK

Failed to load EIO.dll

after srb 1.8.4 start amd tweak stop work.


wtf?

use other option. iff user not use + for tweak not block amd mem tweek . if use block tweak.

i use srbminer but i wont use beter tweak (amd mem tweek) not srb miner tweak.

Use the --disabletweaking parameter if you are going to use an external software to change timings on the fly.

problem je nakon izlaska iz srbminera. i dalje je bllokiran taj EIO. ja koristim tvoj tweek al nakon toga moram restartat cijeli miner da ponistim taj block. to bas i nije normalno.

ktome sto moram nesto disablirat ak nisa mupotrijebio niejdnu opciju koja bi uplaila tweekera niti sam stisnuo + ?

[doktor83]

V1.8.5
- Fixed the 'tweak_profile' changing with + - on keyboard
- Tweaking is now auto disabled if no supported devices found

This release is a quick fix

+ There was a bug with using + - while mining to switch tweak_profiles. Miner reported 0 hash after switch and restarted itself. This should now be fixed.

+ If no tweak supported devices found, tweaking is auto disabled so no unneccessary resources are used

SRBMINER block AMD MEM TWEAK

Failed to load EIO.dll

after srb 1.8.4 start amd tweak stop work.


wtf?

use other option. iff user not use + for tweak not block amd mem tweek . if use block tweak.

i use srbminer but i wont use beter tweak (amd mem tweek) not srb miner tweak.

Use the --disabletweaking parameter if you are going to use an external software to change timings on the fly.

problem je nakon izlaska iz srbminera. i dalje je bllokiran taj EIO. ja koristim tvoj tweek al nakon toga moram restartat cijeli miner da ponistim taj block. to bas i nije normalno.

Ako koristis --disabletweaking onda nije nista blokirano.

[livada]

V1.8.5
- Fixed the 'tweak_profile' changing with + - on keyboard
- Tweaking is now auto disabled if no supported devices found

This release is a quick fix

+ There was a bug with using + - while mining to switch tweak_profiles. Miner reported 0 hash after switch and restarted itself. This should now be fixed.

+ If no tweak supported devices found, tweaking is auto disabled so no unneccessary resources are used

SRBMINER block AMD MEM TWEAK

Failed to load EIO.dll

after srb 1.8.4 start amd tweak stop work.


wtf?

use other option. iff user not use + for tweak not block amd mem tweek . if use block tweak.

i use srbminer but i wont use beter tweak (amd mem tweek) not srb miner tweak.

Use the --disabletweaking parameter if you are going to use an external software to change timings on the fly.

problem je nakon izlaska iz srbminera. i dalje je bllokiran taj EIO. ja koristim tvoj tweek al nakon toga moram restartat cijeli miner da ponistim taj block. to bas i nije normalno.

Ako koristis --disabletweaking onda nije nista blokirano.

pa koristio sam srbminer npr na lite algui s tweakom izadjem van i hocu upotrijebit amd tweakera i ne mogu. eto tu je problem. moras restartat stroj.
jednom kad upotrijebis srbminera bez disable moras restartat stroj jer je zauvjek blokirao amd mem tweakera.

[doktor83]

V1.8.5
- Fixed the 'tweak_profile' changing with + - on keyboard
- Tweaking is now auto disabled if no supported devices found

This release is a quick fix

+ There was a bug with using + - while mining to switch tweak_profiles. Miner reported 0 hash after switch and restarted itself. This should now be fixed.

+ If no tweak supported devices found, tweaking is auto disabled so no unneccessary resources are used

SRBMINER block AMD MEM TWEAK

Failed to load EIO.dll

after srb 1.8.4 start amd tweak stop work.


wtf?

use other option. iff user not use + for tweak not block amd mem tweek . if use block tweak.

i use srbminer but i wont use beter tweak (amd mem tweek) not srb miner tweak.

Use the --disabletweaking parameter if you are going to use an external software to change timings on the fly.

problem je nakon izlaska iz srbminera. i dalje je bllokiran taj EIO. ja koristim tvoj tweek al nakon toga moram restartat cijeli miner da ponistim taj block. to bas i nije normalno.

Ako koristis --disabletweaking onda nije nista blokirano.

pa korstio sam srbminer npr na lite algui s tweakom izadjem van i ocu upotrijebit amd tweakera i ne mogu eto tu je problem. moras restartat stroj.
jednom kad upotrijebis srbminera bez disable moras restartat stroj jer je zauvjek blokirao amd mem tweakera.

Znaci koristi ili samo majnerov tweak ili onaj tweak. Tako je kako je. Necu da mi se iscitavaju strapovi koje kreira majner.

[mrsimit]

hi doc thanks for the awesome miner,

after 1.8.4 my start.bat is;
 SRBMiner-CN.exe --logfile %LOGTIME% --ccryptonighttype normalv4 --cgpuid 0,1,2,3 --cgpuintensity 112,112,112,112 --cgpuworksize 16,16,16,16 --cgputhreads 2,2,2,2 --cgputweakprofile 5,5,5,5 --shutdowntemperature 80  --pools pools.txt

in version 8.4 when miner is start it shows tweaking : enabled. but after I change the version to 1.8.5 and  use same start.bat it shows tweaking : disabled. how can I change this situation ?

thanks in advance

[marcotheminer]

For those mining ETN (good time to pick some up, good on you): https://lab.antpool.com/
They have a month of 0% fee, might as well use them if you trust them.

Please PM me if this is not an appropriate thread to post this in.