20191026 22:35:53
20191026 22:35:53 URL : stratum+tcp://eu.gos.cx:3637
20191026 22:35:53 USER: RBX1G6nYDMHVtyaZiQWySMZw1Bb2DEDpT8.rig
20191026 22:35:53 PASS: x
20191026 22:35:53
20191026 22:35:53 Starting on: eu.gos.cx:3637
20191026 22:35:53 ApiServer: HTTP server started on 0.0.0.0:4067
20191026 22:35:53 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
20191026 22:35:56 T-Rex NVIDIA GPU miner v0.14.6 - [CUDA v9.20]
20191026 22:36:01 r.ad1aa7ca3433
20191026 22:36:01
20191026 22:36:01 NVIDIA Driver v419.67
20191026 22:36:01 CUDA devices available: 4
20191026 22:36:01
20191026 22:36:01 WARN: DevFee 1% (x16rv2)
20191026 22:36:01
20191026 22:36:01 URL : stratum+tcp://eu.gos.cx:3637
20191026 22:36:01 USER: RBX1G6nYDMHVtyaZiQWySMZw1Bb2DEDpT8.rig
20191026 22:36:01 PASS: x
20191026 22:36:01
20191026 22:36:01 Starting on: eu.gos.cx:3637
20191026 22:36:01 ApiServer: HTTP server started on 0.0.0.0:4067
20191026 22:36:02 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
20191026 22:36:04 T-Rex NVIDIA GPU miner v0.14.6 - [CUDA v9.20]
20191026 22:36:04 r.ad1aa7ca3433
20191026 22:36:04
20191026 22:36:04 NVIDIA Driver v419.67
20191026 22:36:04 CUDA devices available: 4
20191026 22:36:04
20191026 22:36:04 WARN: DevFee 1% (x16rv2)
20191026 22:36:04
20191026 22:36:04 URL : stratum+tcp://eu.gos.cx:3637
20191026 22:36:04 USER: RBX1G6nYDMHVtyaZiQWySMZw1Bb2DEDpT8.rig
20191026 22:36:04 PASS: x
20191026 22:36:04
20191026 22:36:04 Starting on: eu.gos.cx:3637
20191026 22:36:04 ApiServer: HTTP server started on 0.0.0.0:4067
20191026 22:36:05 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
20191026 22:36:07 T-Rex NVIDIA GPU miner v0.14.6 - [CUDA v9.20]
20191026 22:36:07 r.ad1aa7ca3433
20191026 22:36:07
20191026 22:36:07 NVIDIA Driver v419.67
20191026 22:36:07 CUDA devices available: 4
20191026 22:36:07
20191026 22:36:07 WARN: DevFee 1% (x16rv2)
20191026 22:36:07
20191026 22:36:07 URL : stratum+tcp://eu.gos.cx:3637
20191026 22:36:07 USER: RBX1G6nYDMHVtyaZiQWySMZw1Bb2DEDpT8.rig
20191026 22:36:07 PASS: x
20191026 22:36:07
20191026 22:36:07 Starting on: eu.gos.cx:3637
20191026 22:36:07 ApiServer: HTTP server started on 0.0.0.0:4067
20191026 22:36:08 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
20191026 22:36:10 T-Rex NVIDIA GPU miner v0.14.6 - [CUDA v9.20]
20191026 22:36:10 r.ad1aa7ca3433
20191026 22:36:10
20191026 22:36:10 NVIDIA Driver v419.67
20191026 22:36:10 CUDA devices available: 4
20191026 22:36:10
20191026 22:36:10 WARN: DevFee 1% (x16rv2)
20191026 22:36:10
20191026 22:36:10 URL : stratum+tcp://eu.gos.cx:3637
20191026 22:36:10 USER: RBX1G6nYDMHVtyaZiQWySMZw1Bb2DEDpT8.rig
20191026 22:36:10 PASS: x
20191026 22:36:10
20191026 22:36:10 Starting on: eu.gos.cx:3637
20191026 22:36:10 ApiServer: HTTP server started on 0.0.0.0:4067
20191026 22:36:10 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
How can I fix it? The problem is only with t-rex, with any pool, any bat, other miners work without problems
Topic: T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 52. (Read 174976 times)
Not seeing any difference thanks.
Does it matter which trex cuda version? Running GTX 1050 Ti.
If u don't see any difference in hashes - it's doesn't matter
Does it matter which trex cuda version? Running GTX 1050 Ti.
Pool side seems fine as I'm mining at the same pool using my other systems too .But in this system's case once it loses GPU0 the miner crashes but the monitor keeps sending the same data again and again even if the miner is not hashing , The funny thing is miner doesn't restart instead it keeps showing previous data
Any more info i can provide you ?
Any more info i can provide you ?
T-rex still continues to run ,even after GPU Lost and miner crashes ,
Please help sort this out in your next update
Have you tried any another pool? seems you can't find any share long time and miner restarts. Also you can increase timeout parameter -T, --timeout - default it's 300 seconds, you can increase to 600 for example. Please help sort this out in your next update
T-rex still continues to run without hashes reflecting in the pool ,even after GPU Lost and miner crashes ,
Please help sort this out in your next update
20191023 08:40:48 Uptime: 16 hours 10 mins 29 secs | Algo: mtp | T-Rex v0.14.6
20191023 08:41:15 .[32m[ OK ].[0m 5780/5801 - 19.54 MH/s, 1038ms
20191023 08:41:25 WARN: NVML: can't get GPU #0, GPU is lost
20191023 08:42:41 mtp block 208498, diff 6995.706
20191023 08:45:41 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20191023 08:45:41 WARN: Connection with pool timed out. Trying to reconnect...
20191023 08:45:42 Authorizing...
20191023 08:45:42 Authorized successfully.
20191023 08:45:42 WARN: Server says: Welcome to the MintPond North American stratum.
20191023 08:45:42 WARN: New difficulty: 0.03125
20191023 08:45:42 mtp block 208498, diff 6995.706
20191023 08:45:42 WARN: Server says: Optimizing difficulty may take several minutes.
20191023 08:46:25 WARN: NVML: can't get GPU #0, GPU is lost
20191023 08:47:46 WARN: New difficulty: 0.015625
20191023 08:50:06 WARN: New difficulty: 0.0078125
20191023 08:51:25 WARN: NVML: can't get GPU #0, GPU is lost
20191023 08:53:06 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20191023 08:53:06 WARN: Connection with pool timed out. Trying to reconnect...
20191023 08:53:07 Authorizing...
20191023 08:53:07 Authorized successfully.
20191023 08:53:07 WARN: Server says: Welcome to the MintPond North American stratum.
20191023 08:53:07 WARN: New difficulty: 0.03125
20191023 08:53:07 mtp block 208498, diff 6995.706
20191023 08:53:07 WARN: Server says: Optimizing difficulty may take several minutes.
20191023 08:55:11 WARN: New difficulty: 0.015625
20191023 08:56:25 WARN: NVML: can't get GPU #0, GPU is lost
20191023 08:57:20 mtp block 208499, diff 6995.706
20191023 08:57:35 WARN: New difficulty: 0.0078125
20191023 09:00:35 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20191023 09:00:35 WARN: Connection with pool timed out. Trying to reconnec
Please help sort this out in your next update
20191023 08:40:48 Uptime: 16 hours 10 mins 29 secs | Algo: mtp | T-Rex v0.14.6
20191023 08:41:15 .[32m[ OK ].[0m 5780/5801 - 19.54 MH/s, 1038ms
20191023 08:41:25 WARN: NVML: can't get GPU #0, GPU is lost
20191023 08:42:41 mtp block 208498, diff 6995.706
20191023 08:45:41 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20191023 08:45:41 WARN: Connection with pool timed out. Trying to reconnect...
20191023 08:45:42 Authorizing...
20191023 08:45:42 Authorized successfully.
20191023 08:45:42 WARN: Server says: Welcome to the MintPond North American stratum.
20191023 08:45:42 WARN: New difficulty: 0.03125
20191023 08:45:42 mtp block 208498, diff 6995.706
20191023 08:45:42 WARN: Server says: Optimizing difficulty may take several minutes.
20191023 08:46:25 WARN: NVML: can't get GPU #0, GPU is lost
20191023 08:47:46 WARN: New difficulty: 0.015625
20191023 08:50:06 WARN: New difficulty: 0.0078125
20191023 08:51:25 WARN: NVML: can't get GPU #0, GPU is lost
20191023 08:53:06 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20191023 08:53:06 WARN: Connection with pool timed out. Trying to reconnect...
20191023 08:53:07 Authorizing...
20191023 08:53:07 Authorized successfully.
20191023 08:53:07 WARN: Server says: Welcome to the MintPond North American stratum.
20191023 08:53:07 WARN: New difficulty: 0.03125
20191023 08:53:07 mtp block 208498, diff 6995.706
20191023 08:53:07 WARN: Server says: Optimizing difficulty may take several minutes.
20191023 08:55:11 WARN: New difficulty: 0.015625
20191023 08:56:25 WARN: NVML: can't get GPU #0, GPU is lost
20191023 08:57:20 mtp block 208499, diff 6995.706
20191023 08:57:35 WARN: New difficulty: 0.0078125
20191023 09:00:35 Wait on data is timed out, 180 seconds have passed, 0 bytes in socket remained
20191023 09:00:35 WARN: Connection with pool timed out. Trying to reconnec
Why won't miner determine what GPU crashes? All it says is:
Also would be nice to have per GPU share(correct\incorrect) counters, not just total. That way you can is if one particular card gets all\most of incorrect shares....
Quote
20191019 21:54:38 [ OK ] 5610/5621 - 21.60 MH/s, 281ms
20191019 21:54:38 [ OK ] 5611/5622 - 21.60 MH/s, 282ms
20191019 21:55:01 [ OK ] 5612/5623 - 21.60 MH/s, 297ms
20191019 21:55:14 [ OK ] 5613/5624 - 21.60 MH/s, 281ms
20191019 21:55:34 WARN: WATCHDOG: T-Rex has a problem with GPU, terminating...
20191019 21:55:35 WARN: WATCHDOG: recovering T-Rex
20191019 21:55:37 T-Rex NVIDIA GPU miner v0.14.6 - [CUDA v10.0]
20191019 21:55:37 r.ad1aa7ca3433
20191019 21:55:37
20191019 21:55:37 NVIDIA Driver v419.35
20191019 21:55:37 CUDA devices available: 5
20191019 21:55:37
20191019 21:54:38 [ OK ] 5611/5622 - 21.60 MH/s, 282ms
20191019 21:55:01 [ OK ] 5612/5623 - 21.60 MH/s, 297ms
20191019 21:55:14 [ OK ] 5613/5624 - 21.60 MH/s, 281ms
20191019 21:55:34 WARN: WATCHDOG: T-Rex has a problem with GPU, terminating...
20191019 21:55:35 WARN: WATCHDOG: recovering T-Rex
20191019 21:55:37 T-Rex NVIDIA GPU miner v0.14.6 - [CUDA v10.0]
20191019 21:55:37 r.ad1aa7ca3433
20191019 21:55:37
20191019 21:55:37 NVIDIA Driver v419.35
20191019 21:55:37 CUDA devices available: 5
20191019 21:55:37
Also would be nice to have per GPU share(correct\incorrect) counters, not just total. That way you can is if one particular card gets all\most of incorrect shares....
Hi
I like the Dark Theme in the T-rex web GUI... But it always defaults back to the normal theme.
Is it possible to forcefully set the Dark Theme in the config file ?
Or is there maybe a way to use http GET or POST to force the Dark Theme ?
I like the Dark Theme in the T-rex web GUI... But it always defaults back to the normal theme.
Is it possible to forcefully set the Dark Theme in the config file ?
Or is there maybe a way to use http GET or POST to force the Dark Theme ?
Sorry, there is no way to disable them at the moment
They are very annoying, esp. in web interface - every time u refresh a page notification pops-up. Please add disabling feature!
How do I disable update notifications in miner and web-interface?
Sorry, there is no way to disable them at the moment
How do I disable update notifications in miner and web-interface?
-q, --quiet Quiet mode. No GPU stats at all.
--hide-date Don't show date in console.
--no-color Disable color output for console.
--no-nvml Disable NVML GPU stats.
--no-watchdog Disable built-in watchdog.
Use these parameters in the bat file.
Did you try to lower your -i intensity or overclocking?
20191013 00:13:22 GPU #0: Zotac GTX 1080 Ti - 31.54 MH/s, [T:63C, P:284W, F:63%, E:116kH/W]
20191013 00:13:22 GPU #1: Zotac GTX 1080 Ti - 32.11 MH/s, [T:66C, P:244W, F:65%, E:119kH/W]
20191013 00:13:22 GPU #2: Zotac GTX 1080 Ti - 31.68 MH/s, [T:65C, P:300W, F:64%, E:114kH/W]
20191013 00:13:22 GPU #3: Zotac GTX 1080 Ti - 31.99 MH/s, [T:65C, P:271W, F:65%, E:118kH/W]
20191013 00:13:22 GPU #4: Zotac GTX 1080 Ti - 31.01 MH/s, [T:67C, P:240W, F:67%, E:124kH/W]
20191013 00:13:22 GPU #5: Zotac GTX 1080 Ti - 31.48 MH/s, [T:62C, P:259W, F:62%, E:122kH/W]
20191013 00:13:22 GPU #6: Zotac GTX 1080 Ti - 31.50 MH/s, [T:61C, P:273W, F:61%, E:119kH/W]
20191013 00:13:22 GPU #7: Zotac GTX 1080 Ti - 31.66 MH/s, [T:62C, P:258W, F:62%, E:122kH/W]
20191013 00:13:22 Shares/min: 4.479 (Avr. 3.889), Avr.Power: 2123W, Avr.Efficiency: 119kH/W
20191013 00:13:22 Uptime: 15 mins 25 secs | Algo: x16rv2 | T-Rex v0.14.6
20191013 00:13:22 WD: shares 252/255, restarts 2
20191013 00:13:22 WD: 1 hour 9 mins 25 secs
20191013 00:13:22 WD: ======== GPU CRASH LIST ========
20191013 00:13:22 WD: GPU#4: 1
20191013 00:13:33 [ OK ] 61/61 - 254.21 MH/s, 195ms
20191013 00:13:47 [ OK ] 62/62 - 255.35 MH/s, 195ms
20191013 00:13:48 ERROR: Can't find nonce with device [ID=6, GPU #6], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 WARN: Messy shutdown...
20191013 00:13:48 ERROR: Can't find nonce with device [ID=3, GPU #3], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=1, GPU #1], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=7, GPU #7], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=0, GPU #0], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=2, GPU #2], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=4, GPU #4], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=5, GPU #5], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 Main loop finished.
20191013 00:13:48 ApiServer: stopped listening on 0.0.0.0:4067
20191013 00:13:48 ApiServer: stopped listening on 0.0.0.0:4068
20191013 00:13:49 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
20191013 00:13:52 T-Rex NVIDIA GPU miner v0.14.6 - [CUDA v10.0]
20191013 00:13:52 r.ad1aa7ca3433
20191013 00:13:52
20191013 00:13:52 NVIDIA Driver v430.86
20191013 00:13:52 CUDA devices available: 8
20191013 00:13:22 GPU #1: Zotac GTX 1080 Ti - 32.11 MH/s, [T:66C, P:244W, F:65%, E:119kH/W]
20191013 00:13:22 GPU #2: Zotac GTX 1080 Ti - 31.68 MH/s, [T:65C, P:300W, F:64%, E:114kH/W]
20191013 00:13:22 GPU #3: Zotac GTX 1080 Ti - 31.99 MH/s, [T:65C, P:271W, F:65%, E:118kH/W]
20191013 00:13:22 GPU #4: Zotac GTX 1080 Ti - 31.01 MH/s, [T:67C, P:240W, F:67%, E:124kH/W]
20191013 00:13:22 GPU #5: Zotac GTX 1080 Ti - 31.48 MH/s, [T:62C, P:259W, F:62%, E:122kH/W]
20191013 00:13:22 GPU #6: Zotac GTX 1080 Ti - 31.50 MH/s, [T:61C, P:273W, F:61%, E:119kH/W]
20191013 00:13:22 GPU #7: Zotac GTX 1080 Ti - 31.66 MH/s, [T:62C, P:258W, F:62%, E:122kH/W]
20191013 00:13:22 Shares/min: 4.479 (Avr. 3.889), Avr.Power: 2123W, Avr.Efficiency: 119kH/W
20191013 00:13:22 Uptime: 15 mins 25 secs | Algo: x16rv2 | T-Rex v0.14.6
20191013 00:13:22 WD: shares 252/255, restarts 2
20191013 00:13:22 WD: 1 hour 9 mins 25 secs
20191013 00:13:22 WD: ======== GPU CRASH LIST ========
20191013 00:13:22 WD: GPU#4: 1
20191013 00:13:33 [ OK ] 61/61 - 254.21 MH/s, 195ms
20191013 00:13:47 [ OK ] 62/62 - 255.35 MH/s, 195ms
20191013 00:13:48 ERROR: Can't find nonce with device [ID=6, GPU #6], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 WARN: Messy shutdown...
20191013 00:13:48 ERROR: Can't find nonce with device [ID=3, GPU #3], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=1, GPU #1], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=7, GPU #7], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=0, GPU #0], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=2, GPU #2], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=4, GPU #4], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 ERROR: Can't find nonce with device [ID=5, GPU #5], cuda exception in [Algorithm::find_nonces, 179], an illegal instruction was encountered
20191013 00:13:48 Main loop finished.
20191013 00:13:48 ApiServer: stopped listening on 0.0.0.0:4067
20191013 00:13:48 ApiServer: stopped listening on 0.0.0.0:4068
20191013 00:13:49 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...
20191013 00:13:52 T-Rex NVIDIA GPU miner v0.14.6 - [CUDA v10.0]
20191013 00:13:52 r.ad1aa7ca3433
20191013 00:13:52
20191013 00:13:52 NVIDIA Driver v430.86
20191013 00:13:52 CUDA devices available: 8
How do I disable update notifications in miner and web-interface?
0.14.6
Bug fixes:
* (Windows) High CPU usage on NVIDIA drivers 431+
* (Linux) SSL connections not working on HiveOS
* (Linux) "T-Rex instance wasn't validated" error despite firewall allowing all connections
* CUDA 9.1/9.2 versions of the miner will no longer work with RTX (Compute Capability 7.5+) cards
This is done because RTX cards either hash slower or don't work correctly (depending on the algo) on these versions, producing "result for ... does not validate on CPU" errors. Use the version built with CUDA 10.0 instead.
Bug fixes:
* (Windows) High CPU usage on NVIDIA drivers 431+
* (Linux) SSL connections not working on HiveOS
* (Linux) "T-Rex instance wasn't validated" error despite firewall allowing all connections
* CUDA 9.1/9.2 versions of the miner will no longer work with RTX (Compute Capability 7.5+) cards
This is done because RTX cards either hash slower or don't work correctly (depending on the algo) on these versions, producing "result for ... does not validate on CPU" errors. Use the version built with CUDA 10.0 instead.
HiveOS. Algo x16rv2. Intensity 23. 1060 3gb.
Every 5-60 minutes it writes an error:
ERROR: Can't find nonce with device [ID=1, GPU #1], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=3, GPU #3], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=0, GPU #0], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=2, GPU #2], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=4, GPU #4], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=5, GPU #5], cuda exception in [find_nonces, 179], an illegal memory access was encountered
Everything works without problems on exactly the same rig.
What could be the problem?
Every 5-60 minutes it writes an error:
ERROR: Can't find nonce with device [ID=1, GPU #1], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=3, GPU #3], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=0, GPU #0], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=2, GPU #2], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=4, GPU #4], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=5, GPU #5], cuda exception in [find_nonces, 179], an illegal memory access was encountered
Everything works without problems on exactly the same rig.
What could be the problem?
Riser
HiveOS. Algo x16rv2. Intensity 23. 1060 3gb.
Every 5-60 minutes it writes an error:
ERROR: Can't find nonce with device [ID=1, GPU #1], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=3, GPU #3], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=0, GPU #0], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=2, GPU #2], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=4, GPU #4], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=5, GPU #5], cuda exception in [find_nonces, 179], an illegal memory access was encountered
Everything works without problems on exactly the same rig.
What could be the problem?
Every 5-60 minutes it writes an error:
ERROR: Can't find nonce with device [ID=1, GPU #1], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=3, GPU #3], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=0, GPU #0], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=2, GPU #2], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=4, GPU #4], cuda exception in [find_nonces, 179], an illegal memory access was encountered
ERROR: Can't find nonce with device [ID=5, GPU #5], cuda exception in [find_nonces, 179], an illegal memory access was encountered
Everything works without problems on exactly the same rig.
What could be the problem?
Riser
Any benchmark on 1660ti ?
GPU #0: EVGA GTX 1660 Ti - 18.13 MH/s, [T:61C, P: 79W, F:25%, E:227kH/W]
TDP 79 watts
Pw 51%
Core 55+
-502 Mem
Afterburner
Algo X16Rv2 18.13 MH/s
EVGA GTX 1660 Ti XC Ultra
does anyone here know why nvidia 436.xx driver versions are eating up cpu resources while using trex miner? 431.xx versions and below doesnt have such issues. anyone encounter the same problem or is there a workaround solution to not use my cpu resources while mining.
This issue is fixed in T-Rex 0.14.5 (available in our discord channel, #download-links room)
Jump to: