Well, this seems like a type casting problem. A floating point value is certainly not a valid integer value. It could also be an integer overflow problem occuring during the assignment of a value that is incorrect (i.e., corrupted data).

It would be handy if the Xolox error messages named the source code module, procedure, and line number that the error occurred on.