I am having the same issue since patch 2.4, I had it previously with patch 2.2x and it happened regularly until the next patch it was fixed. It says it is an interrupted stop clock function on a secondary processor, if that helps.