If the error appears frequently, upgrade to firmware release A.02.xx.
NOTE This problem is solved in any A.02.xx firmware release.