Is that much HID complimant things normal?
View attachment 358132
It's a laptop and the USB-HID class basically allows the manufacturer an easy interface / driver class to use for any additional switches/functions that are not standard. Can't say I've seen many with that much going on.
If you have an alternate keyboard and mouse you could try disabling the laptop ones (there is usually a button to kill the trackpad, and sometimes the keyboard also - maybe only in BIOS options) and seeing if the glitch still happens - that at least will rule them out.
I disabled page file disabled usb suspending and disabled wifi power savings but still same.
Well, it makes no odds really enabling / disabling the wifi adapter power saving options (unless you want to get the best economy you can from them - or use sleep mode often), so up to you if you want to put them back to default. Same goes for the swap file options, although I wouldn't necessarily set it how you had it set before. How Windows 10/11 use the page file isn't the same as how some older versions of Windows managed things and is a lot less aggressive, e.g.
32GB RAM, 20GB memory load = 7GB swap file, only 2% used. That's with system managed settings - really I could fix the page file at a fraction (maybe 1/2) of that size and have no issue... probably get slightly better performance and boot SSD life... too lazy.
Normally Paging RAM pages out to disk is only done if required by the app or if Windows thinks some memory pages are infrequently used enough that it would have little impact to performance and frees up actual RAM for applications. Unless you are in a low RAM situation this then falls back to using the page file to store RAM contents and switching things in and out of the page file as needed.
In reality with your 16GB RAM capacity I don't think you'd even use up a 16GB page file unless you are working with some big datasets (and even then, the performance hit would be painful).
Some people set it to a size just big enough to allow Windows crash dumps to work properly, or based on their expected workloads. The idea of setting it to .5x-1.5x your memory size or some such rule is flawed for most peoples use.
One other thing to look at - assuming Xperf doesn't yield anything useful - check your Event Log for any events around the time a glitch happens, you may find something such as a bad disk access, GPU reset or other issue, e.g.:
This would be under the 'Windows Logs'->'System' log area