Which OMP 3.2 version , you are having ?
We had a similar issue, which was resolved in the latest OMP version, just to check before digginn into the details ?