I have a similar problem.
Best solution that I have found is to compile cgminer (I'm using 3.8.2 on a linux machine), with Line 58 and 59, # DEFINA_REPLY_WAIT_TIME set to 25 and the following line (or thereabouts), #define CMD_REPLY_RETRY = 4 (program has it at
.
Also change line 63 #define KLN_KILLWORK_TEMP to 61.5 and set your bat file to 350, 55. (This is in the klondike.c file, thanks to Zipju and other people for the suggestion, also check projectklondike.org)
The other trick that I have found helps, is start CG_miner with only ONE Klondike.
Let that run maybe 30 seconds, until it gets up to it's maximum hash rate 5.5 Gh/s or more at 350 Mhz.
Then plug in one more (or two more), connect those to the USB hub, unplug and plug in the little fan connector.
Let those get up to maximum hash rate.
Rinse and repeat. Make a note of the KLN number in CGminer, so you know which ones to power cycle back on if the hash rate is too low. Rinse and repeat again.
Most of the time, that will work just fine. If I try to start up all 10 of mine, all at once, two of them at least will have exactly ZERO work units or accepted units, but will display 5+ Gh/s hashing, just no work units. Highly annoying.
In any case, one or two will sometimes hash at half/hash rate. It is annoying, but they are prototype units and you are on the bleeding edge.
If that doesn't work, I usually throw them on my windows machine and let that screw with it for a bit. Some of them seem to work better on Linux than Windows, others work better on Windows....go figure !
Welcome to high BTC prices.