<p>Knowing an exception code, is there a way to find out more about what the actual exception that was thrown means?</p>

<p>My exception in question:
0x64487347</p>

<p>Exception address: 0x1</p>

<p>The call stack shows no information.</p>

<p>I'm reviewing a .dmp of a crash and not actually debugging in Visual Studio.</p>

[{'answer_id': 61431, 'author': 'Rob Wells', 'author_id': 2974, 'author_profile': 'https://Stackoverflow.com/users/2974', 'pm_score': 0, 'selected': False, 'text': '<p>If you know which block threw the exceptioon, can you put more specific handlers in the catch block to try and isolate it that way?</p>\n\n<p>Are you throwing an exception that you rolled yourself?</p>\n\n<p>Edit: I forgot to point you towards <a href="http://www.codeproject.com/Articles/2126/How-a-C-compiler-implements-exception-handling" rel="nofollow noreferrer">this article</a> on Visual C++ exceptions which I\'ve found to be quite useful.</p>\n\n<p>Rob</p>\n'}, {'answer_id': 61435, 'author': 'DGentry', 'author_id': 4761, 'author_profile': 'https://Stackoverflow.com/users/4761', 'pm_score': 3, 'selected': True, 'text': '<p>Because you\'re reviewing a crash dump I\'ll assume it came in from a customer and you cannot easily reproduce the fault with more instrumentation.</p>\n\n<p>I don\'t have much help to offer save to note that the exception code 0x64487347 is ASCII "dShG", and developers often use the initials of the routine or fault condition when making up magic numbers like this.</p>\n\n<p>A little Googling turned up one hit for dHsg in the proper context, the name of a function in a Google Book search for "Using Visual C++ 6" By Kate Gregory. Unfortunately that alone was not helpful.</p>\n'}, {'answer_id': 63409, 'author': 'Mike Dimmick', 'author_id': 6970, 'author_profile': 'https://Stackoverflow.com/users/6970', 'pm_score': 3, 'selected': False, 'text': "<p>A true C++ exception thrown from Microsoft's runtime will have an SEH code of 0xe06d7363 (E0 + 'msc'). You have some other exception.</p>\n\n<p>.NET generates SEH exceptions with the code 0xe0434f4d (E0 + 'COM').</p>\n\n<p>NT's status codes are documented in ntstatus.h, and generally start 0x80 (warnings) or 0xC0 (errors). The most famous is 0xC0000005, STATUS_ACCESS_VIOLATION.</p>\n"}]
['https://Stackoverflow.com/questions/61402', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/3153/']