ser_merged
Newbie
 Offline
Activity: 3
Merit: 0
|
 |
January 10, 2021, 04:51:50 AM |
|
Hello, do you have plans to fix ethash performance under win7 for Nvidia 10 series GPUs?
|
|
|
|
|
|
|
|
|
|
The forum was founded in 2009 by Satoshi and Sirius. It replaced a
SourceForge forum.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
maXonja
Newbie
Offline
Activity: 75
Merit: 0
|
|
January 10, 2021, 09:30:02 AM |
|
Is there any command to reboot rig after every DAG epoch change or if instability is detected?
Can you program that when miner detects instability/incorrect shares it activates reboot.bat in his folder?
This will solve problems with nVidia 3X00 cards and memory overclock issues at DAG epoch change
Because we have no use of this ""Instability detected" message is printed in case there are issues"
There is no command yet because we hope we solved the instability problem with 30xx cards in 0.19.7 for good. Please give it a try and let us know if you still experience issues. Wow, great job man, it seems that you fixed a problem I'm waiting now for next DAG epoch change to see how that's gonna go through But still, I would really like to have a command that restarts the rig on epoch change because when I started the miner on +1300 memory I was getting the message for instability on 2 cards, after that I started a miner with +1000, after 3min raised it on +1300 and it's all good, 0 incorrect shares from yesterday |
|
|
|
|
Da_Saint
Newbie
Offline
Activity: 2
Merit: 0
|
|
January 10, 2021, 12:21:00 PM |
|
0.19.7 works super-stable on SMOS even with OC maxed out - well done!
On top of that I'm getting few more hashes on a 8x1080Ti rig and it eats 20W less.
Thanks also to the SMOS guys, who prepared the update lighting fast. Great community!
|
|
|
|
|
ubik_paris
Newbie
Offline
Activity: 5
Merit: 0
|
|
January 10, 2021, 03:54:39 PM |
|
Hello
Windows defender is detecting a Beareuws.A!ml virus on 0.19.7 release.
What about it? false positive?
Yes, it is a false positive. We charge 1% fee, so spreading viruses and having bad reputation because of it is not what we're after. See https://github.com/trexminer/T-Rex#antivirus-alerts for more details. Not exactly a proof but you got a point.  Thank you for your answer |
|
|
|
|
|
bigslimvdub
|
|
January 10, 2021, 04:43:28 PM |
|
Thoughts on adding easy K12 (sha3) for Nvidia/AMD?
|
|
|
|
|
|
ManuBBXX
|
|
January 11, 2021, 09:30:11 AM |
|
0.19.7 works far better for eth mining with my 3060ti's than phoenixMiner.
Just switched, happy with that !
Thanks
|
|
|
|
|
Hackintoshihope
Jr. Member
Offline
Activity: 37
Merit: 1
|
|
January 11, 2021, 06:16:54 PM |
|
T-Rex 0.19.7* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs * ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues) * Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions * (API) Add new "pause" command for "control" handler to pause and resume mining * (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error Bug fixes: * ("x21s") "incorrect size of extranonce2" error * (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled * (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings). This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock. |
|
|
|
|
DGBfanster
Member
Offline
Activity: 122
Merit: 10
|
|
January 11, 2021, 07:31:11 PM |
|
T-Rex 0.19.7* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs * ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues) * Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions * (API) Add new "pause" command for "control" handler to pause and resume mining * (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error Bug fixes: * ("x21s") "incorrect size of extranonce2" error * (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled * (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings). This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock. What power are you using on the 3060Ti? I'm able to run with +1359 MHz on the memory @131W. With +1400 I get 1% incorrect shares |
|
|
|
|
Hackintoshihope
Jr. Member
Offline
Activity: 37
Merit: 1
|
|
January 11, 2021, 09:10:19 PM |
|
T-Rex 0.19.7* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs * ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues) * Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions * (API) Add new "pause" command for "control" handler to pause and resume mining * (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error Bug fixes: * ("x21s") "incorrect size of extranonce2" error * (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled * (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings). This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock. What power are you using on the 3060Ti? I'm able to run with +1359 MHz on the memory @131W. With +1400 I get 1% incorrect shares I use 60% power. I do not want to run the memory at such inflated values as it will degrade the memory 700 to 800 I have found to be stable in gaming and normal workloads so I am satisfied with this long term performance. However as stated .19.7 is completely unreliable when creating the DAG. |
|
|
|
|
|
ManuBBXX
|
|
January 11, 2021, 09:32:28 PM |
|
T-Rex 0.19.7* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs * ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues) * Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions * (API) Add new "pause" command for "control" handler to pause and resume mining * (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error Bug fixes: * ("x21s") "incorrect size of extranonce2" error * (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled * (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings). This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock. What power are you using on the 3060Ti? I'm able to run with +1359 MHz on the memory @131W. With +1400 I get 1% incorrect shares I use 60% power. I do not want to run the memory at such inflated values as it will degrade the memory 700 to 800 I have found to be stable in gaming and normal workloads so I am satisfied with this long term performance. However as stated .19.7 is completely unreliable when creating the DAG. Unless memory gets too hot (wich is not the case for gddr6 (non X), you'll not attempt to your memory life, trust me  |
|
|
|
|
cryptoinvestor_x
Newbie
Offline
Activity: 71
Merit: 0
|
|
January 11, 2021, 11:23:38 PM |
|
T-Rex 0.19.7* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs * ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues) * Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions * (API) Add new "pause" command for "control" handler to pause and resume mining * (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error Bug fixes: * ("x21s") "incorrect size of extranonce2" error * (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled * (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings). This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock. I have the same issue oddly enough with a 9 GPU rig, my 8 and 7 GPU 3060ti rigs work with no issues. I also freeze on DAG generation at the start of mining causing the rig to reboot. |
|
|
|
|
Hackintoshihope
Jr. Member
Offline
Activity: 37
Merit: 1
|
|
January 11, 2021, 11:49:55 PM |
|
T-Rex 0.19.7* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs * ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues) * Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions * (API) Add new "pause" command for "control" handler to pause and resume mining * (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error Bug fixes: * ("x21s") "incorrect size of extranonce2" error * (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled * (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings). This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock. I have the same issue oddly enough with a 9 GPU rig, my 8 and 7 GPU 3060ti rigs work with no issues. I also freeze on DAG generation at the start of mining causing the rig to reboot. Im glad that you are having the same issue... at first I thought my GPUs were just degrading but the previous version works without issue. Do you notice the same behavior reducing memory clocks increases stability with this release? |
|
|
|
|
DGBfanster
Member
Offline
Activity: 122
Merit: 10
|
|
January 12, 2021, 12:20:59 AM |
|
T-Rex 0.19.7* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs * ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues) * Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions * (API) Add new "pause" command for "control" handler to pause and resume mining * (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error Bug fixes: * ("x21s") "incorrect size of extranonce2" error * (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled * (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings). This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock. What power are you using on the 3060Ti? I'm able to run with +1359 MHz on the memory @131W. With +1400 I get 1% incorrect shares I use 60% power. I do not want to run the memory at such inflated values as it will degrade the memory 700 to 800 I have found to be stable in gaming and normal workloads so I am satisfied with this long term performance. However as stated .19.7 is completely unreliable when creating the DAG. That could or could not be an issue. I have 3 year warranty on my cards so I don't really care if the card is gonna blow up because it's up do Nvidia to limit overclocking capabilities. We're not doing bios mod or anything out of the ordinary. |
|
|
|
|
ipp2
Newbie
Offline
Activity: 37
Merit: 0
|
|
January 12, 2021, 12:45:01 AM |
|
We need the option to just restart rig/miner at this point when the DAG grows.
|
|
|
|
|
Hackintoshihope
Jr. Member
Offline
Activity: 37
Merit: 1
|
|
January 12, 2021, 02:49:28 AM
Last edit: January 12, 2021, 04:33:54 AM by Hackintoshihope |
|
T-Rex 0.19.7* ("ethash", "octopus", "kawpow") Improve stability for 30xx series GPUs * ("ethash") Verify overclock stability after DAG rebuild ("Instability detected" message is printed in case there are issues) * Add "--gpu-report-interval-s" parameter to control hashrate summary report frequency based on the number of share submissions * (API) Add new "pause" command for "control" handler to pause and resume mining * (Watchdog) Display a list of GPUs caused miner restart with "GPU is idle" error Bug fixes: * ("x21s") "incorrect size of extranonce2" error * (UI) Incorrect GPU index in share submission report when "--pci-indexing" mode is enabled * (API) Miner fails to switch algorithms on the fly for some ""<algo_from>" -> "<algo_to>"" combinations Completely unreliable for a 7 card 30series rig with medium memory overclocks 3060Ti +800MHz, 3070 +700MHz and +800MHz, 3090 +350MHz... It cannot create the DAG reliably it will hang and crash miner. However if memory overclocks are reduced by 200MHz on each card it will create DAG why is this? It works perfectly with version 0.19.5 and 0.19.4 (these I have tested with these settings). This is absolutely not a stable build for me... It just hangs unless used with an extremely low memory overclock. What power are you using on the 3060Ti? I'm able to run with +1359 MHz on the memory @131W. With +1400 I get 1% incorrect shares I use 60% power. I do not want to run the memory at such inflated values as it will degrade the memory 700 to 800 I have found to be stable in gaming and normal workloads so I am satisfied with this long term performance. However as stated .19.7 is completely unreliable when creating the DAG. That could or could not be an issue. I have 3 year warranty on my cards so I don't really care if the card is gonna blow up because it's up do Nvidia to limit overclocking capabilities. We're not doing bios mod or anything out of the ordinary. It is not the issue as .19.5 works at DAG creation but after some hours it also crashes... I’m switching to phonies minter for now to see if I continue to get stability issues also I do care as an RMA can take months. |
|
|
|
|
maXonja
Newbie
Offline
Activity: 75
Merit: 0
|
|
January 12, 2021, 07:59:17 AM |
|
We need the option to just restart rig/miner at this point when the DAG grows.
I absolutely agree, T-rex can you implement this? Just make a -dagrestart 1 command that goes to reboot.bat, which should be in the same folder as miner, at every DAG epoch change |
|
|
|
|
fearil
Newbie
Offline
Activity: 2
Merit: 0
|
|
January 12, 2021, 10:22:43 AM |
|
Hi everyone,
I have started mining with my 2060 super and I don't understand if the memory tweak option is really working : there is no effect in the hash rate and I can't see if the parameter is taken into account.
This is the command I start with administrative privilege :
t-rex.exe -a ethash --mt 6 -o stratum+tcp://eu1.ethermine.org:4444 -u my adress -p x -w rig0
Is there something wrong ? How can I check it is taken into account ?
|
|
|
|
|
fearil
Newbie
Offline
Activity: 2
Merit: 0
|
|
January 12, 2021, 10:47:14 AM |
|
Hi everyone,
I have started mining with my 2060 super and I don't understand if the memory tweak option is really working : there is no effect in the hash rate and I can't see if the parameter is taken into account.
This is the command I start with administrative privilege :
t-rex.exe -a ethash --mt 6 -o stratum+tcp://eu1.ethermine.org:4444 -u my adress -p x -w rig0
Is there something wrong ? How can I check it is taken into account ?
Sorry for the stupid question. RTX 2060 super have GDDR6 memory and memory tweak is working for GDDR5/X. I currently have a 42 MH/s rate @123W. Is there a way to be more efficient with my GPU ? |
|
|
|
|
maXonja
Newbie
Offline
Activity: 75
Merit: 0
|
|
January 12, 2021, 01:28:47 PM |
|
DAG epoch change from 387 to 388 passed without any problems on all 3 of my RTX 3060 Ti rigs (6 cards per rig) with +1300 OC on memory
Good job!
|
|
|
|
|
trexminer (OP)
Member
Offline
Activity: 283
Merit: 63
|
|
January 12, 2021, 02:01:52 PM |
|
We need the option to just restart rig/miner at this point when the DAG grows.
I absolutely agree, T-rex can you implement this? Just make a -dagrestart 1 command that goes to reboot.bat, which should be in the same folder as miner, at every DAG epoch change Yes, we plan to implement it in one of the future versions |
|
|
|
|
|
