This happens a lot to the server when characters move to certain locations.
// throw -- terminate on thrown exception REPLACEABLE
#define _HAS_EXCEPTIONS 0
#include <cstdio>
#include <cstdlib>
#include <exception>
#include <crtdbg.h>
_STD_BEGIN
_MRTIMP2_NCEEPURE void __CLRCALL_PURE_OR_CDECL _Debug_message(const char *s1, const char *s2)
{ // legacy report error and die
::fflush(0);
::fputs(s1, _cpp_stderr);
::fputs(s2 != 0 ? s2 : "unknown", _cpp_stderr);
::fputs("\n", _cpp_stderr);
::abort();
}
#ifdef _DEBUG
_MRTIMP2_NCEEPURE void __CLRCALL_PURE_OR_CDECL _Debug_message(const wchar_t *message, const wchar_t *file, unsigned int line)
{ // report error and die
if(::_CrtDbgReportW(_CRT_ASSERT, file, line, NULL, message)==1)
{
::_CrtDbgBreak();
}
}
_MRTIMP2_NCEEPURE void __CLRCALL_PURE_OR_CDECL _Debug_message(const unsigned short *message, const unsigned short *file, unsigned int line)
{ // report error and die
_Debug_message((wchar_t *) message, (wchar_t *) file, line);
}
#endif
_STD_END
_X_STD_BEGIN
_MRTIMP2_NCEEPURE void __CLRCALL_PURE_OR_CDECL _Throw(const exception& ex)
{ // report throw exception and die
std::_Debug_message("exception: ", ex.what());

I'm a little confused about this. What is the problem? In your screen shot everything seems fine.

The server is crashed at this point. and it always seems to crash when this happens there is a debug window in the background and the text i posted is the first debug text from visual studio.

Did they spawn anything before they logged out?

nope.

Next time it happens can you look at the call stack and see where it is being called from? The text you posted was the end result and unfortunately it is useless for tracking down the cause.

The commands /camp and /quit also currently throw this opcode (OP_MapFogDataUpdateMsg), it looks like you may have been receiving the error when the zoneserver was shutting down Antonica. If that is the case, then if you have the latest SVN revision you should no longer have this issue.
Please let us know if you are still having the problem, and as LE suggested, check the call stack to see if you can see what function is throwing the error. Thanks!