I have the same problem. Also, I've noticed, the problem exists only at production and never appear on my local or
testing environment.
Looks like a mysticism or an IE10 rendering bug + production specific settings.
Rishikesh, have you found any solution or workaround?