This issue occurs on a rare condition.
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 8 for SQL Server 2014
Cumulative Update 1 for SQL Server 2014 SP1
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.