Twice in the last couple of weeks I've had a Windows 7 computer come in with a strange issue where when I try to start some programs, some just won't do anything and others will give me a 0xC0000005 error. My memory is really bad, so even though I had it just 2 or 3 weeks ago, I did an hour of diagnostics again before I remembered doing it recently and, thus the solution. Hopefully typing it out here will keep it fresh in my mind if I see it again.
First, a little background. Not all programs give the error, but most do. But everything runs just fine in Safe Mode, in as much as they would normally run in Safe Mode anyway. So the first time around after Googling and wracking my brain I finally decided to us MSConfig to disable things and re-enable them a few at a time to see if I could narrow it down. And that worked. With all non-Microsoft services and all programs disabled, no error. The weird thing is, the issue never came back, even after re-enabling everything. So this time after disabling everything I checked that Chrome would open, then enabled all programs and rebooted. I checked Chrome again, then enabled all services and rebooted. For some reason, disabling and then enabling everything fixed this issue for me twice now.
One note, if you have Avast installed be sure not to disable the aswbIDSAgent service. It will not re-enable and you have to repair Avast to fix it.
I hope this turns a ridiculous issue into a simple fix for someone out there. And I hope I remember it the next time I see it so I don't waste so much time on it next time.
First, a little background. Not all programs give the error, but most do. But everything runs just fine in Safe Mode, in as much as they would normally run in Safe Mode anyway. So the first time around after Googling and wracking my brain I finally decided to us MSConfig to disable things and re-enable them a few at a time to see if I could narrow it down. And that worked. With all non-Microsoft services and all programs disabled, no error. The weird thing is, the issue never came back, even after re-enabling everything. So this time after disabling everything I checked that Chrome would open, then enabled all programs and rebooted. I checked Chrome again, then enabled all services and rebooted. For some reason, disabling and then enabling everything fixed this issue for me twice now.
One note, if you have Avast installed be sure not to disable the aswbIDSAgent service. It will not re-enable and you have to repair Avast to fix it.
I hope this turns a ridiculous issue into a simple fix for someone out there. And I hope I remember it the next time I see it so I don't waste so much time on it next time.