Pages:
Author

Topic: EWBF's Cuda Equihash Miner 0.6 - page 4. (Read 85733 times)

newbie
Activity: 27
Merit: 0
October 25, 2018, 04:29:47 PM
Ok not impressed .6 crashes non stop .5 ran like a charm
member
Activity: 239
Merit: 12
October 24, 2018, 04:32:41 AM
EWBF, any chance to get error log file, to determine which GPU ID caused crash of program? And as i remember on 0.3.5b was watchdog sentinel? If some gpu cause crash miner restart themself?

Lol... 0.3.5b never existed.. At some point there was a trolling post advertising and offering download of 0.3.5b, but was quickly marked as a boobie trap and removed

Actually you can still find it on some Russian forums: http://forum.bitcoinfo.ru/viewtopic.php?f=5&t=41786
newbie
Activity: 176
Merit: 0
October 24, 2018, 04:08:21 AM
EWBF, any chance to get error log file, to determine which GPU ID caused crash of program? And as i remember on 0.3.4b was watchdog sentinel? If some gpu cause crash miner restart themself?
sr. member
Activity: 954
Merit: 250
October 21, 2018, 07:56:20 AM
Help me How do you work with Bitcoin Gold? By ASIC

Just create new ASIC and use it.
member
Activity: 433
Merit: 48
October 21, 2018, 06:37:15 AM
Help me How do you work with Bitcoin Gold? By ASIC

At the moment there is no (publicly available) ASIC for BTG yet. It switched in July to Equihash 144/5 which uses more memory then the older Equihash 200/9 from ZCash and currently there are no ASICs for the new algorithm variant to buy yet.

Best way to mine it is on GPU with one of the many CUDA miners like ewbf (this thread), funakoshi, bminer (etc...) or OpenCL based miner (lolMiner).
newbie
Activity: 1
Merit: 0
October 21, 2018, 05:34:31 AM
Help me How do you work with Bitcoin Gold? By ASIC
sr. member
Activity: 1042
Merit: 328
SIGNATURE CREATION by uralcryptocoin
October 17, 2018, 11:40:51 AM
I mean not system stuck or freeze...i mean some problem with miner or gpu....when appears a lot of repeatedly read rows about GPU stop responses.

In that case you can check enough old BTT thread about Genoil ZEC miner (It's quite unstable software). Here you can find examples of scripts restarting the miner depending on command line output.
But I think EWBF's miner is one of the stablest mining software (Works fine for weeks or even months). So it's recommended to also check the hardware (OC settings, riser plugs etc.)
newbie
Activity: 176
Merit: 0
October 17, 2018, 07:17:18 AM
I mean not system stuck or freeze...i mean some problem with miner or gpu....when appears a lot of repeatedly read rows about GPU stop responses.
sr. member
Activity: 1042
Merit: 328
SIGNATURE CREATION by uralcryptocoin
October 16, 2018, 01:21:39 PM
Need improve auto restart function if error occurs.

In additional to software solutions you can use hardware usb-watchdog if the system hungs at all. Aliexpress will help to find it
Also in BIOS settings auto power-on after power loss function should be ON.
newbie
Activity: 176
Merit: 0
October 16, 2018, 07:23:55 AM
Need improve auto restart function if error occurs.
newbie
Activity: 155
Merit: 0
October 15, 2018, 06:12:12 PM
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 download ETHcontrol from minermonitoring and everything is solved on your side, it restart the miner when an error occur.
https://minermonitoring.com/
newbie
Activity: 20
Merit: 0
October 15, 2018, 01:28:20 PM
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
I set it so if my GPU goes under a certain temp. it runs a batch file that does whatever I want it to do.
newbie
Activity: 164
Merit: 0
October 15, 2018, 12:48:15 PM
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
newbie
Activity: 20
Merit: 0
October 15, 2018, 11:56:55 AM
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.
newbie
Activity: 164
Merit: 0
October 15, 2018, 10:51:14 AM
Quote
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
member
Activity: 239
Merit: 12
October 15, 2018, 03:50:15 AM
Quote
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
newbie
Activity: 164
Merit: 0
October 14, 2018, 07:32:02 PM
Quote
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
newbie
Activity: 164
Merit: 0
October 14, 2018, 01:35:00 PM
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
member
Activity: 113
Merit: 10
October 13, 2018, 11:50:02 PM
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.
newbie
Activity: 164
Merit: 0
October 13, 2018, 11:14:10 PM
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
Pages:
Jump to: