It's either going to be an old Driver or Conflict 99% of the time. Simplest 'test' run MSCONFIG select Diagnostic - if the problem is resolved then App Conflict. Otherwise, go to the OEM site MOBO or PC and update ALL of the drivers.
The ONLY parts of interest are Critical Errors listed in the Event Viewer; if theres an App listed there update it. If it's a Kernel error do the above first; keep in mind it's like billiard balls the ball in the pocket didn't start the problem most of the time.