I have almost the same problem, but the error is 0xc0000005, not 0xc00000e5. I updated to Avast Free 17.1.2286 on Windows 7 Pro 64-bit this morning, and many of my normal programs failed to start with the 0xc0000005 error. Rebooting did not help. The I disabled all of the Avast Shields, and my other programs started normally. I enabled the Shields one at a time, and narrowed the problem to the Behavior Shield, which I have now disabled permanently! I may try to uninstall this component because Avast! complains about it being disabled. This means, though, that Avast! is running crippled. Unless Avast! can fix the problem I may have to look for another Anti-Virus program.
By the way, I do NOT use Comodo.