There could be a situation where packets are duplicated due to Network Load ballancers without using IGMP snooping, were somehow in a complex network a duplicated packet is not dropped, while it was picked up by one of the nodes that handles the Load-ballancing traffic. When that packet, due to routing issues, is delayed and still delivered, it could trigger a error message (almost false positive) like this.