would it be possible to enable a customizable table on the readout? grouping by graphics card model #? I have all 1070s but have some different models with different clocks. would like to group them together in different tables or columns to get averages for each model or group of models I have 14 1070s but 8 are EVGA FTW (model: 08G-P4-6276) the rest are EVGA SCs but 2 model numbers 08G-P4-5173/08G-P4-6173. I'd like to option to group models together. see the averages of the FTW models and the SC models, separately
Order of GPUs isn't random like in EWBF miner, GPUs sorted by bus id, order is same as in nvidia-smi or MSI Afterburner. In next update we are planing also display vendor name (example EVGA GTX 1070 / MSI GTX 1070), may be in future updates we will display full GPU name as well. I'm referring to the table in telemetry. would be nice for the page grouped by model #s. so each group of model #s has their own averages
|
|
|
would it be possible to enable a customizable table on the readout? grouping by graphics card model #? I have all 1070s but have some different models with different clocks. would like to group them together in different tables or columns to get averages for each model or group of models I have 14 1070s but 8 are EVGA FTW (model: 08G-P4-6276) the rest are EVGA SCs but 2 model numbers 08G-P4-5173/08G-P4-6173. I'd like to option to group models together. see the averages of the FTW models and the SC models, separately
|
|
|
I'm putting -b 0.0.0.0:4067 in command line but I cant get the telem to show at any ip. t-rex works but I can't get this to work
|
|
|
on win 10 latest driver, I get: 48 sol/s on Zero gtx 1080ti +122 core +600 mem 70% pl 27 sol/s on Zero gtx 1070 +160 core +600 mem 70% pl
Failed to initialize miner on GPU0: GeForce GTX 980: out of memory but that card works with BTG: 24 sol/s on BTG gtx980 +200 core +200 mem 65% pl
increase pagefile size
|
|
|
can you do some troubleshooting on using remote desktop software while miner is running?
|
|
|
I noticed that the 3 times I got launch errors I was using a remote desktop app, AnyDesk. the mining rig uses onboard video. I disconnected AnyDesk during the current instance and havent received an error yet. the other times the error happened soon after starting the miner instance.
I'd like to be able to use AnyDesk and not have miner crash
|
|
|
I got launch timeout error couple times and now the miner is no longer working. back to doing what it first did before i moved the dll into the folder. I tried removing dll, moving it back in and same resullt
|
|
|
i forgot to put nvml.dll into directory. miner working now
miner search nvml.dll in standard path described in Nvidia documentation: C:\Users\user>echo "%ProgramW6432%\NVIDIA Corporation\NVSMI\nvml.dll" "C:\Program Files\NVIDIA Corporation\NVSMI\nvml.dll"
Do you have another path for nvml.dll? no
|
|
|
i forgot to put nvml.dll into directory. miner working now
|
|
|
i tried 1 device, same result. my pagefile is over 100gb
|
|
|
i've been mining on ewbf for few months. my hardware is setup
|
|
|
I tried that command line and it wouldn't even create the log file and miner had same result. i removed --watchdog 0 from command line and the log file was created, but still same result with miner. curser blinks and nothing else happens. miner doesn't freeze, but doesn't do anything other than blink curser +----------------------------------------------------------------+
| GMiner Equihash Miner v1.04 |
+----------------------------------------------------------------+
Algorithm: Equihash 144_5 "BgoldPoW"
Stratum server:
host: stratum://eu.btgpool.pro:3858
user: address.test
password: x
Power calculator: off
Color output: on
Watchdog: on
Log to file: F:\gminer\miner.log
Selected devices: GPU0 GPU1 GPU2 GPU3 GPU4 GPU5 GPU6 GPU7 GPU8 GPU9 GPU10 GPU11 GPU12 GPU13
Temperature limits: 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C
------------------------------------------------------------------
same thing when i try another pool: +----------------------------------------------------------------+
| GMiner Equihash Miner v1.04 |
+----------------------------------------------------------------+
Algorithm: Equihash 144_5 "BgoldPoW"
Stratum server:
host: stratum://us-east.equihash-hub.miningpoolhub.com:20595
user: user
password: x
Power calculator: on
Color output: on
Watchdog: on
Log to file: miner.log
Selected devices: GPU0 GPU1 GPU2 GPU3 GPU4 GPU5 GPU6 GPU7 GPU8 GPU9 GPU10 GPU11 GPU12 GPU13
Temperature limits: 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C
------------------------------------------------------------------
|
|
|
+----------------------------------------------------------------+ | GMiner Equihash Miner v1.04 | +----------------------------------------------------------------+ Algorithm: Equihash 144_5 "BgoldPoW" Stratum server: host: stratum://eu.btgpool.pro:3858 user: address.test password: x Power calculator: on Color output: on Watchdog: on Log to file: off Selected devices: GPU0 GPU1 GPU2 GPU3 GPU4 GPU5 GPU6 GPU7 GPU8 GPU9 GPU10 GPU11 GPU12 GPU13 Temperature limits: 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C 90C ------------------------------------------------------------------
why does the miner stop here and do nothing more?
this is bat file: miner.exe --algo 144_5 --pers BgoldPoW --server eu.btgpool.pro --port 3858 --user [address].test --pass x --pec
win10 pro, gtx 1070
|
|
|
EWBF_, can you add ability for miner to exit as soon as there is an error with the cuda cores? currently when there is a memory error or something like that it tries to restart the GPUs and stuff. I'd prefer the miner just quit so computer restarts faster. everytime the miner tries to restart GPUs one of them doesnt mine or the computer restarts anyways. It would be more efficient if the program exited right away
I use HWiNFO to monitor GPUs and trigger actions if they go down. I also use SwithMail to alert me via email if anything happens. cool , didnt know hwinfo had that ability
|
|
|
Just had this happen:
took almost 3 minutes to exit after error. I think i found the gpu causing the problem good..next time don't limit yourself with posting log for 2 h only...post your logs for the last month or two...so that it takes several pages of the thread go back to your bridge, get out of your mothers basement, or lose your virginity. Probably need to do all 3
|
|
|
Just had this happen:
14.10.2018 18:22:29 CUDA: Device: 3 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 13 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 12 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 8 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 4 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 0 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 6 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 11 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 1 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 9 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 2 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 7 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 10 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:29 CUDA: Device: 5 Thread exited with message: "the launch timed out and was terminated" 14.10.2018 18:22:30 WARNING: Looks like GPU0 are stopped. Restarting... 14.10.2018 18:22:30 INFO: GPU0 are restarted. 14.10.2018 18:22:30 WARNING: Looks like GPU1 are stopped. Restarting... 14.10.2018 18:22:30 INFO: GPU1 are restarted. 14.10.2018 18:22:30 WARNING: Looks like GPU2 are stopped. Restarting... 14.10.2018 18:22:30 INFO: GPU2 are restarted. 14.10.2018 18:22:30 WARNING: Looks like GPU3 are stopped. Restarting... 14.10.2018 18:22:30 INFO: GPU3 are restarted. 14.10.2018 18:22:30 WARNING: Looks like GPU4 are stopped. Restarting... 14.10.2018 18:22:30 INFO: GPU4 are restarted. 14.10.2018 18:22:31 WARNING: Looks like GPU5 are stopped. Restarting... 14.10.2018 18:22:31 INFO: GPU5 are restarted. 14.10.2018 18:22:31 WARNING: Looks like GPU6 are stopped. Restarting... 14.10.2018 18:22:31 INFO: GPU6 are restarted. 14.10.2018 18:22:31 WARNING: Looks like GPU7 are stopped. Restarting... 14.10.2018 18:22:31 INFO: GPU7 are restarted. 14.10.2018 18:22:31 WARNING: Looks like GPU8 are stopped. Restarting... 14.10.2018 18:22:31 INFO: GPU8 are restarted. 14.10.2018 18:22:31 WARNING: Looks like GPU9 are stopped. Restarting... 14.10.2018 18:22:31 INFO: GPU9 are restarted. 14.10.2018 18:22:32 WARNING: Looks like GPU10 are stopped. Restarting... 14.10.2018 18:22:32 INFO: GPU10 are restarted. 14.10.2018 18:22:32 WARNING: Looks like GPU11 are stopped. Restarting... 14.10.2018 18:22:32 INFO: GPU11 are restarted. 14.10.2018 18:22:32 WARNING: Looks like GPU12 are stopped. Restarting... 14.10.2018 18:22:32 INFO: GPU12 are restarted. 14.10.2018 18:22:32 WARNING: Looks like GPU13 are stopped. Restarting... 14.10.2018 18:22:32 INFO: GPU13 are restarted. 14.10.2018 18:22:42 INFO: Detected new work: a70f 14.10.2018 18:22:50 Temp: GPU0 0C GPU1 0C GPU2 0C GPU3 0C GPU4 0C GPU5 0C GPU6 0C GPU7 0C GPU8 0C GPU9 0C GPU10 0C GPU11 0C GPU12 0C GPU13 0C 14.10.2018 18:22:50 GPU0: 41 Sol/s GPU1: 45 Sol/s GPU2: 41 Sol/s GPU3: 33 Sol/s GPU4: 42 Sol/s GPU5: 46 Sol/s GPU6: 44 Sol/s GPU7: 48 Sol/s GPU8: 44 Sol/s GPU9: 42 Sol/s GPU10: 41 Sol/s GPU11: 41 Sol/s GPU12: 44 Sol/s GPU13: 46 Sol/s 14.10.2018 18:22:50 Total speed: 598 Sol/s 14.10.2018 18:23:21 INFO: Target: 0013813813813814... 14.10.2018 18:23:21 Temp: GPU0 0C GPU1 0C GPU2 0C GPU3 0C GPU4 0C GPU5 0C GPU6 0C GPU7 0C GPU8 0C GPU9 0C GPU10 0C GPU11 0C GPU12 0C GPU13 0C 14.10.2018 18:23:21 GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s GPU4: 0 Sol/s GPU5: 0 Sol/s GPU6: 0 Sol/s GPU7: 0 Sol/s GPU8: 0 Sol/s GPU9: 0 Sol/s GPU10: 0 Sol/s GPU11: 0 Sol/s GPU12: 0 Sol/s GPU13: 0 Sol/s 14.10.2018 18:23:21 Total speed: 0 Sol/s 14.10.2018 18:23:21 INFO: Detected new work: a710 14.10.2018 18:23:52 Temp: GPU0 0C GPU1 0C GPU2 0C GPU3 0C GPU4 0C GPU5 0C GPU6 0C GPU7 0C GPU8 0C GPU9 0C GPU10 0C GPU11 0C GPU12 0C GPU13 0C 14.10.2018 18:23:52 GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s GPU4: 0 Sol/s GPU5: 0 Sol/s GPU6: 0 Sol/s GPU7: 0 Sol/s GPU8: 0 Sol/s GPU9: 0 Sol/s GPU10: 0 Sol/s GPU11: 0 Sol/s GPU12: 0 Sol/s GPU13: 0 Sol/s 14.10.2018 18:23:52 Total speed: 0 Sol/s 14.10.2018 18:24:16 INFO: Target: 001999999999999a... 14.10.2018 18:24:16 INFO: Detected new work: a711 14.10.2018 18:24:23 Temp: GPU0 0C GPU1 0C GPU2 0C GPU3 0C GPU4 0C GPU5 0C GPU6 0C GPU7 0C GPU8 0C GPU9 0C GPU10 0C GPU11 0C GPU12 0C GPU13 0C 14.10.2018 18:24:23 GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s GPU4: 0 Sol/s GPU5: 0 Sol/s GPU6: 0 Sol/s GPU7: 0 Sol/s GPU8: 0 Sol/s GPU9: 0 Sol/s GPU10: 0 Sol/s GPU11: 0 Sol/s GPU12: 0 Sol/s GPU13: 0 Sol/s 14.10.2018 18:24:23 Total speed: 0 Sol/s 14.10.2018 18:24:31 WARNING: Looks like GPU0 are stopped. Restarting... 14.10.2018 18:24:36 ERROR: Looks like GPU0 are stuck. 14.10.2018 18:24:36 WARNING: Looks like GPU1 are stopped. Restarting... 14.10.2018 18:24:41 ERROR: Looks like GPU1 are stuck. 14.10.2018 18:24:41 WARNING: Looks like GPU2 are stopped. Restarting... 14.10.2018 18:24:46 ERROR: Looks like GPU2 are stuck. 14.10.2018 18:24:46 WARNING: Looks like GPU3 are stopped. Restarting... 14.10.2018 18:24:51 ERROR: Looks like GPU3 are stuck. 14.10.2018 18:24:52 WARNING: Looks like GPU4 are stopped. Restarting... 14.10.2018 18:24:53 Temp: GPU0 0C GPU1 0C GPU2 0C GPU3 0C GPU4 0C GPU5 0C GPU6 0C GPU7 0C GPU8 0C GPU9 0C GPU10 0C GPU11 0C GPU12 0C GPU13 0C 14.10.2018 18:24:53 GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s GPU4: 0 Sol/s GPU5: 0 Sol/s GPU6: 0 Sol/s GPU7: 0 Sol/s GPU8: 0 Sol/s GPU9: 0 Sol/s GPU10: 0 Sol/s GPU11: 0 Sol/s GPU12: 0 Sol/s GPU13: 0 Sol/s 14.10.2018 18:24:53 Total speed: 0 Sol/s 14.10.2018 18:24:57 ERROR: Looks like GPU4 are stuck. 14.10.2018 18:24:57 WARNING: Looks like GPU5 are stopped. Restarting... 14.10.2018 18:24:58 INFO: Detected new work: a712 14.10.2018 18:25:02 ERROR: Looks like GPU5 are stuck. 14.10.2018 18:25:02 WARNING: Looks like GPU6 are stopped. Restarting... 14.10.2018 18:25:07 ERROR: Looks like GPU6 are stuck. 14.10.2018 18:25:07 WARNING: Looks like GPU7 are stopped. Restarting... 14.10.2018 18:25:12 ERROR: Looks like GPU7 are stuck. 14.10.2018 18:25:12 WARNING: Looks like GPU8 are stopped. Restarting... 14.10.2018 18:25:17 ERROR: Looks like GPU8 are stuck. 14.10.2018 18:25:18 WARNING: Looks like GPU9 are stopped. Restarting... 14.10.2018 18:25:23 ERROR: Looks like GPU9 are stuck. 14.10.2018 18:25:23 WARNING: Looks like GPU10 are stopped. Restarting... 14.10.2018 18:25:24 Temp: GPU0 0C GPU1 0C GPU2 0C GPU3 0C GPU4 0C GPU5 0C GPU6 0C GPU7 0C GPU8 0C GPU9 0C GPU10 0C GPU11 0C GPU12 0C GPU13 0C 14.10.2018 18:25:24 GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s GPU4: 0 Sol/s GPU5: 0 Sol/s GPU6: 0 Sol/s GPU7: 0 Sol/s GPU8: 0 Sol/s GPU9: 0 Sol/s GPU10: 0 Sol/s GPU11: 0 Sol/s GPU12: 0 Sol/s GPU13: 0 Sol/s 14.10.2018 18:25:24 Total speed: 0 Sol/s 14.10.2018 18:25:28 ERROR: Looks like GPU10 are stuck. 14.10.2018 18:25:28 WARNING: Looks like GPU11 are stopped. Restarting... 14.10.2018 18:25:33 ERROR: Looks like GPU11 are stuck. 14.10.2018 18:25:33 WARNING: Looks like GPU12 are stopped. Restarting... 14.10.2018 18:25:38 ERROR: Looks like GPU12 are stuck. 14.10.2018 18:25:39 WARNING: Looks like GPU13 are stopped. Restarting... 14.10.2018 18:25:44 ERROR: Looks like GPU13 are stuck. 14.10.2018 18:25:45 WARNING: Looks like GPU0 are stopped. Restarting... 14.10.2018 18:25:50 ERROR: Looks like GPU0 are stuck. 14.10.2018 18:25:50 INFO: Exit...
took almost 3 minutes to exit after error. I think i found the gpu causing the problem
|
|
|
yes, i have it on exit 3. i'll look into 3rd party software. maybe that'll help the gpu's restart without having to restart machine. probably would be faster. currently the time from error to restarting machine to mining again is about 4-5 minutes. instant-restart would save 1 min most of the time, but sometimes it goes longer. got 14 cards on win10
If you were on Linux, I could point you to something. I haven't done windows in over 12 years, so unfortunately, I would be of no help. Here is a thought. Run each card in separate miner instance. Make a log entry when a specific instance resets for you to review when you return to the machine. That should at least point you to the problem GPU. Then lower overclock on that one or change out the riser and see if that fixes it. Hope you find your solution. I've done all that, I got the settings closing in on the max. errors once every 24-48 hrs the more pressing issue im having recently is if it errors and restarts sometimes only 13 gpus are recognized by windows and the I have to manually go into device manager and scan for 14th which is then installed by windows
|
|
|
yes, i have it on exit 3. i'll look into 3rd party software. maybe that'll help the gpu's restart without having to restart machine. probably would be faster. currently the time from error to restarting machine to mining again is about 4-5 minutes. instant-restart would save 1 min most of the time, but sometimes it goes longer. got 14 cards on win10
|
|
|
|