SOS Best Practice: Match the SOS version with the process being analyzed

I haven't seen a whole of of issues around this as of yet, but now that 3.5 SP1 has released that may change.  If you copy SOS.dll to another location and then load it out of that directory to troubleshoot dumps, you may start seeing problems.  Namely, things like !clrstack not returning any valid names for functions and just printing out the numbers.  For example: 0:006> !clrstack OS Thread Id: 0x1154 (6) ESP EIP 0154cfdc 7614f35f [HelperMethodFrame: 0154cfdc] 0154d080 5fb7b8cd 0154d094 5fb7b78b 0154d0bc 5fd26907 0154d0d0 5f95a87c 0154d0e8 5f959458 0154d108 5f9634f1 0154d124 5f96342d 0154d150 65525e55 0154d17c 5e339ea3 0154d1f8 5e33ce4d 0154d37c 5e3400cc 0154d380 5dd60d14 0154d3b4 5e56def3 0154d408 5dce876b 0154d438 5dd12799...(read more)

Source Click Here.