Bitcoin Forum
June 18, 2021, 01:05:20 PM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 [173] 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 ... 457 »
  Print  
Author Topic: PhoenixMiner 5.6d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)  (Read 663319 times)
miner582
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
June 27, 2019, 11:50:54 PM
 #3441

Question, please advice?

I am running Phoenixminer (lastest version), I had reported 165/2/64 shares however no ones of the gpus reported incorrect shares, only the phoenixminer summary and of course the hashrate at the pool is low, what could cause this? How do I troubleshoot this? is this is related with too much OC although the gpus are not reporting incorrect shares?

Thanks in advance for your advice

Edit: pool is ethermine.org         OC core 1220 mem 2140, I am using -robost 30 hashrate 30.5 gpus 580s 8g
What drivers?
I am using smos (linux distro) 4.17.19-smos15 / AMD 18.20
1624021520
Hero Member
*
Offline Offline

Posts: 1624021520

View Profile Personal Message (Offline)

Ignore
1624021520
Reply with quote  #2

1624021520
Report to moderator
1624021520
Hero Member
*
Offline Offline

Posts: 1624021520

View Profile Personal Message (Offline)

Ignore
1624021520
Reply with quote  #2

1624021520
Report to moderator
1624021520
Hero Member
*
Offline Offline

Posts: 1624021520

View Profile Personal Message (Offline)

Ignore
1624021520
Reply with quote  #2

1624021520
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1624021520
Hero Member
*
Offline Offline

Posts: 1624021520

View Profile Personal Message (Offline)

Ignore
1624021520
Reply with quote  #2

1624021520
Report to moderator
UnclWish
Sr. Member
****
Offline Offline

Activity: 1414
Merit: 253


View Profile
June 28, 2019, 05:02:11 AM
 #3442

Question, please advice?

I am running Phoenixminer (lastest version), I had reported 165/2/64 shares however no ones of the gpus reported incorrect shares, only the phoenixminer summary and of course the hashrate at the pool is low, what could cause this? How do I troubleshoot this? is this is related with too much OC although the gpus are not reporting incorrect shares?

Thanks in advance for your advice

Edit: pool is ethermine.org         OC core 1220 mem 2140, I am using -robost 30 hashrate 30.5 gpus 580s 8g
What drivers?
I am using smos (linux distro) 4.17.19-smos15 / AMD 18.20

I didn't know about linux... But you must check if Phoenix miner supported your drivers or not. On Windows miner write driver support just 1st several strings on launch.
Bohr256
Jr. Member
*
Offline Offline

Activity: 77
Merit: 1


View Profile
June 28, 2019, 09:16:27 PM
 #3443

This happened to my rig today:



The current hash rate took a dive. It began at 7:10 and it lasted till 12:20. It stayed at around 40-60 MH/s for the entire 5 hours. When I fired up Ethminer it went back up to normal. The growth shows when I switched to Ethminer. Any ideas what could've happened here?

The pool is ethermine.org too, and latest phoenix version.
Stihlus
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
June 29, 2019, 10:10:55 AM
 #3444

I have a few nVidia 1080Ti mining the ETH. I noticed the hash rate decreased about 5% in the last few months. Is it due to the DAG file size similar to old AMD cards?
you are complaining about 5% drop in the hash rate while there are other coins that you can mine with your 1080ti that are nearly 100% more profitable than ETH   Roll Eyes Huh
Hello guys,

I have the same issue with 7 x GPU 1070. In the last months from 230 Mh dropped now to 215-216 Mh ... I don't know why and I want to solve somehow the hash rate problem if it is possible.

Thanks!
anbe2305
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
June 29, 2019, 01:38:53 PM
 #3445

With 7x nvidia cards you should mine BEAM instead of ETH for making profit...
Antoni4EVA1984
Member
**
Offline Offline

Activity: 183
Merit: 27


View Profile
June 29, 2019, 03:54:54 PM
 #3446

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.


Quote
Read this if you can't mine ETH or ETC with PhoenixMiner: important message for everyone that is running older versions of PhoenixMiner (before 4.2).

IMPORTANT! The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. Both ETC and ETH has reached epoch 266 already. To ensure uninterrupted operation, please upgrade to 4.2. If you are mining other coins, you can safely disregard this message.

The reason for this limitation is that we need to perform some quite complex calculations for each future DAG epoch in order to increase the hashrate of the optimized kernels. Recently we have added more computational resources and PhoenixMiner 4.2 will work without problems up to DAG epoch 329. We will increase this number significantly (e.g. 400 or more) in the next version.
Changes in version 4.2c (since 4.1c):

  • Added support for dual mining Ethash and Blake2s on Nvidia GPUs
  • Added new Nvidia kernels v3 with slightly higher hashrate and lower power consumption (up to about 1-1.5% less power). The new kernels are supported only on GTX1050/1060/1070/1080/Ti GPUs and are enabled by default on these GPUs. Note that you can't use these kernels for dual-mining, only -nvkernel 2 works for dual mining on Nvidia.
  • Added new command-line option -nvkernel to select the old (v1 CUDA kernels from PhoenixMiner 3.5), newer (v2 introduced with PhoenixMiner 4.0), or the latest CUDA kernels (v3). The possible values are 0 (auto; the default, selects the best kernel for each GPU), 1 , 2, or 3 (forces v1, v2, or v3 kernels respectively). Note that only v2 CUDA kernels support dual mining.
  • Added experimental support for ProgPOW mining of Bitcoin Interest (BCI). Note that the kernels are not optimized and only work on AMD. You must add -coin bci to the command line (or COIN: bci to your epools.txt file) in order to mine BCI.
  • Added parameter to enable or disable driver-specific optimizations on Nvidia GPUs. Use -nvdo 1 (the default is 0) to enable the optimizations. This won't change hashrate (or will change it only slightly) but can make the cards more stable depending on the concrete Nvidia driver.
  • Added support for EthereumStratum/2.0.0 protocol (use -proto 5 if the pool requires it).
  • AMD hardware control code was rewritten, now should be more stable and work on older cards too
  • Added command-line option -fcm to set the way fans are controlled (AMD/Windows only). The possible values are 0 (auto; the default behavior), 1 (use VBIOS/driver), 2 (force custom control of the fans regardless of VBIOS/drivers fan curves, etc). Use -fcm 2 if the  fans are not controlled properly or at all
  • Added support for Radeon VII
  • Added support for Windows AMD drivers 19.3.3
  • Increased the maximum supported DAG epoch to 329. This should be fine for at least a year or so.
  • Added support for direct mining without DAG switching of Yocoin (YOC), Bitcoiin2Gen (B2G), Ethersocial (ESN), Atheios (ATH), and REOSC. See the -coin parameter in Readme.txt for more information.
  • Fixed the slower DAG generation on Vega and Radeon VII GPUs
  • Fixed the problem with the watchdog timer when solo mining
  • Other small improvements and fixes.

PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supports
both AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64 and Linux x64
and has a developer fee of 0.65% (the lowest in the industry). This means that every 90
minutes the miner will mine for us, its developers, for 35 seconds.

PhoenixMiner also supports Ubqhash for mining UBQ, ProgPOW for mining BCI, and dual mining
Ethash/Ubqhash with Blake2s.

The speed is generally faster than Claymore's Ethereum miner in eth only mode
(we have measured about 0.4-1.3% speed improvement but your results may be slightly lower or
higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed
to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed
interactively with the + and - keys while the miner is running).

If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner with
minimal hassle as we support most of Claymore's command-line options and confirguration
files.

Please note that PhoenixMiner is extensively tested on many mining rigs but there still may be some bugs.
Additionally, we are actively working on bringing many new features in the future releases.
If you encounter any problems or have feature requests, please post them here (in this thread).
We will do our best to answer in timely fashion.

Screenshot:


1. Quick start

You can download PhoenixMiner 4.2c from here:

https://mega.nz/#F!2VskDJrI!lsQsz1CdDe8x5cH3L8QaBw (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes:
Code:
   File: PhoenixMiner_4.2c_Windows.zip
    ===================================
   SHA-1: 6905a662d9d0ad790f2d13447252262ec66ea4d4
 SHA-256: b2ad6398594d4f92a55f8b03895bdc9be13d875ae9d373611b9ac4bd59554afc
 SHA-512: eaf6e810fa75fa977035f96d2d65902e99cb403b918ef50f2da44529302cabe15afe7c26e358fad3cf04be225d068457c717688de4bbcdf2ca6a3c531ea863e5

    File: PhoenixMiner_4.2c_Linux.tar.gz
    ====================================
   SHA-1: 487904d69dd671844dbaea3bd665adb2d38a7446
 SHA-256: b46c13db685c17884ebc73e23aedef3513d1d2bd0b52f20c0a2824e7bc90e9a0
 SHA-512: ae11c0998b2c96a0b380d539fddef9637a809212fbbf4c9cbfecfd820ec5f22f1b5544fdebf69f934b8b05523636e336b81014e00652aac287dc0a8ec2e91bf0

Here are the command line parameters for some of the more popular pools and coins:

ethermine.org (ETH):
  PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName -proto 3
ethermine.org (ETH, secure connection):
  PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3
ethpool.org (ETH):
  PhoenixMiner.exe -pool eu1.ethpool.org:3333 -pool2 us1.ethpool.org:3333 -wal YourEthWalletAddress.WorkerName -proto 3  
dwarfpool.com (ETH):
  PhoenixMiner.exe -pool eth-eu.dwarfpool.com:8008 -wal YourEthWalletAddress/WorkerName -pass x
nanopool.org (ETH):
  PhoenixMiner.exe -pool eth-eu1.nanopool.org:9999 -wal YourEthWalletAddress/WorkerName -pass x
nicehash (ethash):
  PhoenixMiner.exe -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0
f2pool (ETH):
  PhoenixMiner.exe -epool eth.f2pool.com:8008 -ewal YourEthWalletAddress -pass x -worker WorkerName  
miningpoolhub (ETH):
  PhoenixMiner.exe -pool us-east.ethash-hub.miningpoolhub.com:20535 -wal YourLoginName.WorkerName -pass x -proto 1
coinotron.com (ETH):
  PhoenixMiner.exe -pool coinotron.com:3344 -wal YourLoginName.WorkerName -pass x -proto 1
ethermine.org (ETC):
  PhoenixMiner.exe -pool eu1-etc.ethermine.org:4444 -wal YourEtcWalletAddress.WorkerName
epool.io (ETC):
  PhoenixMiner.exe -pool eu.etc.epool.io:8008 -pool2 us.etc.epool.io:8008 -worker WorkerName -wal YourEtcWalletAddress -pass x -retrydelay 2
whalesburg.com (ethash auto-switching):
  PhoenixMiner.exe -pool proxy.pool.whalesburg.com:8082 -wal YourEthWalletAddress -worker WorkerName -proto 2
dwarfpool.com (EXP):
  PhoenixMiner.exe -pool exp-eu.dwarfpool.com:8018 -wal YourExpWalletAddress/WorkerName
miningpoolhub (MUSIC):
  PhoenixMiner.exe -pool europe.ethash-hub.miningpoolhub.com:20585 -wal YourLoginName.WorkerName -pass x -proto 1
maxhash.org (UBIQ):
  PhoenixMiner.exe -pool ubiq-us.maxhash.org:10008 -wal YourUbqWalletAddress -worker WorkerName -coin ubq
ubiq.minerpool.net (UBIQ):
  PhoenixMiner.exe -pool lb.geo.ubiqpool.org:8001 -wal YourUbqWalletAddress -pass x -worker WorkerName -coin ubq
ubiqpool.io (UBIQ):
  PhoenixMiner.exe -pool eu2.ubiqpool.io:8008 -wal YourUbqWalletAddress.WorkerName -pass x -proto 4 -coin ubq
minerpool.net (PIRL):
  PhoenixMiner.exe -pool pirl.minerpool.net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerName
dodopool.com (Metaverse ETP):
  PhoenixMiner.exe -pool etp.dodopool.com:8008 -wal YourMetaverseETPWalletAddress -worker Rig1 -pass x
minerpool.net (Ellaism):
  PhoenixMiner.exe -pool ella.minerpool.net:8002 -wal YourEllaismWalletAddress -worker Rig1 -pass x
etherdig.net (ETH PPS):
  PhoenixMiner.exe -pool etherdig.net:4444 -wal YourEthWalletAddress.WorkerName -proto 4 -pass x
etherdig.net (ETH HVPPS):
  PhoenixMiner.exe -pool etherdig.net:3333 -wal YourEthWalletAddress.WorkerName -proto 4 -pass x
epool.io (CLO):
  PhoenixMiner.exe -pool eu.clo.epool.io:8008 -pool2 us.clo.epool.io:8008 -worker WorkerName -wal YourEthWalletAddress -pass x -coin clo -retrydelay 2
baikalmine.com (CLO):
  PhoenixMiner.exe -pool clo.baikalmine.com:3333 -wal YourEthWalletAddress -pass x -coin clo -worker rigName


  
Dual-mining command-line examples:

ETH on ethermine.org ETH, Blake2s on Nicehash:
  PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3 -dpool blake2s.eu.nicehash.com:3361 -dwal YourBtcWalletAddress -dcoin blake2s
Nicehash (Ethash + Blake2s):
  PhoenixMiner.exe -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0 -dpool blake2s.eu.nicehash.com:3361 -dwal YourBtcWalletAddress -dcoin blake2s

ProgPOW command-line examples:
BCI on BCI-Server:
  PhoenixMiner.exe -pool eu-1.pool.bci-server.com:3869 -wal YourBciWalletAddress.Rig1 -coin bci -proto 1

2. Features, requirements, and limitations

* Supports AMD Vega, 580/570/480/470, 460/560, Fury, 390/290 and older AMD GPUs with enough VRAM
* Supports Nvidia 20x0, 10x0 and 9x0 series as well as older cards with enough VRAM
* Highly optimized OpenCL and CUDA cores for maximum ethash mining speed
* Optional "green" kernels for RX580/570/560/480/470/460 to lower the power consumption by 2-3% with small, or no drop in hashrate
* Lowest developer fee of 0.65% (35 seconds defvee mining per each 90 minutes)
* Dual mining ethash/Blake2s with lowest devfee of 0.9% (35 seconds defvee mining per each 65 minutes)
* Advanced statistics: actual difficulty of each share, effective hashrate at the pool, and optional showing of estimated income in USD
* DAG file generation in the GPU for faster start-up and DAG epoch switches
* Supports all ethash mining pools and stratum protocols
* Supports secure pool connections (e.g. ssl://eu1.ethermine.org:5555) to prevent IP hijacking attacks
* Detailed statistics, including the individual cards hashrate, shares, temperature and fan speed
* Unlimited number of fail-over pools in epools.txt configuration file (or two on the command line)
* Automatic GPU tuning for the AMD GPUs to achieve maximum performance with your rig
* Supports devfee on alternative ethash currencies like ETC, EXP, Music, UBQ, Pirl, Ellaism, Metaverse ETP, PGC, Akroma, WhaleCoin, Victorium, Nekonium, Mix, EtherGem, Aura, HBC, Genom, EtherZero, Callisto, DubaiCoin, MOAC, Ether-1, and EtherCC. This allows you to use older cards with small VRAM or low hashate on current DAG epochs (e.g. GTX970).
* Full compatibility with the industry standard Claymore's Dual Ethereum miner, including most of command-line options, configuration files, and remote monitoring and management.
* Supports the new Ubqhash algorithm for the UBQ coin. Please note that you must add -coin ubq to your command line (or COIN: ubq to your epools.txt file) in order to mine UBQ
* Supports the ProgPOW algorithm for the Bitcoin Interest (BCI) coin mining. Please note that you must add -coin bci to your command line (or COIN: bci to your epools.txt file) in order to mine BCI
* Supports the ProgPOW algorithm for mining BCI.
* More features coming soon!

PhoenixMiner requires Windows x64 (Windows 7, Windows 10, etc.), or Linux x64 (tested on Ubuntu LTS
and Debian stable).

PhoenixMiner also supports dual mining (simultaneous mining of ethash/ubqhash and other cryptocoin algorithm).
Currently we support only Blake2s as secondary algorithm for dual mining. Note that when using dual mining,
there is no devfee on the secondary coin but the devfee on the main coin is increased to 0.9%. In other words,
if you are using the dual mining feature PhoenixMiner will mine for us for 35 seconds every 65 minutes.

Solo mining is supported since version 2.7c.

While the miner is running, you can use some interactive commands. Press the key 'h' while the
miner's console window has the keyboard focus to see the list of the available commands. The
interactive commands are also listed at the end of the following section.

3. Command-line arguments

Note that PhoenixMiner supports most of the command-line options of Claymore's dual Ethereum miner
so you can use the same command line options as the ones you would have used with Claymore's miner.

Pool options:
  -pool <host:port> Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining)
  -wal <wallet> Ethash wallet (some pools require appending of user name and/or worker)
  -pass <password> Ethash password (most pools don't require it, use 'x' as password if unsure)
  -worker <name> Ethash worker name (most pools accept it as part of wallet)
  -proto <n> Selects the kind of stratum protocol for the ethash pool:
     1: miner-proxy stratum spec (e.g. coinotron)
     2: eth-proxy (e.g. dwarfpool, nanopool) - this is the default, works for most pools
     3: qtminer (e.g. ethpool)
     4: EthereumStratum/1.0.0 (e.g. nicehash)
     5: EthereumStratum/2.0.0
  -coin <coin> Ethash coin to use for devfee to avoid switching DAGs:
     auto: Try to determine from the pool address (default)
     eth: Ethereum
     etc: Ethereum Classic
     exp: Expanse
     music: Musicoin
     ubq: UBIQ
     pirl: Pirl
     ella: Ellaism
     etp: Metaverse ETP
     pgc: Pegascoin
     akroma: Akroma
     whale: WhaleCoin
     vic: Victorium
     nuko: Nekonium
     mix: Mix
     egem: EtherGem
     aura: Aura
     hbc: Hotelbyte Coin
     gen: Genom
     etz: EtherZero
     clo: Callisto
     dbix: DubaiCoin
     moac: MOAC
     etho: Ether-1
     etcc: EtherCC
     yoc: Yocoin
     b2g: Bitcoiin2Gen
     esn: Ethersocial
     ath: Atheios
     reosc: REOSC
  -stales <n> Submit stales to ethash pool: 1 - yes (default), 0 - no
  -pool2 <host:port>  Failover ethash pool address. Same as -pool but for the failover pool
  -wal2 <wallet> Failover ethash wallet (if missing -wal will be used for the failover pool too)
  -pass2 <password> Failover ethash password (if missing -pass will be used for the failover pool too)
  -worker2 <name> Failover ethash worker name (if missing -worker will be used for the failover pool too)
  -proto2 <n> Failover ethash stratum protocol (if missing -proto will be used for the failover pool too)
  -coin2 <coin> Failover devfee Ethash coin (if missing -coin will be used for the failover pool too)
  -stales2 <n> Submit stales to the failover pool: 1 - yes (default), 0 - no
  -dpool <host:port> Dual mining pool address
  -dwal <wallet> Dual mining wallet
  -dpass <password> Dual mining pool password (most pools don't require it, use 'x' as password if unsure)
  -dworker <name> Dual mining worker name
  -dcoin blake2s Currently only the Blake2s algorithm is supported for dual mining. If you want to put
        all dual mining pools in dpools.txt, you need to set -dcoin blake2s in the command-line or in config.txt
   to force the miner to load the dual mining pools from dpools.txt
  -dstales <n> Submit stales to the dual mining pool: 1 - yes (default), 0 - no
General pool options:
  -fret <n> Switch to next pool afer N failed connection attempts (default: 3)
  -ftimeout <n> Reconnect if no new ethash job is receved for n seconds (default: 600)
  -ptimeout <n> Switch back to primary pool after n minutes. This setting is 30 minutes by default;
     set to 0 to disable automatic switch back to primary pool.
  -retrydelay <n> Seconds to wait before reconnecting (default: 20)
  -gwtime <n> Recheck period for Solo/GetWork mining (default: 200 ms)
  -rate <n> Report hashrate to the pool: 1 - yes, 0 - no (1 is the default)
Benchmark mode:
  -bench [<n>],-benchmark [<n>] Benchmark mode, optionally specify DAG epoch. Use this to test your rig.
Remote control options:
  -cdm <n> Selects the level of support of the CDM remote monitoring:
     0: disabled
     1: read-only - this is the default
     2: full (only use on secure connections)
  -cdmport <port> Set the CDM remote monitoring port (default is 3333). You can also specify
     <ip_addr:port> if you have a secure VPN connection and want to bind the CDM port to it
  -cdmpass <pass> Set the CDM remote monitoring password
  -cdmrs Reload the settings if config.txt is edited/uploaded remotely. Note that most options require restart in order to change.
      Currently the follwing options can be changed without restarting: -mi, -gt, -sci, -clf, -nvf, and all hardware control parameters
      (-tt, -fanmin, -fanmax, -powlim, -tmax, -cclock, -cvddc, -mclock, -mvddc).
Mining options:
  -amd  Use only AMD cards
  -acm  Turn on AMD compute mode on the supported GPUs. This is equivalent of pressing 'y' in the miner console.
  -nvidia  Use only Nvidia cards
  -gpus <123 ..n> Use only the specified GPUs (if more than 10, separate the indexes with comma)
  -mi <n> Set the mining intensity (0 to 14; 12 is the default for the new kernels). You may specify this option per-GPU.
  -gt <n> Set the GPU tuning parameter (6 to 400). The default is 15. You can change the
          tuning parameter interactively with the '+' and '-' keys in the miner's console window.
          If you don't specify -gt or you specify value 0, the miner will start auto-tuning to determine the best GT value for each GPU
          Note that when the GPU is dual-mining, it ignores the -gt values, and uses -sci instead.
  -sci <n> Set the dual mining intensity (1 to 1000). The default is 30. As you increase the value of -sci,
           the secondary coin hashrate will increase but the price will be higher power consumption and/or
           lower ethash hashrate.
           You can change the this parameter interactively with the '+' and '-' keys in the miner
           console window. You may specify this option per-GPU. If you set -sci to 0,
      the miner will use auto-tuning to determine the best value, while trying to maximize the
      ethash hashrate regardless of the secondary coin hashrate.
  -clKernel <n> Type of OpenCL kernel: 0 - generic, 1 - optimized, 2 - alternative, 3 - turbo (1 is the default)
  -clGreen <n> Use the power-efficient ("green") kernels (0: no, 1: yes; default: 0).
                 You may specify this option per-GPU. Note that you have to run auto-tune again as the
                 optimal GT values are completely different for the green kernels
  -clNew <n> Use the new AMD kernels (0: no, 1: yes; default: 1)
  -clf <n> AMD kernel sync (0: never, 1: periodic; 2: always; default: 1)
  -nvKernel <n> Type of Nvidia kernel: 0 auto (default), 1 old (v1), 2 newer (v2), 3 latest (v3).
                Note that v3 kernels are only supported on GTX10x0 GPUs. Also note that dual mining is
                supported only by v2 kernels. You may specify this option per-GPU.
  -nvdo <n> Enable Nvidia driver-specific optimizations (0 - no, the default; 1 - yes). Try -nvdo 1 if your
            are unstable. You may specify this option per-GPU.
  -nvNew <n> Use new Nvidia kernels if supported (0: no, 1: yes; default: 1)
  -nvf <n> Nvidia kernel sync (0: never, 1: periodic; 2: always; 3: forced; default: 1). You may specify this option per-GPU.
  -mode <n> Mining mode (0: dual mining if dual pool(s) are specified; 1: ethash only even if dual pools are specified).
            You may specify this option per-GPU.
  -list List the detected GPUs devices and exit
  -minRigSpeed <n> Restart the miner if avg 5 min speed is below <n> MH/s
  -eres <n> Allocate DAG buffers big enough for n epochs ahead (default: 2) to
      avoid allocating new buffers on each DAG epoch switch, which should improve DAG switch stability
  -lidag <n> Slow down DAG generation to avoid crashes when swiching DAG epochs
      (0-3, default: 0 - fastest, 3 - slowest). This option works only on AMD cards
  -gser <n> Serializing DAG creation on multiple GPUs (0 - no serializing, all GPUs generate the DAG simultaneously, this is the default;
      1 - partial overlap of DAG generation on each GPU; 2 - no overalp (each GPU waits until the previous one has finished generating the DAG);
      3-10 - from 1 to 8 seconds delay after each GPU DAG generation before the next one)
  -gpureset <n> Fully reset GPU when paused (0 - no, 1 - yes; default: no, except on 1080Ti). You may specify this option per-GPU.
  -altinit Use alternative way to initialize AMD cards to prevent startup crashes
  -rvram <n> Minimum free VRAM in MB (-1: don't check; default: 384 for Windows, and 128 for Linux)
  -wdog <n> Enable watchdog timer: 1 - yes, 0 - no (1 is the default). The watchdog timer checks
      periodically if any of the GPUs freezes and if it does, restarts the miner (see the -rmode
      command-line parameter for the restart modes)
  -wdtimeout <n> Watchdog timeout (30 - 300; default 45 seconds). You can use this parameter to increase
      the default watchdog timeout in case it restarts the miner needlessly
  -rmode <n> Selects the restart mode when a GPU crashes or freezes:
     0: disabled - miner will shut down instead of restarting
     1: restart with the same command line options - this is the default
     2: reboot (shut down miner and execute reboot.bat)
  -log <n> Selects the log file mode:
     0: disabled - no log file will be written
     1: write log file but don't show debug messages on screen (default)
     2: write log file and show debug messages on screen
  -logfile <name> Set the name of the logfile. If you place an asterisk (*) in the logfile name, it will be
      replaced by the current date/time to create a unique name every time PhoenixMiner is started. If there
      is no asterisk in the logfile name, the new log entries will be added to end of the same file. If you
      want to use the same logfile but the contents to be overwritten every time when you start the miner,
      put a dollar sign ($) character in the logfile name (e.g. -logfile my_log.txt$).
  -logdir <path> Set a path where the logfile(s) will be created
  -logsmaxsize <n> Maximum size of the logfiles in MB. The default is 200 MB (use 0 to turn off the limitation).
      On startup, if the logfiles are larger than the specified limit, the oldest are deleted. If you use a
      single logfile (by using -logfile), then it is truncated if it is bigger than the limit and a new one
      is created.
  -timeout <n> Restart miner according to -rmode after n minutes
  -pauseat <hh:mm> Pause the miner at hh::mm (24 hours time). You can specify multiple times: -pauseat 6:00,12:00
  -resumeat <hh:mm> Resume the miner at hh::mm (24 hours time). You can specify multiple times: -resumeat 8:00,22:00
  -gswin <n> GPU stats time window (5-30 sec; default: 15; use 0 to revert to pre-2.8 way of showing momentary stats)
  -gsi <n> Speed stats interval (5-30 sec; default: 5; use 0 to disable). The detailed stats are still
           shown every 45 seconds and aren't affected by the -gsi value
  -astats <n> Show advanced stats from Web sources (0: no; 1: yes). By default the coin exchange rates are updated every
              4 hours, and the coin difficulty is updated every 8 hours. You can increase these periods by specifying
              for example -astats 12, which will increase update periods to 12 and 24 hours respectively
  -gpow <n> Lower the GPU usage to n% of maximum (default: 100). If you already use -mi 0 (or other low value) use -li instead
  -li <n> Another way to lower the GPU usage. Bigger n values mean less GPU utilization; the default is 0.
  -resetoc Reset the hardware overclocking settings on startup
  -leaveoc Do not reset overclocking settings when closing the miner
Hardware control options (most are for AMD cards only, only tt 0-4, tstop, and tstart are supported on Nvidia GPUs), use comma to specify different values for each GPU:
  -tt <n> Set fan control target temperature (special values: 0 - no HW monitoring on ALL cards,
     1-4 - only monitoring on all cards with 30-120 seconds interval, negative - fixed fan speed at n %)
  -fanmin <n> Set fan control min speed in % (-1 for default)
  -fanmax <n> Set fan control max speed in % (-1 for default)
  -fcm <n> Set fan control mode (0 - auto, 1 - use VBIOS fan control, 2 - forced fan control; default: 0)
  -tmax <n> Set fan control max temperature (0 for default)
  -powlim <n> Set GPU power limit in % (from -75 to 75, 0 for default)
  -cclock <n> Set GPU core clock in MHz (0 for default)
  -cvddc <n> Set GPU core voltage in mV (0 for default)
  -mclock <n> Set GPU memory clock in MHz (0 for default)
  -mvddc <n> Set GPU memory voltage in mV (0 for default)
  -tstop <n> Pause a GPU when temp is >= n deg C (0 for default; i.e. off)
  -tstart <n> Resume a GPU when temp is <= n deg C (0 for default; i.e. off)
General Options:
  -v,--version  Show the version and exit
  -vs Show short version string (e.g. "4.1c") and exit
  -h,--help  Show information about the command-line options and exit

Per-GPU options
Some of the PhoenixMiner options can provide either the same setting for all GPUs, or a different
setting for each of the GPUs. For example, to specify the -gt value for all cards you would write
-gt 90 but if you want to specify a different GT value for each of the cards, use something like this:
-gt 20,15,40,90,90 for a five-GPU mining rig. This would set GT to 20 for the first GPU, 15 for the second
GPU, and so on. If you specify less values than you have GPUs, the rest of the GPUs will use the default
value for the parameter.  
  
Additionally, while the miner is running, you can use the following interactive commands
in the console window by pressing one of these keys:
  s   Print detailed statistics
  1-9 Pause/resume GPU1 ... GPU9 (if you have more than 9 GPUs, type 010 for card 10, 011 for card 11, etc.)
  p   Pause/resume the whole miner
  +,- Increase/decrease GPU tuning parameter
  g   Reset the GPU tuning parameter (and stop auto-tuning if active)
  x   Select the GPU(s) for manual or automatic GT tuning
  z   Start AMD auto-tune process
  r   Reload epools.txt and switch to primary ethash pool
  e   Select the current ethash pool (if you have more than 9 pools in the list, type 010 for pool 10, 011 for pool 11, etc.)
  d   Select the current dual-mining pool
  y   Turn on AMD Compute mode if it is off on some of the GPUs
  c   Reload the config.txt file (some settings require restart, see -cdmrs option above for details)
  h   Print this short help  

4. Configuration files

Note that PhoenixMiner supports the same configuration files as Claymore's dual Ethereum miner
so you can use your existing configuration files without any changes.

Instead of using command-line options, you can also control PhoenixMiner with configuration
files. If you run PhoenixMiner.exe without any options, it will search for the file config.txt
in the current directory and will read its command-line options from it. If you want, you can
use file with another name by specifying its name as the only command-line option
when running PhoenixMiner.exe.

You will find an example config.txt file in the PhoenixMiner's directory.

Instead of specifying the pool(s) directly on the command line, you can use another configuration
file for this, named epools.txt. There you can specify one pool per line (you will find an example
epools.txt file in the PhoenixMiner's directory).

For the dual mining pools, you can use the dpools.txt file, which has the same format as epools.txt
but for the secondary coin. You will find an example epools.txt file in the PhoenixMiner's directory.
Note that unlike the epools.txt, which is loaded each time when the miner starts, the dpools.txt file
is only read if you specify a dual mining pool on the command line with -dpool, or at least add
the -dcoin blake2s command-line option.

The advantages of using config.txt and epools.txt/dpools.txt files are:
- If you have multiple rigs, you can copy and paste all settings with these files
- If you control your rigs via remote control, you can change pools and even the miner options by
uploading new epools.txt files to the miner, or by uploading new config.txt file and restarting
the miner.

5. Remote monitoring and management

Phoenix miner is fully compatible with Claymore's dual miner protocol for remote monitoring and
management. This means that you can use any tools that are build to support Claymore's dual miner,
including the "Remote manager" application that is part of Claymore's dual miner package.

We are working on much more powerful and secure remote monitoring and control functionality and
control center application, which will allow better control over your remote or local rigs and some
unique features to increase your mining profits.

6. Hardware control options

 Here are some important notes about the hardware control options:
  • Hardware control options are supported only under Windows and for AMD cards. For Nvidia cards or under Linux, only monitoring (reporting) of the fan speeds and temperatures is supported. We will add full support for hardware control without this limitations in the next release of PhoenixMiner.
  • If you specify a single value (e.g. -cvddc 1150), it will be used on all cards. Specify different values for each card like this (separate with comma): -cvddc 1100,1100,1150,1120,1090 If the specified values are less than the number of GPUs, the rest of GPUs will use the default values.
  • We have tested only on relatively recent AMD GPUs (RX460/470/480/560/570/580 and Vega). Your results may vary with older GPUs.
  • The blockchain beta drivers from AMD show quite unstable results - often the voltages don't stick at all or revert back to the default after some time. For best results use the newer drivers from AMD: 18.2.1 or 18.5.1, where most of the bugs are fixed.
  • -tmax specifies the temperature at which the GPU should start to throttle (because the fans can't keep up).
  • If you use other programs for hardware control, conflicts are possible and quite likely. Use something like GPU-Z to monitor the voltages, etc. MSI Afterburner also seems to behave OK (so you can use it to control the Nvidia cards while AMD cards are controller by PhoenixMiner).
  • This should be obvious but still: if given clocks/voltages are causing crahses/freezes/incorrect shares when set with third-party program, they will be just as much unstable when set via PhoenixMiner hardware control options.
  • If you have problems with hardware control options of PhoenixMiner and you were using something else to control clocks, fans, and voltages (MSI Aftrerburner, OverdriveNTool, etc.), which you were happy with, it is probably best to keep using it and ignore the hardware control options of PhoenixMiner (or use only some of them and continue tweaking the rest with your third-party tools).

7. FAQ

Q001: Why another miner?
   A: We feel that the competition is good for the end user. In the first releases of PhoenixMiner
   we focused on the basic features and on the mining speed but we are now working on making our
   miner easier to use and even faster.
  
Q002: Can I run several instances of PhoenixMiner on the same rig?
   A: Yes, but make sure that each GPU is used by a single miner (use the -gpus, -amd, or -nvidia
   command-line options to limit the GPUs that given instance of PhoenixMiner actually uses).
      Another possible problem is that all instances will use the default CDM remote port 3333,
   which will prevent proper remote control for all but the first instance. To fix this problem,
   use the -cdmport command-line option to change the CDM remote port form its default value.
  
Q003: Can I run PhoenixMiner simultaneously on the same rig with other miners?
   A: Yes, but see the answer to the previous question for how to avoid problems.
  
Q004: What is a stale share?
   A: The ethash coins usually have very small average block time (15 seconds in most instances).
   On the other hand, to achieve high mining speed we must keep the GPUs busy so we can't switch
   the current job too often. If our rigs finds a share just after the someone else has found a
   solution for the current block, our share is a stale share. Ideally, the stale shares should be
   minimal as same pools do not give any reward for stale shares, and even these that do reward
   stale shares, give only partial reward for these shares. If the share is submitted too long
   after the block has ended, the pool may even fully reject it.
  
Q005: Why is the percentage of stale shares reported by PhoenixMiner smaller than the one shown
   by the pool?
   A: PhoenixMiner can only detect the stale shares that were discovered after it has received a
   new job (i.e. the "very stale") shares. There is additional latency in the pool itself, and in
   the network connection, which makes a share stale even if it was technically found before the
   end of the block from the miner's point of view. As pools only reports the shares as accepted
   or rejected, there is no way for the miner to determine the stale shares from the pool's
   point of view.
  
Q006: What is the meaning of the "actual share difficulty" shown by PhoenixMiner when a share is
   found?
   A: It allows you to see how close you were to finding an actual block (a rare event these days
   for the most miners with reasonable-sized mining rigs). You can find the current difficulty for
   given coin on sites like whattomine.com and then check to see if you have exceeded it with your
   maximum share difficulty. If you did, you have found a block (which is what the mining is all
   about).
  
Q007: What is the meaning of "effective speed" shown by PhoenixMiner's statistics?
   A: This is a measure of the actually found shares, which determines how the pool sees your
   miner hashrate. This number should be close to the average hashrate of your rig (usually a 2-4%
   lower than it) depending you your current luck in finding shares. This statistic is meaningless
   in the first few hours after the miner is started and will level off to the real value with
   time.
  
Q008: Why is the effective hashrate shown by the pool lower than the one shown by PhoenixMiner?
   A: There are two reasons for this: stale shares and luck. The stale shares are rewarded at only
   about 50-70% by most pools. The luck factor should level itself off over time but it may take
   a few days before it does. If your effective hashrate reported by the pool is consistently lower
   than the hashrate of your rig by more than 5-7% than you should look at the number of stale shares
   and the average share acceptance time - if it is higher than 100 ms, try to find a pool that is
   near to you geographically to lower the network latency. You can also restart your rig, or
   try another pool.

8. Troubleshooting

P001: I'm using AMD RX470/480/570/580 or similar card and my hashrate dropped significantly in the past
     few months for Ethereum and Ethereum classic!
     S: This is known problem with some cards. For the newer cards (RX470/480/570/580), this can be
     solved by using the special blockchain driver from AMD (or try the latest drivers, they may
     incorporate the fix). For the older cards there is no workaround but you still can mine EXP,
     Musicoin, UBQ or PIRL with the same speed that you mined ETH before the drop.
     
P002: My Nvidia GTX9x0 card is showing very low hashrate under Windows 10!
      S: While there is a (convoluted) workaround, the best solution is to avoid Windows 10
      for these cards - use Windows 7 instead.
      
P003: I'm using Nvidia GTX970 (or similar) card and my hashrate dropped dramatically for Ethereum or
      Ethereum classic!
      S: GTX970 has enough VRAM for larger DAGs but its hashate drops when the DAG size starts
      to exceed 2 GB or so. Unlike the AMD Polaris-based cards, there is no workaround for this
      problem. We recommend using these cards to mine EXP, Musicoin, UBQ or PIRL with the same speed
      that you used to ETH before the drop.
      
P004: I can't see some of my cards (or their fan speed and temperature) when using Windows Remote Desktop (RDP)!
      S: This is a known problem with RDP. Use VNC or TeamViewer instead.
      
P005: On Windows 10, if you click inside the PhoenixMiner console, it freezes!
      S: This is a known problem on Windows 10, related to so called "Quick Edit" feature of the command
     prompt window. From PhoenixMiner 2.6, the QuickMode is disabled by default, so you shouldn't experience
     this problem. If you still, do, read here how to solve it: https://stackoverflow.com/q/33883530

P006: Immediately after starting, PhoenixMiner stops working and the last message is "debugger detected"
      S: If you have only Nvidia cards, add the option -nvidia to the PhoenixMiner.exe command line.
     If you have only AMD cards, add the option -amd to the command line.
     
P007: PhoenixMiner shows an error after allocating DAG buffer and shuts down.
      S: If you have more than one GPU, make sure that your Windows page file minimal size is set to at
          least (N x DS + 4) GB, where N is the number of GPUs, and DS is the size of DAG in GB (about 2.9 GB around
          January 2019 for ETC and ETH). For example, if you have 10 GPUs, you need 10 x 2.9 + 4 = 33 GB minimal
          size of the page file. Note that this will increase as the DAG sizes increase. If you are using -clkernel 3, for each GPU add size of
          the DAG twice instead of once (e.g. for 3 GPUs mining with -clkenel 3 you will need 3 x 2 x 2.9 + 4 = 21.4 GB minimal page file size)
     
P008: The miner sometimes crashes when the DAG epoch change.
      S: During DAG generation, the GPUs are loaded more than during the normal operation. If you have
     overclocked or undervolted the GPUs "to the edge", the DAG generation ofter pushes them "over the
     edge". Another possible reason for the crash (especially if the whole rig crashes) is the higher
     power usage during this process. You can lower the DAG generation speed by specifying the -lidag
     command-line option. The possible values are 0 (no slow down), 1, 2, and 3 (max slowdown).
     In order to check if your rig would be stable during DAG generation, run it in benchmark mode
     by specifying the -bench 210 command line option. Then every time when you press the key 'd'
     the miner will advance to the next DAG epoch, and you will be able to see if it is stable during
     multiple DAG generations. If it isn't you can try to alter the -lidag and -eres command line options
     until the desired stability is achieved.



UnclWish
Sr. Member
****
Offline Offline

Activity: 1414
Merit: 253


View Profile
June 29, 2019, 04:18:23 PM
 #3447

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.
For me it works fine. I checked it over 36+ hours. And always devfee works as it must...
Bohr256
Jr. Member
*
Offline Offline

Activity: 77
Merit: 1


View Profile
June 29, 2019, 05:46:20 PM
 #3448

Have you checked your pool statistics for inconsistencies in hash rate? I tried it again today, and at around 7:10 the hash rate went down yet again like the previous day. I have no idea why at 7:10 AM PST. I left it running for a 3 hours and it kept reporting low shares. I then switched to ethminer and the hash rate climbed up to normal.  Logs show it mined 3x for dev. @ 36 secs. Wtf is going on here?

https://i.imgur.com/d5LrU03.png
ManDoneKTM
Newbie
*
Offline Offline

Activity: 150
Merit: 0


View Profile
June 29, 2019, 09:07:48 PM
 #3449

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.


WHY did you quote entire post of the dev Huh? How did you survive until 2019 ? OMG ...
UnclWish
Sr. Member
****
Offline Offline

Activity: 1414
Merit: 253


View Profile
June 29, 2019, 09:36:08 PM
 #3450

Have you checked your pool statistics for inconsistencies in hash rate? I tried it again today, and at around 7:10 the hash rate went down yet again like the previous day. I have no idea why at 7:10 AM PST. I left it running for a 3 hours and it kept reporting low shares. I then switched to ethminer and the hash rate climbed up to normal.  Logs show it mined 3x for dev. @ 36 secs. Wtf is going on here?

https://i.imgur.com/d5LrU03.png
Check your miner, comp etc. For my rig Phoenix miner mines fine. Only official devfee time every hour. All other time it mines on my pool. I checking accepted hasrate on pool statistics every day. Effective hashrate from miner equals to pool side. Pool even shows more effective hashrate than miner...
bategojko74
Jr. Member
*
Offline Offline

Activity: 209
Merit: 5


View Profile
June 30, 2019, 07:42:53 AM
Last edit: June 30, 2019, 08:39:24 AM by bategojko74
 #3451

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.

Just remove the Phoenix miner's address from epools.txt file and add your backup pools there if you like. Phoenixminer has put it for demo purpose and the miner mines to this address when your pool is down. He had explained this many times.
Bigdrago
Newbie
*
Offline Offline

Activity: 312
Merit: 0


View Profile
June 30, 2019, 07:56:21 PM
 #3452

Hi.
How to restart the mining rig when the program crash?
How to restart the mining rig if hashrate is below XXX ?
hesido
Jr. Member
*
Offline Offline

Activity: 148
Merit: 5


View Profile
July 01, 2019, 10:28:43 PM
 #3453

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.

You don't need to quote the entire original post to talk here.

I have been mining on and off for a total of 2-3 months with phoenixminer, and this never happened. Probably, you have not configured the pools properly and it falls back to dev pools in the config files.
Bohr256
Jr. Member
*
Offline Offline

Activity: 77
Merit: 1


View Profile
July 02, 2019, 01:50:13 AM
 #3454

I solved the issue by using the olde unplug/replug technique. It's working fine, but still have no idea what it was.
NordicWrapping
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
July 02, 2019, 10:18:05 PM
 #3455

i like this one.
Baimer
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
July 05, 2019, 03:38:38 PM
 #3456

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.


if you are using command line mode of this miner make sure you remove epools.txt and dpools.txt from folder
due to crashes, it turns to link inside of those and mine devfee's instead of yours...



deleted everything, pools are registered correctly, DEV still happens a couple of hours a day
darkCryptoMiner
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
July 05, 2019, 03:41:06 PM
 #3457

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.
deleted everything, pools are registered correctly, DEV still happens a couple of hours a day


if you are using command line mode of this miner make sure you remove epools.txt and dpools.txt from folder
due to crashes, it turns to link inside of those and mine devfee's instead of yours...



deleted everything, pools are registered correctly, DEV still happens a couple of hours a day

Sanity check: downloaded the correct binaries? Compared the hashes?
Baimer
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
July 05, 2019, 10:43:37 PM
 #3458

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.
deleted everything, pools are registered correctly, DEV still happens a couple of hours a day


if you are using command line mode of this miner make sure you remove epools.txt and dpools.txt from folder
due to crashes, it turns to link inside of those and mine devfee's instead of yours...



deleted everything, pools are registered correctly, DEV still happens a couple of hours a day

Sanity check: downloaded the correct binaries? Compared the hashes?
downloaded the new archive, reinstalled the windows - all as before
UnclWish
Sr. Member
****
Offline Offline

Activity: 1414
Merit: 253


View Profile
July 06, 2019, 01:00:05 AM
 #3459

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.


if you are using command line mode of this miner make sure you remove epools.txt and dpools.txt from folder
due to crashes, it turns to link inside of those and mine devfee's instead of yours...



deleted everything, pools are registered correctly, DEV still happens a couple of hours a day
Problem is on your side. All mines via Phoenix without problems. How and what pools you're registered? How you launch miner?
Baimer
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
July 06, 2019, 05:44:37 AM
 #3460

Your miner is shocking, it is brilliant for power & speed but a couple of times I have stopped the miner due to mining on your address for over 3 hours, everyone do NOT use this miner it mines for the DEV for hours at a time. total sham.


if you are using command line mode of this miner make sure you remove epools.txt and dpools.txt from folder
due to crashes, it turns to link inside of those and mine devfee's instead of yours...



deleted everything, pools are registered correctly, DEV still happens a couple of hours a day
Problem is on your side. All mines via Phoenix without problems. How and what pools you're registered? How you launch miner?
2019.07.04:22:36:01.600: main Phoenix Miner 4.2c Windows/msvc - Release build
2019.07.04:22:36:01.600: main Cmd line:
2019.07.04:22:36:01.600: main config.txt: -pool eth-ru2.dwarfpool.com:8008 -pool2 eth-ru.dwarfpool.com:8008 -wal 0x5d80ff4a5ce4a9983917b145f88293b09ca7a1c4/Baimer -pass x -proto 2 -cdm 1 -powlim 50 -cclock 1175 -cvddc 866 -mclock 2185 -mvddc 860 -mi 14 -wdog 1 -rmode 2 -clgreen 1 -tstop 80 -tstart 50 -clkernel 3 -nvdo 1 -nvkernel 3 -nvf 3 -minRigSpeed 155
2019.07.04:22:36:01.954: main CUDA version: 10.0, CUDA runtime: 8.0
2019.07.04:22:36:03.823: main OpenCL driver version: 19.2/3
2019.07.04:22:36:03.826: main Available GPUs for mining:
2019.07.04:22:36:03.826: main GPU1: GeForce GTX 1060 6GB (pcie 1), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2019.07.04:22:36:03.826: main GPU2: GeForce GTX 1060 6GB (pcie 2), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2019.07.04:22:36:03.826: main GPU3: GeForce GTX 1060 6GB (pcie 3), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2019.07.04:22:36:03.826: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 32 CUs
2019.07.04:22:36:03.826: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs
2019.07.04:22:36:03.826: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs
2019.07.04:22:36:03.858: main ADL library initialized
2019.07.04:22:36:03.863: main NVML library initialized
2019.07.04:22:36:03.906: main Nvidia driver version: 430.64
2019.07.04:22:36:05.877: main Eth: the pool list contains 2 pools (2 from command-line)
2019.07.04:22:36:05.877: main Eth: primary pool: eth-ru2.dwarfpool.com:8008
2019.07.04:22:36:05.877: main Starting GPU mining
2019.07.04:22:36:05.877: main Matched GPU4 to ADL adapter index 0 (method 1)
2019.07.04:22:36:05.910: main GPU4: Created ADL monitor for adapter 0; overdrive version: 7
2019.07.04:22:36:05.918: main GPU4: using AMD driver ver 19.4.3
2019.07.04:22:36:05.918: main Matched GPU5 to ADL adapter index 8 (method 1)
2019.07.04:22:36:05.950: main GPU5: Created ADL monitor for adapter 8; overdrive version: 7
2019.07.04:22:36:05.950: main GPU5: using AMD driver ver 19.4.3
2019.07.04:22:36:05.950: main Matched GPU6 to ADL adapter index 16 (method 1)
2019.07.04:22:36:05.981: main GPU6: Created ADL monitor for adapter 16; overdrive version: 7
2019.07.04:22:36:05.981: main GPU6: using AMD driver ver 19.4.3
2019.07.04:22:36:05.981: wdog Starting watchdog thread
2019.07.04:22:36:05.982: main Eth: Connecting to ethash pool eth-ru2.dwarfpool.com:8008 (proto: EthProxy)
2019.07.04:22:36:05.993: hwmc GPU4: set GPU clocks to 1175 MHz (Vddc 866 mV)
2019.07.04:22:36:05.997: hwmc GPU4: set VMEM clocks to 2185 MHz (Vddc 860 mV)
2019.07.04:22:36:05.998: hwmc GPU5: set power limit 50% (90C max temp)
2019.07.04:22:36:06.004: hwmc GPU5: set GPU clocks to 1175 MHz (Vddc 866 mV)
2019.07.04:22:36:06.008: hwmc GPU5: set VMEM clocks to 2185 MHz (Vddc 860 mV)
2019.07.04:22:36:06.010: hwmc GPU6: set power limit 50% (90C max temp)
2019.07.04:22:36:06.016: hwmc GPU6: set GPU clocks to 1175 MHz (Vddc 866 mV)
2019.07.04:22:36:06.020: hwmc GPU6: set VMEM clocks to 2185 MHz (Vddc 860 mV)
2019.07.04:22:36:06.077: eths Eth: Connected to ethash pool eth-ru2.dwarfpool.com:8008 (87.98.182.61)
2019.07.04:22:36:06.077: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x5d80ff4a5ce4a9983917b145f88293b09ca7a1c4/Baimer","x"]}

2019.07.04:22:36:06.146: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2019.07.04:22:36:06.146: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:36:06.187: main Listening for CDM remote manager at port 3333 in read-only mode
2019.07.04:22:36:06.187: main GPU1: 43C 67%, GPU2: 40C 76%, GPU3: 44C 75%, GPU4: 46C 99%, GPU5: 38C 79%, GPU6: 43C 79%
2019.07.04:22:36:06.215: eths Eth: Received: {"result":["0x76ee93e8b8eb7416b2b4c5bdf24b8f9e3df3a6a68bf05ddab43b77ece4d8641b","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:36:06.218: eths Eth: New job #76ee93e8 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:36:06.218: GPU1 GPU1: Starting up... (0)
2019.07.04:22:36:06.218: GPU1 GPU1: Generating ethash light cache for epoch #269
2019.07.04:22:36:06.234: GPU2 GPU2: Starting up... (0)
2019.07.04:22:36:06.249: GPU3 GPU3: Starting up... (0)
2019.07.04:22:36:06.265: GPU4 GPU4: Starting up... (0)
2019.07.04:22:36:06.281: GPU5 GPU5: Starting up... (0)
2019.07.04:22:36:06.296: GPU6 GPU6: Starting up... (0)
2019.07.04:22:36:09.129: GPU1 Light cache generated in 2.9 s (17.1 MB/s)
2019.07.04:22:36:09.403: GPU2 GPU2: Allocating DAG (3.12) GB; good for epoch up to #271
2019.07.04:22:36:09.405: GPU3 GPU3: Allocating DAG (3.12) GB; good for epoch up to #271
2019.07.04:22:36:09.537: GPU2 GPU2: Allocating light cache buffer (49.9) MB; good for epoch up to #271
2019.07.04:22:36:09.537: GPU3 GPU3: Allocating light cache buffer (49.9) MB; good for epoch up to #271
2019.07.04:22:36:09.576: GPU1 GPU1: Allocating DAG (3.12) GB; good for epoch up to #271
2019.07.04:22:36:09.675: GPU2 GPU2: Generating DAG for epoch #269
2019.07.04:22:36:09.676: GPU3 GPU3: Generating DAG for epoch #269
2019.07.04:22:36:09.683: GPU1 GPU1: Allocating light cache buffer (49.9) MB; good for epoch up to #271
2019.07.04:22:36:09.824: GPU1 GPU1: Generating DAG for epoch #269
2019.07.04:22:36:09.962: GPU4 GPU4: Allocating DAG (2x 3.12) GB; good for epoch up to #271
2019.07.04:22:36:09.980: GPU4 GPU4: Allocating light cache buffer (49.9) MB; good for epoch up to #271
2019.07.04:22:36:10.104: GPU4 GPU4: Generating DAG for epoch #269
2019.07.04:22:36:10.388: GPU5 GPU5: Allocating DAG (2x 3.12) GB; good for epoch up to #271
2019.07.04:22:36:10.405: GPU5 GPU5: Allocating light cache buffer (49.9) MB; good for epoch up to #271
2019.07.04:22:36:10.528: GPU5 GPU5: Generating DAG for epoch #269
2019.07.04:22:36:10.829: GPU6 GPU6: Allocating DAG (2x 3.12) GB; good for epoch up to #271
2019.07.04:22:36:10.843: GPU6 GPU6: Allocating light cache buffer (49.9) MB; good for epoch up to #271
2019.07.04:22:36:10.968: GPU6 GPU6: Generating DAG for epoch #269
2019.07.04:22:36:11.107: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:11.107: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
2019.07.04:22:36:11.203: GPU3 GPU3: DAG   9%
2019.07.04:22:36:11.376: GPU2 GPU2: DAG  11%
2019.07.04:22:36:11.462: GPU1 GPU1: DAG  11%
2019.07.04:22:36:11.665: GPU4 GPU4: DAG  28%
2019.07.04:22:36:12.077: GPU5 GPU5: DAG  28%
2019.07.04:22:36:12.514: GPU6 GPU6: DAG  28%
2019.07.04:22:36:12.718: GPU3 GPU3: DAG  20%
2019.07.04:22:36:13.073: GPU2 GPU2: DAG  23%
2019.07.04:22:36:13.084: GPU1 GPU1: DAG  23%
2019.07.04:22:36:13.238: GPU4 GPU4: DAG  60%
2019.07.04:22:36:13.649: GPU5 GPU5: DAG  60%
2019.07.04:22:36:14.087: GPU6 GPU6: DAG  60%
2019.07.04:22:36:14.232: GPU3 GPU3: DAG  31%
2019.07.04:22:36:14.706: GPU1 GPU1: DAG  36%
2019.07.04:22:36:14.771: GPU2 GPU2: DAG  36%
2019.07.04:22:36:14.810: GPU4 GPU4: DAG  93%
2019.07.04:22:36:15.222: GPU5 GPU5: DAG  93%
2019.07.04:22:36:15.484: GPU4 GPU4: DAG generated in 5.4 s (590.3 MB/s)
2019.07.04:22:36:15.485: GPU4 GPU4: Using Ethash OCL kernels (Ellesmere; -clkernel 3)
2019.07.04:22:36:15.485: GPU4 GPU4: no -gt value specified, switching to auto-tune
2019.07.04:22:36:15.485: GPU4 GPU4: starting auto-tune process
2019.07.04:22:36:15.659: GPU6 GPU6: DAG  93%
2019.07.04:22:36:15.747: GPU3 GPU3: DAG  42%
2019.07.04:22:36:15.898: GPU5 GPU5: DAG generated in 5.4 s (591.5 MB/s)
2019.07.04:22:36:15.898: GPU5 GPU5: Using Ethash OCL kernels (Ellesmere; -clkernel 3)
2019.07.04:22:36:15.898: GPU5 GPU5: no -gt value specified, switching to auto-tune
2019.07.04:22:36:15.898: GPU5 GPU5: starting auto-tune process
2019.07.04:22:36:16.091: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:36:16.159: eths Eth: Received: {"result":["0x7889bbfee7c37dfe69d2a3c529ee01aec5f560e6c0d2bbe81a7ef4022fd0a409","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:36:16.159: eths Eth: New job #7889bbfe from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:36:16.186: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:16.186: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
2019.07.04:22:36:16.336: GPU6 GPU6: DAG generated in 5.4 s (591.7 MB/s)
2019.07.04:22:36:16.337: GPU6 GPU6: Using Ethash OCL kernels (Ellesmere; -clkernel 3)
2019.07.04:22:36:16.337: GPU6 GPU6: no -gt value specified, switching to auto-tune
2019.07.04:22:36:16.337: GPU6 GPU6: starting auto-tune process
2019.07.04:22:36:16.340: GPU1 GPU1: DAG  48%
2019.07.04:22:36:16.470: GPU2 GPU2: DAG  48%
2019.07.04:22:36:17.262: GPU3 GPU3: DAG  53%
2019.07.04:22:36:17.960: GPU1 GPU1: DAG  61%
2019.07.04:22:36:18.168: GPU2 GPU2: DAG  61%
2019.07.04:22:36:18.778: GPU3 GPU3: DAG  64%
2019.07.04:22:36:19.581: GPU1 GPU1: DAG  73%
2019.07.04:22:36:19.866: GPU2 GPU2: DAG  73%
2019.07.04:22:36:20.293: GPU3 GPU3: DAG  75%
2019.07.04:22:36:20.319: GPU6 Eth: GPU6: ETH share found!
2019.07.04:22:36:20.319: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x3ca93cfd488eae93","0x7889bbfee7c37dfe69d2a3c529ee01aec5f560e6c0d2bbe81a7ef4022fd0a409","0xd73cda1efa45f12985cae28d41e1f49fccbab81a8e2f3493d0d1f33a796e23e3"]}

2019.07.04:22:36:20.319: eths Eth: Share actual difficulty: 7845 MH
2019.07.04:22:36:21.201: GPU1 GPU1: DAG  86%
2019.07.04:22:36:21.261: main Eth speed: 74.789 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:21.261: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 25.745 MH/s (0) 5: 25.739 MH/s (0) 6: 23.305 MH/s (0)
2019.07.04:22:36:21.564: GPU2 GPU2: DAG  86%
2019.07.04:22:36:21.809: GPU3 GPU3: DAG  86%
2019.07.04:22:36:22.727: GPU1 GPU1: DAG  98%
2019.07.04:22:36:22.727: GPU1 GPU1: DAG generated in 12.9 s (246.2 MB/s)
2019.07.04:22:36:22.729: GPU1 GPU1: Using v3 Ethash CUDA kernels (GeForce GTX 1060 6GB)
2019.07.04:22:36:23.160: GPU2 GPU2: DAG  98%
2019.07.04:22:36:23.160: GPU2 GPU2: DAG generated in 13.5 s (235.5 MB/s)
2019.07.04:22:36:23.163: GPU2 GPU2: Using v3 Ethash CUDA kernels (GeForce GTX 1060 6GB)
2019.07.04:22:36:23.324: GPU3 GPU3: DAG  97%
2019.07.04:22:36:23.438: GPU3 GPU3: DAG generated in 13.8 s (230.8 MB/s)
2019.07.04:22:36:23.440: GPU3 GPU3: Using v3 Ethash CUDA kernels (GeForce GTX 1060 6GB)
2019.07.04:22:36:26.104: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:36:26.105: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:36:26.173: eths Eth: Received: {"result":["0xb04d2b071dc40577b8d73352964a8e808105d5c65c3718cb02396b885b0b5e5b","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:36:26.173: eths Eth: New job #b04d2b07 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:36:27.111: main Eth speed: 135.086 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:27.111: main GPUs: 1: 22.276 MH/s (0) 2: 17.603 MH/s (0) 3: 17.837 MH/s (0) 4: 26.125 MH/s (0) 5: 26.123 MH/s (0) 6: 25.121 MH/s (0)
2019.07.04:22:36:32.196: main Eth speed: 129.693 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:32.196: main GPUs: 1: 23.146 MH/s (0) 2: 19.936 MH/s (0) 3: 19.737 MH/s (0) 4: 22.336 MH/s (0) 5: 22.333 MH/s (0) 6: 22.205 MH/s (0)
2019.07.04:22:36:34.633: main GPU1: 45C 70%, GPU2: 44C 74%, GPU3: 47C 83%, GPU4: 52C 99%, GPU5: 45C 79%, GPU6: 48C 79%
2019.07.04:22:36:36.117: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:36:36.186: eths Eth: Received: {"result":["0xb1790495f7990f8a39aa64e59e30d204b177db8257e6a011a48cc6684aa59d97","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:36:36.186: eths Eth: New job #b1790495 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:36:37.273: main Eth speed: 124.031 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:37.273: main GPUs: 1: 23.779 MH/s (0) 2: 20.295 MH/s (0) 3: 20.304 MH/s (0) 4: 19.878 MH/s (0) 5: 19.875 MH/s (0) 6: 19.900 MH/s (0)
2019.07.04:22:36:42.350: main Eth speed: 134.434 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:42.350: main GPUs: 1: 24.343 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 23.599 MH/s (0) 5: 22.373 MH/s (0) 6: 21.910 MH/s (0)
2019.07.04:22:36:46.130: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:36:46.130: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:36:46.199: eths Eth: Received: {"result":["0xff5bafaedd465344d97292eef8fece78537d90d57de03605aa7934db5b349b3e","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:36:46.199: eths Eth: New job #ff5bafae from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:36:47.427: main Eth speed: 148.119 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:47.427: main GPUs: 1: 24.575 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 27.746 MH/s (0) 5: 27.198 MH/s (0) 6: 26.392 MH/s (0)
2019.07.04:22:36:51.082: main 
2019.07.04:22:36:51.082: main *** 0:00 *** 7/4 22:36 **************************************
2019.07.04:22:36:51.082: main Eth: Mining ETH on eth-ru2.dwarfpool.com:8008 for 0:00
2019.07.04:22:36:51.082: main 3 GPU(s) are auto-tuning. Hashrate may be low until they are ready.
2019.07.04:22:36:51.082: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.07.04:22:36:51.082: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.07.04:22:36:51.082: main Eth: Maximum difficulty of found share: 7845 MH
2019.07.04:22:36:51.082: main Eth: Average speed (5 min): 0.000 MH/s
2019.07.04:22:36:51.082: main 
2019.07.04:22:36:51.691: GPU1 Eth: GPU1: ETH share found!
2019.07.04:22:36:51.691: eths Eth: Send: {"id":8,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xb6f22b38389012ee","0xff5bafaedd465344d97292eef8fece78537d90d57de03605aa7934db5b349b3e","0x2d173d43a8e86dd13747f0c56b3aac39594824b0b1a66155d624c0e8b3f8813f"]}

2019.07.04:22:36:51.691: eths Eth: Share actual difficulty: 2639 MH
2019.07.04:22:36:52.504: main Eth speed: 157.915 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:52.504: main GPUs: 1: 24.328 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 30.613 MH/s (0) 5: 30.519 MH/s (0) 6: 30.246 MH/s (0)
2019.07.04:22:36:56.144: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:36:56.212: eths Eth: Received: {"result":["0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:36:56.212: eths Eth: New job #c7b7c668 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:36:57.581: main Eth speed: 160.408 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:36:57.581: main GPUs: 1: 24.339 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 31.597 MH/s (0) 5: 31.250 MH/s (0) 6: 31.014 MH/s (0)
2019.07.04:22:37:02.658: main Eth speed: 162.073 MH/s, shares: 0/0/0, time: 0:00
2019.07.04:22:37:02.658: main GPUs: 1: 24.104 MH/s (0) 2: 21.108 MH/s (0) 3: 21.101 MH/s (0) 4: 31.949 MH/s (0) 5: 31.899 MH/s (0) 6: 31.911 MH/s (0)
2019.07.04:22:37:03.064: main GPU1: 44C 70%, GPU2: 44C 74%, GPU3: 47C 84%, GPU4: 55C 99%, GPU5: 48C 79%, GPU6: 51C 79%
2019.07.04:22:37:06.157: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:37:06.157: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:37:06.226: eths Eth: Received: {"result":["0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:37:07.735: main Eth speed: 161.977 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:07.735: main GPUs: 1: 24.105 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 31.816 MH/s (0) 5: 31.855 MH/s (0) 6: 31.993 MH/s (0)
2019.07.04:22:37:12.812: main Eth speed: 160.808 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:12.812: main GPUs: 1: 24.106 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 31.499 MH/s (0) 5: 31.479 MH/s (0) 6: 31.515 MH/s (0)
2019.07.04:22:37:16.170: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:37:16.239: eths Eth: Received: {"result":["0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:37:17.888: main Eth speed: 161.041 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:17.888: main GPUs: 1: 24.109 MH/s (0) 2: 21.108 MH/s (0) 3: 21.101 MH/s (0) 4: 31.600 MH/s (0) 5: 31.578 MH/s (0) 6: 31.545 MH/s (0)
2019.07.04:22:37:20.804: GPU1 Eth: GPU1: ETH share found!
2019.07.04:22:37:20.804: eths Eth: Send: {"id":9,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xac7a60568689c56a","0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x0e6d5d6def615fc13f76b670ef49bd87426ec02acaeb05796462833972bf3108"]}

2019.07.04:22:37:20.804: eths Eth: Share actual difficulty: 9660 MH
2019.07.04:22:37:22.965: main Eth speed: 162.975 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:22.965: main GPUs: 1: 24.110 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 32.293 MH/s (0) 5: 32.279 MH/s (0) 6: 32.085 MH/s (0)
2019.07.04:22:37:26.183: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:37:26.183: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:37:26.252: eths Eth: Received: {"result":["0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:37:27.995: main Eth speed: 163.363 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:27.995: main GPUs: 1: 24.113 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 32.345 MH/s (0) 5: 32.354 MH/s (0) 6: 32.344 MH/s (0)
2019.07.04:22:37:31.448: main GPU1: 44C 71%, GPU2: 45C 74%, GPU3: 48C 83%, GPU4: 57C 99%, GPU5: 49C 79%, GPU6: 53C 79%
2019.07.04:22:37:33.072: main Eth speed: 163.386 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:33.072: main GPUs: 1: 24.107 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 32.353 MH/s (0) 5: 32.353 MH/s (0) 6: 32.365 MH/s (0)
2019.07.04:22:37:36.119: main 
2019.07.04:22:37:36.119: main *** 0:01 *** 7/4 22:37 **************************************
2019.07.04:22:37:36.119: main Eth: Mining ETH on eth-ru2.dwarfpool.com:8008 for 0:01
2019.07.04:22:37:36.119: main 3 GPU(s) are auto-tuning. Hashrate may be low until they are ready.
2019.07.04:22:37:36.119: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.07.04:22:37:36.119: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.07.04:22:37:36.119: main Eth: Maximum difficulty of found share: 9660 MH
2019.07.04:22:37:36.119: main Eth: Average speed (5 min): 0.000 MH/s
2019.07.04:22:37:36.119: main Eth: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
2019.07.04:22:37:36.119: main 
2019.07.04:22:37:36.197: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:37:36.265: eths Eth: Received: {"result":["0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:37:38.137: GPU4 Eth: GPU4: ETH share found!
2019.07.04:22:37:38.137: eths Eth: Send: {"id":10,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xdc396bc46cd76818","0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x93eb1ed3d83219cdc330c9e178c110053dc4643955136583c8e3ab8dd6d6e98c"]}

2019.07.04:22:37:38.137: eths Eth: Share actual difficulty: 3420 MH
2019.07.04:22:37:38.150: main Eth speed: 162.938 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:38.150: main GPUs: 1: 24.093 MH/s (0) 2: 21.108 MH/s (0) 3: 21.101 MH/s (0) 4: 32.205 MH/s (0) 5: 32.228 MH/s (0) 6: 32.204 MH/s (0)
2019.07.04:22:37:43.226: main Eth speed: 163.004 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:43.226: main GPUs: 1: 24.092 MH/s (0) 2: 21.108 MH/s (0) 3: 21.101 MH/s (0) 4: 32.216 MH/s (0) 5: 32.245 MH/s (0) 6: 32.243 MH/s (0)
2019.07.04:22:37:46.210: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:37:46.210: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:37:46.279: eths Eth: Received: {"result":["0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:37:48.303: main Eth speed: 163.284 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:48.303: main GPUs: 1: 24.093 MH/s (0) 2: 21.108 MH/s (0) 3: 21.101 MH/s (0) 4: 32.334 MH/s (0) 5: 32.348 MH/s (0) 6: 32.299 MH/s (0)
2019.07.04:22:37:53.396: main Eth speed: 163.564 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:53.396: main GPUs: 1: 24.106 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 32.418 MH/s (0) 5: 32.413 MH/s (0) 6: 32.419 MH/s (0)
2019.07.04:22:37:55.706: GPU5 Eth: GPU5: ETH share found!
2019.07.04:22:37:55.706: eths Eth: Send: {"id":11,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x27c079976a5214af","0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x81a61766c3b90040a8a9d04cb4fe5b86230344b48a76eb8dead0fd8060f07c57"]}

2019.07.04:22:37:55.706: eths Eth: Share actual difficulty: 7588 MH
2019.07.04:22:37:56.223: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:37:56.292: eths Eth: Received: {"result":["0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:37:58.473: main Eth speed: 163.566 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:37:58.473: main GPUs: 1: 24.103 MH/s (0) 2: 21.107 MH/s (0) 3: 21.100 MH/s (0) 4: 32.416 MH/s (0) 5: 32.418 MH/s (0) 6: 32.422 MH/s (0)
2019.07.04:22:37:59.896: main GPU1: 44C 70%, GPU2: 45C 74%, GPU3: 48C 83%, GPU4: 58C 99%, GPU5: 51C 79%, GPU6: 54C 79%
2019.07.04:22:38:03.550: main Eth speed: 163.306 MH/s, shares: 0/0/0, time: 0:01
2019.07.04:22:38:03.550: main GPUs: 1: 24.099 MH/s (0) 2: 21.107 MH/s (0) 3: 21.100 MH/s (0) 4: 32.331 MH/s (0) 5: 32.322 MH/s (0) 6: 32.347 MH/s (0)
2019.07.04:22:38:06.236: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:38:06.237: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:38:06.305: eths Eth: Received: {"result":["0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:38:08.627: main Eth speed: 163.187 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:08.627: main GPUs: 1: 24.099 MH/s (0) 2: 21.107 MH/s (0) 3: 21.100 MH/s (0) 4: 32.298 MH/s (0) 5: 32.285 MH/s (0) 6: 32.298 MH/s (0)
2019.07.04:22:38:12.799: GPU5 Eth: GPU5: ETH share found!
2019.07.04:22:38:12.799: eths Eth: Send: {"id":12,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x27c07997cd4fa84e","0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x900de9ec0d755ffeef53f4426ceb3a16f68db31392aa59280e3fb1564ba50680"]}

2019.07.04:22:38:12.799: eths Eth: Share actual difficulty: 9941 MH
2019.07.04:22:38:13.703: main Eth speed: 163.267 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:13.703: main GPUs: 1: 24.105 MH/s (0) 2: 21.107 MH/s (0) 3: 21.100 MH/s (0) 4: 32.331 MH/s (0) 5: 32.323 MH/s (0) 6: 32.299 MH/s (0)
2019.07.04:22:38:15.125: GPU6 Eth: GPU6: ETH share found!
2019.07.04:22:38:15.125: eths Eth: Send: {"id":13,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xb3d34ef9d09f2cbb","0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0xb4d7b98eaa3588989c3b17e7b63aeecb765abff92d2caef9f6988dcd9414552c"]}

2019.07.04:22:38:15.125: eths Eth: Share actual difficulty: 27.7 GH (!)
2019.07.04:22:38:15.732: GPU3 Eth: GPU3: ETH share found!
2019.07.04:22:38:15.732: eths Eth: Send: {"id":14,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xa546692e9895ebb1","0xc7b7c668bcf27aaa1162870eceb82931c281675930e75211f5ed6e1e53700fc8","0x3dd42e97c78ec4c11a176ddbf39660dcddab2ee66e3f7b4a23765454230f4b58"]}

2019.07.04:22:38:15.732: eths Eth: Share actual difficulty: 8058 MH
2019.07.04:22:38:16.250: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:38:16.319: eths Eth: Received: {"result":["0xab3999a589eb8e5147620cea0e7eb3c0e57ed2a58fb3b2bbce80ec833e4391d1","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:38:16.319: eths Eth: New job #ab3999a5 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:38:18.780: main Eth speed: 164.174 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:18.780: main GPUs: 1: 24.893 MH/s (0) 2: 21.107 MH/s (0) 3: 21.100 MH/s (0) 4: 32.338 MH/s (0) 5: 32.354 MH/s (0) 6: 32.380 MH/s (0)
2019.07.04:22:38:20.648: GPU1 Eth: GPU1: ETH share found!
2019.07.04:22:38:20.648: eths Eth: Send: {"id":15,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x662140ff39f8fe13","0xab3999a589eb8e5147620cea0e7eb3c0e57ed2a58fb3b2bbce80ec833e4391d1","0x756865e22017fbfb9d05cafbdf81d00a4f0eb277c4546e6e3cb65b5e9c0a07c6"]}

2019.07.04:22:38:20.648: eths Eth: Share actual difficulty: 29.5 GH (!)
2019.07.04:22:38:21.219: main 
2019.07.04:22:38:21.219: main *** 0:02 *** 7/4 22:38 **************************************
2019.07.04:22:38:21.219: main Eth: Mining ETH on eth-ru2.dwarfpool.com:8008 for 0:02
2019.07.04:22:38:21.219: main 3 GPU(s) are auto-tuning. Hashrate may be low until they are ready.
2019.07.04:22:38:21.219: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.07.04:22:38:21.219: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.07.04:22:38:21.219: main Eth: Maximum difficulty of found share: 29.5 GH (!)
2019.07.04:22:38:21.219: main Eth: Average speed (5 min): 0.000 MH/s
2019.07.04:22:38:21.219: main Eth: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
2019.07.04:22:38:21.219: main 
2019.07.04:22:38:21.770: GPU5 Eth: GPU5: ETH share found!
2019.07.04:22:38:21.770: eths Eth: Send: {"id":16,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x2098e94836d87fd6","0xab3999a589eb8e5147620cea0e7eb3c0e57ed2a58fb3b2bbce80ec833e4391d1","0x09bc09c9ba85155be27db998be135558b374b2e845a4cc80d965ec46320e5fc8"]}

2019.07.04:22:38:21.770: eths Eth: Share actual difficulty: 2108 MH
2019.07.04:22:38:23.857: main Eth speed: 163.671 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:23.857: main GPUs: 1: 24.871 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 32.150 MH/s (0) 5: 32.207 MH/s (0) 6: 32.235 MH/s (0)
2019.07.04:22:38:26.263: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:38:26.263: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:38:26.332: eths Eth: Received: {"result":["0xab3999a589eb8e5147620cea0e7eb3c0e57ed2a58fb3b2bbce80ec833e4391d1","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:38:28.278: main GPU1: 44C 70%, GPU2: 45C 74%, GPU3: 48C 83%, GPU4: 59C 99%, GPU5: 51C 79%, GPU6: 55C 79%
2019.07.04:22:38:28.887: main Eth speed: 162.980 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:28.887: main GPUs: 1: 24.851 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 31.932 MH/s (0) 5: 31.966 MH/s (0) 6: 32.024 MH/s (0)
2019.07.04:22:38:33.964: main Eth speed: 162.170 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:33.964: main GPUs: 1: 24.086 MH/s (0) 2: 21.107 MH/s (0) 3: 21.101 MH/s (0) 4: 31.913 MH/s (0) 5: 31.923 MH/s (0) 6: 32.041 MH/s (0)
2019.07.04:22:38:34.401: GPU6 Eth: GPU6: ETH share found!
2019.07.04:22:38:34.401: eths Eth: Send: {"id":17,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x583a54e52b1933b0","0xab3999a589eb8e5147620cea0e7eb3c0e57ed2a58fb3b2bbce80ec833e4391d1","0x5b1c170246cf5b0c82e73868227c103caa8463a5c5c2a05958e407a517d946d6"]}

2019.07.04:22:38:34.401: eths Eth: Share actual difficulty: 2658 MH
2019.07.04:22:38:36.276: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:38:36.345: eths Eth: Received: {"result":["0x0e83c0034337dcc1dc77bd7d95f41d20d915066125cb506c46775ae6bdcaba0d","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:38:36.345: eths Eth: New job #0e83c003 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:38:38.688: GPU1 Eth: GPU1: ETH share found!
2019.07.04:22:38:38.688: eths Eth: Send: {"id":18,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xf6c1607bc7e4e4f6","0x0e83c0034337dcc1dc77bd7d95f41d20d915066125cb506c46775ae6bdcaba0d","0xce93571f2f3944875d1fbc1bb61fa519d01059118cb1f0856b0c6a617616013c"]}

2019.07.04:22:38:38.688: eths Eth: Share actual difficulty: 2212 MH
2019.07.04:22:38:39.041: main Eth speed: 162.568 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:39.041: main GPUs: 1: 24.499 MH/s (0) 2: 21.118 MH/s (0) 3: 21.127 MH/s (0) 4: 31.918 MH/s (0) 5: 31.923 MH/s (0) 6: 31.983 MH/s (0)
2019.07.04:22:38:44.118: main Eth speed: 162.825 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:44.118: main GPUs: 1: 24.713 MH/s (0) 2: 21.120 MH/s (0) 3: 21.130 MH/s (0) 4: 31.969 MH/s (0) 5: 31.950 MH/s (0) 6: 31.944 MH/s (0)
2019.07.04:22:38:46.290: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:38:46.290: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:38:46.358: eths Eth: Received: {"result":["0x194996fa11165f1f415438e5c7a92083b6217cc1db8070490cae4d17784ed888","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:38:46.358: eths Eth: New job #194996fa from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:38:49.195: main Eth speed: 163.126 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:49.195: main GPUs: 1: 24.747 MH/s (0) 2: 21.125 MH/s (0) 3: 21.141 MH/s (0) 4: 32.072 MH/s (0) 5: 32.081 MH/s (0) 6: 31.959 MH/s (0)
2019.07.04:22:38:53.323: GPU4 Eth: GPU4: ETH share found!
2019.07.04:22:38:53.323: eths Eth: Send: {"id":19,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xcc9cfafee28ad412","0x194996fa11165f1f415438e5c7a92083b6217cc1db8070490cae4d17784ed888","0x3312af40c134b66d9fe95c38cfcfa357554a666f3d078f9d35fe79aa5aa11c38"]}

2019.07.04:22:38:53.323: eths Eth: Share actual difficulty: 6625 MH
2019.07.04:22:38:54.181: GPU6 Eth: GPU6: ETH share found!
2019.07.04:22:38:54.181: eths Eth: Send: {"id":20,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xdd9112180111ee36","0x194996fa11165f1f415438e5c7a92083b6217cc1db8070490cae4d17784ed888","0x7288d11f9e77e5ddfdab8ddb582e4f9717fb76095b7bc11cddbef5f51cba4ccb"]}

2019.07.04:22:38:54.181: eths Eth: Share actual difficulty: 117.4 GH (!)
2019.07.04:22:38:54.273: main Eth speed: 162.867 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:54.273: main GPUs: 1: 24.107 MH/s (0) 2: 21.114 MH/s (0) 3: 21.115 MH/s (0) 4: 32.194 MH/s (0) 5: 32.199 MH/s (0) 6: 32.138 MH/s (0)
2019.07.04:22:38:55.968: GPU4 Eth: GPU4: ETH share found!
2019.07.04:22:38:55.968: eths Eth: Send: {"id":21,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xcc9cfafef1fcac78","0x194996fa11165f1f415438e5c7a92083b6217cc1db8070490cae4d17784ed888","0x3ac00f018690d7ba80b9f8d8c256bb11cf1a23ae50a426db964e44142354cd90"]}

2019.07.04:22:38:55.968: eths Eth: Share actual difficulty: 9981 MH
2019.07.04:22:38:56.303: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:38:56.372: eths Eth: Received: {"result":["0x99076ceb5a0a00509bc29a68c20d33767a56fd3cec88d8ad44d56993d17873f0","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:38:56.372: eths Eth: New job #99076ceb from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:38:56.709: main GPU1: 44C 70%, GPU2: 46C 74%, GPU3: 49C 83%, GPU4: 60C 99%, GPU5: 52C 79%, GPU6: 56C 79%
2019.07.04:22:38:59.349: main Eth speed: 163.181 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:38:59.349: main GPUs: 1: 24.092 MH/s (0) 2: 21.121 MH/s (0) 3: 21.128 MH/s (0) 4: 32.278 MH/s (0) 5: 32.311 MH/s (0) 6: 32.253 MH/s (0)
2019.07.04:22:39:04.426: main Eth speed: 163.426 MH/s, shares: 0/0/0, time: 0:02
2019.07.04:22:39:04.426: main GPUs: 1: 24.090 MH/s (0) 2: 21.114 MH/s (0) 3: 21.116 MH/s (0) 4: 32.373 MH/s (0) 5: 32.385 MH/s (0) 6: 32.348 MH/s (0)
2019.07.04:22:39:06.254: main 
2019.07.04:22:39:06.254: main *** 0:03 *** 7/4 22:39 **************************************
2019.07.04:22:39:06.254: main Eth: Mining ETH on eth-ru2.dwarfpool.com:8008 for 0:03
2019.07.04:22:39:06.254: main 3 GPU(s) are auto-tuning. Hashrate may be low until they are ready.
2019.07.04:22:39:06.254: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.07.04:22:39:06.254: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.07.04:22:39:06.254: main Eth: Maximum difficulty of found share: 117.4 GH (!)
2019.07.04:22:39:06.254: main Eth: Average speed (5 min): 0.000 MH/s
2019.07.04:22:39:06.254: main Eth: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
2019.07.04:22:39:06.254: main 
2019.07.04:22:39:06.316: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:39:06.316: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x9bf5ddf","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:39:06.385: eths Eth: Received: {"result":["0x363dfa8457c0e36fe3614bb31abe71ad0fd2a21c4cd75bd32d393be7bb8bfa5c","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:39:06.385: eths Eth: New job #363dfa84 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:39:09.503: main Eth speed: 163.591 MH/s, shares: 0/0/0, time: 0:03
2019.07.04:22:39:09.503: main GPUs: 1: 24.055 MH/s (0) 2: 21.121 MH/s (0) 3: 21.129 MH/s (0) 4: 32.440 MH/s (0) 5: 32.447 MH/s (0) 6: 32.398 MH/s (0)
2019.07.04:22:39:14.580: main Eth speed: 163.655 MH/s, shares: 0/0/0, time: 0:03
2019.07.04:22:39:14.580: main GPUs: 1: 24.048 MH/s (0) 2: 21.115 MH/s (0) 3: 21.117 MH/s (0) 4: 32.458 MH/s (0) 5: 32.459 MH/s (0) 6: 32.458 MH/s (0)
2019.07.04:22:39:16.329: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:39:16.398: eths Eth: Received: {"result":["0x9a978ba14c0c226ed778ceae109b5278bdaa311ebab76a6d82e3a2386b71f778","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:39:16.398: eths Eth: New job #9a978ba1 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:39:19.657: main Eth speed: 163.699 MH/s, shares: 0/0/0, time: 0:03
2019.07.04:22:39:19.657: main GPUs: 1: 24.077 MH/s (0) 2: 21.121 MH/s (0) 3: 21.129 MH/s (0) 4: 32.457 MH/s (0) 5: 32.458 MH/s (0) 6: 32.457 MH/s (0)
2019.07.04:22:39:24.734: main Eth speed: 163.728 MH/s, shares: 0/0/0, time: 0:03
2019.07.04:22:39:24.734: main GPUs: 1: 24.131 MH/s (0) 2: 21.114 MH/s (0) 3: 21.115 MH/s (0) 4: 32.455 MH/s (0) 5: 32.456 MH/s (0) 6: 32.456 MH/s (0)
2019.07.04:22:39:24.821: GPU2 Eth: GPU2: ETH share found!
2019.07.04:22:39:24.822: eths Eth: Send: {"id":22,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x24e0d2dd28814d16","0x9a978ba14c0c226ed778ceae109b5278bdaa311ebab76a6d82e3a2386b71f778","0xa35e87f8c57e672d18971bb271f6365ae5a65e9449e79c5cefde400574479fae"]}

2019.07.04:22:39:24.822: eths Eth: Share actual difficulty: 5745 MH
2019.07.04:22:39:25.140: main GPU1: 45C 70%, GPU2: 47C 74%, GPU3: 50C 83%, GPU4: 61C 99%, GPU5: 52C 79%, GPU6: 56C 79%
2019.07.04:22:39:26.343: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:39:26.343: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x3126ad489f49ce1c2894814a847acadaa125117dca55d57412f66b06b477c317"]}

2019.07.04:22:39:26.411: eths Eth: Received: {"result":["0x0bd780b02ec18c95ef069da38ded07892e10974ae27680b76b485a9ebdcf7647","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:39:26.412: eths Eth: New job #0bd780b0 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:39:29.779: main Eth speed: 163.720 MH/s, shares: 0/0/0, time: 0:03
2019.07.04:22:39:29.779: main GPUs: 1: 24.113 MH/s (0) 2: 21.114 MH/s (0) 3: 21.128 MH/s (0) 4: 32.455 MH/s (0) 5: 32.454 MH/s (0) 6: 32.455 MH/s (0)
2019.07.04:22:39:34.856: main Eth speed: 163.659 MH/s, shares: 0/0/0, time: 0:03
2019.07.04:22:39:34.856: main GPUs: 1: 24.067 MH/s (0) 2: 21.107 MH/s (0) 3: 21.116 MH/s (0) 4: 32.456 MH/s (0) 5: 32.456 MH/s (0) 6: 32.458 MH/s (0)
2019.07.04:22:39:36.356: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.07.04:22:39:36.425: eths Eth: Received: {"result":["0x83931594e52f70cf21eebf12ca1d4729168ae9ecf5893d85f50bacf8befb07f1","0x955f33cf01218e21b8282ab6c8953e4e753331201bb84de43f8fe89e053f9cef","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
2019.07.04:22:39:36.425: eths Eth: New job #83931594 from eth-ru2.dwarfpool.com:8008; diff: 2000MH
2019.07.04:22:39:39.933: main Eth speed: 163.658 MH/s, shares: 0/0/0, time: 0:03
2019.07.04:22:39:39.933: main GPUs: 1: 24.058 MH/s (0) 2: 21.107 MH/s (0) 3: 21.123 MH/s (0) 4: 32.456 MH/s (0) 5: 32.457 MH/s (0) 6: 32.457 MH/s (0)
2019.07.04:22:39:43.811: unkn Quitting...
2019.07.04:22:39:44.087: GPU1 Eth: GPU1: ETH share found!
2019.07.04:22:39:44.088: eths Eth: Send: {"id":23,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xd4de3df99f36d4d2","0x83931594e52f70cf21eebf12ca1d4729168ae9ecf5893d85f50bacf8befb07f1","0x46366b84c613028aba354256c94239ba9c388fa7224b95cd2de1a91c038aaa87"]}

2019.07.04:22:39:44.088: eths Eth: Share actual difficulty: 2288 MH

finds balls at start but does not count
Pages: « 1 ... 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 [173] 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 ... 457 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!