20181107 10:29:33 WARN: Messy shutdown...
20181107 10:29:33 ERROR: Can't find share with device [ID=4, GPU #4], cuda exception in [Algorithm::find_shares, trexMemcpy(h_nonces, d_nonces, sizeof(h_nonces), trexMemcpyDeviceToHost), 170], an illegal memory access was encountered
20181107 10:29:33 ERROR: Can't find share with device [ID=0, GPU #0], cuda exception in [Algorithm::find_shares, trexMemcpy(h_nonces, d_nonces, sizeof(h_nonces), trexMemcpyDeviceToHost), 170], an illegal memory access was encountered
20181107 10:29:33 ERROR: Can't find share with device [ID=1, GPU #1], cuda exception in [Algorithm::find_shares, trexMemcpy(h_nonces, d_nonces, sizeof(h_nonces), trexMemcpyDeviceToHost), 170], an illegal memory access was encountered
20181107 10:29:33 ERROR: Can't find share with device [ID=13, GPU #13], cuda exception in [Algorithm::find_shares, trexMemcpy(h_nonces, d_nonces, sizeof(h_nonces), trexMemcpyDeviceToHost), 170], an illegal memory access was encountered
20181107 10:29:33 WARN: Logger: failed to copy file from 'F' to 'F': The system cannot find the file specified
20181107 10:29:33 ERROR: Can't find share with device [ID=10, GPU #10], cuda exception in [Algorithm::find_shares, trexMemcpy(h_nonces,
20181107 10:29:33 WARN: Logger: failed to copy file from 'F' to 'F': The system cannot find the file specified
Miner fails to rename and copy the log file into a new file and instead just writes over the log file when it crashes. using 7.3
Topic: T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 76. (Read 174982 times)
trexminer:
Issue of trex crashing after mining dev fee still exists in 0.7.3:
Issue of trex crashing after mining dev fee still exists in 0.7.3:
Code:
20181107 19:34:46 [ OK ] 210/210 - 4903.21 kH/s, 10ms
20181107 19:34:46 GPU #1: Zotac GTX 1050 Ti - 4903.21 kH/s, [T:54C, F:56%]
20181107 19:34:46 Uptime: 55 mins 46 secs
20181107 19:35:22 [ OK ] 211/211 - 4905.11 kH/s, 12ms
20181107 19:35:26 Started mining dev fee
20181107 19:36:26 Done mining dev fee
20181107 19:36:46 [ OK ] 212/212 - 4903.78 kH/s, 10ms
20181107 19:36:46 WARN: Messy shutdown...
20181107 19:36:47 Main loop finished.
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4067
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4068
Waiting for 0 seconds, press a key to continue ...
20181107 19:36:53 T-Rex NVIDIA GPU miner v0.7.3 - [CUDA v9.20]
20181107 19:36:53
20181107 19:36:53 NVIDIA Driver v416.16
20181107 19:36:53 CUDA devices available: 2
20181107 19:34:46 GPU #1: Zotac GTX 1050 Ti - 4903.21 kH/s, [T:54C, F:56%]
20181107 19:34:46 Uptime: 55 mins 46 secs
20181107 19:35:22 [ OK ] 211/211 - 4905.11 kH/s, 12ms
20181107 19:35:26 Started mining dev fee
20181107 19:36:26 Done mining dev fee
20181107 19:36:46 [ OK ] 212/212 - 4903.78 kH/s, 10ms
20181107 19:36:46 WARN: Messy shutdown...
20181107 19:36:47 Main loop finished.
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4067
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4068
Waiting for 0 seconds, press a key to continue ...
20181107 19:36:53 T-Rex NVIDIA GPU miner v0.7.3 - [CUDA v9.20]
20181107 19:36:53
20181107 19:36:53 NVIDIA Driver v416.16
20181107 19:36:53 CUDA devices available: 2
Thanks. This issue has just been identified and fixed.
0.7.4 will contain the fix
Maybe it also fixes the problem of not detecting socket closed as I reported at https://bitcointalksearch.org/topic/m.47650272 ?
trexminer:
Issue of trex crashing after mining dev fee still exists in 0.7.3:
Issue of trex crashing after mining dev fee still exists in 0.7.3:
Code:
20181107 19:34:46 [ OK ] 210/210 - 4903.21 kH/s, 10ms
20181107 19:34:46 GPU #1: Zotac GTX 1050 Ti - 4903.21 kH/s, [T:54C, F:56%]
20181107 19:34:46 Uptime: 55 mins 46 secs
20181107 19:35:22 [ OK ] 211/211 - 4905.11 kH/s, 12ms
20181107 19:35:26 Started mining dev fee
20181107 19:36:26 Done mining dev fee
20181107 19:36:46 [ OK ] 212/212 - 4903.78 kH/s, 10ms
20181107 19:36:46 WARN: Messy shutdown...
20181107 19:36:47 Main loop finished.
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4067
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4068
Waiting for 0 seconds, press a key to continue ...
20181107 19:36:53 T-Rex NVIDIA GPU miner v0.7.3 - [CUDA v9.20]
20181107 19:36:53
20181107 19:36:53 NVIDIA Driver v416.16
20181107 19:36:53 CUDA devices available: 2
20181107 19:34:46 GPU #1: Zotac GTX 1050 Ti - 4903.21 kH/s, [T:54C, F:56%]
20181107 19:34:46 Uptime: 55 mins 46 secs
20181107 19:35:22 [ OK ] 211/211 - 4905.11 kH/s, 12ms
20181107 19:35:26 Started mining dev fee
20181107 19:36:26 Done mining dev fee
20181107 19:36:46 [ OK ] 212/212 - 4903.78 kH/s, 10ms
20181107 19:36:46 WARN: Messy shutdown...
20181107 19:36:47 Main loop finished.
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4067
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4068
Waiting for 0 seconds, press a key to continue ...
20181107 19:36:53 T-Rex NVIDIA GPU miner v0.7.3 - [CUDA v9.20]
20181107 19:36:53
20181107 19:36:53 NVIDIA Driver v416.16
20181107 19:36:53 CUDA devices available: 2
Thanks. This issue has just been identified and fixed.
0.7.4 will contain the fix
why antivirus start to see 0.7.3 as virus but in older version it's not detect any thing .
trexminer:
Issue of trex crashing after mining dev fee still exists in 0.7.3:
Issue of trex crashing after mining dev fee still exists in 0.7.3:
Code:
20181107 19:34:46 [ OK ] 210/210 - 4903.21 kH/s, 10ms
20181107 19:34:46 GPU #1: Zotac GTX 1050 Ti - 4903.21 kH/s, [T:54C, F:56%]
20181107 19:34:46 Uptime: 55 mins 46 secs
20181107 19:35:22 [ OK ] 211/211 - 4905.11 kH/s, 12ms
20181107 19:35:26 Started mining dev fee
20181107 19:36:26 Done mining dev fee
20181107 19:36:46 [ OK ] 212/212 - 4903.78 kH/s, 10ms
20181107 19:36:46 WARN: Messy shutdown...
20181107 19:36:47 Main loop finished.
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4067
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4068
Waiting for 0 seconds, press a key to continue ...
20181107 19:36:53 T-Rex NVIDIA GPU miner v0.7.3 - [CUDA v9.20]
20181107 19:36:53
20181107 19:36:53 NVIDIA Driver v416.16
20181107 19:36:53 CUDA devices available: 2
20181107 19:34:46 GPU #1: Zotac GTX 1050 Ti - 4903.21 kH/s, [T:54C, F:56%]
20181107 19:34:46 Uptime: 55 mins 46 secs
20181107 19:35:22 [ OK ] 211/211 - 4905.11 kH/s, 12ms
20181107 19:35:26 Started mining dev fee
20181107 19:36:26 Done mining dev fee
20181107 19:36:46 [ OK ] 212/212 - 4903.78 kH/s, 10ms
20181107 19:36:46 WARN: Messy shutdown...
20181107 19:36:47 Main loop finished.
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4067
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4068
Waiting for 0 seconds, press a key to continue ...
20181107 19:36:53 T-Rex NVIDIA GPU miner v0.7.3 - [CUDA v9.20]
20181107 19:36:53
20181107 19:36:53 NVIDIA Driver v416.16
20181107 19:36:53 CUDA devices available: 2
What are the changes in the new version?
Can someone compare t-rex 072 and z-enemy 123 for x16r?
https://bitcointalksearch.org/topic/m.47207733
Miner v0.7.3 does not detect pool connection dropped.
With ZPool.ca, I use the algo autoswitch. When you connect to the "wrong" algo, the pool immediately disconnects. The miner waits the network timeout (default: 180 seconds) until it detects the pool is not there anymore. Other miners, such as ccminer, immediately detects the connection is lost, and if you have retries set to 0 (-r 0) it immediately exits.
Can this be fixed please?
With ZPool.ca, I use the algo autoswitch. When you connect to the "wrong" algo, the pool immediately disconnects. The miner waits the network timeout (default: 180 seconds) until it detects the pool is not there anymore. Other miners, such as ccminer, immediately detects the connection is lost, and if you have retries set to 0 (-r 0) it immediately exits.
Can this be fixed please?
Version updated to 0.7.3 Now you can download it on github
Can someone compare t-rex 072 and z-enemy 123 for x16r?
In my test at the same rigs ( 36h test ) t-rex 0.7.2 was faster than 1.23 z-enemy by 6^ 
@trexminer is this page fake?
https://github.com/trexminer/T-Rex/releases/tag/0.7.3
It shows he Joined GitHub on November 4, 2018.
https://github.com/trexminer
and i see here (bitcointalk ann page) there is version like 0.7.3
https://github.com/trexminer/T-Rex/releases/tag/0.7.3
It shows he Joined GitHub on November 4, 2018.
https://github.com/trexminer
and i see here (bitcointalk ann page) there is version like 0.7.3
No, this is our new github release repo. Our discord release message points to that page as well. We'll update this topic with the links soon if there are no major issues with 0.7.3
Tested on GTX1070, GTX1080, GTX1080ti. I've got about 2% increase of miner reported hashrate in comparision of v 0.7.2 at the same OC settings. Differences of power consumption aren't found. Will observe to the pool...
By the way if we don't reply to your message/issue here, that would likely mean we don't have the answer or simply don't have time. So please join our Discord channel at https://discord.gg/gj7jcYf , there's a large community and I'm sure someone will help you with your issue. Many thanks for understanding, guys.
@trexminer is this page fake?
https://github.com/trexminer/T-Rex/releases/tag/0.7.3
It shows he Joined GitHub on November 4, 2018.
https://github.com/trexminer
and i see here (bitcointalk ann page) there is version like 0.7.3
https://github.com/trexminer/T-Rex/releases/tag/0.7.3
It shows he Joined GitHub on November 4, 2018.
https://github.com/trexminer
and i see here (bitcointalk ann page) there is version like 0.7.3
No, this is our new github release repo. Our discord release message points to that page as well. We'll update this topic with the links soon if there are no major issues with 0.7.3
@trexminer is this page fake?
https://github.com/trexminer/T-Rex/releases/tag/0.7.3
It shows he Joined GitHub on November 4, 2018.
https://github.com/trexminer
and i see here (bitcointalk ann page) there is version like 0.7.3
https://github.com/trexminer/T-Rex/releases/tag/0.7.3
It shows he Joined GitHub on November 4, 2018.
https://github.com/trexminer
and i see here (bitcointalk ann page) there is version like 0.7.3
Quote
Use windows 10 1709 - it's 100% result.
Of couce I du this. But it is almost 2019 Year now and sometimes I want to try new version of windows with better DPI scale on 4k monitor. ))And as a relult because of this arror I can't install new Windows. ))
There is a big problem for gtx1050ti cards on x16r.
Firstly i will explain the problem.
I have many rigs and they are just include seperately gtx1070(8x quantity)- gtx1060 6gb(6x quantity) and they don't have any problem.
But i have another rig too and it include gtx1060 6gb (4 quantity) and gtx1050ti(2quantity). Total 4+2= 6 card
Time to talk about problem..
I don't set overclock for gtx1050ti. I gave different values for every cards on this rig but it set same overclock settings for gtx1060 6gb. I m explaining again, gtx1050ti works with gtx1060 6gb overclock settings despite give different values.
Also, on the motherboard gtx1050ti plug on gpu2 and gpu4 slot. But t-rex miner shows that they are plug on gpu4 and gpu5 slot. I think that problem is connected with this reason.
I added screenshots about that.
https://i.hizliresim.com/zMWaZ7.jpg overclock settings,
https://i.hizliresim.com/6N4rB0.jpg it shows that my gtx1050ti plug on gpu4 and gpu5
https://i.hizliresim.com/GDqP7r.png look at the temperatures, you can understand that gpu2 and gpu4 slot is gtx1050ti because of high temperatures. it works same overclock settings with gtx1060 6gb so their temperatures are high. Normally they works 1-2°C hight temparature than gtx1060 6gb.
Firstly i will explain the problem.
I have many rigs and they are just include seperately gtx1070(8x quantity)- gtx1060 6gb(6x quantity) and they don't have any problem.
But i have another rig too and it include gtx1060 6gb (4 quantity) and gtx1050ti(2quantity). Total 4+2= 6 card
Time to talk about problem..
I don't set overclock for gtx1050ti. I gave different values for every cards on this rig but it set same overclock settings for gtx1060 6gb. I m explaining again, gtx1050ti works with gtx1060 6gb overclock settings despite give different values.
Also, on the motherboard gtx1050ti plug on gpu2 and gpu4 slot. But t-rex miner shows that they are plug on gpu4 and gpu5 slot. I think that problem is connected with this reason.
I added screenshots about that.
https://i.hizliresim.com/zMWaZ7.jpg overclock settings,
https://i.hizliresim.com/6N4rB0.jpg it shows that my gtx1050ti plug on gpu4 and gpu5
https://i.hizliresim.com/GDqP7r.png look at the temperatures, you can understand that gpu2 and gpu4 slot is gtx1050ti because of high temperatures. it works same overclock settings with gtx1060 6gb so their temperatures are high. Normally they works 1-2°C hight temparature than gtx1060 6gb.
x16r algo
1080ti
Does this miner depend on memory?
in another words if I under clocking memory clock does it affect performance?
I'm mining with it on suprnova pool but I cant determine the avg hashrate per day is there any way to print it out?
Can I use static difficulty with t-rex?
Thank you
1080ti
Does this miner depend on memory?
in another words if I under clocking memory clock does it affect performance?
I'm mining with it on suprnova pool but I cant determine the avg hashrate per day is there any way to print it out?
Can I use static difficulty with t-rex?
Thank you
Windows 10 LTSC 2019. Miner error on GTX 1080ti MSI. Dll nvml not found in folder C:\Program Files\NVIDIA Corporation\NVSMI.
This last version of drivers in this windows does not hav folder NVSMI.
Use windows 10 1709 - it's 100% result. This last version of drivers in this windows does not hav folder NVSMI.
Windows 10 LTSC 2019. Miner error on GTX 1080ti MSI. Dll nvml not found in folder C:\Program Files\NVIDIA Corporation\NVSMI.
This last version of drivers in this windows does not hav folder NVSMI.
This last version of drivers in this windows does not hav folder NVSMI.
Jump to: