• You're not running the latest build for SQL 2014. You're missing SP2 and CU1. Maybe the fix you're referring to is included in one of those.

    I would test in a test environment to see if applying SP2 and CU1 help.

    -- Gianluca Sartori