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.aspxClaymore 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. |
|
|
|
|
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.
|
|
|
|
Not sure what happened with jaschaknack Github. PBE works great for me. Here is PBE 1.6.2 through 1.6.7 I uploaded. https://mega.nz/#F!JGg1HRqA!3MzOfV1Y9N52SARgfu9wwA
SHA256SUM
ae66252cb7c19d8c32ea6d8cb4235ccdbc1416b298210cfbc628bbe6f0663b52 PolarisBiosEditor-v1.62.7z
8a3842ac66f2fb4d25a8d9dca9bf2ca07c177ec0020e8d039c973a26dd20638f PolarisBiosEditor-v1.63.7z
03d10e7b928b24e37ccf83bd6cc4e3987cad297e0cdd7958d27aff48298e940d PolarisBiosEditor-v1.64.7z
c47d0cb5599ed0603bf9cd519fd9e0bd4ee6058d50bdb9ff990932ed58a6fc9d PolarisBiosEditor-v1.65.7z
86506431c581327d3c037f6bd831bdc4de757a6767e10253555d6413e0def266 PolarisBiosEditor-v1.66.7z
4da378c27164af86406b52eb8cc30baa734b1a8bfefccb692e054fce79abad1d PolarisBiosEditor-v1.67.7z |
|
|
|
|
Diversification and for poor people, a JOB.
|
|
|
|
|
Do a clean install of Windows 1709 with only a single GPU in the primary x16 PCI-E slot. After the install is finished, on the first logon disable Windows feature updates in gpedit, then run Windows Update to get the latest updates and reboot. Go back in to gpedit and disable driver updates to keep Windows Update from modifying your drivers.
gpedit ==> Navigate to: Computer Configuration ==> Administrative Templates ==> Windows Components ==> Windows Update and set 'Do not include drivers with Windows Update' to enabled.
Download the latest driver for your GPU's and run DDU in safe mode to remove the Windows installed driver and disable automatic driver installation when prompted by DDU. Shutdown, install the rest of the GPU's and then run the GPU driver setup.
|
|
|
|
What cards do have? Make sure they are showing in the Windows Device Manager without any errors.
If you mean me, they're a couple of 470 and 570 of 4GB, they all good in device manager, and patched with amd patcher. If you are on Windows 1803, it could be from the update. There are many mining related issues from incompatiblity with the 1803 update. There is no need to use Aferburner with the Claymore miner anyway. You can set the core clock, memry clock, power limit, undervolt and fan speed directly in the miner configuration file or .bat file something like this -cclock 1150,1150
-mclock 2000,2000
-powlim -15,-15
-cvddc 875,875
-mvddc 875,875
-fanmax 80
-fanmin 30
-tt 68
-tstop 75 |
|
|
|
|
What cards do have? Make sure they are showing in the Windows Device Manager without any errors.
|
|
|
|
I would suggest investing in a DataVac electronic air duster instead of using canned air. More effective and you don't have to keep buying canned air. A small air compressor is another option, but it's less convinient and easy to overdue it with too much air pressure. You also have to be aware of moisture and condensation from using compressed air. https://www.newegg.com/Product/Product.aspx?Item=N82E16896367002&cm_re=duster-_-96-367-002-_-ProductWith any cleaning method involving air be sure to keep the fan blades from moving as it's easy to damage them from spinning too fast and also shattering the blades off if it hits something while it's spinning. |
|
|
|
|
I've had my H110 Pro BTC+ running with 13 RX 580's for almost a year since it came out without issue. Very easy board to configure for multiple cards. If anything, the PCI-E slot layout is poorly thought out since it will cause the usb connector on the riser to short out on the back of the adjacent PCI-E connector causing the GPU to not be recognized, but it's an easy fix with two pieces of electrical tape to cover the back of the riser connectors. Otherwise a solid board, but I get it can be frustraing when things are not working out.
The Asus B250 mining expert, Biostar TB250-BTC Pro or Gigabyte GA-B250-FinTech are also good choices for 12-13 GPU rigs and should work fine with your current hardware.
|
|
|
|
|
Check to see if the CPU slot on the mobo has bent pins.
|
|
|
|
|
Double check the riser connections, try another riser or USB cable. If a known good riser/cable is still not working and you checked all the other things I mentioned, it could only be bad hardware. Either the mobo/cpu is bad or has bent pins or incompatible memory. What memory module are you using?
|
|
|
|
|
Remove the DVI adapter and connect the monitor to a single GPU placed directly in the x16 PCI-E slot.
|
|
|
|
|
Double check all of the board connections, 8-pin CPU power, 24-pin ATX cable, RAM, CPU and fan connection. Reset the CMOS by cutting the power at the PSU switch, waiting 15 seconds for the remaining power to drain and then removing the battery and shorting the CMOS jumper. Afterwards put the jumper back in the default position and directly connect the monitor to either the onbard DVI or a single GPU in the x16 PCI-E slot only. Power the PSU switch back on, power up and you should see the POST screen and enter the Bios. If successful, update to the latest Bios from a USB drive as explained in the manual before continuing with the Bios configuration.
|
|
|
|
|
In 2014 when the Crypto market was at a marketcap of 10B> and a fraction of what it currently is, the majority of GPU minable coins were based on Scrypt and X11. Mining was then taken over by ASIC's, FPGA's and multipools, which combined with a 60% correction in BTC caused GPU mining to become unprofitable across the board and negative in many cases after power costs. Back then many people said it was the end of GPU mining, but they were wrong. New POW algorithms were developed and those that kept mining were able to reap huge returns once the market recovered.
What I have learned is profitability comes and goes with market, but as long as the market keeps growing and developing, its not a reason to stop mining. When profitability is low, if you can afford to keep your rigs running without having to sell the majority of your Crypto, it's an opportunity to accumulate coins at a lower cost that you can buy them for when the market eventually recovers.
|
|
|
|
|
There are many problems from a mining perspective with Windows 10 1803, even more than usual with new Windows feature updates. To avoid compatibility issues with new feature updates, It's a good idea to defer feature updates until programs and drivers have been updated to be compatible.
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 ==> 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'.
|
|
|
|
On Windows 10, 4GB cards should be able to mine ETH until epoch 282, or ~09/2019 at the current block times. Since Windows 10 reserves 20% of GPU memory, once the DAG gets over 3.2GB, you will need to switch to Windows 7 or Linux to keep mining ETH for about another year and a half with 4GB cards. Just like once the DAG got over 2.4GB, 3GB can no longer mine ETH on Windows 10.  https://investoon.com/tools/dag_sizeAlso generally speaking, GPU manufacturers will use the best binned chips and memory for the higher priced models within a linup vs the entry level cards. |
|
|
|
I don't use smOS but your miner string looks to be correct. The Claymore ETHminer thread and Readme explains all the different command line options and their meaning. https://bitcointalk.org/index.php?topic=1433925.0-epool is where you put the main ETH pool stratum address and port, just as you already did and -mport is the IP/port where you can view the miner state in a browser. There are also lots of videos on Youtube on how to get started with smOS. https://www.youtube.com/watch?v=wEo3jgIAwds |
|
|
|
|
Show Posts
