>If you've logged the exact time(s) when the problem starts, look at all your Windows Event Logs around those time(s). Look at all recorded events, don't filter them so you're only seeing errors and warnings.

Nothing to report there, at first we thought it could have been to the Application Experience Windows Service, which was logging a numerous amount of logging, and used to happen at the same time, but it was not related. We disabled that service yesterday and when I tried later on last night, I got it again.