T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 41.

DGBfanster

member

Activity: 122

Merit: 10

Quote from: Hackintoshihope on January 11, 2021, 09:49:28 PM

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.

What I do is send to RMA (I only had to do it twice ever, so I'm lucky), buy a new card and sell the one that comes back from RMA. But you need to have spare cash for that.

dlh1963ua

jr. member

Activity: 61

Merit: 3

trexminer, can you implement option "-minspeed" or "-minhash" for control total hashrate?

ZeeeN

jr. member

Activity: 298

Merit: 3

trex is fastest miner for octopus?

trexminer

member

Activity: 283

Merit: 63

Quote from: maXonja on January 12, 2021, 02:59:17 AM

Quote from: ipp2 on January 11, 2021, 07:45:01 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

maXonja

newbie

Activity: 77

Merit: 0

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!

fearil

newbie

Activity: 2

Merit: 0

Quote from: fearil on January 12, 2021, 05: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 ?

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 ?

fearil

newbie

Activity: 2

Merit: 0

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 ?

maXonja

newbie

Activity: 77

Merit: 0

Quote from: ipp2 on January 11, 2021, 07:45:01 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

Hackintoshihope

jr. member

Activity: 37

Merit: 1

Quote from: DGBfanster on January 11, 2021, 07:20:59 PM

Quote from: Hackintoshihope on January 11, 2021, 04:10:19 PM

Quote from: DGBfanster on January 11, 2021, 02:31:11 PM

Quote from: Hackintoshihope on January 11, 2021, 01:16:54 PM

Quote from: trexminer on January 09, 2021, 08:22:56 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 """ -> """ 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.

ipp2

newbie

Activity: 37

Merit: 0

We need the option to just restart rig/miner at this point when the DAG grows.

DGBfanster

member

Activity: 122

Merit: 10

Quote from: Hackintoshihope on January 11, 2021, 04:10:19 PM

Quote from: DGBfanster on January 11, 2021, 02:31:11 PM

Quote from: Hackintoshihope on January 11, 2021, 01:16:54 PM

Quote from: trexminer on January 09, 2021, 08:22:56 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 """ -> """ 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.

Hackintoshihope

jr. member

Activity: 37

Merit: 1

Quote from: cryptoinvestor_x on January 11, 2021, 06:23:38 PM

Quote from: Hackintoshihope on January 11, 2021, 01:16:54 PM

Quote from: trexminer on January 09, 2021, 08:22:56 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 """ -> """ 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?

cryptoinvestor_x

newbie

Activity: 71

Merit: 0

Quote from: Hackintoshihope on January 11, 2021, 01:16:54 PM

Quote from: trexminer on January 09, 2021, 08:22:56 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 """ -> """ 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.

ManuBBXX

full member

Activity: 839

Merit: 100

Quote from: Hackintoshihope on January 11, 2021, 04:10:19 PM

Quote from: DGBfanster on January 11, 2021, 02:31:11 PM

Quote from: Hackintoshihope on January 11, 2021, 01:16:54 PM

Quote from: trexminer on January 09, 2021, 08:22:56 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 """ -> """ 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 Wink

Hackintoshihope

jr. member

Activity: 37

Merit: 1

Quote from: DGBfanster on January 11, 2021, 02:31:11 PM

Quote from: Hackintoshihope on January 11, 2021, 01:16:54 PM

Quote from: trexminer on January 09, 2021, 08:22:56 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 """ -> """ 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.

DGBfanster

member

Activity: 122

Merit: 10

Quote from: Hackintoshihope on January 11, 2021, 01:16:54 PM

Quote from: trexminer on January 09, 2021, 08:22:56 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 """ -> """ 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

Activity: 37

Merit: 1

Quote from: trexminer on January 09, 2021, 08:22:56 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 """ -> """ 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.

ManuBBXX

full member

Activity: 839

Merit: 100

0.19.7 works far better for eth mining with my 3060ti's than phoenixMiner.
Just switched, happy with that !
Thanks

bigslimvdub

member

Activity: 349

Merit: 23

Thoughts on adding easy K12 (sha3) for Nvidia/AMD?

ubik_paris

newbie

Activity: 5

Merit: 0

Quote from: trexminer on January 09, 2021, 11:35:11 PM

Quote from: ubik_paris on January 09, 2021, 05:23:12 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

Topic: T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 41. (Read 175032 times)