Is there serious only sexy pool to mine to.  All the other either have no user or no instructions to port to them!!??

Anyone else LOST all their mining time on http://dbix.mole-pool.net:86/

No trace of me mining on there after finding about 15000 shares.

This is gonna sound strange but I think my mining address might have been changed to 0x39417a34fb9e7ab9fee61a12802020887ecebb55 during mining.

Anyway not sure if this has anything to do with it but now I try to start up the same miner with MY address it gives and error on start up of msvcp140.dll not found and also vcruntime140 not found.

Anyone know what this file is or does as it's strange it the miner doesn't fire up now!

Not happy.

Same problem today. I am suspecting one card is causing the problem but not sure yet.  Hopefully someone works this out.


--cuda-block-size 128 --cuda-grid-size 8192 less than
--cuda-block-size 64 --cuda-grid-size 16384
64 and 16384 best so far defailt --cuda-parallel-hash <1 2 ..8> *[4]

  i  08:00:45|main  Solution found; Submitting to 127.0.0.1:8080 ...
  i  08:00:48|main    Nonce: 26f776b0fe1d452d
  i  08:00:48|main  B-) Submitted and accepted.
CUDA error in func 'ethash_cuda_miner::search' at line 346 : unknown error.
  X  08:01:06|cudaminer0  Error CUDA mining: unknown errorCUDA error in func 'ethash_cuda_miner::search' at line 346 : unknown error.
CUDA error in func 'ethash_cuda_miner::search' at line 346 : unknown error.
CUDA error in func 'ethash_cuda_miner::search' at line 346 : unknown error.
CUDA error in func 'ethash_cuda_miner::search' at line 346 : unknown error.

Anyone else have the above problem or know if this is being addressed.

It's causing my set up to become highly unstable!

Currently just mining etherium and this happens on all recent releases of CUDA miners

Running win 10 4gb DDR4 ram and Pentium G440 3.3 ghz 6xGTX 1060's

I was told expensive cpu wasn't important for mining but now I'm questioning this!

Anyone any idea as to why this might have happened?

m  16:23:00|main  Mining on PoWhash #ba883931 : 115.34MH/s [A0+0:R0+0:F0]
CUDA error in func 'ethash_cuda_miner::search' at line 355 : unknown error.
CUDA error in func 'ethash_cuda_miner::search' at line 355 : unknown error.
CUDA error in func 'ethash_cuda_miner::search' at line 355 : unknown error.
CUDA error in func 'ethash_cuda_miner::search' at line 355 : unknown error.
CUDA error in func 'ethash_cuda_miner::search' at line 355 : unknown error.
CUDA error in func 'ethash_cuda_miner::search' at line 355 : unknown error.
  X  16:23:01|cudaminer3  Error CUDA mining: unknown error
  m  16:23:02|main  Mining on PoWhash #ba883931 : 24.09MH/s [A0+0:R0+0:F0]
  X  16:23:03|cudaminer0  Error CUDA mining: unknown error
  X  16:23:03|cudaminer5  Error CUDA mining: unknown error
  X  16:23:03|cudaminer2  Error CUDA mining: unknown error
  m  16:23:04|main  Mining on PoWhash #ba883931 : 0.00MH/s [A0+0:R0+0:F0]
  X  16:23:05|cudaminer4  Error CUDA mining: unknown error
  X  16:23:05|cudaminer1  Error CUDA mining: unknown error

Hey Rob

I just went to your pool but nothing comes up on the site apart from one line of text!

Correct me if I'm wrong but according to my calculations current average mining payout per day going by block discovery frequency should be:

Current block average discovery time = 80secs

8640 (seconds in a day) / 80 secs = 1080 blocks per day

1080 blocks x 6 = 6480 coins

Network hashrate = 1,000,000 MH's / (rig hash rate) lets use 100MH's for example

So 6480 coins going to 1,000,000 MH's over a day = 0.00648 coins per day

So multiply 0.00648 by your rig hashrate and you get an accurate average of what you should be earning

eg 0.00648 x 100mh = 0.648 (not bad huh)!

Quick question on using stratum setting on miner.

What is difference between entering (or not) the stratum+tcp://dbix.krokipool.pro:5005 part before an address v's the -S command before the address?  

Also has anyone been using (or do we need to use) the -SP, --stratum-protocol command which chooses which stratum protocol to use:

        0: official stratum spec: ethpool, ethermine, coinotron, mph, nanopool (default)
        1: eth-proxy compatible: dwarfpool, f2pool, nanopool
        2: EthereumStratum/1.0.0: nicehash

What is the effect of not changing it say if mining with nanopool with is SP1?

Note sure what's going on at http://213.154.202.174:5550/ DubaiCoin(dbix) POOL but i'm certainly not gonna use it again.

Found a block while only 3 other miners were going online with a pool total of 1140 mh/h I was hashing at about 10% of the pool and get this I got a paultry 0.3 Dbix for finding a block!  Hmmm they can put that 0.3 Dbix where the sun don't shine!

Does anyone know why livecoin exchange has restricted the deposit ability of Dbix?

How are we supposed to trade the coin now?

Regarding the wallet http parse error in the log from what I can see it doesn't seem to affect anything from working.

Few things to consider though as my account disappeared from it a few times:

- After the wallet has synced with the block chain be sure to select the account (which on my pc you have to hover below it and select the line as though you were copying text) 

- Then select export gbix account to directory and save that file somewhere safe as a backup (preferable not on the computer).

- After say five mins or so check you wallet address entered the blockchain by going to http://dbixscan.io/home and entering you address in the search bar.  If you see your wallet address there you're good to go.

So I got a question regarding solo mining.  Once my wallet is synched with the blockchain do I need to include my wallet address in the miner file or not as I think -O MY_ADDRESS is causing a parse error!?

The miner is working and going through the block but I don't know how the chain passes the address if I manage to find a block.  Thanks!