I was crashing out every 5-20 minutes for a whole week, using the stand-alone version, as well as with 3 different browsers, using both the regular & alternate browser launcher. Tried all sorts of things & theories, nothing worked, until I finally got a clue and tracked this down as a common problem caused by an bug in current versions of the game's Unity3D engine when used in conjunction with certain anti-virus products or similar. In my case, the culprit is Avast 8.0, but it's also said to happen with Kaspersky, ESet, and probably others. Even disabling your AV won't help, you would actually have to uninstall it! There is a good thread on this issue here at Unity forums here: http://forum.unity3d.com/threads/17...0-1482-quot-getThreadContextfailed-quot-error. There is a fix given there on page 3, by CreativeChris. It has instantly solved my issue with this and I haven't seen the crash since, even with AVast enabled. It has also helped most others. Even though this was identified in March, it is not yet part of the current release of Unity 3D, which is 4.1.x. It is supposed to be released whenever 4.2 comes out. Not that while the post suggest that this is only supposed to be a fix for the Unity dev kit "editor", I've tried applied it to just the Windows Player and it works fine. Until then, you need to apply it manually as follows: 1) Download the modified mono.dll file from here: https://docs.google.com/file/d/0Bz4rtnpF8SvMNm0tLUpRdUxrVzA/edit 2) Go to the Windows Player / Mono subdirectory Project Gorgon installation. On Win7 it should be here: C:\Users\<YourUsername>\AppData\LocalLow\ProjectGorgon\GorgonLauncher\WindowsPlayer\WindowsPlayer_Data\Mono. 3) Rename the mono.dll file there as something else like mono-orig.dll, in case you need to go back because this failed or makes it worse. 4) Copy the mono.dll file you've downloaded into this directory. This seems to be a fairly common problem with Unity in many games for years now, so hopefully this saves someone a lot of headaches... EDIT: I've just discovered that whenever there is a version update, the launcher/patcher will replace the mono.dll file with the broken version from the server again. So you'll most likely need to repeat this every time there is an update. The "bad" version of the file is 2046K, the "good" one is 2048K. I've tried making it read-only, not sure if that will work. Perkus P.S. I've actually so far only tested it with the stand-alone launcher, as I prefer that, so I'm not sure if this also fixes the bug if using the browser version, since I don't know if it accesses this same file location.