are you using the last binary? its size is 1028203 bytes with creation date 2014-01-08.
Looks the same, SHA-256 for bfgminer.exe is 362C886B7E097C4F11B72F459BDD4B73E3D1CD8F6AE50FAAD1476B6ED6695B76
if you solo mine, it is correct to see very few sent blocks (because the miner discover by itself if a solution is valid or not).
It is about miner finding hash that is bellow target (for example 900/799) but no block is generated. At the same time no block is
added to blockchain by other miners. 30 seconds or more can pass till the next block on network. In other words, hash that should
get me some MED do nothing instead. It happens occassionaly with both CG and BFG miners. On screenshot bellow check accepted
hash at 20:56:15. It did nothing, compare it's time with time of transactions in MED wallet. It was not block mined then orphaned.
... and one more happened few seconds ago, while I was posting screenshot. In the end, it's like I'm mining with 3 USB Erupters!
We are giving a look at the log of some nodes;
assuming that all the clocks are synced, we see:
...
received: block (189 bytes)
received block fdd515c3ef1f7f1279df9ae5410068cd3c23736f24372d6913daa0d9225d25ed
Committing 2 changed transactions to coin database...
SetBestChain: new best=fdd515c3ef1f7f1279df9ae5410068cd3c23736f24372d6913daa0d9225d25ed height=12071 log2_work=54.651201 tx=12163 date=2014-01-08 20:54:41 progress=0.999947
ProcessBlock: ACCEPTED
...
...
received block a984c4638c5db9f32d9e2c7e0b61c90840a1a8f4f4b963f73078f331feee844e
Committing 1 changed transactions to coin database...
SetBestChain: new best=a984c4638c5db9f32d9e2c7e0b61c90840a1a8f4f4b963f73078f331feee844e height=12072 log2_work=54.651376 tx=12164 date=2014-01-08 20:55:12 progress=0.999989
ProcessBlock: ACCEPTED
...
...
received block 627d1cbb0f1561c0794ac47d27db7a804243babf56c28457afdb8686e5caa2b4
Committing 2 changed transactions to coin database...
SetBestChain: new best=627d1cbb0f1561c0794ac47d27db7a804243babf56c28457afdb8686e5caa2b4 height=12073 log2_work=54.651551 tx=12165 date=2014-01-08 20:57:42 progress=0.999989
ProcessBlock: ACCEPTED
...
there is no orphaned block in the log; also the other nodes of which we can access the logs show exactly the same accept times.
if possible, would it be possible for you to show the mcproxy log output of when the miner posted that accepted block (that in the end was not accepted)? And also the debug.log file of the wallet?
It would really help to understand the issue. If the file debug.log is not present in the wallet directory, then you should relaunch the wallet with -debug and -debugnet options.
We have now setup a machine similar to yours (with five usb block erupters) with full debug log in order to see some lost blocks.
edit:
it seems that we got one case where the miner got an accepted block but it was not accredited as new block ,so we have the logs to study.... will follow up later.
