My Church has a computer that keeps getting this same error, so when any new information comes out, please post it!
I checked system logs and app error reports and found that the beginning of the problems for us coincided with the instalation of a windows update 2 weeks ago- almost to the minute. Our computers are set to update at 3am, and at 3:26am on the Sept. 7th, this error hit for the first time. It re-occurred several times that day, then was dormant until a week later, at the same time, when another update was applied, and from that point on it has been an increasingly annoying issue. The Windows updates that were applied (and no others were applied at these times,) had to do with trusted certificates.