The error is generic. Hundreds of different issues may give rise to this error. So same error reported over long time does not mean same issue.
Since 10th July hundreds of users were affected by a bad windows update which Microsoft fixed 6 days later however not all users got the fix automatically see post in the topic where most users reported the issue
In that thread there are a number of posts that show how one can establish if it was the issue caused by the windows update
