This is a known issue. Sometimes, due to the state of the object being polled, the utilization reaches an absurd value. This is one such example. This is being addressed in DFM 3.2 due out this summer.
In the meantime, assuming there isn't a counter bug on the device, removing the device from DFM, and re-adding it should allow DFM to resume proper management. You can also try unmanaging the affected interface(s) under DFM > Device Management > Device Details (don't forget to apply changes). Then remanage the objects.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...