Cameron Boote
Tera Guru

We're seeing the same issue.  Haven't been able to figure out any kind of pattern as to why it only happens on certain machines.  Seems to be related to the configuration item getting the wrong correlation ID from SCCM.