Hi,
Unfortunately this is due to a bug in the .NET framework that only happens with IE 10, see this related thread. Since it is a bug in the .NET framework it is not something I can fix. The only solutions are to either use .NET 4.5 which has this bug fixed, or use a differnet web browser for any place where that error happens.
Hope that helps,
Joe