|
You will get MUCH fewer stale shares on Ethermine if you use the ssl stratum on the server closest to you e.g.
-epool stratum+ssl://us1.ethermine.org:5555
|
|
|
|
|
Nanopool doesn't report stale shares separately. They use a calculated hash rate and show a 2-hour simple moving average (SMA) compared to your reported hash rate on the graph.
|
|
|
|
|
A bad GPU can make the whole system unstable, which is why you want to disconnect it from the motherboard so you can isolate the problem. You could also try that GPU in another system by itself.
|
|
|
|
|
Yes. Only one PSU should power both VGA power connectors. If you use two different PSU's, they could go out of phase and damage the GPU. Disconnect that card from the PCI-E slot on the motherboard and see if you can boot without out it.
|
|
|
|
|
Yes. How many PSU's are powering the VGA power connectors on that card?
|
|
|
|
it looks like almost everyone with this board is running a combination of amd and nvidia cards? any reason not to do all amd or all nvidia? is anyone using simplemining? are all 3 molex/ATX connectors necessary? i have a server psu with a breakout board and i'm still playing with various mobo/cpu/card combinations trying to find the ideal one. having a lot of issues with the asrock h81 pro btc 2.0 and simplemining :/
I'm running on 2 13 gpu nvidia rigs using this mobo without any problems....only problem i have is the heat  I find it easier to not mix amd and nvidia to be honest with you.. i have some experience with about other motherboards but i always prefer to keep the gpus the same brand/style. evga 1060, pny 1080ti, msi 580. it makes it not only easier for bookkeeping for troubleshooting as well. i was just wondering why so many people were mixing gpus with this thing? i just setup this board about 10 minutes ago with 6 pny 1060 6gb, i'm about to go try to add 6 more. have you tried getting more than 13 gpus on this thing? edit: got 12 running fine, gonna try to do 16 on monday For the millionth and one time in this thread...13 GPUs will work just fine but #14 - #19 has to be a P series card. IE: P106-100. And there is no need to keep with the same brand or model series. The board doesnt care when it comes to using #1 - #13 cards. Troubleshooting is the same no matter what brand or series card used. what's special about the P106-100 that this board prefers them? i've read a lot of thread and seen the example photos but i don't know how the P106 is markedly different from the gtx1060 I believe mining cards operate in TCC mode by default. In BBT's testing with the Asus B250 Mining expert and how many cards he could run, he mentioned the mining cards were running in TCC mode instead of WDDM mode used by standard gaming GPU's. BBT had to download mining specific drivers for the mining cards to be detected by the OS, so it could also be a limitation with how many cards standard drivers will run in WDDM mode VS in TCC mode. https://docs.nvidia.com/gameworks/content/developertools/desktop/nsight/tesla_compute_cluster.htmhttps://youtu.be/TzuSwO6I_oA?t=113 |
|
|
|
The xmr-stak-alloy CPU miner gives invalid shares with the new cryptonight_alloy algo when building from source. The compiled Windows version is also not working for CPU mining with the new algo. One of the files is missing some code. I fixed it by patching the file minethd.cpp in xmr-stak-alloy/xmrstak/backend/cpu/ with the patch below. --- minethd.cpp 2018-05-05 06:56:05.689507712 -0700
+++ minethd2.cpp 2018-05-05 06:58:10.249099121 -0700
@@ -549,6 +549,9 @@
case cryptonight_aeon:
algv = 4;
break;
+ case cryptonight_alloy:
+ algv = 5;
+ break;
default:
algv = 2;
break;
@@ -641,7 +644,7 @@
cryptonight_penta_hash<cryptonight_aeon, true, true>,
- cryptonight_double_hash<cryptonight_alloy, false, false>,
+ cryptonight_double_hash<cryptonight_alloy, false, false>,
cryptonight_double_hash<cryptonight_alloy, true, false>,
cryptonight_double_hash<cryptonight_alloy, false, true>,
cryptonight_double_hash<cryptonight_alloy, true, true>, |
|
|
|
|
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 when the Crimson compute drivers were released for Windows 10 v1709, AMD incorporated the fix from the blockchain driver.
If you want to accumulate BTCP, with your cards you would be better off mining a more profitable and stable coin like ETH and converting it or the other coin. By doing so you can accumulate more coins than by mining a less profitable coin directly.
|
|
|
|
|
The main advantage of a 1070 over a RX 580 is lower power consumption for about the same mining performance in many algorithms. The hashing advantage of the 1070 is mostly with smaller, less popular algorithms. Mainly because AMD miners for those algorithms haven't been optimized. A good example is Neoscrypt, where once Claymore released his optimized AMD miner a RX 580 gets 1000 KH/s. Same as a 1070.
|
|
|
|
I am planning to buy asus B250 mining expert. I will be running 13 cards in the beginning as per https://www.asus.com/support/FAQ/1034921Asus supports 11*amd + 2 Nvidia however, I have seen a few comments that it can run 13 AMDs as well. Is there anybody who is actually successfully running 13 amds only without nvidia or any other card? If so, can you please advise the cards that you are using. we are planning to buy 13x Sapphire Pulse RX580, if anybody has experience with these, please let us know. Yes, BBT built a 60 card farm with the ASUS B250 Mining Expert and Sapphire Pulse 4GB cards, 13 cards per motherboard. https://www.youtube.com/watch?v=xKlXDHdCtqM&feature=youtu.be&t=136 |
|
|
|
|
For the current Polaris cards stick with the latest Adrenaline drivers. There is no point in mining Equihash with AMD cards. You are much better off mining Ethash or Cryptonight which is more profitable. Even with 2GB cards, Equihash would not be my first choice.
|
|
|
|
|
I have the policy set to 'Semi-Annual Channel', as I mentioned and i'm not getting the update, so if it was just released to the pubic, I won't get it for another ~4 months until it's been thoroughly tested.
|
|
|
|
Major problems with windows 1803 update. All of my rigs use 570 or 580 After update. I can't get any rig to have more than 6 gpus attached, 10 out of 12 I can only get 5 gpus working. Takes a very long time to initialize claymore miner. If I try to go past 5 or 6 gpus claymore timesout/reset after 5 min. Everything was working fine before the 1803 update with latest claymore and amd latest drivers basically i have the same problem as https://bitcointalk.org/index.php?topic=1433925.msg36032619#msg36032619There is nothing useful in logs/debug. It's not a good idea to update to a new major Windows feature update as soon as it's released, since they often break compatibility with drivers and programs. It's better to wait until the mainstream build is released. The current v1803 build is essentially a beta preview build so that vendors can update drivers and software to be compatible with the new build. In the Windows 10 Pro Group Policy Editor you can set Windows to only upgrade to feature updates when there enter a final release build. Enable this policy to specify the level of Preview Build or Feature Updates to receive, and when.
* Preview Build - Fast: Devices set to this level will be the first to receive new builds of Windows with features not yet available to the general public. Select Fast to participate in identifying and reporting issues to Microsoft, and provide suggestions on new functionality.
* Preview Build - Slow: Devices set to this level receive new builds of Windows before they are available to the general public, but at a slower cadence than those set to Fast, and with changes and fixes identified in earlier builds.
* Release Preview: Receive builds of Windows just before Microsoft releases them to the general public.
* Semi-Annual Channel (Targeted): Receive feature updates when they are released to the general public.
* Semi-Annual Channel: Feature updates will arrive when they are declared Semi-Annual Channel. This usually occurs about 4 months after Semi-Annual Channel (Targeted), indicating that Microsoft, Independent Software Vendors (ISVs), partners and customer believe that the release is ready for broad deployment. 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'. |
|
|
|
Once the card reaches around 83°C, the clocks level out at around 1705 MHz, which is still 100 MHz higher than the base clock. ^^^^still higher than base clock, and those few mhz make basically no difference in the real world. Here is one of my GTX 1070 machines as an example: ETH: GPU0 26.668 Mh/s - GPU0 t=82C fan=96% GPU1 26.694 Mh/s - GPU1 t=74C fan=81% GPU2 26.685 Mh/s - GPU2 t=69C fan=64% GPU3 26.673 Mh/s - GPU3 t=82C fan=96% GPU4 26.685 Mh/s - GPU4 t=81C fan=93% All cards are within 0.03Mh or so......does that really look like a bunch of thermal throttling? I can post hundreds of other miner status lists showing the same thing. As noted in the second part of the review, modern Nvidia cards begin to progressively throttle in 13 MHz increments as low 40C. Once the temperature exceeds 82C, there was a drop to the base clock. Which means modern cards DO in fact progressively throttle the core frequency and voltage according to the temperature, not just at the thermal limit cutoff. We can see a linear trend that has clocks go down as the temperature increases, in steps of 13 MHz, which is the clock generator's granularity. Once the card exceeds 82°C (I had to stop the fan manually to do that), the card will drop all the way down to its base clock, but will never go below that guaranteed minimum (until 95°C where thermal trip will kick in).
This means that for the first time in GPU history, lower temperatures directly translate into more performance - at any temperature point and not only in the high 80s. I just hope that this will not tempt custom board manufacturers to go for ultra-low temperatures while ignoring fan noise. Ethash is a memory dependent algorithm which is not affected as much by by a lower core clock. Especially given that for mining ETH, you should UNDERCLOCK the core to LESS than the default clock. For other core intensive algorithms such as Equihash, where you need to INCREASE the core overclock, the thermal throttling would affect the hash rate much more. |
|
|
|
|
Generally you can run cards at <75C before they will begin to throttle. As long as you have good airflow, it shouldn't be a problem to stay below that.
|
|
|
|
As explained in the README.txt, you need to add the ETH backup pools to epools.txt and secondary coin backup pools to dpools.txt. If the main pool goes down the miner will automatically cycle to the backup pools and return to the main pool once it's back online. You can also adjust the amount of time before the miner will switch back to the main pool with -ftime (default is 30 minutes). FAILOVER
Use "epools.txt" and "dpools.txt" files to specify additional pools (you can use "-epoolsfile" and "-dpoolsfile" options to use different filenames).
These files have text format, one pool per line. Every pool has 3 connection attempts.
Miner disconnects automatically if pool does not send new jobs for a long time or if pool rejects too many shares.
If the first character of a line is ";" or "#", this line will be ignored.
Do not change spacing, spaces between parameters and values are required for parsing.
If you need to specify "," character in parameter value, use two commas - ,, will be treated as one comma.
You can reload "epools.txt" and "dpools.txt" files in runtime by pressing "r" key.
Pool specified in the command line is "main" pool, miner will try to return to it every 30 minutes if it has to use some different pool from the list.
If no pool was specified in the command line then first pool in the failover pools list is main pool.
You can change 30 minutes time period to some different value with "-ftime" option, or use "-ftime 0" to disable switching to main pool.
You can also use environment variables in "epools.txt", "dpools.txt" and "config.txt" files. For example, define "WORKER" environment variable and use it as "%WORKER%" in config.txt or in epools.txt.
You can also select current pool in runtime by pressing "e" or "d" key. |
|
|
|
|
Show Posts
