Topic: "Share is above target" messages when mining cutting half of hashing power? (Read 6843 times)

Alright but you guy should try the 'services' section because that's not so easy to fix that here.

I am encountering the same issue with wemineltc and cgminer

1:03] Share above target
 [2013-12-24 11:01:08] (5s):6.258K (avg):7.497Kh/s | A:0  R:0  HW:11
 [2013-12-24 11:01:12] Work update message received
 [2013-12-24 11:01:13] (5s):6.258K (avg):7.494Kh/s | A:0  R:0  HW:11
 [2013-12-24 11:01:18] (5s):6.259K (avg):7.492Kh/s | A:0  R:0  HW:11
 [2013-12-24 11:01:21] Share above target
 [2013-12-24 11:01:22] Share above target
 [2013-12-24 11:01:22] Share above target
 [2013-12-24 11:01:23] (5s):6.259K (avg):7.490Kh/s | A:0  R:0  HW:11
 [2013-12-24 11:01:27] Share above target
 [2013-12-24 11:01:28] (5s):6.249K (avg):7.487Kh/s | A:0  R:0  HW:11  WU:6.1/m
 [2013-12-24 11:01:33] (5s):6.246K (avg):7.485Kh/s | A:0  R:0  HW:11  WU:6.1/m

I'm getting a lot of "Share above target" messages when I put cgminer in verbose mode. My hardward ghs as reported in cgminer is right, but in the pools it always gives me a lot less credit, like half. Here's a log:


 cgminer version 3.8.1 - Started: [2013-11-14 03:31:56]
--------------------------------------------------------------------------------
 (5s):25.56G (avg):25.37Gh/s | A:512  R:0  HW:2  WU:197.7/m
 ST: 2  SS: 0  NB: 1  LW: 1080  GF: 0  RF: 0
 Connected to nl1.ghash.io diff 512 with stratum as user me.worker1
 Block: 58afacd9...  Diff:511M  Started: [03:31:55]  Best share: 719
--------------------------------------------------------------------------------
 BAL 0:  max 56C 3.26V | 25.49G/25.37Gh/s | A:512 R:0 HW:2 WU:197.7/m
--------------------------------------------------------------------------------

 [2013-11-14 03:34:44] Share above target
 [2013-11-14 03:34:44] Share above target
 [2013-11-14 03:34:44] Share above target
 [2013-11-14 03:34:44] (5s):25.32G (avg):25.35Gh/s | A:512  R:0  HW:2  WU:198.2/m
 [2013-11-14 03:34:45] Share above target
 [2013-11-14 03:34:45] Share above target
 [2013-11-14 03:34:45] Share above target
 [2013-11-14 03:34:46] Share above target
 [2013-11-14 03:34:47] Share above target
 [2013-11-14 03:34:48] Share above target
 [2013-11-14 03:34:48] Share above target
 [2013-11-14 03:34:48] Share above target
 [2013-11-14 03:34:49] Share above target
 [2013-11-14 03:34:49] Share above target
 [2013-11-14 03:34:49] Share above target
 [2013-11-14 03:34:49] Share above target
 [2013-11-14 03:34:49] Share above target
 [2013-11-14 03:34:49] Share above target
 [2013-11-14 03:34:49] Share above target
 [2013-11-14 03:34:49] Share above target
 [2013-11-14 03:34:50] (5s):25.56G (avg):25.37Gh/s | A:512  R:0  HW:2  WU:197.7/m

-----

Here are some ways I've tried invoking it:

rem causes "Share is above target" messages
rem cgminer -o stratum+tcp://mint.bitminter.com:3333 -u me.1 -p 1 --bflsc-overheat 90

rem also causes "Share is above target" messages
rem cgminer -o http://mint.bitminter.com:8332 -u me.1 -p 1 --bflsc-overheat 90


rem also causes "Share is above target" messages
rem cgminer -o stratum+tcp://nl1.ghash.io:3334 -u me.worker1 -p 1 --bflsc-overheat 90

rem also causes "Share is above target" messages
rem cgminer -o http://mint.bitminter.com:8332 -u me.1 -p 1 --bflsc-overheat 90 --fix-protocol


Any ideas on what this is about or how to fix it?