Thank you very much for posting this.

This problem appears to be caused by invalid data being received by the miner from the pool connection and not being processed correctly (this was most likely due to a network error of some sort).  In this case, the miner should treat this as a network error, causing it to close the connection to the pool and attempt to reconnect.  However, after examining the code, there is a bug that prevents the miner from properly clearing it's receiving network buffer in this case.  This bug causes the miner to repeatedly see the invalid data in every future reconnect attempt.  I will have a fix for this bug out as soon as I can.

I advise anyone using version 0.2.0.0 or earlier to monitor their rigs closely in case of this error occurring.  If your pool supports alert/monitoring emails, please use them.

Network errors like this are usually not common, but can occur more frequently on unstable/unreliable network connections.
Edit: New version with potential fix posted.

I wanted to mine but stopped because of MPH, I need to have freedom to choose from otherwise it's not good as we can see.
Linux setup is pain in the butt, one rig worked (but went back to other coin) and on second rig I can't make it work. Windows is needed.

Actually there are enough xzc pools: suprnova, f2pool, mintpond, bsod, omnious, zpool, and of course mph. It's just hashrate distribution that sucks, everyone mines on mph. I can't understand why. Suprnova has 0% fee, f2pool is PPS, mintpond  has great interface and statistics...
I guess people got used to mph.

F2pool might change this, it already has 70 GH/s vs MPH 98 GH/s....

My experience with MPH has not been great.  In the process of developing the miner I've found two bugs in their XZC pool.  One of which allows a user exploiting the bug to get credit for a higher share rate than they are actually submitting, while at the same time not contribute to actually finding a block.  I've reported the bugs to the MPH guys, but they have yet to get back to me about the bug that basically allows cheating.

I've used suprnova's pools before, and have had a great experience.  However, their XZC pool seems to have some issues that make me worry: the stats on the pool seem to be completely broken, the hash rates it reports are ~30% higher than actual hashrates, it reports previous block effort incorrectly making the pool look like it has better historical returns than it actually has (any block that took more than 4,294,967,295 shares is reported as taking 4,294,967,295 shares).

Ominous network is new and they seem to currently have great support and 0% fee as they are trying to attract miners.  I ran a rig against them for a week and had no problems, also no returns since I was the only one on the pool.  The way the pool issues jobs can result in some rejected shares, due to every new job invalidating all previous jobs.  But in my time running this rejection rate was low, under 1%.  This will be more of an issue for miners running with high network latencies to the pool.

I had tried to run with f2pool, but the language barrier slowed me down a bit.  Also I couldn't find a web front for their pool stats, which is something I would like to have in the pools I use.

If enough of you guys can agree on a good pool to use, I would be happy to redirect my rigs and the dev fee hashes to it to help total hashrate.  Personally I'm leaning towards either Ominous or Mintpond, what do you guys think?

F2pool works same as yiimp, you put your wallet as username, autopayouts, and it has web statistics...
https://www.f2pool.com/zcoin/aAeTNKeYx42uhwyQKPRphGKf1oWmzExgnA

Mintpond is also very nice, haven't tried omnious.

Works nice ans stable rx480 8gb - 3,5mh,  core:1200 mem:-400

Haha, I better get merit for this  Ran into the same issues myself! Linux is... different. You'll need to navigate to the folder where you put the miner, open a terminal window from that location, and run the miner using a command like ./tdxminer from the terminal.

You'll have to pass the parameters into the miner from the command line as well. use ./tdxminer --help to get the list of parameters, and then pass one long line of parameters into the command line on one go.

Something like

 ./tdxminer --pool stratum.your.pool. --user yourusername --algo lyra2z ... etc.

I'm at work, or I'd give you more details and can't see my miner currently.

I've got 5 cards running, did not include a gpu parameter so something else is wrong. which drivers are you using?

Edit: Also, I'm using suprnova not MPH.

that'll do it  

honestly, rather than doing a write-up, I'll just drop this here. Follow step 4.

http://www.cryptobadger.com/2017/04/build-ethereum-mining-rig-linux/

edit: I just didn't like XZC's hashrate distribution and heard a lot of bad things about MPH, so avoiding it for now and using suprnova. Problem with Suprnova is that on average looks like a day between blocks. Been lucky so far and found 2 since I've been on though.

Of course, suprnova website has been down today, not sure what's going on. Have still been able to connect to the stratum and mine though.