Quote from: wetblanket on January 26, 2018, 06:03:35 PM

Quote from: realbminer on January 26, 2018, 12:08:09 AM

Quote from: PIR3lly on January 26, 2018, 07:18:34 AM

Run for two days and still cannot reproduce the error.

Have you tried different mining pool?

Not yet, no.
This pool gives me the best payout at the moment. I've been running Ewfb miner for days on it without problems.
Since it stopped mining with Bminer I switched to dstm and its been running great with about the same reported hash rates.

Would love to run Bminer, if it was faster or if it had lower fee than the others. But stability problems is a much bigger concern than slightly higher hash rates.

realbminer, it almost sounds like a stratum protocol parsing issue, specific to the one pool's implementation? Although, PIR3lly stated that it ran well for a day before starting to fail.

Perhaps something related to the mining 'session' (re: mining.subscribe ID used to resubscribe after disconnect) - not sure if bminer supports resuming mining sessions. Given the slow, staggered startup, I'm guessing 'no'. (and it's very unlikely that it would resume between fresh bminer starts, anyway) But if so, maybe starting subscribing fresh, without resuming would help?

Thanks for the info. Will look into it.