I've not encountered the error again... I wonder if it is related to a sleep / wake-up cycle... I'll have a look at that option. If I catch the error again, I'll post the info. Otherwise, I may just close the bug.