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

[ZeDRoYMaN]

Oh, 1070 on algo - mtp rig reboot every day.
1070Ti all ok. Maybe somebody knows how to fix it?
T-rex 0.15.8, nvidia 451.67, swap-30Gb, memory-16Gb

[tbearhere]

Hello,
I'm getting this error:
"can't find nonce with device [ID=0, GPU=0], cuda exception in [ProgPOW::ProgPOW::initEpoch, 342], out of memory"

I've been told GTX 1060 3gb can no longe mine RVN, is that true?
I got trex0.15.8 version cuda 10.0

Can some1 help me?

I had seen same problem 25.07.20.All my twelve rig showed this error. Changes pool and miners(T-Rex 15.8,Kawpowminer,NBMiner) don't help.
Interestingly 6GB cards work normal , but need disable 3GB cards on rig.Nowhere information for this problem(pools,miner guide,forums,official social network and programs ravencoin).
There was such an impression as if I alone faced this problem.But yours post shows me that I'm not the only one.
It is clear that the problem lies in the lack of RAM, despite the fact that this volume should be enough until next summer.Or this is another CUDA error

Yeah it was around that day mine stopped working, I asked in trex's discord channel and some1 said the 3gb stopped working... now idk what to mine since I kinda like RVN and gotta waste time researching another coin to mine and it's probably not as good as mining RVN

PROGPOW IS BASED ON ETHEREUM ALGORITHM--

And so is KAWPoW.  Notice that in the remark within the error message "cuda exception in [ProgPOW::ProgPOW::initEpoch, 342], out of memory", it states that KAWPoW is hashing on a DAG from "epoch 342".  The algorithm was developed to use all aspects of a GPU's compute capabilities as well as the GPU memory.  It is a really stressful and ASIC resistant algorithm.  Your 3GB card has no room in memory for the DAG.       --scryptr

A work around.
Yes! 3GB & 4GB GPUs can still mine cryptocurrency.
https://www.youtube.com/watch?v=ktxXKGlHg24

[sxemini]

Hello,
I'm getting this error:
"can't find nonce with device [ID=0, GPU=0], cuda exception in [ProgPOW::ProgPOW::initEpoch, 342], out of memory"

I've been told GTX 1060 3gb can no longe mine RVN, is that true?
I got trex0.15.8 version cuda 10.0

Can some1 help me?

I had seen same problem 25.07.20.All my twelve rig showed this error. Changes pool and miners(T-Rex 15.8,Kawpowminer,NBMiner) don't help.
Interestingly 6GB cards work normal , but need disable 3GB cards on rig.Nowhere information for this problem(pools,miner guide,forums,official social network and programs ravencoin).
There was such an impression as if I alone faced this problem.But yours post shows me that I'm not the only one.
It is clear that the problem lies in the lack of RAM, despite the fact that this volume should be enough until next summer.Or this is another CUDA error

Yeah it was around that day mine stopped working, I asked in trex's discord channel and some1 said the 3gb stopped working... now idk what to mine since I kinda like RVN and gotta waste time researching another coin to mine and it's probably not as good as mining RVN

PROGPOW IS BASED ON ETHEREUM ALGORITHM--

And so is KAWPoW.  Notice that in the remark within the error message "cuda exception in [ProgPOW::ProgPOW::initEpoch, 342], out of memory", it states that KAWPoW is hashing on a DAG from "epoch 342".  The algorithm was developed to use all aspects of a GPU's compute capabilities as well as the GPU memory.  It is a really stressful and ASIC resistant algorithm.  Your 3GB card has no room in memory for the DAG.       --scryptr

GTX 1060 6GB,Win 10 64-bit ,TT-miner 5.0.1.Output video in system Intel hd 610.MSI shows 89mb loading gp memory in idle and 2569mb  on miner(3072-2569=503mb).So we have 503mb free video memory and why GTX 1063 can not creating DAG file.In the error shown miner concerning lack of memory there is no point.in this situation I am surprised by the lack of any information.If you look 25 June (GMT+3)7:00 p.m from to 3:00 a.m
 https://2miners.com/ru/rvn-network-hashrate we see drop in network power Ravencoin by about 20-25 percent respectively and Difficulty.Conclusion almost all or part 3gb card dropped.Two weeks no information.All this is a little disappointing.

On Nvidia Cards, Windows10 reserve much vram. So a GTX 1060 3GB has only around 2500 mb available. Only solution is to switch to Linux or other coin.

[trexminer]

0.16.1
* Add memory tweaks for GDDR5 and GDDR5X cards (10xx series)
  --mt  Memory tweak mode (default: 0 - disabled). Range from 0 to 6.

* (kawpow, progpow) Faster DAG generation

NOTE:
Memory tweak mode

General recommendation is to start with 1, and then increase only if the GPU is stable.
The effect is similar to that of ETHlargementPill and can potentially increase hashrate by up to 7% when mining kawpow.
Supported on graphics cards with GDDR5 or GDDR5X memory only.
Requires running the miner with administrative privileges ("Run As Administrator" / "sudo").
Can be set to a comma separated list to apply different values to different cards.
Example: --mt 4 (applies tweak mode #4 to all cards that support this functionality)
                --mt 3,3,3,0 (applies tweak mode #3 to all cards except the last one)

[Divinity666]

Hm, i set mt 1 to test mining MTP, but if any mt parameter is set I can't change intensity through web interface, it remains same as in config forever.

ps This disappointing bug aside this update is quite good cos unlike ethpill --mt 1(only tried 1 so far) affects 1070 as well. Still even 1080Ti got better hashrate with mt 1 than with pill and mt-0. Lets hope OC will remain stable!

[chafer99]

I use T-rex for Kawpow (1080Ti´s) but still more rejected on Miningpoolhub (0.6%).

[tbearhere]

  Running cuda 11 decreased my hashrate without --mt. I'm unable to get it to run with --mt as Administrator through my batch file.  Error ... not recognized as an internal or external command. So I'm back to  T-REX 0.15.8  Running MTP algo win 10.

EDIT: I needed to open T-REX app. properties and set "it" as run as administrator.

[Bathmat]

  Running cuda 11 decreased my hashrate without --mt. I'm unable to get it to run with --mt as Administrator through my batch file.  Error ... not recognized as an internal or external command. So I'm back to  T-REX 0.15.8  Running MTP algo win 10.

When you run as admin it changes your folder to the Windows\system32 folder. You have to change directory back to your folder with the miner to launch it. Basic windows command line navigation stuff....

[tbearhere]

  Running cuda 11 decreased my hashrate without --mt. I'm unable to get it to run with --mt as Administrator through my batch file.  Error ... not recognized as an internal or external command. So I'm back to  T-REX 0.15.8  Running MTP algo win 10.

When you run as admin it changes your folder to the Windows\system32 folder. You have to change directory back to your folder with the miner to launch it. Basic windows command line navigation stuff....

Got it thx.... I needed to open T-REX app. properties and set "it" as run as administrator.  

[trexminer]

0.16.2
* (UI, API) Show which GPU generated nonce/solution for share submission
* (UI, API) Show per-GPU rejected/total share statistics
* (Web monitoring page) Auto-saving web monitoring page preferences (dark theme, chart on/off etc.)
* Add "--low-load" cmd line parameter to optionally opt in for using CUDA kernels that put less stress on the GPUs where running regular kernels cause instability. See "t-rex -h" or "t-rex-help.txt" for more details. Currently this is only applicable to "kawpow" and DAG generation in particular.

Bug fixes:
* "can't init enumerate, code -6" error when applying memory tweaks to P102/104/106 cards
* "can't init 999, 0x800b01a" error when applying memory tweaks on Windows 7
* memory tweaks stuck after the miner termination
* memory tweaks becoming inactive in case of network issues or overclock adjustments
* setting intensity through the web monitoring page is broken

[angelbbs]

X16Rv2 broken. Win 7

20200910 10:34:49 T-Rex NVIDIA GPU miner v0.16.2  -  [CUDA v11.0]
20200910 10:34:50 r.555a9ecfbe3a
20200910 10:34:50
20200910 10:34:50 NVIDIA Driver v445.87
20200910 10:34:50 CUDA devices available: 5
20200910 10:34:50
20200910 10:34:50 WARN: DevFee 1% (x16rv2)
20200910 10:34:50
20200910 10:34:50 URL : stratum+tcp://x16rv2.na.mine.zpool.ca:3637
20200910 10:34:50 USER: *****
20200910 10:34:50 PASS: c=BTC
20200910 10:34:50
20200910 10:34:50 Starting on: x16rv2.na.mine.zpool.ca:3637
20200910 10:34:50 ApiServer: HTTP server started on 0.0.0.0:4067
20200910 10:34:50 -------------------------------------------------------
20200910 10:34:50 For control navigate to: http://192.168.1.112:4067/trex
20200910 10:34:50 -------------------------------------------------------
20200910 10:34:50 ApiServer: Telnet server started on 0.0.0.0:4068
20200910 10:34:50 WARN: GPU #0[10000]: ASUS GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:50 Authorizing...
20200910 10:34:50 WARN: GPU #1[20000]: Gigabyte GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:50 Authorized successfully.
20200910 10:34:50 WARN: GPU #2[30000]: ASUS GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:51 WARN: GPU #3[50000]: ASUS GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:51 WARN: GPU #4[70000]: ASUS GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:57 WARN: New difficulty: 8 (0.03125)
20200910 10:34:57 x16rv2 block 378814, diff 12.451
20200910 10:34:57 Hash order DADE165098E2C923
20200910 10:34:57 ERROR: Can't find nonce with device [ID=1, GPU #1], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 WARN: Messy shutdown...
20200910 10:34:57 ERROR: Can't find nonce with device [ID=0, GPU #0], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 ERROR: Can't find nonce with device [ID=4, GPU #4], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 ERROR: Can't find nonce with device [ID=2, GPU #2], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 ERROR: Can't find nonce with device [ID=3, GPU #3], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 Main loop finished.
20200910 10:34:57 ApiServer: stopped listening on 0.0.0.0:4067
20200910 10:34:57 ApiServer: stopped listening on 0.0.0.0:4068
20200910 10:34:59 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...

[trexminer]

X16Rv2 broken. Win 7

Should be fixed in 0.17.2

[trexminer]

0.17.2
* Add "ethash" algorithm (for Ethereum). For Nicehash mining use "nicehash+tcp://" pool url prefix.
* Add "progpowz" algorithm (for Zano)
* Add "--pci-indexing" parameter: orders GPUs by PCI Bus Id (same as "--ab-indexing" but starts with 0)
* Add "--gpu-init-mode" parameter: enables sequential DAG generation to reduce load on power supplies
* Print hash rate if no shares have been found for more than 1 minute to indicate miner's activity

Bug fixes:
* CUDA 11 build not working on some algorithms (x25x and similar), and with RTX cards
* "GPU is idle" error when generating DAG on low-end cards
* "nan(ind)" in share rejection GPU stats
* Log files not rotated correctly

[joseph32]

"Add "ethash" algorithm (for Ethereum). For Nicehash mining use "nicehash+tcp://" pool url prefix."

This will be a problem when mining at NiceHash and using a management software like AwesomeMiner with multiple GPUs and Miners. Setting that prefix would also use the same prefix on other miners, which wont work. And so we cant use T-Rex for Ethereum.

Is it possible to just auto detect the pool? Thank you!

[tomaroc]

0.17.2
* Add "ethash" algorithm (for Ethereum). For Nicehash mining use "nicehash+tcp://" pool url prefix.

On gtx1070 works perfect! thanks

[Dr_Victor]

0.17.2
* Add "ethash" algorithm (for Ethereum). For Nicehash mining use "nicehash+tcp://" pool url prefix.

On gtx1070 works perfect! thanks

What do you have on gtx 1070 on ETH, 30+?

[tomaroc]

What do you have on gtx 1070 on ETH, 30+?

HiveOs power limit :
90W -> ~ 25
120W -> ~ 30
(Micron memory) works stable than claymore (nicehash)

[trexminer]

0.17.3
* ethash optimisations (1-2% on some cards, see --kernel in the help file for more details)
* Add x33 algorithm (for Qureno)

Bug fixes:
* Add --worker parameter to mitigate the issue with usernames containing dots
* Improved compatibility with various mining pools / protocols

[Shadow59]

0.17.3
* Add x33 algorithm (for Qureno)

Don't u plan to add new qureno algo?

[joseph32]

Hey Trex,

is it possible to add CTXC Cortex?

Would be awesome!