This is another attempt to resolve the problem stated here. Unfortunately the topic was closed without adequate resolution found, as apparently the original poster had issues wi
The hotfix 2588507 ended up resolving the issue after all. I am running several instances of visual studio 2012 for several days, and debugging remote processes constantly, and have not seen yet a single "invalid access to memory location"