|
Title: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: riceburner55 on June 16, 2018, 12:35:44 PM Never thought I would be posting here because I thought I've ran into every issue ever while mining for the past year. This is the first time this has stumped me. Please note that this miner has been running with no issues for over 8 months on the given drivers/claymore until this point.
Claymore miner (10.0 and 9.8) will open, identify the pool, and then immediately closes. Typically this triggers me to reinstall video driver and all works well. So I used driver sweeper and removed the Nvidia and AMD driver, and freshly installed the same drivers I have been using since day one. Windows defender is completely not enabled. -mode 1 and pause are being used in my coding. ALL GPUS are detected and running according to windows devices. Claymore will still not spit out an error in the log so I am kinda lost here.... Does anyone have any suggestions for next steps? Below is an screen shot of windows devices, claymore error log, and drivers used (keep in mind these are the drivers I've always used). https://ibb.co/ebhvXy here is miner log text: 08:17:38:613 2348 args: -epool us1.ethermine.org:4444 -ewal 0xAF69c954a7Cddc9D3BDD4dDF04FDC4870c851825 -epsw x -mode 1 -ftime 10 08:17:38:613 2348 08:17:38:613 2348 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 08:17:38:613 2348 º Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.8 º 08:17:38:613 2348 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 08:17:38:613 2348 08:17:38:816 2348 ETH: 2 pools are specified 08:17:38:816 2348 Main Ethereum pool is us1.ethermine.org:4444 Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: Vann on June 16, 2018, 12:41:48 PM I believe that's an error related to the Windows v1803 April feature update. The latest Adrenaline drivers on Windows 10 v1709 are working great.
On Windows 10 Pro you can set a Group Policy to defer feature updates until they have been targeted for business deployment, which is about 4 months after the public release, or you can also defer feature updates for up to 365 days. This way you still get the security updates. gpedit ==> Computer Configuration ==> Administrative Templates ==> Windows Components ==> Windows Updates ==> Windows Update for Business ==> Select when Preview Builds and Feature Updates are Received ==> Set to 'enabled' and in the drop down select 'Semi-Annual Channel'. Also disable driver updates to keep Windows Update from modifying your drivers. gpedit ==> Computer Configuration ==> Administrative Templates ==> Windows Components ==> Windows Update and set 'Do not include drivers with Windows Update' to enabled. Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: riceburner55 on June 16, 2018, 12:53:57 PM I believe that's an error related to the Windows v1803 April feature update. The latest Adrenaline drivers on Windows 10 v1709 are working great. On Windows 10 Pro you can set a Group Policy to defer feature updates until they have been targeted for business deployment, which is about 4 months after the public release, or you can also defer feature updates for up to 365 days. This way you still get the security updates. gpedit ==> Computer Configuration ==> Administrative Templates ==> Windows Components ==> Windows Updates ==> Windows Update for Business ==> Select when Preview Builds and Feature Updates are Received ==> Set to 'enabled' and in the drop down select 'Semi-Annual Channel'. Also disable driver updates to keep Windows Update from modifying your drivers. gpedit ==> Computer Configuration ==> Administrative Templates ==> Windows Components ==> Windows Update and set 'Do not include drivers with Windows Update' to enabled. Dang... Does this mean I am stuck waiting until a new Driver release from AMD to solve the current situation? Or are you suggesting the latest Adrenaline driver will solve this? The current drivers I have tried using are the Crimson BETA they released exclusively for blockchain and Adrenaline 18.3.4. I am assuming the remedy suggested regarding feature updates will only fix this issue in the future?... well at least prolong a windows update and what the update will affects? Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: Vann on June 16, 2018, 01:03:03 PM The AMD blockchain driver was a patch released to fix the Ethash Dag file growth issue that caused Polaris cards to lose hash rate with every new epoch once the Dag file reached over 2GB. Starting with the Crimson Relive compute drivers that were released for Windows 10 v1703, AMD incorporated the fix from the blockchain driver in to the mainstream release drivers when the cards are set to compute mode.
The correct driver to use for mining Ethash on Windows 10 v1703 Fall Creator update and newer versions is the latest AMD Adrenaline driver and set the cards to compute mode. https://support.amd.com/en-us/kb-articles/Pages/DH-024.aspx Claymore updated his miner to be compatible with the new AMD drivers a long time ago. Some older miners that haven't been updated, like SGminer won't run with the new AMD drivers. The latest AMD Adrenaline drivers are compatible with Windows v1803. The problem related to Windows v1803 is Windows feature updates tend to break compatibility and many programs, haven't been updated, so there are many mining related issues. That's why it's a good idea to defer feature updates until programs have been updated to be compatible with the update. Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: warrior333 on June 16, 2018, 01:23:38 PM I had such a problem. Periodically, this operating system performs an automatic update. After that, you can have any problems. I had a similar drop in Claymore Miner. After reinstalling windows everything will be restored. It will be faster than searching what exactly does not work for you.
Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: riceburner55 on June 16, 2018, 03:10:56 PM The AMD blockchain driver was a patch released to fix the Ethash Dag file growth issue that caused Polaris cards to lose hash rate with every new epoch once the Dag file reached over 2GB. Starting with the Crimson Relive compute drivers that were released for Windows 10 v1703, AMD incorporated the fix from the blockchain driver in to the mainstream release drivers when the cards are set to compute mode. The correct driver to use for mining Ethash on Windows 10 v1703 Fall Creator update and newer versions is the latest AMD Adrenaline driver and set the cards to compute mode. https://support.amd.com/en-us/kb-articles/Pages/DH-024.aspx Claymore updated his miner to be compatible with the new AMD drivers a long time ago. Some older miners that haven't been updated, like SGminer won't run with the new AMD drivers. The latest AMD Adrenaline drivers are compatible with Windows v1803. The problem related to Windows v1803 is Windows feature updates tend to break compatibility and many programs, haven't been updated, so there are many mining related issues. That's why it's a good idea to defer feature updates until programs have been updated to be compatible with the update. Well... I've updated to AMD Adrenalin Edition 18.6.1 Optional which was released 3 days ago from AMD (of course after sweeping previous driver for a clean install). I've changed all settings to compute and.... still have the same issue. Sigh... I believe I will be going with warrior's advice below if no one has any other suggestions. I had such a problem. Periodically, this operating system performs an automatic update. After that, you can have any problems. I had a similar drop in Claymore Miner. After reinstalling windows everything will be restored. It will be faster than searching what exactly does not work for you. It's unfortunate that a clean install of windows is the only way to fix windows updates :( …. I will give the thread about a hour or so for any additional suggestions before re-installing Windows. Thanks everyone! Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: Raja_MBZ on June 16, 2018, 03:19:12 PM The AMD blockchain driver was a patch released to fix the Ethash Dag file growth issue that caused Polaris cards to lose hash rate with every new epoch once the Dag file reached over 2GB. Starting with the Crimson Relive compute drivers that were released for Windows 10 v1703, AMD incorporated the fix from the blockchain driver in to the mainstream release drivers when the cards are set to compute mode. The correct driver to use for mining Ethash on Windows 10 v1703 Fall Creator update and newer versions is the latest AMD Adrenaline driver and set the cards to compute mode. https://support.amd.com/en-us/kb-articles/Pages/DH-024.aspx Claymore updated his miner to be compatible with the new AMD drivers a long time ago. Some older miners that haven't been updated, like SGminer won't run with the new AMD drivers. The latest AMD Adrenaline drivers are compatible with Windows v1803. The problem related to Windows v1803 is Windows feature updates tend to break compatibility and many programs, haven't been updated, so there are many mining related issues. That's why it's a good idea to defer feature updates until programs have been updated to be compatible with the update. Well... I've updated to AMD Adrenalin Edition 18.6.1 Optional which was released 3 days ago from AMD (of course after sweeping previous driver for a clean install). I've changed all settings to compute and.... still have the same issue. Sigh... I believe I will be going with warrior's advice below if no one has any other suggestions. I had such a problem. Periodically, this operating system performs an automatic update. After that, you can have any problems. I had a similar drop in Claymore Miner. After reinstalling windows everything will be restored. It will be faster than searching what exactly does not work for you. It's unfortunate that a clean install of windows is the only way to fix windows updates :( …. I will give the thread about a hour or so for any additional suggestions before re-installing Windows. Thanks everyone! Go with the "Reset this PC" located at Recovery tab of Settings. This is the fastest way of fixing new Windows updates. Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: Vann on June 16, 2018, 03:19:33 PM The problem is the Windows v1803 update, not the drivers. The latest drivers are compatible with the Windows 10 v1803, more than likely it's the Claymore miner that's not been updated to be compatible with v1803. The 18.6.1 drivers are working with Claymore v11.8 in Windows v1709. You may be able to roll back the v1803 update, or follow these steps to do a clean install of Windows v1709. Then disable Windows Feature updates in gpedit.
https://bitcointalk.org/index.php?topic=4459808.msg40031896#msg40031896 Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: vuli1 on June 16, 2018, 03:52:26 PM claymore v 11 is running fine on 1803 and 18.5.1
Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: riceburner55 on June 16, 2018, 06:02:29 PM Go with the "Reset this PC" located at Recovery tab of Settings. This is the fastest way of fixing new Windows updates. Went with this as the option. Reset PC, clean installed NVIDIA and AMD old drivers, INCREASED VIRTUAL MEMORY (resetting Windows reset increased Virtual Mem settings), back up and mining. Needless to say I changed Windows update settings in GP. Much less of a headache than all the rabbit holes I've been going down! Thank you all for the help! Title: Re: Claymore Miner Starts then Immediate Stops. No error in log and used all options Post by: alexkywalker on June 30, 2018, 04:27:00 PM Never thought I would be posting here because I thought I've ran into every issue ever while mining for the past year. This is the first time this has stumped me. Please note that this miner has been running with no issues for over 8 months on the given drivers/claymore until this point. Claymore miner (10.0 and 9.8) will open, identify the pool, and then immediately closes. Typically this triggers me to reinstall video driver and all works well. So I used driver sweeper and removed the Nvidia and AMD driver, and freshly installed the same drivers I have been using since day one. Windows defender is completely not enabled. -mode 1 and pause are being used in my coding. ALL GPUS are detected and running according to windows devices. Claymore will still not spit out an error in the log so I am kinda lost here.... Does anyone have any suggestions for next steps? Below is an screen shot of windows devices, claymore error log, and drivers used (keep in mind these are the drivers I've always used). https://ibb.co/ebhvXy here is miner log text: 08:17:38:613 2348 args: -epool us1.ethermine.org:4444 -ewal 0xAF69c954a7Cddc9D3BDD4dDF04FDC4870c851825 -epsw x -mode 1 -ftime 10 08:17:38:613 2348 08:17:38:613 2348 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 08:17:38:613 2348 º Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.8 º 08:17:38:613 2348 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 08:17:38:613 2348 08:17:38:816 2348 ETH: 2 pools are specified 08:17:38:816 2348 Main Ethereum pool is us1.ethermine.org:4444 I just started experiencing this issue yesterday. I shut off all my miners due to a huge thunderstorm crossing my area, and when I turned them all back on, the ones I have with AMD GPUs continued working as normal, but the ones with Nvidia cards exhibited the issue above. I tried reinstalling drivers, applying all windows 10 updates, re-downloading Claymore, checking for the Exception from the Windows virus thing, and so far no luck whatsoever. How can that be? They were working fine for weeks and a simple shut-down (not forced), on 2 similar rigs (not exact same MoBo and GPUs), have the same issue. UPDATE: I fixed my issue by booting into the BIOS and forcing the default GPU to be the iGPU, switched my monitor to the iGPU connectors and bingo. |