Marvell2
|
|
November 03, 2017, 08:11:38 PM |
|
anyone have a good way on windows 10 to restart the miner if after the reboot.bat script runs ?
|
|
|
|
Blkmktinsurance
Newbie
Offline
Activity: 25
Merit: 0
|
|
November 03, 2017, 11:40:26 PM |
|
I have one rig showing 850mh/s on lbry 290x win10 17.7 drivers
Other rigs running 8.1 or 7 show 85mh/s 290x win 7 16.9 drivers
Is it the drivers or the os? Is the high hashrate not indicating correct?
|
|
|
|
hardworker27
Newbie
Offline
Activity: 58
Merit: 0
|
|
November 03, 2017, 11:54:55 PM |
|
Hello guys, thanks Claymore for the miner, but i have one question, Is now this miner work with both suprnova pools , because i am mining eth there ?
PS. I read all 10 pages, nothing about eth suprnova, so i suppose that not work ?
Yes, it does work with suprnova pools.
|
|
|
|
DD47
Newbie
Offline
Activity: 11
Merit: 0
|
|
November 03, 2017, 11:55:48 PM Last edit: November 04, 2017, 12:10:16 AM by DD47 |
|
anyone have a good way on windows 10 to restart the miner if after the reboot.bat script runs ?
I followed this guy's instructions - works great. https://www.youtube.com/watch?v=SUvQ0UH-sV0&t=850s
|
|
|
|
|
kkourmousis
Member
Offline
Activity: 119
Merit: 10
|
|
November 04, 2017, 01:53:32 AM |
|
Regarding the issues I had updating my AMD drivers, where my Claymore miner would freeze while building OpenCL: I performed a clean install of Windows and everything worked great with latest drivers 17.11.1 . It was the 1st time that my miner run without a single crash for 24h straight. Then out of the sudden, my rig restarted (I think it restarted because of windows updates) and the same freeze problem reappeared! I let my rig cool down just to be sure that it is not a hardware issue, I tested it again and the problem remained. I once again performed a clean install of Windows and now once again everything is fine with latest drivers 17.11.1. I did my best to block Windows from updating again. When I have more info, I will let you know, in case some other poor fellow has the same issues I had. My rig: ASUZ Prime Z270-P 8x RX 580 8GB Nitro+ (Hynix) Windows 10 Pro Radeon™ Software Crimson ReLive Edition 17.11.1 Claymore Dual Miner v.10.1 Modded BIOS
|
Buy me a souvlaki: ETH: 0x22D1C05F89dbe036aABFFEc197949E635903C6FA BTC: 1FHwEyiCqUTpauGfvPg5czMYoWMKqYGBWx
|
|
|
Marvell2
|
|
November 04, 2017, 01:57:44 AM |
|
Oh i know of the shell startup method, I used it in the past but is seems to load too fast sometimes
|
|
|
|
Vann
|
|
November 04, 2017, 02:13:10 AM |
|
You can put 'TIMEOUT 10' above the miner command in the bat file to delay it for 10 seconds.
|
|
|
|
jeoarx
Newbie
Offline
Activity: 24
Merit: 0
|
|
November 04, 2017, 03:04:57 AM |
|
Regarding the issues I had updating my AMD drivers, where my Claymore miner would freeze while building OpenCL: I performed a clean install of Windows and everything worked great with latest drivers 17.11.1 . It was the 1st time that my miner run without a single crash for 24h straight. Then out of the sudden, my rig restarted (I think it restarted because of windows updates) and the same freeze problem reappeared! I let my rig cool down just to be sure that it is not a hardware issue, I tested it again and the problem remained. I once again performed a clean install of Windows and now once again everything is fine with latest drivers 17.11.1. I did my best to block Windows from updating again. When I have more info, I will let you know, in case some other poor fellow has the same issues I had. My rig: ASUZ Prime Z270-P 8x RX 580 8GB Nitro+ (Hynix) Windows 10 Pro Radeon™ Software Crimson ReLive Edition 17.11.1 Claymore Dual Miner v.10.1 Modded BIOS you should disable windows updates and everything will run normally use the mining.bat file in this article to disable non important windows features http://1stminingrig.com/best-windows-setup-configuration-tweaks-for-mining/
|
|
|
|
syraka76
Member
Offline
Activity: 83
Merit: 10
|
|
November 04, 2017, 04:12:47 AM |
|
you have noticed that the latest version of Afeterburner allows you to go to -200coreV
|
|
|
|
Marvell2
|
|
November 04, 2017, 04:21:40 AM |
|
you have noticed that the latest version of Afeterburner allows you to go to -200coreV
Funny the AB dev posted here a while back and I requested this feature, no shout out to me tho smh
|
|
|
|
Southy
Newbie
Offline
Activity: 23
Merit: 0
|
|
November 04, 2017, 04:38:30 AM |
|
Trying to download the latest version i have all virus expeptions and turned off, it just fails from virus detected in chrome or winrar i suppose any way to by pass this would be really appreciated, Thanks.
|
|
|
|
syraka76
Member
Offline
Activity: 83
Merit: 10
|
|
November 04, 2017, 08:01:49 AM |
|
a question, do you still find hashs of hash? regardless of the pool? I think the problem is the claymore miner, there are too many hash oscillations, from 30.5, down to 21.9, then back up, some 30mh / s gpu, down to 22mhs, 25, and then after 40 seconds about, goes back,. @Claymore could you take a look if you need some fix?
|
|
|
|
kkourmousis
Member
Offline
Activity: 119
Merit: 10
|
|
November 04, 2017, 10:39:19 AM |
|
Wow nice to see all of them summed up! I have already done most of those things by hand but it was nice to see "what am I missing" on a list (for example I forgot to disable Hibernation). Thanks a lot!
|
Buy me a souvlaki: ETH: 0x22D1C05F89dbe036aABFFEc197949E635903C6FA BTC: 1FHwEyiCqUTpauGfvPg5czMYoWMKqYGBWx
|
|
|
Jonet
Jr. Member
Offline
Activity: 82
Merit: 3
|
|
November 04, 2017, 12:00:49 PM |
|
I'm using the AMD blockchain drivers with Afterburner on Windows 10 Pro v1703 and it works fine. If you updated to the Windows 10 Fall Creators Update (v1709), that may be your problem as the blockchain drivers don't support the FCU.
I'm using the Aug 23 Blockchain driver on several rigs running v1709. FCU will replace the driver but you can remove 17.7.2 (or whatever FCU installs) and reinstall Aug 23 Blockchain driver. But, if I wan't to try Claymore 10.1, do I have to disable antivirus completly? Windows defender says \cuda7.5\EthDcrMiner64.exe is a Trojan called Tiggre!plock I also want to try 17.10.2 or above. In order to enable "compute" I will have to install AMD settings and thus Wattman will be installed. But does not Wattman interfere with other oc and monitoring software like Afterburner and OverdriveNTool? I installed 17.10.2 and OverdriveNTool is unable to set the clocks and voltages. Wattman works but it's not the ideal tool.
|
|
|
|
Jombazi
Newbie
Offline
Activity: 15
Merit: 0
|
|
November 04, 2017, 12:37:13 PM |
|
Is there a command to show how much power the cards are pulling? (like the --pec command in EWBF)
|
|
|
|
Vann
|
|
November 04, 2017, 12:50:46 PM |
|
I'm using the AMD blockchain drivers with Afterburner on Windows 10 Pro v1703 and it works fine. If you updated to the Windows 10 Fall Creators Update (v1709), that may be your problem as the blockchain drivers don't support the FCU.
I'm using the Aug 23 Blockchain driver on several rigs running v1709. FCU will replace the driver but you can remove 17.7.2 (or whatever FCU installs) and reinstall Aug 23 Blockchain driver. But, if I wan't to try Claymore 10.1, do I have to disable antivirus completly? Windows defender says \cuda7.5\EthDcrMiner64.exe is a Trojan called Tiggre!plock I also want to try 17.10.2 or above. In order to enable "compute" I will have to install AMD settings and thus Wattman will be installed. But does not Wattman interfere with other oc and monitoring software like Afterburner and OverdriveNTool? I installed 17.10.2 and OverdriveNTool is unable to set the clocks and voltages. Wattman works but it's not the ideal tool. Since the blockchain drivers don't support the Creators fall update, there is no point in updating to v1709. The blockchain drivers install and worked for me on v1709, but it makes the Windows UI very unstable e.g. you can't select the Taskbar icons or Windows menu. If you want to stick with the blockchain drivers, it's best to stay on v1703 and defer the Windows feature updates in the Group policy editor until a stable version of the new Crimson Relive compute toggle drivers is out. gpedit ==> Computer Configuration ==> Administrative Templates ==> Windows Components ==> Windows Update ==> Defer Windows Updates ==> Select when Feature Updates are received There you can defer Windows version updates for up to one year. While in the Group Policy Editor, you can also keep Windows Update from updating the the drivers. gpedit ==> Computer Configuration ==> Administrative Templates ==> Windows Components ==> Windows Update and set 'Do not include drivers with Windows Update' to enabled. Completely disabling Windows Update is unnecessary and opens your network to zero days. The release notes for the Crimson Relive 17.11.1 driver that is out also mention the new drivers have a known issue with 12 GPU's in compute mode. https://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-17.11.1-Release-Notes.aspxA random system hang may be experienced after extended periods of use on system configurations using 12 GPU's for compute workloads.
|
|
|
|
MikeGR7
Newbie
Offline
Activity: 36
Merit: 0
|
|
November 04, 2017, 02:41:51 PM |
|
Sorry to disagree but i have FCU update + all recent updates since it was released + 23Aug Blockchain drivers = All working great 0 issues.
I type this from that very system with 30 tabs open on Chrome + Claymore 10.1 mining stable ETH+ LBRY on the background...
|
|
|
|
Vann
|
|
November 04, 2017, 03:01:11 PM Last edit: November 04, 2017, 03:20:58 PM by Vann |
|
Sorry to disagree but i have FCU update + all recent updates since it was released + 23Aug Blockchain drivers = All working great 0 issues.
I type this from that very system with 30 tabs open on Chrome + Claymore 10.1 mining stable ETH+ LBRY on the background...
That was definitely not my experience when I did a clean install of Windows 10 v1709 and tried using the blockchain drivers after I couldn't get the Crimson Relive drivers that support the FCU to work with Afterburner. In any case from a mining standpoint, there is no benefit in updating to v1709 if you are using the blockchain drivers, which don't support the FCU. That's why I'm sticking with v1703 until a stable release of the Crimson relive compute drivers is out.
|
|
|
|
MikeGR7
Newbie
Offline
Activity: 36
Merit: 0
|
|
November 04, 2017, 03:10:53 PM |
|
No idea what went wrong in your system. I also have AB working fine too...
|
|
|
|
|