Ok two steps to do.
- Move to version 2.4.6 which contains tons of bugfixes already, could be that this was solved.
- If the error persists, then try to find out by debugging which line of code generates the error.
Once you know that report back, so we can have a look at it :)