Congratulations, you found a bug in the CLR. If you ever see this exception type pop up, make sure to let the CLR people at Microsoft know through channels like Connect. Not to discourage you, but I have only seen a single occurrence of this exception in my 10 years of experience with the platform, while test-driving .NET Framework 4.5 beta interoperability with Windows Runtime.
Readers with a hacking mindset are invited to corrupt the process’s memory through some native debugger to mimic an error condition in the execution engine. Chances are you’ll cause it to throw this exception to acknowledge your disruptive interactions. Let’s move on to something more realistic.