With regards to my Titan, the 4.17 build appears to either fixed or introduced bugs in the validation of hashes using the CPU. The perspective just depends on if I want to believe I've possibly damaged my Titan.

The 4.17 build reports a bad GPU hash about once every 30-45 seconds while the 4.14 build never reported a single one. This is using the exact same startup parameters (-l 294x2 -C 0 -i 0). The rejected rate from 4.14 also matches with p2pool. I also briefly tried -C 1, -C 2 incase they might have any performance impact but I didn't see anything noticeable.