I believe in the most recent example, it was traced back to a Ricoh driver and the AV service itself was showing high CPU % consumption, and in our case removing the driver was the "fix", which removing all non-MS drivers would've also probably worked.
Granted, I'm quick to blame AV these days because it's been such a shitshow in our env.