A guess, and it can only be a guess without being able to reproduce the crash, is the application or driver wrote over memory where is should have not touched, in this case the system clock. Years ago we often hacked into the "timer tick" interrupt for Terminate Stay Resident DOS coding, if that went wrong the clock would easily be all over the place. Now days I thought a memory access requests has to be made to access memory outside an applications sandbox, so I suspect it was a driver that pulled the machine done, they tend to have more low level access by default.
If it's all back, no harm done ;)