WHERE is POOLS?? HOW can i MINE it?? 

Im not sure about usb risers but those powered ribbon extensions connect +12V directly to mb and straight to primary psu. So thats the connection shorting two psu-s and if voltages differ there's unwanted current that does nothing but stress mb and riser and atx connection. Have some risers burned but after connecting all to primary no more problems.

I've also ran rig from 3 lo-end psu-s and this way connecting all works fine.

did ya a little favor.

Lisk Forging Profit sharing sites/delegates so far...  Possibly more but I just copied the easy picking ones I could find.


http://getlisk.com
http://lisker.io
http://www.lisknode.com.ar/
http://liskit.me
https://forum.lisk.io/viewtopic.php?f=6&t=157
https://forum.lisk.io/viewtopic.php?f=6&t=223

please show your support and vote for these nodes if you want automatic forged lisk sent to your wallet address automatically in most cases.

What's going on ETH pool? Stats delay for a few hours, and now all my unconfirmed balance and shares from last 8 hours have disappeared.

Im trying to specify settings for proxy and i have an error.

https://snag.gy/mBe0QP.jpg

Proxy config


###
# Examples of command line for miners:
#
#   ethminer.exe --farm-recheck 200 -G -F http://HOST:PORT/
#   ethminer.exe --farm-recheck 300 -G -F http://HOST:PORT/rig1
#
#   ethminer.exe -G -F http://127.0.0.1:8080/
#   ethminer.exe --farm-recheck 100 -G -F http://192.168.0.33:8080/rig1
#
#  farm-recheck parameter is very individual. Just test different values.
#
#  You can submit shares without workername or
#  You can provide workername:
#   - with url like "/rig1"
#   - or use automatically numbering(integer) based on IP of miner
#
#  Servers:
#    EU-Server:  eth-eu.dwarfpool.com  (France)
#    US-Server:  eth-us.dwarfpool.com  (EastCoast: Montreal,Canada)
#    US-Server:  eth-us2.dwarfpool.com (WestCoast: Las Vegas)
#    RU-Server:  eth-ru.dwarfpool.com  (Moscow)
#    CN-Server:  eth-cn.dwarfpool.com  (Shanghai)
#    SG-Server:  eth-sg.dwarfpool.com  (Singapore)
#    AU-Server:  eth-au.dwarfpool.com  (Melbourne)
#    ASIA-Server:  eth-asia.dwarfpool.com  (Taiwan)
#
###

# Select Ethereum ETH or Expanse EXP
COIN = "ETH"

# Host and port for your workers
HOST = "127.0.0.1"
PORT = 8085

# Coin address where money goes
WALLET = "0xa0f5578094e713c58b901ec43fb58bbbd7a63372"

# To donate please use wallet "0xea7263feb7d8a8ab0a11eedd8f1ce04412ab0820"

# It's useful for individually monitoring and statistic
ENABLE_WORKER_ID = True

# On DwarfPool you have option to monitor your workers via email.
# If WORKER_ID is enabled, you can monitor every worker/rig separately.
MONITORING = True
MONITORING_EMAIL = "keugere@gmail.com"

# Main pool
POOL_HOST = "eth-ru.dwarfpool.com"
POOL_PORT = 8008

# Failover pool
POOL_FAILOVER_ENABLE = True

POOL_HOST_FAILOVER1 = "eth-eu.dwarfpool.com"
POOL_PORT_FAILOVER1 = 8008

POOL_HOST_FAILOVER3 = "eth-asia.dwarfpool.com"
POOL_PORT_FAILOVER3 = 8008

POOL_HOST_FAILOVER2 = "eth-us.dwarfpool.com"
POOL_PORT_FAILOVER2 = 8008

POOL_HOST_FAILOVER2 = "eth-us2.dwarfpool.com"
POOL_PORT_FAILOVER2 = 8008


# Logging
LOG_TO_FILE = True

# Enable debug
DEBUG = False




Miner config


setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool http://127.0.0.1:8085 -ewal 0xA0F5578094e713c58B901eC43FB58bbbD7A63372 -epsw x -eworker dw1



What is wrong?

thanks
calculate reward for every voter daily and automatically on teswnet. payout will be activated if the reward balance is greater than or equal 1 LISK
details please visit lisker.io

Anyone else noticing some sort of memory or power leak with this?

I'm mining on Win10 with a 370 and 390 in ETH only mode. When I start mining I draw about 470 watts at the wall but over the hours this keeps increasing. I checked my rig today after about 18 hours and it was pulling 570 watts! I restarted the miner and it instantly dropped back to 470 watts. My CPU and system memory were normal during this so the problem doesn't seem to be there.