Someone else posted a similar crash. The error message you got is a purely random thing; as you can see from the disassembly, the crash location doesn't contain valid executable code at all, just repetitious garbage.
I would bet that the true cause is the same as your previous crashes, because the call stack is the same each time. The only difference is that this crash tossed the CPU into a different block of repetitious garbage.
But Avery seems to have a good idea of what's happening, and he's fixing problems left and right. Stay tuned.
