An incorrect period value is used for paths that cross clock domains. (This only occurs if either the source or destination register is covered by multiple PERIOD constraints.) How do I avoid this?
You can avoid this situation by eliminating the extra PERIOD constraints.
This issue was fixed in the 4.2i software.