I didn't see the boot error, but I'll keep an eye out for that next time I see it. It sounds like there's no workaround...
On 06/ 2/10 09:34 PM, David Van Couvering wrote:The stack trace looks similar to the one provided here:
> I am seeing this exception fairly regularly, does anyone know what I
> might be doing to cause this?