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

[ZeeeN]

trex is fastest miner for octopus?

[1714175094]

1714175094

[dlh1963ua]

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

[DGBfanster]

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.

[trexminer]

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

So, what should happen when total hashrate drops to "minspeed"?

[maXonja]

I think that you can again redirect it to reboot.bat for example, phoenix can do that, claymore was also doing that

[ipp2]

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

You got 4 days to do it lol

[dlh1963ua]

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

So, what should happen when total hashrate drops to "minspeed"?

I think, if the last three or five "checks" of the total hash rate are lower than the one specified in "minspeed" - redirect it to reboot.bat for example
It would be ideal to define the time of this "checks" as a separate parameter (for example every 3, 5, 10 minutes) and
print it (total hashrate, total shares, etc) to stream and/or log file

[joseph32]

Hey T-Rex,

can you please add Cortex CTXC?

[denaiser]

Hello, do you have plans to fix ethash performance under win7 for Nvidia 10 series GPUs?

It's really!

Millions of miners around the world are waiting for this

[Blockpusher]

Hello, do you have plans to fix ethash performance under win7 for Nvidia 10 series GPUs?

It's really!

Millions of miners around the world are waiting for this

Millions of miners around the world have upgraded to windows10 or Linux to solve this problem
Or maybe Gminer v2.38 fix this? (not tested, no more win7 here) and Gminer give less shares than T-Rex with my 1070 rig.

Upgrade!

[geck]

I'm seeing hashrate fluctuation on my 3090s of about 3MH/s (119-122MH/s) whereas phoenixminer is relatively stable (~0.1MH/s variation with a hashrate of 125MH/s). GPU-Z does not indicate power or thermal throttling.
T-rex works perfectly fine on all other 30 series cards.

[guyman]

I have an Asus Strix RTX 3090 OC along with a Gigabyte 1660 Super.  I mine ETH using t-rex and phoenix miner 5.4c and am getting very low hash rates with my 3090. 

When I start the miner, my 3090's core clock drops from 1860mhz to fluctuating around 900-1200mhz and memory clock drops from 9751mhz to 9501mhz.  Temp is about 50 and 270W.  Hash rate starts around 100 then drops to around 92. 

No issues with my 1660 Super.  If I unplug the 1660 Super, I still have the same problem with the 3090. 

I have a relatively new build (Asus X570 MB, Ryzen 7 3800X).  The 3090 performs great on bench mark test (userbenchmark) and stress tests (Kombustor) where I can go +160 mhz core clock and +1000mhz memory clock and be stable.  When I turn those OC settings on with MSI Afterburner when mining, my hash rate actually goes down even further (core clock sticks about 900, memory clock goes up to 1051 with hash rate of 90) . 

Any idea what could be causing the problem and how to fix it so I can get around a 120 hash rate?

[Hackintoshihope]

I have an Asus Strix RTX 3090 OC along with a Gigabyte 1660 Super.  I mine ETH using t-rex and phoenix miner 5.4c and am getting very low hash rates with my 3090. 

When I start the miner, my 3090's core clock drops from 1860mhz to fluctuating around 900-1200mhz and memory clock drops from 9751mhz to 9501mhz.  Temp is about 50 and 270W.  Hash rate starts around 100 then drops to around 92. 

No issues with my 1660 Super.  If I unplug the 1660 Super, I still have the same problem with the 3090. 

I have a relatively new build (Asus X570 MB, Ryzen 7 3800X).  The 3090 performs great on bench mark test (userbenchmark) and stress tests (Kombustor) where I can go +160 mhz core clock and +1000mhz memory clock and be stable.  When I turn those OC settings on with MSI Afterburner when mining, my hash rate actually goes down even further (core clock sticks about 900, memory clock goes up to 1051 with hash rate of 90) . 

Any idea what could be causing the problem and how to fix it so I can get around a 120 hash rate?

Yes memory power throttle you need air flow on the backplate of your 3090.

[pr0ximus]

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

So, what should happen when total hashrate drops to "minspeed"?

I think, if the last three or five "checks" of the total hash rate are lower than the one specified in "minspeed" - redirect it to reboot.bat for example
It would be ideal to define the time of this "checks" as a separate parameter (for example every 3, 5, 10 minutes) and
print it (total hashrate, total shares, etc) to stream and/or log file

Yes, this would be a very useful thing to have. I also had noticed only after many hours of reduced (throttled) hash rates and had to manually restart the rig to bring it back to normal hash rates.
Having a way to check min hash speed 'x' after certain minutes 't' and take action (to call reboot.bat) would help many users of t-rex

[guyman]

I have an Asus Strix RTX 3090 OC along with a Gigabyte 1660 Super.  I mine ETH using t-rex and phoenix miner 5.4c and am getting very low hash rates with my 3090. 

When I start the miner, my 3090's core clock drops from 1860mhz to fluctuating around 900-1200mhz and memory clock drops from 9751mhz to 9501mhz.  Temp is about 50 and 270W.  Hash rate starts around 100 then drops to around 92. 

No issues with my 1660 Super.  If I unplug the 1660 Super, I still have the same problem with the 3090. 

I have a relatively new build (Asus X570 MB, Ryzen 7 3800X).  The 3090 performs great on bench mark test (userbenchmark) and stress tests (Kombustor) where I can go +160 mhz core clock and +1000mhz memory clock and be stable.  When I turn those OC settings on with MSI Afterburner when mining, my hash rate actually goes down even further (core clock sticks about 900, memory clock goes up to 1051 with hash rate of 90) . 

Any idea what could be causing the problem and how to fix it so I can get around a 120 hash rate?

Yes memory power throttle you need air flow on the backplate of your 3090.

Thank you.  With that info, I found this thread.  Looks like the latest 3090 driver update is causing the problem as NVIDIA dialed things back due to high memory temps.
 
https://www.techpowerup.com/forums/threads/nvidia-461-09-driver-on-a-3090-and-the-secret-memory-perfcap.276968/

 
   
 

[ubik_paris]

I have an Asus Strix RTX 3090 OC along with a Gigabyte 1660 Super.  I mine ETH using t-rex and phoenix miner 5.4c and am getting very low hash rates with my 3090. 

When I start the miner, my 3090's core clock drops from 1860mhz to fluctuating around 900-1200mhz and memory clock drops from 9751mhz to 9501mhz.  Temp is about 50 and 270W.  Hash rate starts around 100 then drops to around 92. 

No issues with my 1660 Super.  If I unplug the 1660 Super, I still have the same problem with the 3090. 

I have a relatively new build (Asus X570 MB, Ryzen 7 3800X).  The 3090 performs great on bench mark test (userbenchmark) and stress tests (Kombustor) where I can go +160 mhz core clock and +1000mhz memory clock and be stable.  When I turn those OC settings on with MSI Afterburner when mining, my hash rate actually goes down even further (core clock sticks about 900, memory clock goes up to 1051 with hash rate of 90) . 

Any idea what could be causing the problem and how to fix it so I can get around a 120 hash rate?

Yes memory power throttle you need air flow on the backplate of your 3090.

Thank you.  With that info, I found this thread.  Looks like the latest 3090 driver update is causing the problem as NVIDIA dialed things back due to high memory temps.
 
https://www.techpowerup.com/forums/threads/nvidia-461-09-driver-on-a-3090-and-the-secret-memory-perfcap.276968/

 
   
 

Interesting I have the same pb on a 3090. Core Mhz at 900 - 855 Mhz, Mem at 9501 Mhz.

[bigslimvdub]

Good miner. I was running ethminer and 61c 28.5Mh on 1070ti. Trex miner I am running 49c and 29Mh same clock settings -40 +550 80% power. IIRC I had this same issue in the past with ethminer.

Is this the max these cards can run? Asus rog 1070ti on latest win10 Nvidia drivers.

[joseph32]

Yes, this would be a very useful thing to have. I also had noticed only after many hours of reduced (throttled) hash rates and had to manually restart the rig to bring it back to normal hash rates.
Having a way to check min hash speed 'x' after certain minutes 't' and take action (to call reboot.bat) would help many users of t-rex

Just use AwesomeMiner. You can create rules for everything.

[trexminer]

T-Rex 0.19.9

* Add ability to execute custom scripts upon certain events with new parameters:
"--script-start"
"--script-epoch-change"
"--script-crash"
"--script-low-hash"
* ("ethash", "kawpow", "octopus") Add "--dag-build-mode" parameter to fine tune DAG build mode (mostly to help with various stability issues, see readme for details)
* Allow non-existent GPU indices passed in to "--devices" / "-d" parameter: the miner will display a warning message but will continue mining using the GPUs it could find)
* Cosmetic changes: improve error descriptions, display block number when mining solo at some pools (2miners)

Bug fixes:
* ("ethash", "kawpow", "octopus") Stability regression for Pascal GPUs
* Mining pool difficulty is not always updated in the summary report (https://github.com/trexminer/T-Rex/issues/131)

**NOTE**: if you experience stability issues when mining "ethash" right at the start or upon epoch change, e.g. some GPUs fail start with "GPU is idle" or "NVML: can't get GPU#" errors, try running with "--gpu-init-mode 1", it will force sequential GPU initialisation and reduce the load on your hardware (set to 2, 3, etc to indicate how many cards may be generating DAG in parallel)

[maXonja]

Wow, I'm going to test it later... Thank you man, it's really nice to see a miner dev who's listening to miners and doing fast updates!