Reduce Raw Input background event rate
On this page
Recommendation
Enable 50 HzFor a gaming PC, limit compatible background Raw Input handlers to approximately 50-60 Hz.
Background applications will process mouse movements less often. In the tested scenario, the active game window continues to receive input at full frequency.
- Background handlers
- About 50-60 Hz
- Game in the foreground
- Full frequency
- System
- Windows 11
In short
Section titled “In short”Some programs receive mouse events via Raw Input even in the background. These can be messaging apps, launchers, browsers, overlays and other applications. If such a handler is compatible with the system frequency limit, increasing the interval to 20 ms reduces the number of messages delivered to it WM_INPUT. As the mouse moves, it has to process fewer events.
A physical measurement on Windows 11 24H2 showed about 125.5 Hz for a background handler under the system frequency limit; the active window received input at full frequency. In a public test of the 20 ms interval, the background frequency was approximately 50-60 Hz. This confirms a reduction in background event processing regardless of the effect on FPS.
Registry changes
Section titled “Registry changes”| Field | Value |
|---|---|
| Hive and path | HKEY_CURRENT_USER\Control Panel\Mouse |
| Enabling | RawMouseThrottleEnabled, REG_DWORD, 1 |
| Interval | RawMouseThrottleDuration, REG_DWORD, 20 ms |
| Reverting | Delete both values via the Windows default state in BoosterX |
The setting is intended for supported Windows 11 builds. On Windows 10 and early Windows 11, BoosterX does not offer it.
What exactly will improve
Section titled “What exactly will improve”- compatible background handlers will receive and process fewer mouse movement messages;
- the active game will retain a high input frequency: the 50 Hz limit does not apply to it;
- background work is reduced while the mouse is moving, when events arrive.
Applications may not use RIDEV_INPUTSINK or may react differently to the system limit. To find out whether a specific version of Discord, Steam or Chrome receives such background input, a separate test is required. For a compatible background handler, the 20 ms interval reduces the event delivery frequency.
Cost of the setting
Section titled “Cost of the setting”Background visualization of mouse movement or hotkey handling that depends on frequent events may respond less smoothly. For normal gaming this is an acceptable trade-off: the active game retains full input frequency, and inactive windows usually have enough at 50 Hz.
How to change and revert
Section titled “How to change and revert”In BoosterX, open “Optimization” → “Tweaks” → “Input” → “Reduce the frequency of background Raw Input events” and enable the toggle. The 20 ms interval will be selected, that is approximately 50-60 Hz for compatible background handlers. Click “Apply” at the bottom of the page. If “Instant apply” is enabled, the change is applied immediately.
If a specific background application needs a higher frequency, turn off this toggle, click “Apply” again and completely restart the application.
Sources and scope of verification
Section titled “Sources and scope of verification”- Background Raw Input throttling research with physical measurements and screenshots.
- RawMouseThrottleBufferTester, a public tester and source code.
- Microsoft KB5027303, a change in the handling of high report rate mice.
The measurements confirm a reduced event delivery frequency in the background and the retention of full input frequency in the active window in the tested scenario. They do not determine FPS gains or CPU load reduction for any given set of programs.
Last verified: 2026-09-20.