So, looking at the first error, it is trying to call out to a Webservice, and in the meantime, this requires .NET to load up an assembly, and it is getting a COM error when attempting to do so. The second error is probably just a symptom of the first, although I would be interested to know if the file it is looking for actually exists, e.g. E:\game\InnerSpace\InnerSpace.xml (I suspect it does, because the second error ends up being the same as the first!).
With your reinstall of Windows, your game, InnerSpace and ISBoxer, what else went on??.
The first error, is actually saying it cannot load a .NET file (System.Configuration), but it then goes on to indicate that the calling convention is incorrect. As the location of the call is near the Windows Kernel then it is highly likely to be something injecting itself into the core of Windows. The error is a little hard to explain if you are not into C++/C programming, but essentially the manner in which the Stack and CPU registers are being set, is not as expected for the call being made to the loadlibrary method (a bit of creative licence as to what is actually being called here).
My first port of call for stuff like this would be
- Antivirus
- bad drivers
- some kind of corruption - seeing as it is consistant after a reinstall, then maybe a full on memory failure?)
- missing some vital Windows components (although I don't think you would have got as far as you did if this was the case)
- some kind of malware/rootkit
- debug/checked builds of Windows?
- hacking tools of various kinds
- dodgy Windows versions from the back of a truck