Can someone give me a .bat file to auto start this hole machine. Cant figure how to.
There is no batch file, I mean all you have to do is to put only your wallet number in the batch, after that in red team miner always you have to run the program as administrator, so right click to the exe-compatibility-run this program as administrator-apply-OK and after that you have to run your batch and play with mem tweak.... 
Topic: AMD Mem Tweak XL - Read/modify timings/pp/straps on the fly - page 35. (Read 58892 times)
@eliovp
@bobymoore
Thanks...I think I figured it out now...at least how it is working. I have yet to get the date sheets on samsung HBM2 but I digress. Anyhow it seems setting it lower then then default does nothing....after I checked what was told to me I was using extreme values to check. However actually raising it has increased my hashrate but I now I am not sure what the range is...but guessing it is just a range...and anything out of that range sets the default.
@bobymoore
Thanks...I think I figured it out now...at least how it is working. I have yet to get the date sheets on samsung HBM2 but I digress. Anyhow it seems setting it lower then then default does nothing....after I checked what was told to me I was using extreme values to check. However actually raising it has increased my hashrate but I now I am not sure what the range is...but guessing it is just a range...and anything out of that range sets the default.
Try latest GUI mate, you're using an old version.
You won't need overdriventool anymore, can do it all in the gui.
Cheerio!
[/quote
Yes I know that Eliovp! For some windows bug reason your last version don't work to this rig, but it works to another rig of mine, but as I said to my post before my rig lag-stuck a little bit and jam trying to find out why.
@eliovp sorry I do not know how quotes works on this forum.
Anyhow HBM2 on vega64 with Samsung. It does not seem to matter what setting you put in. I can do some screen shots. I mean the tool reads the setting you imput...but it does not have any actual effect on anything...as if it is being ignore.
Anyhow HBM2 on vega64 with Samsung. It does not seem to matter what setting you put in. I can do some screen shots. I mean the tool reads the setting you imput...but it does not have any actual effect on anything...as if it is being ignore.
Yeah, i'm aware ;-)
Check my post above
this part here
Quote
For HBM2 you can raise tCL to offer a little bit of extra stability.
It is however a fact that changing this, or lowering this to a crazy number won't have any effect.
I read somewhere that there are two places these timings are set, on the ASIC and on the RAM side.
The ASIC side is the one being changed here, which is not a problem, however, the RAM value is the one being used. (This only applies to Cas Latency and Write Latency i believe)
Thus, to be able to change this, we're going to have to change vbios strap or do this before the timings get loaded into the registers.
It is however a fact that changing this, or lowering this to a crazy number won't have any effect.
I read somewhere that there are two places these timings are set, on the ASIC and on the RAM side.
The ASIC side is the one being changed here, which is not a problem, however, the RAM value is the one being used. (This only applies to Cas Latency and Write Latency i believe)
Thus, to be able to change this, we're going to have to change vbios strap or do this before the timings get loaded into the registers.
Did you ever know that you're my hero? You are everything I would like to be.
@eliovp sorry I do not know how quotes works on this forum.
Anyhow HBM2 on vega64 with Samsung. It does not seem to matter what setting you put in. I can do some screen shots. I mean the tool reads the setting you imput...but it does not have any actual effect on anything...as if it is being ignore.
Anyhow HBM2 on vega64 with Samsung. It does not seem to matter what setting you put in. I can do some screen shots. I mean the tool reads the setting you imput...but it does not have any actual effect on anything...as if it is being ignore.
Yeah, i'm aware ;-)
Check my post above
this part here
Quote
For HBM2 you can raise tCL to offer a little bit of extra stability.
It is however a fact that changing this, or lowering this to a crazy number won't have any effect.
I read somewhere that there are two places these timings are set, on the ASIC and on the RAM side.
The ASIC side is the one being changed here, which is not a problem, however, the RAM value is the one being used. (This only applies to Cas Latency and Write Latency i believe)
Thus, to be able to change this, we're going to have to change vbios strap or do this before the timings get loaded into the registers.
It is however a fact that changing this, or lowering this to a crazy number won't have any effect.
I read somewhere that there are two places these timings are set, on the ASIC and on the RAM side.
The ASIC side is the one being changed here, which is not a problem, however, the RAM value is the one being used. (This only applies to Cas Latency and Write Latency i believe)
Thus, to be able to change this, we're going to have to change vbios strap or do this before the timings get loaded into the registers.
@eliovp sorry I do not know how quotes works on this forum.
Anyhow HBM2 on vega64 with Samsung. It does not seem to matter what setting you put in. I can do some screen shots. I mean the tool reads the setting you imput...but it does not have any actual effect on anything...as if it is being ignore. Unless I missing something. Other timings are working and do change things.
Anyhow HBM2 on vega64 with Samsung. It does not seem to matter what setting you put in. I can do some screen shots. I mean the tool reads the setting you imput...but it does not have any actual effect on anything...as if it is being ignore. Unless I missing something. Other timings are working and do change things.
Eliovp - can you possibly add a version somewhere on the gui?
I know its a pain, but I am looking at multiple version and comparing things and i get lost.
Thank you!
I know its a pain, but I am looking at multiple version and comparing things and i get lost.
Thank you!
Hey,
Yeah, i can do that.
There has been a request to add a --version flag to the cli version as well.
It's on my todo list!
For now, you could always check assembly info (right click exe), you can find version info in there.
@eliovp can you check something tCL does not seem to change anything. This was pointed out by someone else on reddit. Anyhow I tested it, and it does indeed seem to be true. You can set the tCL value to 0, 1 up to 50.
Are you referring to HBM2 or GDDR5?
For GDDR5 i disabled this (for the GUI) on purpose.
You can create a strap for the vbios with tCL being at 24 (decimal) for example and it will work just fine.
Now the strange thing about this is the fact that it should in theory be a value between 0 and 20.
I have to be honest here, i believe programming it on a live system with a value between 0 to 20 might just be possible, it should! , i have only tested this with a default Cas Latency of higher than 20. So that might have been the reason for the GPU to bail on me.
I will look into this in more depth.
For HBM2 you can raise tCL to offer a little bit of extra stability.
It is however a fact that changing this, or lowering this to a crazy number won't have any effect.
I read somewhere that there are two places these timings are set, on the ASIC and on the RAM side.
The ASIC side is the one being changed here, which is not a problem, however, the RAM value is the one being used. (This only applies to Cas Latency and Write Latency i believe)
Thus, to be able to change this, we're going to have to change vbios strap or do this before the timings get loaded into the registers.
In a way, perhaps a bit comparable to the dram values on the GDDR5 side.
These get loaded into the registers and based on clocks, they change.
I wish i had all the answers, but unfortunately, not "yet"
Cheers
Edit:
I made a good set up for my two vega 56@64,i get 2350 hash each, but my pc lag, stuck when I do anything even when I move mouse, I use red team miner, the amd mem tweak tool, win 10 pro 64,drivers 19.4.1,19.42.
what's your setup, can you share it, and what card you own?Try latest GUI mate, you're using an old version.
You won't need overdriventool anymore, can do it all in the gui.
Cheerio!
I made a good set up for my two vega 56@64,i get 2350 hash each, but my pc lag, stuck when I do anything even when I move mouse, I use red team miner, the amd mem tweak tool, win 10 pro 64,drivers 19.4.1,19.42.
what's your setup, can you share it, and what card you own?
@eliovp can you check something tCL does not seem to change anything. This was pointed out by someone else on reddit. Anyhow I tested it, and it does indeed seem to be true. You can set the tCL value to 0, 1 up to 50.
Eliovp - can you possibly add a version somewhere on the gui?
I know its a pain, but I am looking at multiple version and comparing things and i get lost.
Thank you!
I know its a pain, but I am looking at multiple version and comparing things and i get lost.
Thank you!
Thank you, latest version is working well with my Vega 64 running the lucky timings @ 1400/1060/900 averaging 2351h/s
https://i.imgur.com/rLe5ffu.png
https://i.imgur.com/rLe5ffu.png
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 clockhave 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
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
Quote from: CN_MAX_YOUR_VEGA.txt
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
--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
I get 50Mhs on Ethereum with these settings but on XMR only 876 any ideas why?,thx in advance!
I made a good set up for my two vega 56@64,i get 2350 hash each, but my pc lag, stuck when I do anything even when I move mouse, I use red team miner, the amd mem tweak tool, win 10 pro 64,drivers 19.4.1,19.42.
what's your setup, can you share it, and what card you own?
I made a good set up for my two vega 56@64,i get 2350 hash each, but my pc lag, stuck when I do anything even when I move mouse, I use red team miner, the amd mem tweak tool, win 10 pro 64,drivers 19.4.1,19.42.
Okay let's do this. Or moreover, please help a rookie out to reduce his wattage use and squeeze a few extra hash out with these non-modded cards.
First image is a RX580 4G & the second pic on the link is an RX480 8G.
Link: https://imgur.com/a/VOPhgjR
Many thanks!
First image is a RX580 4G & the second pic on the link is an RX480 8G.
Link: https://imgur.com/a/VOPhgjR
Many thanks!
Lower your voltage to 900mV for both core and memory. I had 2130MHz stable mem with a RX574 (Samsung mem) and less than 900mV. I lowered the speed to 2100MHz only because of the fans noise.
For the core, @1150MHz, the same GPU (Gigabyte gaming) only needed 850mV.
i cant because of bios mod need that voltage, if i undervolt it will drop the hashrate a lotFor the core, @1150MHz, the same GPU (Gigabyte gaming) only needed 850mV.
You should reconsider that mod - 31-32 ethash is doable w/ a simple strap update for samsung/micron at 900mv or less. 1150mv is extreme overkill for any algorithm.
So you were able to gain Mh with a RX480 bios modded?
How much gain you got ?
I was wondering since I have RX580s bios modded so I wanted to know if the gain is worth it.
thx
How much gain you got ?
I was wondering since I have RX580s bios modded so I wanted to know if the gain is worth it.
thx
Lower your voltage to 900mV for both core and memory. I had 2130MHz stable mem with a RX574 (Samsung mem) and less than 900mV. I lowered the speed to 2100MHz only because of the fans noise.
For the core, @1150MHz, the same GPU (Gigabyte gaming) only needed 850mV.
Lower your voltage to 900mV for both core and memory. I had 2130MHz stable mem with a RX574 (Samsung mem) and less than 900mV. I lowered the speed to 2100MHz only because of the fans noise.
For the core, @1150MHz, the same GPU (Gigabyte gaming) only needed 850mV.
rx480 8 gb, Happy mining!
Dude, you need to undervolt this GPU.
Jump to: