 Show Posts
|
|
Pages: [1]
|
Thank you for the suggestion, I tried it, disabled defender, ran program, no restart, same issue no change. I also went through disabled all other types of software and network related policies, tried again, no change. I guess ill bite the bullet and do a full wipe and reinstall of windows.
It's a good choice that you have decided to fresh install Windows. Anyway, I'll recommend installing Windows 10 LTSC version as it is very stable, no feature updates so it won't go updating itself middle of the night and break something. After installing, perform all the security updates, then disable automatic updates through group policy and start mining. It'll run as stable as a Linux system. Thank you very much for this information, I did not know about this version before and i will definitely be using it for the fresh install. thanks again |
|
|
|
Having issue after windows update, miner can no longer restart itself when thread crash or manual restart time. Miner shows restarting waiting 15s but after 15s CMD closes. I also have had random CMD closure after a few days or sometimes less than 12hours of running.
Anyone with the same issues? Or know a fix ? (its getting annoying waking up or coming home to find no errors messages in windows or in the miner log, but the program had just turned off and will not restart.) This seems like Windows Defender issue. Turn off Windows Defender completely (it can be done with gpedit.msc) and see if the issues go away. Dear developers. Do you know why every month the ETH hashrate decreases a bit on 1070-1080Ti video cards? About 2-3 MX per year. On AMD cards and on 1066 - this does not happen, everything is ok there. Thank you in advance!
I also wants to know answer this question. In the first half of this year my 6 1070 have 192Mh. Now they have 183.8Mh. Moreover I decreased MC, because with MC I used before, hashrate is even less. But there is nothing incorrect shares, so looks like hardware works good. This is a long-standing problem with Nvidia 10x0 cards. As it started above certain size of DAG and gradually lowers the hashrate with each new epoch, it seems to be related to the TLB size (yes, TLB strikes again). At this point the only workaround is to increase the power limit (and thus indirectly the core clock) but whether it is worth it depends on your electricity prices. We are testing some theoretical fixes for this problem but the results are not very encouraging. Nvidia could probably fix this with driver update by increasing the page size as AMD did in the past but it is not very likely that they will bother to do it. Thank you for the suggestion, I tried it, disabled defender, ran program, no restart, same issue no change. I also went through disabled all other types of software and network related policies, tried again, no change. I guess ill bite the bullet and do a full wipe and reinstall of windows. |
|
|
|
Having issue after windows update, miner can no longer restart itself when thread crash or manual restart time. Miner shows restarting waiting 15s but after 15s CMD closes. I also have had random CMD closure after a few days or sometimes less than 12hours of running.
Anyone with the same issues? Or know a fix ? (its getting annoying waking up or coming home to find no errors messages in windows or in the miner log, but the program had just turned off and will not restart.) |
|
|
|
|
Having issue after windows update, miner can no longer restart itself when thread crash or manual restart time. Miner shows restarting waiting 15s but after 15s CMD closes. I also have had random CMD closure after a few days or sometimes less than 12hours of running.
|
|
|
|
I think there's a bug with --maxnosharessent , Whether I set it to 5 or 10, it resets miner after only 1 minutes (and it says 1 minute in the log, not the 5 or 10 I'm setting..). Anybody else have a similar problem?
its been like that since the version it was added. |
|
|
|
|
So found another issue, now when i try to connect to a etc pool right after dag creation or before the last gpu's dag completes i get "Stratum thread not responsive for 51s" and it shuts down. watchdog is disabled as well. Ive went back to claymore and it does not have this issue. what could be causing this?
|
|
|
|
|
For some reason, about 90% of the time i get incorrect shares after the dev fee switch is over, and it continues to create incorrects on other gpus until i restart the miner. But 10% of time it runs perfect after the dev switch with no incorrects. This wouldnt be an issue but when i get these incorrects my effective hashrate drops 20% and stays that low until i restart the miner. Any idea how to fix this ? (this does not happen in claymore )
|
|
|
|
|
Ok thanx for the assurance. Does the Dev fee show up in the logs? i would like to check them after a few days just to be sure. This miner is truly an upgraded claymore, getting 1.2% higher hash rate with 2% less power usage.
|
|
|
|
why does the dev fee start after 18mins? and ive seen it start at other random time intervals as well. Seems very shady https://imgur.com/VYRAvlP |
|
|
|
|
