Do you have a repro? That is, a simple script that builds a database, populates a table, creates a full-text index and then runs a query that produces this error?
I would not really expect that it is simple to produce such a repro, as it is likely to be dependent on your data and maybe a few more circumstances.
As Cris says, first apply CU11 just to see if this may fix the issue.
But if that does not work out, I would recommend that you open a support case. Assuming that it is a bug in the product, the support case should be of no cost for you at the end.
There is a small risk that it is due to corruption of some sort, so you could run DBCC CHECKDB on the database before you open a support case. You could also work on a copy of the database where you drop and recreate the full-text index.