<<  >> (p.46)
    Author Topic: EWBF's Cuda Equihash Miner 0.6  (Read 86016 times)

    • hell_slayer
    Full Member
    ***
    Offline Offline

    Activity: 728
    Merit: 139


    View Profile WWW
    October 10, 2018, 05:27:30 PM
     #901
    Quote from: uralcryptocoin on October 10, 2018, 05:05:30 PM
    Which error appears miner closing with? Use logging to get error message
    No error messages . Step 1 , 2 are working fine without any errors , but step 3 causes system to reboot . As I said before 0.5 version is working fine , so I guess it's not a hardware issue

    Quote from: uralcryptocoin on October 10, 2018, 05:05:30 PM
    There is a lack of info. What is your rig configuration? What hardware espessially PSU and number of GPUs? Would you check power consumption of the GPU? NVSMI tool will help
    Only a single gpu is running on my gaming PC powered by 600w platinum psu . GPU power consumption is locked at 200W . Total energy consumption of the system is 410w , so it's not a problem

  • uralcryptocoin
    Sr. Member
    ****
    Offline Offline

    Activity: 1042
    Merit: 328


    SIGNATURE CREATION by uralcryptocoin


    View Profile
    October 12, 2018, 05:52:57 PM
     #902
    Quote from: hell_slayer on October 10, 2018, 05:27:30 PM
    ....
    Only a single gpu is running on my gaming PC powered by 600w platinum psu . GPU power consumption is locked at 200W . Total energy consumption of the system is 410w , so it's not a problem


    Looks really strange...
    I try to suppose the following: 200W is enough low power limit for GTX1080ti with typical PL at 250W. So what is your OC settings and working core\memory clocks?
    Maybe try to reduce OC or increase PL to 220W or more
    BTC   Bitcoin: A Peer-to-Peer Electronic Cash System   BTC
    A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone.

  • hell_slayer
    Full Member
    ***
    Offline Offline

    Activity: 728
    Merit: 139


    View Profile WWW
    October 13, 2018, 10:47:31 AM
     #903
    Quote from: uralcryptocoin on October 12, 2018, 05:52:57 PM
    Looks really strange...
    I try to suppose the following: 200W is enough low power limit for GTX1080ti with typical PL at 250W. So what is your OC settings and working core\memory clocks?
    Maybe try to reduce OC or increase PL to 220W or more
    Nothing special : +150 core clock , +500 mem , 80% power limit . Now I use version 0.5 again and everything works well, I just wonder what has changed in the new version and could cause such strange system behavior.

  • BitSquare
    Newbie
    *
    Offline Offline

    Activity: 28
    Merit: 0


    View Profile
    October 13, 2018, 11:45:50 AM
     #904
    Quote from: markiz73 on October 09, 2018, 12:52:51 PM
    memory +1000 ? Am I right?
    This is a very large overclocking for this graphics card. Try + 700 and add gradually if it is stable.
    Perhaps it is better to keep the video card and not to put above 800.

    My nVidia 1080Ti can only +700.

  • fistsofgod
    Newbie
    *
    Offline Offline

    Activity: 164
    Merit: 0


    View Profile
    October 13, 2018, 07:46:31 PM
     #905
    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

  • Overdrive5
    Member
    **
    Offline Offline

    Activity: 114
    Merit: 14


    View Profile
    October 14, 2018, 02:10:37 AM
     #906
    Quote from: fistsofgod on October 13, 2018, 07:46:31 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

    fistsofgod,

    Have you tried the --eexit 3 setting?

    Otherwise you will need a separate software watchdog that monitors GPU utilization.

    Hope this helps

    Overdrive5

  • fistsofgod
    Newbie
    *
    Offline Offline

    Activity: 164
    Merit: 0


    View Profile
    October 14, 2018, 03:14:10 AM
    Last edit: October 14, 2018, 03:35:56 AM by fistsofgod
     #907
    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

  • Overdrive5
    Member
    **
    Offline Offline

    Activity: 114
    Merit: 14


    View Profile
    October 14, 2018, 03:50:02 AM
     #908
    Quote from: fistsofgod on October 14, 2018, 03:14:10 AM
    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.

  • fistsofgod
    Newbie
    *
    Offline Offline

    Activity: 164
    Merit: 0


    View Profile
    October 14, 2018, 05:35:00 PM
    Last edit: October 14, 2018, 11:10:32 PM by fistsofgod
     #909
    Quote from: Overdrive5 on October 14, 2018, 03:50:02 AM
    Quote from: fistsofgod on October 14, 2018, 03:14:10 AM
    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

  • fistsofgod
    Newbie
    *
    Offline Offline

    Activity: 164
    Merit: 0


    View Profile
    October 14, 2018, 11:32:02 PM
    Last edit: October 15, 2018, 03:53:01 AM by fistsofgod
     #910
    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

  • crypper
    Member
    **
    Offline Offline

    Activity: 239
    Merit: 12


    View Profile
    October 15, 2018, 07:50:15 AM
     #911
    Quote from: fistsofgod on October 14, 2018, 11:32:02 PM
    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

  • fistsofgod
    Newbie
    *
    Offline Offline

    Activity: 164
    Merit: 0


    View Profile
    October 15, 2018, 02:51:14 PM
     #912
    Quote from: crypper on October 15, 2018, 07:50:15 AM
    Quote from: fistsofgod on October 14, 2018, 11:32:02 PM
    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

  • slim33
    Newbie
    *
    Offline Offline

    Activity: 20
    Merit: 0


    View Profile
    October 15, 2018, 03:56:55 PM
     #913
    Quote from: fistsofgod on October 13, 2018, 07:46:31 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.

  • fistsofgod
    Newbie
    *
    Offline Offline

    Activity: 164
    Merit: 0


    View Profile
    October 15, 2018, 04:48:15 PM
     #914
    Quote from: slim33 on October 15, 2018, 03:56:55 PM
    Quote from: fistsofgod on October 13, 2018, 07:46:31 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

  • slim33
    Newbie
    *
    Offline Offline

    Activity: 20
    Merit: 0


    View Profile
    October 15, 2018, 05:28:20 PM
     #915
    Quote from: fistsofgod on October 15, 2018, 04:48:15 PM
    Quote from: slim33 on October 15, 2018, 03:56:55 PM
    Quote from: fistsofgod on October 13, 2018, 07:46:31 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.

  • Juniormkl
    Newbie
    *
    Offline Offline

    Activity: 155
    Merit: 0


    View Profile
    October 15, 2018, 10:12:12 PM
     #916
    Quote from: fistsofgod on October 15, 2018, 04:48:15 PM
    Quote from: slim33 on October 15, 2018, 03:56:55 PM
    Quote from: fistsofgod on October 13, 2018, 07:46:31 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/

  • Andrey09
    Newbie
    *
    Offline Offline

    Activity: 176
    Merit: 0


    View Profile
    October 16, 2018, 11:23:55 AM
     #917
    Need improve auto restart function if error occurs.

  • uralcryptocoin
    Sr. Member
    ****
    Offline Offline

    Activity: 1042
    Merit: 328


    SIGNATURE CREATION by uralcryptocoin


    View Profile
    October 16, 2018, 05:21:39 PM
     #918
    Quote from: Andrey09 on October 16, 2018, 11:23:55 AM
    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.
    BTC   Bitcoin: A Peer-to-Peer Electronic Cash System   BTC
    A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone.

  • Andrey09
    Newbie
    *
    Offline Offline

    Activity: 176
    Merit: 0


    View Profile
    October 17, 2018, 11:17:18 AM
     #919
    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.

  • uralcryptocoin
    Sr. Member
    ****
    Offline Offline

    Activity: 1042
    Merit: 328


    SIGNATURE CREATION by uralcryptocoin


    View Profile
    October 17, 2018, 03:40:51 PM
     #920
    Quote from: Andrey09 on October 17, 2018, 11: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.

    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.)
    BTC   Bitcoin: A Peer-to-Peer Electronic Cash System   BTC
    A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone.
    Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 [46] 47 48 49 50 »
      Print  
Page 45
Viewing Page: 46

IRLBTC™ © 2025 IRLBTC.com