hey guys. i flashed a rom over my xfx rx580 gts xxx 8gb samsung cards. now 3/6 are running at 30MH/s and the other 3 at 22.33. one of the slow 3s started at 30, too, but jumped back to 22.33 after a while. NEED HELP!!!

All I can find is average block times, but I need to see the actual ones. Does anybody know where I can get this data? Thank you.

This is just a quick guide for how to flash you RX470/RX480 cards. I hope it helps.

Download these.
https://www.techpowerup.com/downloads/2728/atiflash-2-74
https://github.com/caa82437/PolarisBiosEditor
https://www.techpowerup.com/gpuz/

If you want a custom rom (Higher hash, lower power), you can contact Heliox
For example: RX 480 8G Samsung: 32+Mh ETH, RX 470 4G Hynix: 31+Mh ETH

Use GPU-Z to see what kind of memory your card has

1, open atiflash, MUST RUN AS ADMINISTRATOR
2, click on save to save the original bios, save it as RX470ogBIOS.ROM or RX480ogBIOS.ROM (for convenience)
3, open polaris bios editor
4, click open at the top left and open the OG bios you just saved
5, edit the timings according to your cards memory
6, click save, save it as RX470modBIOS.ROM or RX480modBIOS.ROM
7, open atiflash again, MUST RUN AS ADMINISTRATOR
8, at the top select the card you want to flash
9, click load image at the bottom left
10, search for the modded bios you just saved and open it
11, click program
12...wait a minute to finish, when its done it'll say to restart...if you're done click yes, if you have more cards to flash click no and repeat steps 8-12 until you're done.

Also, when selecting cards to flash, it will only show 3 cards, so if you want to flash more than 3 cards, only have 3 cards connected to the motherboard at a time, flash the cards, restart, make sure it worked, shutdown, switch cards and repeat. And then make sure you have the right driver installed.

This is what works for me. I hope it works for you too.

https://miningchamp.com/gpus/56/MSI-GTX-970-hashrate

Hi. Been running ethOS for a little bit now. Kinda like it (coming from Windows mining and self-configured Linux mining) it's nice that ethOS is simple to get up and running! However, I have a number of questions that I just can't seem to find answers to.

Specs: ASRock H110 BTC, PowerColor Red Devil Golden Sample 8GB, ethOS 1.2.9.

Maybe @kotarius from this thread: https://forum.ethereum.org/discussion/4298/ethos-linux-ethereum-mining-platform/p1 could shed some light.

- How do we see rejected shares?
- It appears that Claymore miner will show this, but using the default ethminer, how do we see them?

- How do we see Watts on our dashboard?
- i've seen some dashboards that show it. so is it the cards in use? some setting that was missed?



- Minestop / minestart doesn’t work. Sends the cards into limp mode (300mv) and they won't start mining again
- Not sure if, again, it's the cards in use, or if there is something bigger that is wrong. I am using 'minestop && sleep 5 && r' to get the rig back up and running.

- Undervolting RX580s, doesn’t have an effect
- I haven't done a voltage mod in the BIOS, but according to the changelog, setting the vlt parameter in the local.conf will impact the voltage on the card. It doesn't appear that way. The 'show stats' will report it as the same value we set in the local.conf, but the watts at the wall are not any different (and in some cases, higher!)

- Where is the ethminer binary?
- This is connected to my next question as well. But I am trying to find the ethminer binary on the filesystem. I thought my Linux skillz were good enough, but alas, i can't find it!

- How to update to the latest miner? It's stuck on 0.13.0rc1
- Is the miner.version file a list of the current version of the installed miners? Or is it where the version to update to is specified? ie: do I edit that file to reference 0.13.0 and then run update-miners?

Thanks for any help / insight!

https://miningchamp.com/calculator

Changes in version 3.1 a (starting with 3.0 c):
* Reduced amount of rejected shares.
* Fix a reconnection issue in the network layer.
* Show additional statistics in console.
* Improve reconnection in cases where servers
become reachable but respond with malformed data.
* Improved speed by 3-7%, depends on GPU model.
* Fixed issue with possible GPU crash during miner shutdown.
* Reduced mining fee
Lots of small fixes and changes

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 has a developer fee of 0.35% (the lowest in the industry). This means that every 120
minutes the miner will mine for us, its developers, for 20 seconds.

The speed is generally faster than Claymore's Ethereum miner in eth only mode
(we have measured about 1.2-1.7% 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 with the notable exception of the dual mining feature (yet).

Please note that PhoenixMiner is extensively tested on many mining rigs but this is the
first public release and 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

1. Quick start

You can download PhoenixMiner 3.1a from here:

https://mega.nz/#!6Vl3xaRa!EpYC92eRKD2gCZpvSH1GSAvrBsjr-61E7EVGcFfN_7g Download PhoenixMiner (MEGA)
If you want to check the integrity of the downloaded file, please use the following hashes:

Code:
File: PhoenixMiner_3.1a.zip
CRC32: B338AE2A
MD5: 6BDF4994DD28FB2BCEC68B7E779F74DC
SHA-1: 6FF9592E3F694EB0B3958A4B3D5B05C63210F319


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 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
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
ubiqpool (UBIQ):
PhoenixMiner.exe -pool stratum+tcp://eu.ubiqpool.io:8008 -wal YourUbiqWalletAddress -pass x -worker WorkerName
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

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 10x0 and 9x0 series as well as older cards with enough VRAM
* Highly optimized OpenCL and CUDA cores for maximum ethash mining speed
* Lowest developer fee of 0.35% (20 seconds defvee mining per each 120 minutes)
* Advanced statistics: actual difficulty of each share as well as effective hashrate at the pool
* 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)
* 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, and Metaverse ETP. 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.
* More features coming soon!

PhoenixMiner requires Windows x64 (Windows 7, Windows 10, etc.). We are planning a Linux version in
the future but it may take some time.

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 Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining)
-wal Ethash wallet (some pools require appending of user name and/or worker)
-pass Ethash password (most pools don't require it, use 'x' as password if unsure)
-worker Ethash worker name (most pools accept it as part of wallet)
-proto 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)
-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
-stales Submit stales to ethash pool: 1 - yes (default), 0 - no
-pool2 Failover ethash pool address. Same as -pool but for the failover pool
-wal2 Failover ethash wallet (if missing -wal will be used for the failover pool too)
-pass2 Failover ethash password (if missing -pass will be used for the failover pool too)
-worker2 Failover ethash worker name (if missing -worker will be used for the failover pool too)
-proto2 Failover ethash stratum protocol (if missing -proto will be used for the failover pool too)
-coin2 Failover devfee Ethash coin (if missing -coin will be used for the failover pool too)
-stales2 Submit stales to the failover pool: 1 - yes (default), 0 - no
General pool options:
-fret Switch to next pool afer N failed connection attempts (default: 3)
-ftimeout Reconnect if no new ethash job is receved for n seconds (default: 600)
-ptimeout 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 Seconds to wait before reconnecting (default: 20)
-gwtime Recheck period for Solo/GetWork mining (default: 200 ms)
-rate Report hashrate to the pool: 1 - yes, 0 - no (1 is the default)
Benchmark mode:
-bench [],-benchmark [] Benchmark mode, optionally specify DAG epoch. Use this to test your rig.
Remote control options:
-cdm 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 Set the CDM remote monitoring port (default is 3333). You can also specify
if you have a secure VPN connection and want to bind the CDM port to it
-cdmpass 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, -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 Set the mining intensity (0 to 14; 12 is the default for the new kernels). You may specify this option per-GPU.
-gt 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
-clKernel Type of OpenCL kernel: 0 - generic, 1 - optimized, 2 - alternative (1 is the default)
-clNew Use the new AMD kernels (0: no, 1: yes; default: 1)
-clf AMD kernel sync (0: never, 1: periodic; 2: always; default: 1)
-nvNew Use new Nvidia kernels if supported (0: no, 1: yes; default: 1)
-nvf Nvidia kernel sync (0: never, 1: periodic; 2: always; 3: forced; default: 1). You may specify this option per-GPU.
-list List the detected GPUs devices and exit
-minRigSpeed Restart the miner if avg 5 min speed is below MH/s
-eres 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 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 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 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
-wdog 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)
-rmode 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 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 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 Set a path where the logfile(s) will be created
-logsmaxsize 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 Restart miner according to -rmode after n minutes
-gswin GPU stats time window (5-30 sec; default: 15; use 0 to revert to pre-2.8 way of showing momentary stats)
-gsi 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
-gpow Lower the GPU usage to n% of maximum (default: 100). If you already use -mi 0 (or other low value) use -li instead
-li 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
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 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 Set fan control min speed in % (-1 for default)
-fanmax Set fan control max speed in % (-1 for default)
-tmax Set fan control max temperature (0 for default)
-powlim Set GPU power limit in % (from -75 to 75, 0 for default)
-cclock Set GPU core clock in MHz (0 for default)
-cvddc Set GPU core voltage in mV (0 for default)
-mclock Set GPU memory clock in MHz (0 for default)
-mvddc Set GPU memory voltage in mV (0 for default)
-tstop Pause a GPU when temp is >= n deg C (0 for default; i.e. off)
-tstart Resume a GPU when temp is <= n deg C (0 for default; i.e. off)
General Options:
-v,--version Show the version 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.)
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).

The advantages of using config.txt and epools.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:
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 newest drivers from AMD: 18.1.1 or 18.2.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: PhonixMiner 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 16 GB. If this doesn't help, start PhoenixMiner by running the start_miner.bat that is in the
miner's folder. You MUST change the wallet address that is specified in start_miner.bat to make
sure that the miner mines to your address. Also, make sure that all lines, starting with setx are
not commented (i.e. they doesn't start with REM command).

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 170 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.

official link :https://bitcointalk.org/index.php?topic=4610435.0

I've been thinking about expanding my mini farm to include some P102-100 cards. They seem to be one of the fastest cards on the market right now (aside from modded 1080Ti).

50MH/s mining ETH at around 180-200W is solid performance. My only concern is that the card uses 2 x 8-pin ATX connector, which would place additional requirement on my PSU set-up.

A preview of P102-100 card: https://www.bitnand.com/nvidia-p102-100-gpu-mining-preview

I am mining ETH as of last night, using the following guide: https://forum.ethereum.org/discussion/5592/how-to-mine-get-started-fast-and-easy-for-windows-7-detailed-guide


I have installed the Ethereum wallet, synced the blockchain, and I'm running Geth.

The miner appears to be working fine:

https://s10.postimg.org/k22s46se1/eth.jpg


I ran it all night, but when I checked this morning I couldn't find any stats at Nanopool. My ETH address was also empty.
So I tried Dwarfpool, but when I check my worker it returns a blank page Huh
http://dwarfpool.com/eth/address?wallet=0x0b77f98ba29cd46520ae83f534b10aef82cc9cde

What am I doing wrong?

Do I need to install eth-proxy?

Only thing im doing diffrent is not using catalyst 15.12, I'm using 16.8x

Call me an idiot... But I cannot find the download link for 15.12 anywhere on this page?

http://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-Software-Crimson-Edition-15.12.aspx

Thanks in advance.

Hello, recently I've been having some issues with Claymore Crashing. Here's what the problem is
"WATCHDOG: GPU 0 hangs in OpenCL call, exit
08:32:42:037 1adc watchdog - thread 1, hb time 76254
08:32:42:037 1adc WATCHDOG: GPU 0 hangs in OpenCL call, exit
08:32:42:037 1adc watchdog - thread 2, hb time 125
08:32:42:038 1adc watchdog - thread 3, hb time 328
08:32:42:038 1adc watchdog - thread 4, hb time 16
08:32:42:038 1adc watchdog - thread 5, hb time 219
08:32:42:038 1adc watchdog - thread 6, hb time 76222
08:32:42:039 1adc WATCHDOG: GPU 3 hangs in OpenCL call, exit
08:32:42:039 1adc watchdog - thread 7, hb time 76020
08:32:42:039 1adc WATCHDOG: GPU 3 hangs in OpenCL call, exit
08:32:42:039 1adc watchdog - thread 8, hb time 156
08:32:42:040 1adc watchdog - thread 9, hb time 63
08:32:43:100 1adc Restarting OK, exit..."

Whenever this happens, the whole computer freezes (Not using the computer for anything else) It is interesting to note, though, how GPU 4 doesn't hang like the others.

What might be causing this, it wasn't running for very long when it did this. Yesterday it ran for 24 hours and 2 minutes, then did the same thing.

Hi,
I got this error (see picture).


Everything was ok before with the ethereum pool.
I am not a pro.
I need your help please!
Excuse my english.
Annie

I just managed to get primecoin cloud mining up and running through digitalocean.com, following these instructions: http://www.cryptocoinsnews.com/2013/12/04/primecoin-cloud-mining-using-digital-ocean-complete-guide/

(With one addition, "make" was not installed, but that was resolved by adding the line "apt-get update && apt-get install make”)

In any case, what are the developers' thoughts on doing ether mining in the same way?

If there's not going to be anything other than CPU mining, it may be a good bet, no?

Hi,
I got this error (see picture).


Everything was ok before with the ethereum pool.
I am not a pro.
I need your help please!
Excuse my english.
Annie

It's here! PiMP 1.9 and 2.0 are released.

Announce video: https://getpimp.org/video-brand-new-pimp-software-to-mine-cryptocurrency/




Quick Start
Comes as a pre-built image so you don't have to install drivers and programs yourself.
Default configs and miners are provided so you can mine out of the box.
Simple commands can change all your workers, wallets, and pools in config files.
You also get a GUI desktop for easy local operation of the rig.

Easy to use
Manage your miners with easy commands: stop/start, switch, edit, del, and status
Customized PiMP editor provides syntax highlighting and integrated syntax checking for easy config edits.
Remote VNC/RDP is preinstalled to make it even easier for Windows miners to upgrade to PiMP.
While tweaking and tuning, use the test commands and attach to screen of miners to get a closer look.
integration with miner.farm makes easy online web monitoring a snap and problems easy to see.
You get simple backup tools that save a copy of your confs and miner builds for later.
Control all GPU, CPU, and ASIC miners from the same interface

Real support
GPU types and counts are shown at the login screen for instant troubleshooting information.
You have a team of developers, miners, testers, and other community members available in chat to help you use the software 24/7.
Built in diagnostic tools provide the critical information you can share, so you can get help faster.

State of the art
You have support for nearly all open-source and binary miner software out of the box.
All data communications to miner.farm are SSL/TLS encrypted for your security.
Use a platform built fresh on a modern distro release, all new from the ground up.
Volume license and mass deployment commands and tools are included for multi-rig setups.
Enjoy support for the latest AMD GPUs with custom tools to manipulate the settings.
Have a professional look so you can impress your friends or your clients.
Secure coding done is by professional, experienced developers and sysadmins.
Check stats at a glance with USB LCD backpack display support.

Hello people,

I'm just starting my research into my future first mining rig (I'm planning on using ethminer through nanopool btw). I have done a ton of research and have done some tests myself, and it seems that all of the 470/480/570/580 cards are taken up and sell at least for $500 USD. However, I did a lot of searching on Ebay and my local Craigslist and I found some sweet deals.

There are many auctions on used MSI Twin Frozr R9 270x used 2 GB cards with the highest bids currently going for around $60-$80 USD. This seems like a good deal when compared to a brand new RX 550/560, but I'm afraid that 2 GB cards are simply no longer profitable anymore, since there are way more people using 4 GB or 8 GB cards now. Currently, all of the cards going on for auction have not been used for mining of any sort. If 270x cards are still profitable (I checked Ethereum calculator and here are the results:
)

There are also some 280x 3 GB cards on auction with the highest bids being ~$120 USD. I checked the description for each of them and it seems that none of them have been used for any mining, only gaming. There was also another one that is on sale on my local Craigslist (specifically a Gigabyte Windforce) 280x 3 GB for $160, and if the 280x is more profitable than the 270x in the long term, I might consider buying it for asking price.

It's likely that I'm probably going to have a mix of 270x/280x cards, since 290x cards are going upwards of $230 on Ebay, and considering that the 280x cards are selling for ~$100 less, the extra profit isn't going to matter.

But I hope that at the very least 270x/280x cards will be able to hold up for the next 3 years or so.

Selling Brand New Antminers, We ship worldwide and delivery takes 3 days.
A brand-new, unused, unopened, undamaged Antminers

Baikal Giant X10 Power Supply------$1,200
Antminer E3, Batch 3---------------$1,100
Antminer Z9------------------------$2,700
Antminer Z9 mini-------------------$1,700
Antminer S9i-13.5TH/s with PSU-----$850

Interested buyer should contact me at :

Email : ramonvidic1@gmail.com

WhatsApp : +1 929 266 7402

Skype : zahil.export2

What is the recommended best proxy to use ? I have seen "sammy's" and "Dwarfpools" proxy servers, and a few others. Is there anything that is newer/updated? Most of them are from 2016, which is fine if there is no need for improvement I guess.. any suggestions appreciated.

Has anyone had a chance to test out the RX 580's yet, either 4GB or 8GB? If so, what hash-rate are you getting? I'm debating getting the 580's because where I live, they are cheaper than the Sapphire Nitro RX 480's.

Thanks

Now that the RX 470 is out is it to be preferred over the RX 480. Comparison metrics are hash rate, power consumption, purchase cost, driver stability and availability.