This is very strange and the first case I have seen on the forums where the usual culprit another AV once removed resolves the issue. For it to also effect other AVs I'm really baffled as to what it could be.
Whilst I have had no issue with outpost pro, that really is the only common denominator other than your OS. Are you using the anti-spyware plug-in in OP Pro, if so I would suggest you disable it and see if that makes any difference.
Before you posted the windows event log entry for this, if you can go to the latest one and see if clicking the for more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp link and see if it does produce more and perhaps more helpful information.
I turned off the anti spyware program for outpost and still have the error. I clicked on the link in the event veiwer and got this:
Details
Product: Windows Operating System
ID: 7034
Source: Service Control Manager
Version: 5.2
Symbolic Name: EVENT_SERVICE_CRASH_NO_ACTION
Message: The %1 service terminated unexpectedly. It has done this %2 time(s).
Explanation
The specified service could not continue. This service is configured to report the number of failures and, after a specific number of failures are reported, the Service Control Manager will perform the recovery action configured for the specified service.
User Action
For information that can help you identify possible causes for this error, view the WIN32_EXIT_CODE error that SCM encountered. To view the error, at the command prompt, type
sc query service name
I did what it said to do but I get an error saying " the specified services does not exist as a service."