> It might have been a core stuck in a loop and it just needed a re-boot. You> never can tell.
You can get task manager to show the CPU usage for each core
(Performance -> View -> CPU History -> One Graph Per CPU), it should
then be obvious if any of the cores are stuck in a loop.
