According to TID 3453520 this was fixed in SP1 IR3a and I haven't seen
the problem since.. However since applying SP1IR4HP4, it started again.
I bumped the version # on a force run app after adding an msp to the
patches, and now I'm seeing it again.

Has anyone else seen this in the latest revision?