 Show Posts
|
|
Pages: « 1 2 3 [4]
|
|
robertclaudiu is the pool already online?
The link has been removed, can you PM me?
Merci
|
|
|
|
Have you done this to try to stop Windows Update ?
Maybe you already did that, but it has worked for me.
run services.msc
Scroll down to Windows Update.
If its shows running, right click and select STOP.
Then right click again and select Properties.
Set Startup Type to Disabled.
Exit the Services Menu.
Reboot.
Then check again to be sure its really disabled.
Actually I have done that about 4 months ago. It's currently set to "manual", so I must have either not applied this tweak properly, or it somehow mysteriously switched. Thanks for the reminder - I have gone ahead and disabled it. Additionally, thanks to you I tried using a 4-port HDMI switcher that I had laying around to see if it would give me the same result as those dummy plugs you spoke of - and it has indeed solved my problem  Cheers! The only way to disable Win Updates is by local GPO: https://social.technet.microsoft.com/Forums/windows/en-US/0a46b8ac-0b16-4b87-a881-260c8d5609f7/disabling-windows-update-via-group-policy?forum=winserverGP  |
|
|
|
What happened guys, i was mining very good with v.11.4 with the fixed stale shares and everything was great 1-2 % stale shares. But now (12 hours already) i got 8-12 % stale shares and nothing was changed. Is there any problem with ethermine ?
Anyone else noticed doubled stale shares last 12 hours ?
Same here, restarted everything and still registering double stales. Conclusion would be that Ethermine is having some issues or very high fluctuation in hash-rate. But one thing is certain, the time of uploading a share has increased from 40ms to 60ms now (without any hardware, software or bandwidth changes). |
|
|
|
The current AMD drivers in compute mode are optimized for Windows 10 v1709 FCU. Those are the fastest drivers to use with RX 570/580 cards. The only reason to use the blockchain drivers on Windows v1709 with RX 570/580's is some old miners like SGminer don't work with the latest drivers.
In my experience, in what mining is concerned, the Beta Blockchain drivers are identical to all new drivers. No speed difference whatsoever. If someone has proof otherwise please come forward. Beta blockchain drivers have a limit of upto 8 GPUs. New drivers don't... Speedwise maybe no difference so what is the harm of using newer drivers? Installed new drivers and afterburner doesn't work. Went back to blockchain drivers. That is why I use overdriventool instead of MSI afterburner... https://forums.guru3d.com/threads/overdriventool-tool-for-amd-gpus.416116/But it doesn't have the graphical (mathematical) function of rpm setup which only AB has. |
|
|
|
The current AMD drivers in compute mode are optimized for Windows 10 v1709 FCU. Those are the fastest drivers to use with RX 570/580 cards. The only reason to use the blockchain drivers on Windows v1709 with RX 570/580's is some old miners like SGminer don't work with the latest drivers.
In my experience, in what mining is concerned, the Beta Blockchain drivers are identical to all new drivers. No speed difference whatsoever. If someone has proof otherwise please come forward. I have a six card RX 570/580 rig with dual boot Windows 10 v1709 partitions. The latest Adrenaline drivers on one and the Aug 23rd blockchain drivers on the other, so I can run older miners that are not compatible with the current drivers if I need to. Using the same settings for both, in addition to the blockchain drivers being noticeably slower by 3-4 MH/s, they have frequent drops in hash rate and issues with Windows as well. The AMD blockchain drivers came out before the Windows 10 v1709 FCU and are NOT supported. The v1709 FCU was a major update to how Windows interacts with GPU's and also expanding the previous GPU limit from 8 to 13, which is why AMD had to release new drivers that were compatible with the FCU. In what 1709 is concerned, might be, but I run 1703 and on it there a re no differences between drivers. Also you loose AB rpm graph settings if you update to 1709 and new drivers (and I'm not referring to the graphical interface but to the graph definition of it as a mathematical function). Also I have only max of 7 cards, so 8 limit doesn't bother me. |
|
|
|
The current AMD drivers in compute mode are optimized for Windows 10 v1709 FCU. Those are the fastest drivers to use with RX 570/580 cards. The only reason to use the blockchain drivers on Windows v1709 with RX 570/580's is some old miners like SGminer don't work with the latest drivers.
In my experience, in what mining is concerned, the Beta Blockchain drivers are identical to all new drivers. No speed difference whatsoever. If someone has proof otherwise please come forward. |
|
|
|
|
Yes, disable it through GPO, it will never turn on again!
|
|
|
|
I repeat my question:
Could anyone confirm if crimson version 17.11.4 runs better in claymore dual eth+dcr than august blockchain drivers??
thanks in advance
Maybe, it would be .5mhs at most, but I've had stability issues. From my experience with it, only trouble. Zero difference in performance. Went back to beta driver, much more stable. |
|
|
|
@Claymore How to fix this issue ?
got incorrect temperature 511, ignore
It has resurfaced and my miner always hangs as soon as the mining starts and have to do manual reboot
It's hardware-related issue, drivers report wrong temperature, usually it means that this GPU is not stable. Check its riser, OC, PSU. What about: 14:51:23:183 1e90 Temperature control thread hangs, need to restart miner!
14:51:25:355 1e90 Restarting OK, exit...
This appeared only for 10.2. I've never seen it on older versions on the exact same OS, drivers, updates, OC. So it's something with this 10.2... Check OP or History.txt: Latest version is v10.2:
...
- in rare cases ADL API calls can hang, now watchdog checks it as well.
... So v10.1 could not restart due to ADL API problems, watchdog did not check it. Moreover, both watchdog and temperature control works in same thread in v10.1 so if ADL hangs, watchdog hangs too and fails to restart miner even if some GPU fails after it. It was fixed in v10.2, now temperature control works in separate thread. If you think that watchdog works incorrectly, you can PM me the log file and I will check it. Thanks for clearing that up. Now that rig has been upgraded to Win 1709, ADM 17.1.4. If this will appear again I will PM you with complete logs. It appears my upgrade of FCU (1709) went crazy and I can't access the start meniu... I tried everything.. no solution. I reverted to 1703 and beta Radeon drivers. With this and the OC from 10.2 it kept crashing. After reboot, even if the OC apparently was applied, only 1 of the 4 cards worked at full speed (the one with the monitor in it). Meaning first card worked at 30Mh/s, rest of 3 at 25Mh/s. So I had to go back to using MSI AB, unfortunately. It applies the OC correctly. Let's see if it's stable. |
|
|
|
@Claymore How to fix this issue ?
got incorrect temperature 511, ignore
It has resurfaced and my miner always hangs as soon as the mining starts and have to do manual reboot
It's hardware-related issue, drivers report wrong temperature, usually it means that this GPU is not stable. Check its riser, OC, PSU. What about: 14:51:23:183 1e90 Temperature control thread hangs, need to restart miner!
14:51:25:355 1e90 Restarting OK, exit...
This appeared only for 10.2. I've never seen it on older versions on the exact same OS, drivers, updates, OC. So it's something with this 10.2... Check OP or History.txt: Latest version is v10.2:
...
- in rare cases ADL API calls can hang, now watchdog checks it as well.
... So v10.1 could not restart due to ADL API problems, watchdog did not check it. Moreover, both watchdog and temperature control works in same thread in v10.1 so if ADL hangs, watchdog hangs too and fails to restart miner even if some GPU fails after it. It was fixed in v10.2, now temperature control works in separate thread. If you think that watchdog works incorrectly, you can PM me the log file and I will check it. Thanks for clearing that up. Now that rig has been upgraded to Win 1709, ADM 17.1.4. If this will appear again I will PM you with complete logs. |
|
|
|
@Claymore How to fix this issue ?
got incorrect temperature 511, ignore
It has resurfaced and my miner always hangs as soon as the mining starts and have to do manual reboot
It's hardware-related issue, drivers report wrong temperature, usually it means that this GPU is not stable. Check its riser, OC, PSU. What about: 14:51:23:183 1e90 Temperature control thread hangs, need to restart miner!
14:51:25:355 1e90 Restarting OK, exit...
This appeared only for 10.2. I've never seen it on older versions on the exact same OS, drivers, updates, OC. So it's something with this 10.2... |
|
|
|
Trying Clay 10.2 will see how it goes. 10.1 was highly unstable and unusable..
A clean Windows install+FCU, AMD 17.11.2 and Claymore's v.10.1 is the most stable setup I have ever had. 1 month now with no problems at all Btw, 17.11.4 got released, did anyone try it out? Thanks all for the help with Claymore config file examples. I got it running with Win 10 1709 (FCU) + Claymore 10.2 + AMD 17.11.4 All running smooth. PS. there is no change from Beta drivers + Clay 10.0 + Win 10 1703. So the down time is not worth it. I will keep my other miner on the old setup. |
|
|
|
|
Thanks for the details, hopefully tomorrow I have some time to try it out.
What about the fan RPM, has anyone made MSI AB work at least for fan control in Win 10 1709 (FCU) with latest official AM driver (11.3)?
|
|
|
|
Thanks. In config file it says: # WARNING! Miner loads options from this file only if there are not any options in the command line! So in start.bat you should only have this: setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe And then add all options in config file like: -epool us1.ethpool.org:3333
-ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F
-epsw x
-esm 1
-mode 1
-cclock 1140
-mclock 2080,2070,2060,2200,2050
-cvddc 850
-mvddc 850
is this correct? |
|
|
|
Everything you seek is in the first post of this thread for the most part, don't be lazy. At least try and we can help you if it doesn't work. Hello fellow miners, I have a question for the more experienced ones: Can you give me a complete setup example for Claymore from those who only use Claymore setup and no other programs? This would be for a rig with multiple AMD cards from different manufacturers. I am running Win 10 FCU, latest AMD drivers, and MSI AB for fan control. What I want to set-up is individual OC and voltage for each card like: 1st card GPU 1140MHz, GPU voltage 950, Mem 2019MHz, Mem voltage 950 2nd card GPU 1140MHz, GPU voltage 950, Mem 2119MHz, Mem voltage 950 and so on How should this look like and will it work with MSI AB for fan control? Thanks PS. Ursule..?  Hi, it's not laziness it's the risk of not being able to mine. Now I'm running Win 10 1703 (not 1709) and using only MSI AB for everything on beta blokchain drivers. If I go and do the updates above, and switch to Calymore OC, I can't easily revert so I will have huge downtime. I just want an example of an working config, not for someone to write my config. Based on that I will adapt it and write my own. Thanks for understanding. PS. I also hear that with latest Drivers you AB will not be able to change any settings, does this apply to the fan control also? |
|
|
|
Hello fellow miners, I have a question for the more experienced ones: Can you give me a complete setup example for Claymore from those who only use Claymore setup and no other programs? This would be for a rig with multiple AMD cards from different manufacturers. I am running Win 10 FCU, latest AMD drivers, and MSI AB for fan control. What I want to set-up is individual OC and voltage for each card like: 1st card GPU 1140MHz, GPU voltage 950, Mem 2019MHz, Mem voltage 950 2nd card GPU 1140MHz, GPU voltage 950, Mem 2119MHz, Mem voltage 950 and so on How should this look like and will it work with MSI AB for fan control? Thanks PS. Ursule..? |
|
|
|
|
