Hmm, that is interesting. It's well below the layer of our game, being in kernel.dll, etc. It's even below the level of .NET, from the looks of it. Most likely something was just having a bad day with Windows, and hopefully it won't do that again, or will stop after a reboot, or something of that sort. I don't think I've ever seen an AI War error that was this deep into the OS stack before...