Um, guys, I think you're getting a little confused with ISR Count and what it means.
It's meant to go up, that's how it works. Whenever you move the mouse it generates an interrupt to say "hey, I've moved, do something!" - ISR Count is how many times this interrupt has fired.
On mutli-core systems you'll normally find stuff like Wdf01000 happens on the least favoured core so it causes the least impact.
It's only an issue if there's something causing the Highest Execution time to go up too high, which is what causes stutters etc.
USB2 uses this interrupt system via Wdf01000.sys, USB3 doesn't, so by using a different controller, presumably now USB3, you're shifting the ISR somewhere else, but it's still happening, otherwise your mouse pointer wouldn't move.
EDIT: For those interested, USB3 uses an MSI interrupt system by default vs the USB2 favoured legacy mode
Last edited by SpecChum; 06-02-2020 at 04:09 AM.