Pages:
Author

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

newbie
Activity: 24
Merit: 0
Quick test ZCoin(XZC) MTP 3 minutes
CryptoDredge vs T-Rex vs TT-Miner

https://youtu.be/krYKmET_UzM
sr. member
Activity: 658
Merit: 250
Windows Defender keeps removing the exe because of Conteban.B!ml, whatever that's supposed to be. You should report that to Microsoft as the developer so they can remove this false positive. Surely it's that, right? Smiley
newbie
Activity: 40
Merit: 0
Has anyone else had an issue with version 0.11.1 and above having the miner shutdown after around 3 minutes with the error "T-Rex instance wasn't validated", "Messy shutdown"?

I'm mining MTP and have 2 RTX 2080's running in Windows 7 on the latest 430.86 nvidia drivers.

If I revert back to 0.11.0 I don't have any issues.

The miner tries to connect to *.trex-miner.com:443 to get the list of dev fee pools and then shuts down if failed. Please make sure connections to port 443 of those servers are not blocked by your firewall.

Thank you for the reply!

I tried checking my computer's firewall as you suggested and there are no blocks in place for port 443, or trex-miner.com. I also checked my router and there are no blocks there either.

I reinstalled Windows as I thought maybe there could have been a problem deeper in the machine, but again, after the reinstall, I still have issues with 0.11.1 and up halting with "T-Rex instance wasn't validated".

It's odd because I have 3 other computers running on the same network that have no issues. I even tried giving the machine a new IP address just in case I missed something on the router, but no luck.

I'm somewhat at a loss here  Undecided
member
Activity: 283
Merit: 63
Has anyone else had an issue with version 0.11.1 and above having the miner shutdown after around 3 minutes with the error "T-Rex instance wasn't validated", "Messy shutdown"?

I'm mining MTP and have 2 RTX 2080's running in Windows 7 on the latest 430.86 nvidia drivers.

If I revert back to 0.11.0 I don't have any issues.

The miner tries to connect to *.trex-miner.com:443 to get the list of dev fee pools and then shuts down if failed. Please make sure connections to port 443 of those servers are not blocked by your firewall.
newbie
Activity: 40
Merit: 0
Has anyone else had an issue with version 0.11.1 and above having the miner shutdown after around 3 minutes with the error "T-Rex instance wasn't validated", "Messy shutdown"?

I'm mining MTP and have 2 RTX 2080's running in Windows 7 on the latest 430.86 nvidia drivers.

If I revert back to 0.11.0 I don't have any issues.
newbie
Activity: 35
Merit: 0
T-REX 11.1 seems to be infected. Anti-virus reported it inflected. Maybe a false positive? Not taking the risk.

It's a false positive. Don't worry about it.

Anyone mining MTP successfully with t-rex? Teared down my rig after 12h  Embarrassed Would love to use T-rex for MTP because reported hashrate is higher than cryptodredges.
gtx1070, 70%tpd, 100core.

e:/ more infos on the crash: had a black screen, only mouse pointer visible and trex flooded my trex-directory with .log files every few seconds a new one. but there was not much info in these .logs, no crash report or similar.

I'm mining using GTX 1080, 16GB Virtual Memory with 4 GB RAM. No problems so far.
Do you have virtual memory set to high enough number? Which CPU are using with the rig?

4x1070ti, 8x1070, 8GB RAM, Intel Pentium G4560, v-mem 122'880 (12x(1024x8)mb.
what oc settings are you using?

e:/ giving it another try with 196'608mb v-mem.

Did this help?   I've got 2 6x1080ti rigs that have been working fine on MTP for weeks with 75000mb of VM but my machine with 1 x 1080ti and 2 x 2080ti's crashes almost instantly on MTP, all other algos are fine with the Trex miner...I'm a bit baffled...Uninstalled the driver completely and reinstalled...It's always one of the 2080 ti's that crashes and goes to full fan...Sometimes one sometimes another...1080ti is fine.

In my case yes, doubled the VMem and since then I‘m fine.
newbie
Activity: 17
Merit: 0
Code:
20190618 23:38:51 Starting on: pool.minermore.com:4501
20190618 23:38:51 ApiServer: HTTP server started on 0.0.0.0:4067
20190618 23:38:51 WARN: NVML: can't get power for GPU #0, not supported
20190618 23:38:51 ------------------------------------------------------
20190618 23:38:51 For control navigate to: http://192.168.0.10:4067/trex
20190618 23:38:51 ------------------------------------------------------
20190618 23:38:51 ApiServer: Telnet server started on 0.0.0.0:4068
20190618 23:38:51 Authorizing...
20190618 23:38:51 ERROR: Can't initialize device [ID=0, GPU #0], cuda exception in [trexInitializerM, 207], unspecified launch failure
20190618 23:38:51 WARN: Messy shutdown...
20190618 23:38:51 Authorized successfully.
20190618 23:38:51 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...


Help. I'm getting this when ever I try and run it. I'm using a 780ti.

Hi, 780ti is Compute Capability 3.5 (read: too old), T-Rex only supports CC 5.0+ cards. https://developer.nvidia.com/cuda-gpus
Yikes, guess I won't be mining x16rt Sad
member
Activity: 640
Merit: 56
minerstat


Help, how do I solve this? I am mining veil, this one is from bsod.pw pool and miner doesn't connect at all. The same problem occurs when I connect to suprnova pool but it connects after couple tries.


Port already in use or blocked by firewall.
newbie
Activity: 6
Merit: 0
https://imgur.com/Gk1RvtT

Help, how do I solve this? I am mining veil, this one is from bsod.pw pool and miner doesn't connect at all. The same problem occurs when I connect to suprnova pool but it connects after couple tries.
member
Activity: 283
Merit: 63
Code:
20190618 23:38:51 Starting on: pool.minermore.com:4501
20190618 23:38:51 ApiServer: HTTP server started on 0.0.0.0:4067
20190618 23:38:51 WARN: NVML: can't get power for GPU #0, not supported
20190618 23:38:51 ------------------------------------------------------
20190618 23:38:51 For control navigate to: http://192.168.0.10:4067/trex
20190618 23:38:51 ------------------------------------------------------
20190618 23:38:51 ApiServer: Telnet server started on 0.0.0.0:4068
20190618 23:38:51 Authorizing...
20190618 23:38:51 ERROR: Can't initialize device [ID=0, GPU #0], cuda exception in [trexInitializerM, 207], unspecified launch failure
20190618 23:38:51 WARN: Messy shutdown...
20190618 23:38:51 Authorized successfully.
20190618 23:38:51 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...


Help. I'm getting this when ever I try and run it. I'm using a 780ti.

Hi, 780ti is Compute Capability 3.5 (read: too old), T-Rex only supports CC 5.0+ cards. https://developer.nvidia.com/cuda-gpus
newbie
Activity: 17
Merit: 0
Code:
20190618 23:38:51 Starting on: pool.minermore.com:4501
20190618 23:38:51 ApiServer: HTTP server started on 0.0.0.0:4067
20190618 23:38:51 WARN: NVML: can't get power for GPU #0, not supported
20190618 23:38:51 ------------------------------------------------------
20190618 23:38:51 For control navigate to: http://192.168.0.10:4067/trex
20190618 23:38:51 ------------------------------------------------------
20190618 23:38:51 ApiServer: Telnet server started on 0.0.0.0:4068
20190618 23:38:51 Authorizing...
20190618 23:38:51 ERROR: Can't initialize device [ID=0, GPU #0], cuda exception in [trexInitializerM, 207], unspecified launch failure
20190618 23:38:51 WARN: Messy shutdown...
20190618 23:38:51 Authorized successfully.
20190618 23:38:51 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...


Help. I'm getting this when ever I try and run it. I'm using a 780ti.
jr. member
Activity: 161
Merit: 1
T-REX 11.1 seems to be infected. Anti-virus reported it inflected. Maybe a false positive? Not taking the risk.

It's a false positive. Don't worry about it.

Anyone mining MTP successfully with t-rex? Teared down my rig after 12h  Embarrassed Would love to use T-rex for MTP because reported hashrate is higher than cryptodredges.
gtx1070, 70%tpd, 100core.

e:/ more infos on the crash: had a black screen, only mouse pointer visible and trex flooded my trex-directory with .log files every few seconds a new one. but there was not much info in these .logs, no crash report or similar.

I'm mining using GTX 1080, 16GB Virtual Memory with 4 GB RAM. No problems so far.
Do you have virtual memory set to high enough number? Which CPU are using with the rig?

4x1070ti, 8x1070, 8GB RAM, Intel Pentium G4560, v-mem 122'880 (12x(1024x8)mb.
what oc settings are you using?

e:/ giving it another try with 196'608mb v-mem.

Did this help?   I've got 2 6x1080ti rigs that have been working fine on MTP for weeks with 75000mb of VM but my machine with 1 x 1080ti and 2 x 2080ti's crashes almost instantly on MTP, all other algos are fine with the Trex miner...I'm a bit baffled...Uninstalled the driver completely and reinstalled...It's always one of the 2080 ti's that crashes and goes to full fan...Sometimes one sometimes another...1080ti is fine.
newbie
Activity: 3
Merit: 0
Getting a lot of rejects saying "MTP Verify Failed"   
sr. member
Activity: 954
Merit: 250
Please, share speed on Beenode for cards, you have tested.
member
Activity: 283
Merit: 63
T-Rex 0.12.0
Add honeycomb algorithm (Beenode coin)
Fix "GPU ... is idle" error when there is a pool connection problem
newbie
Activity: 35
Merit: 0
T-REX 11.1 seems to be infected. Anti-virus reported it inflected. Maybe a false positive? Not taking the risk.

It's a false positive. Don't worry about it.

Anyone mining MTP successfully with t-rex? Teared down my rig after 12h  Embarrassed Would love to use T-rex for MTP because reported hashrate is higher than cryptodredges.
gtx1070, 70%tpd, 100core.

e:/ more infos on the crash: had a black screen, only mouse pointer visible and trex flooded my trex-directory with .log files every few seconds a new one. but there was not much info in these .logs, no crash report or similar.

I'm mining using GTX 1080, 16GB Virtual Memory with 4 GB RAM. No problems so far.
Do you have virtual memory set to high enough number? Which CPU are using with the rig?

4x1070ti, 8x1070, 8GB RAM, Intel Pentium G4560, v-mem 122'880 (12x(1024x8)mb.
what oc settings are you using?

e:/ giving it another try with 196'608mb v-mem.
sr. member
Activity: 861
Merit: 281
T-REX 11.1 seems to be infected. Anti-virus reported it inflected. Maybe a false positive? Not taking the risk.

It's a false positive. Don't worry about it.

Anyone mining MTP successfully with t-rex? Teared down my rig after 12h  Embarrassed Would love to use T-rex for MTP because reported hashrate is higher than cryptodredges.
gtx1070, 70%tpd, 100core.

e:/ more infos on the crash: had a black screen, only mouse pointer visible and trex flooded my trex-directory with .log files every few seconds a new one. but there was not much info in these .logs, no crash report or similar.

I'm mining using GTX 1080, 16GB Virtual Memory with 4 GB RAM. No problems so far.
Do you have virtual memory set to high enough number? Which CPU are using with the rig?
newbie
Activity: 35
Merit: 0
Anyone mining MTP successfully with t-rex? Teared down my rig after 12h  Embarrassed Would love to use T-rex for MTP because reported hashrate is higher than cryptodredges.
gtx1070, 70%tpd, 100core.

e:/ more infos on the crash: had a black screen, only mouse pointer visible and trex flooded my trex-directory with .log files every few seconds a new one. but there was not much info in these .logs, no crash report or similar.
newbie
Activity: 11
Merit: 0
Turns out (after reinstalling the Cuda drivers) that I have a flaky 1080Ti card.. :-(
Good thing it's under warranty! :-)

Been mining fine for a few hours with the suspect card excluded in the command line.





For the past few weeks, T-Rex has been shutting down multiple times during the day. Causing me to have to restart the whole miner. 4x1080T1 on Unbuntu.
No errors are entered in the T-Rex logs. The program just stops and crashes..

I have the cards running at default voltages and no overclock at all.

I'm seeing other users who are having similar issues.

Hi, could you please try the latest version 0.10.2? We fixed a few stability issues. https://github.com/trexminer/T-Rex/releases/tag/0.10.2
newbie
Activity: 15
Merit: 0
Guys what does " WD: shares 100/120 " mean ??

https://i.imgur.com/SSUjDDn.png

It's the number of accepted/total shares. The internal miner share counter starts from 0 every time the miner is restarted while the watchdog preserve the stats across miner restarts.

thank you Trexminer  Wink thats nice functionality

Can you help me please with setting logging? I managed to set it, but it always rewrites the log whenever miner restarts, instead of creating new file (with date/time ).  Roll Eyes
My command is :

Code:
--logpath log.txt
Pages:
Jump to: