DLL detected by AV as virus inside the %temp% folder. The miner is not used for mining in this pc, it is used to monitor another remote node. Im ok with exlcuding a folder in AV for awesome miner, but y is this in the %temp% path? Dll list: - ehokahrd.dll
- cz1kbcwg.dll
- veochfjs.dll
- 2dssckxt.dll
- jjncdwlh.dll
- cygfd1rd.dll
All files detected as RiskTool.MSIL.BitcoinMiner.gen and are shown to be in use by awesome miner. It's quite common for security software to give warnings about mining related tools. Awesome Miner is downloading mining software to %appdata%\AwesomeMinerService or %localappdata%\AwesomeMiner. These two folders can be added as exceptions. Awesome Miner also uses dynamic C# scripting, for example for the dynamic update of coin properties. This scripting feature may result in small dll-files being automatically generated in the temp-folder so it might be those files you see here. These files are however not at all related to mining and this is the first time I get a report that security software would flag these files. I can investigate if the auto generation could be made to a different folder as well. Thx dude !! I'm ok with marking awesome miner specific folders Currently exlcuded: Install location Appdata Now that you mention dynamic coin prop update it did pop up after i re-configured some coins for incorrect data a few days back. Never has the report for last 1 year. Would be nice to have those dll in a safe to exlcude folder. Excluding the %temp% seems like a surefire way to get hit by virus !! |
|
|
|
Thx for linking and testing it  |
|
|
|
DLL detected by AV as virus inside the %temp% folder. The miner is not used for mining in this pc, it is used to monitor another remote node. Im ok with exlcuding a folder in AV for awesome miner, but y is this in the %temp% path? Dll list: - ehokahrd.dll
- cz1kbcwg.dll
- veochfjs.dll
- 2dssckxt.dll
- jjncdwlh.dll
- cygfd1rd.dll
All files detected as RiskTool.MSIL.BitcoinMiner.gen and are shown to be in use by awesome miner. |
|
|
|
just an update on my settings and results: have 3 vega's mining ETH on my rig (have a mix of rx470s, 480s and 570s, using phoenix 4.1c, amd driver 18.5.1 but will try 19.2.2 soon) all vega reference 56's flashed to 64. using wattman to adjust settings windoze 10 1803 gpu 1012mhz @ 0.825v mem 1085mhz @ 0.825v power limit -35% previously getting max of ~43.4mhs before winamdtweak changes now getting between ~49.95mhz and ~50.9mhz (depends on gpu) with : winamdtweak --i 6,8,9 --CL 19 --RAS 30 --RCDRD 12 --RCDWR 6 --RC 44 --RP 13 --RRDS 5 --RRDL 5 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248 0 errors over 3 gpus over 13+ hours. happy to leave everything alone now  Yes, good straps for eth! Thanx. 50.7mhs with vega64lc and 1090 mem clock For cn-r mine posted here are slightly better (2350 vs 2280 yours) And I recommend latest (I use 19.4.1 but 19.4.3 should be good too) drivers. They are awesome! lol !! Those are the same timing as suggested by TRM team in their CN_MAX_YOUR_VEGA.txt guide !! Give credit where its due !! CN_MAX_YOUR_VEGA.txt inside the TeamRedMiner release folder Lucky Vega 64 or flashed 64 (Samsung):
--CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248
Weaker Vega 64 or flashed 64 (Samsung) - use if lucky timings aren't stable:
--CL 19 --RAS 30 --RCDRD 12 --RCDWR 6 --RC 44 --RP 13 --RRDS 5 --RRDL 5 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248
Lucky Vega 56 (Hynix):
--RAS 22 --RCDRD 17 --RCDWR 4 --RC 35 --RP 13 --RRDS 4 --RRDL 4 --RFC 148 --REF 15600
Weaker Vega 56 (Hynix):
--RAS 24 --RCDRD 19 --RCDWR 4 --RC 35 --RP 13 --RRDS 4 --RRDL 5 --RFC 148 --REF 15600 |
|
|
|
why pool speed low? my hash 76 kh but i see average 65 kh on pool
15 minutes is just tooo low. thank you for answer. but i tried last day with no diff and i have got similar result
now i try low static diff. thanks
@rednoW @Mashy81
I actually have this same problem with TRTL with 1220/940/850mv with stock mem timings. It's consistently 10kh lower at pool side Well my vega 64 is just perfect. The pool HR in miner matches with the one reported in the pool with a minor difference. Clocks : 1408/1100/875 in ODT : 1356/1100/850 in hwinfo  |
|
|
|
|
The star mode (*) is not for turtle, use the normal (+/-)
|
|
|
|
Results: Cards : Vega 64 (aircooled, reference, samsung) Platform : Windows 10, 18.6.1 Miner : PheonixMiner 4.2c Algo : Ethash Clocks : 1216/1107/875 (ODT) Actual : 1187/1107/850 (HWinfo) Stock : 44.75 mh/s Current Timing --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --CL 19 --RAS 28 --REF 15600 : 50.12 (12% inc over stock) Finally broke the Ethash 50mh/s barrier in windows |
|
|
|
Results:
Cards : Vega 64 (aircooled, reference, samsung)
Miner : SRBMiner 1.8.3
Algo : Cryptonight litev7
Clocks : 1408/1107/875 (ODT)
Actual : 1354/1107/850 (HWinfo)
Stock : 4530
Todxx --rp 10 --rc 44 --rfc 300 --rrd 3 --rcdrd 12 --rcdwr 5 : 4800
My current --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 : 4865 (7.4% inc over stock)
pbfarmer --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --CL 19 --RAS 28 --REF 15600 : 4980 (9.9% inc over stock)
Results: Cards : Vega 64 (aircooled, reference, samsung) Platform : Windows 10, 18.6.1 Miner : PheonixMiner 4.2c Algo : EthashClocks : 1216/1107/875 (ODT) Actual : 1187/1107/850 (HWinfo) Stock : 44.75 mh/s Current Timing --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --CL 19 --RAS 28 --REF 15600 : 50.12 (12% inc over stock) Finally broke the Ethash 50mh/s barrier in windows |
|
|
|
That is some crazy efficiency. I guess that is not even possible on windows, right? Maybe it is time for me to stop being scared and tried alternative operating systems.
pbfarmer is our resident magician, we strive to reach his god tier levels of efficiency Was waiting for his take on the timing to replicate  First - quick results for cn-trtl, w/ efficiency-focused settings, using timings mostly borrowing from others here, w/ some minor tweaks:
Vega 64 air, ubuntu 18.04 + amdgpu-pro 18.50, TRM 0.4.3 (L18+18), 852 cclock (p0)/1107 mclock/818mv, power readings at the wall
stock timings:
--CL 20 --RAS 33 --RCDRD 16 --RCDWR 10 --RC 47 --RP 14 --RRDS 4 --RRDL 6 --RFC 260 (--REF 3900)
18.5 kh/s @ 135w (137 h/w)
modded timings 1
--CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --RFC 248
19.75 kh/s @ 137w (144 h/w)
modded timings 2
same as above, plus --REF 15600
20.71 kh/s @ 137w (151 h/w)
Ill test ur CL, RAS and REF timing. Thx pbfarmer. Results: Cards : Vega 64 (aircooled, reference, samsung) Miner : SRBMiner 1.8.3 Algo : Cryptonight litev7 Clocks : 1408/1107/875 (ODT) Actual : 1354/1107/850 (HWinfo) Stock : 4530 Todxx --rp 10 --rc 44 --rfc 300 --rrd 3 --rcdrd 12 --rcdwr 5 : 4800 My current --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 : 4865 (7.4% inc over stock) pbfarmer --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --CL 19 --RAS 28 --REF 15600 : 4980 (9.9% inc over stock) In all seriousness, was w8ing for ur numbers the most and u didnt disappoint |
|
|
|
Vega 64, aircooled, samsung: - Highest Hashrate impact : lower RC (good cards : 44, lower cards 45) - too low leads to invalid shares
- RP has high impact on stabilty, but low impact on hashrate (preferred 12 as average for stability) -- too low leads to gpu crash withing minutes
- Second highest HR impact : lower RFC (248) - too low crashes cards
- Having RRDS and RRDL as same value helps in stability
- Better to leave CL unimpacted in my tests, it is pretty much linked to all values.
- There are some hidden param that are not exposed by the tool, so it is advised that if you are not gonna change a value, dont use that param to set the default value, ignore the parameter
- Normal memory overclock plays a huge part in this tuning. 1107mhz is the highest you can reach without breaking the SOC barrier. You must have a stable non invalid shares throwing OC b4 appling the timing.
- My 6 cards timing and OC:
- 1. 1107 : --rcdrd 12 --rcdwr 5 --rc 44 --rp 12 --rrds 3 --rrdl 3 --rfc 248 : Valid Shares : Highest OC, Timing
- 2. 1107 : --rcdrd 12 --rcdwr 5 --rc 44 --rp 12 --rrds 3 --rrdl 3 --rfc 248 : Valid Shares : Highest OC, Timing
- 3. 1050 : --rcdrd 12 --rcdwr 5 --rc 44 --rp 12 --rrds 3 --rrdl 3 --rfc 248 : Highest Timing, Invalid Shares if 1107 OC - 1 invalid per 10 mins
- 4. 1050 : --rcdrd 12 --rcdwr 5 --rc 44 --rp 12 --rrds 3 --rrdl 3 --rfc 248 : Highest Timing, Invalid Shares if 1107 OC - 1 invalid per 10 mins
- 5. 1107 : --rcdrd 12 --rcdwr 5 --rc 45 --rp 12 --rrds 3 --rrdl 3 --rfc 248 : Highest OC, Invalid Shares if --rc 44 - 1 invalid per 4 hours
- 6. 1107 : --rcdrd 12 --rcdwr 5 --rc 45 --rp 12 --rrds 3 --rrdl 3 --rfc 248 : Highest OC, Invalid Shares if --rc 44 - 1 invalid per 3 hours
My testing have been limited to only few params, yet to fully test the other params. |
|
|
|
Stock Timing : 4530 h/s
Todxx Timing : 4800 h/s
Is that working stable for anybody? that rcdwr is very low. GPU crashes in a few minutes for me. Yeah it crashs after 1.5 hours. Also curiously it crashed on the best silicon i had  Not the weaker cards. I'm also stable with the same timings and --rfc 250 which gave me an additional boost. Modified timings would be --rp 10 --rc 44 --rfc 250 --rrd 3 --rcdrd 12 --rcdwr 5 EDIT2: here we go, increased --rp from 10 to 12 and that weaksauce-GPU is doing 21+ kh/s like his little buddies. Ka-pow!
BTW for current version '--rrd 3' should be replaced with '--rrds 3 --rrdl 3' otherwise it won't be set
Results: Cards : Vega 64 (aircooled, reference, samsung) Miner : SRBMiner 1.8.3 Algo : Cryptonight litev7 Clocks : 1408/1107/875 (ODT) Actual : 1354/1107/850 (HWinfo) Stock : 4530 Todxx --rp 10 --rc 44 --rfc 300 --rrd 3 --rcdrd 12 --rcdwr 5 : 4800 crashes in 10-15 Based on above --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 : 4870 stable |
|
|
|
Eliovp, great work on this tool. Here are some of my results:
OS: linux/Ubuntu 18.04
miner: teamredminer 0.4.3
card: Vega 64 air cooled (MSI air boost OC w/ samsung mem)
core clock: ~1150Mhz
mem clock: 1100Mhz
timings modified: --rp 10 --rc 44 --rfc 300 --rrd 3 --rcdrd 12 --rcdwr 5
hashrate w/ stock timings: ~19.5kh/s
hashrate w/ new timings: 21.36kh/s
Unfortunately I don't have power readings from this rig, so I'm not sure how much the power usage increased with the new timings.
I think the card can be pushed more, but I don't have the time to keep tuning at the moment.
Holy OMG !!!!!! I dont understand the various parameters, but i just followed todxx timings on my vega 64(air cooled/samsung). Results: Miner : SRBMiner 1.8.3 Algo : Cryptonight litev7 Clocks : 1408/1107/875 (ODT) Actual : 1354/1107/850 (HWinfo) Stock Timing : 4530 h/s Todxx Timing : 4800 h/s Thx Eliovp for the tool and todxx for making it way easier. Will keep posting the magic as i try more algorithms |
|
|
|
Modified the startup code from wildrigminer to run SRBminer. Can others with the "miner has stopped working" bug also test it out and suggest any other alternatives to this issue. start_miner.bat setx GPU_MAX_HEAP_SIZE 100
setx GPU_MAX_USE_SYNC_OBJECTS 1
setx GPU_SINGLE_ALLOC_PERCENT 100
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_MAX_SINGLE_ALLOC_PERCENT 100
@echo off
cd %~dp0
cls
:loop
for /f "tokens=2 delims==" %%a in ('wmic OS Get localdatetime /value') do set "dt=%%a"
set LOGTIME=%dt:~0,4%_%dt:~4,2%_%dt:~6,2%_%dt:~8,2%_%dt:~10,2%_%dt:~12,2%
set LOGTIME=%LOGTIME: =%
set LOGTIME=%LOGTIME:,=.%.txt
SRBMiner-CN.exe --ccryptonighttype XXX --cpool POOL --cwallet WALLET --cpassword P --cworker R --startupscript ABC.bat --rebootscriptgpuwatchdog XYZ.bat --cjobtimeout 24000 --ckeepalive true --apienable --apiport API --apirigname ZZ --logfile Log\%LOGTIME% --gpuerrorsalert 5 --gpureorder
if ERRORLEVEL 1000 goto custom
timeout /t 5
goto loop
:custom
echo Fucking Error again, killing the damn thing
TASKKILL /F /IM SRBMiner-CN.exe
timeout /t 5
goto loop
|
|
|
|
The miner has stopped working bug is getting pretty annoying very quickly. |
|
|
|
As there are so many positive feedback I will definitely try it out. I am very curious if we can follow all the parameters which are described in the first post.
If you mean does it actually support all those miners,asics and pool, then yeah That surprised me the first time too Check out the demo link adn join in. |
|
|
|
Dok & guys, quick one please:
is the "heavy-x" algo needed to mine x-cash giving the same sort of hashrates as the other heavy/heaven variants (i.e. approx 1750 h/s on Vegas)? I can't seem to find much on this. The Excel spreadsheet does not include any community contributions for that specific algo...
Yeah x-cash uses heavy-x algo. I made this chart to keep track of my hashrates. CN Cheat Sheet |
|
|
|
sure, just around 19:00. will come back with results, thanks
same, 1100Hs  SRBMiner-CN.exe --setcomputemode (sets AMD gpu's to compute mode & disables crossfire - run as admin) |
|
|
|
what is the best web monitoring for this miner?
kerney666 said sometime ago "I have some plans on getting a little Python hack going that acts as an adapter against the messier sgminer API and provides an xmr stak equivalent html and http/json interface. Time time time."
Maybe an adapter for claymore monitor or xmr-stak
I use this one : https://dashboard.foreman.mn/dashboard/Pretty much a one stop for all miner and algos. |
|
|
|
Just Update win 10 pro (to last version) + driver to 19.3.2 version from 18.6.1 because no need for ppt table and read that this driver is OK. Update OverdriveNtool to last 0.28.beta 1 too.
Strange: CNR on 19.3.2 work just like on 18.6.1 driver but Turtle algo with 19.3.2 driver on Vega 56 (64 bios) or Vega 64 (Asus) drop hashrate from 18 kh/s to 10 kh/s
Did someone try turtle algo on 19.3.2?
Seems like I am not the only one. I had similar results. L28+28 gives 10-11 Khs. Try 26+26, it would work fine around 17-18.5 Khs still not as good as other folks who can get L28+28 with earlier drivers. I was also lured by the no ppt arguments. Either i need to use wattman or my cards silicon are crap. I gave up and used the same 850mv ppt and ran at L26+26 getting 19.61 kh @ 1408/1100/850mv on 19.3.3. |
|
|
|
Even at 870mV, I am still unable to get a stable system running. Dead GPUs and hashrate drop to 15kH/s still occurs after several tens of minutes of mining. And the weird thing is hashrate drops happens to Hynix mem GPUs only. I can confirm the same behaviour on Vega 64 with samsung memory at L28+28, tried droping to L26+26 and still same results. Normal : 19.56, and after some random time 19.06 |
|
|
|
|
Show Posts
