One month before I modified USB overclocking software for work at Win8 - Win10.
First and only fat bug was debugged yesterday
But nothing can stop overclocker. In development process I see one feature in code of USB3.0 host controller driver - so it's here: trying to reach polling rates higher than 1000 Hz!
What we need to try?
1. USB3.x host controller
2. Windows 8, 8.1 or 10 (actually we need microsoft driver for USB3.x host controller - USBXHCI.SYS)
3. USB mouse (low/full speed) attached to this controller. Don't mix "controller" and "port" - it's different concepts. You can verify which controller process your mouse in Device Manager, Devices By Connection (device tree) view (qsxcv screenshot from here http://i.imgur.com/wbm0WyX.png
Do not use USB hubs (for first try), it can restrict rate, attach mouse to controller ports directly. In Device Manager mouse (or HID or composite devices) must be attached to "USB Root Hub" as at screenshot above. Some xHCI controllers like this VIA
can have built-in/embedded USB hub for low/full/high speed devices so it's not possible to have 2000+ Hz on such hardware. And some non chipset
controllers are just restricted (hardware bug?) in interrupt rate probably.
hidusbf.zip - My official package from 2018/12/16
Edit: High rate driver versions now included in this package (in appropriate folders).
How to install:
1. Install HIDUSBF and try to change rate (simply change). If this is successed goto 2
2. Take drivers from 2khz-4khz or 4khz-8khz folders and install it (copy to %systemroot%\system32\drivers\ directly or to the folder of hidusbf setup and then install service).
3. Reboot after 2!
4. Run setup.exe, and try to change rate to 31 or 62. Rate=31 actually equal to 2000 Hz, 62 - 4000 Hz for 2khz-4khz version. Rate=31 actually equal to 4000 Hz, 62 - 8000 Hz for 4khz-8khz version. (Don't forget to restart device.)
5. Check the rate (dimr or mouserate or other software). If rate is 31(62) then you done something wrong (new driver installation, USB controller type, newer version of USBXHCI.SYS not known to driver). If rate more than 31(62), but not more then 1000 Hz - you mouse is not capable of HARD overclocking
You can read manual README.2kHz-8kHz.ENG.TXT from jeshuastarr in hidusbf package too.
If anybody can reach actual rate more than 1000 Hz - post your mouse name here.
I personally try this already and my best overclockable mouse (a4tech bw-35) reach 1400 Hz average (unstable).
HARD result (thanks to qsxcv and mlt04):
WMO DOES 8000HZ POLLING
Other good results:
And other not so good result:
rog gladius fake 2000 Hz
P.S. Under modern versions of Windows 10 (whether you want hard or ordinary overclocking):
1. If you have problem with driver loading on version x64 1607+ disable Secure Boot
or use registry settings
2. If you have EHCI (USB2.0) Controller only on version x64 1703+ or any controller on version 1803+ use these drivers
and (Test Mode or atsiv method
with non Test Mode).
P.P.S. If you came here for ordinary (1000 Hz-) overclocking drivers and have Windows 7 (or previous version) and Intel chipset with both EHCI and XHCI controllers (i.e. series 7x-9x) then read this manual
with this optional addition
in case you can not overclock your mouse but still want to use XHCI controller.
Or you can use hidusbfn.zip
and one of the two methods described above especially if you have modern Intel hardware with xHCI controller only.