Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've been having some trouble with Visual Studio 2010. It stops working, and I see it increases in memory usage. So I suspect a memory leak (in one of the plugins maybe). I took a Full Dump with Process Explorer (procexp.exe), but am a bit at loss of what to do with it.

I tried loading it in WinDbg (through File > Open Crash Dump), but get an error 'Symbol file could not be found'.

Can anyone point me in the right direction? Making dump files is easy, but what do you do with them afterwards?

share|improve this question
up vote 3 down vote accepted

You might want to check this out for more information:

share|improve this answer
Thanks. Although the article is about debugging dump from driver errors, I was able to follow it for my VS2010 crash. Together with this page ( I loaded in the SOS.DLL and could retrieve the necessary info. – Peter Mar 7 '12 at 11:09
Please add the actual content of the answer, not just a link. – rossipedia May 22 '14 at 18:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.