ANSWER: POP QUIZ: Why would you get this error from Windbg?

So it was kind of a trick question posting both of these errors.  They both mean the same thing.  Basically this is the error you get in SOS when the .NET Framework isn’t loaded in the process yet.   Problem 1 is from a SOS used to debug 1.1 issues and Problem 2 is from a SOS used to debug 2.0 issues.

Comments (3)

  1. L8Again says:

    I know this is an old post, but I am having an exact similar issue, with a memory dump. So, what does it mean? You have to wait for the .NET framework to be loaded in the process?

  2. Yes, in order for the debugger extension to actually do anything, it needs to have .NET loaded.  So if you let the process run a little more and see clr.dll or mscorwks.dll load, then they will work.

Skip to main content