I started receiving the same error message several weeks ago. I went into msconfig and stopped the service from running at startup. This stopped me from receiving the error message. I'm not sure what the log was for but I haven't seen any issues associated with stopping the service. If you don't know now to do this go to start then run and type in "msconfig". Click on the services tab and find the one for the proset event log and uncheck it. Click "OK" and you're done. You can always go back onto the msconfig and turn it back on by putting the check mark back in. Hope this helps.