Should You Disable HPET for Gaming? An Honest Answer
Published
On this page
Should you disable HPET for gaming? On modern Windows 10 and 11, the honest answer is no — leave it on automatic. Forcing HPET on or off with bcdedit is an old tweak-forum ritual that produces inconsistent results and can actually increase latency on some systems. The real, reliable latency wins are elsewhere, and this guide points you to them.
HPET is a clock source, not a magic latency switch — and Windows already picks the right one.
What HPET actually is
HPET — the High Precision Event Timer — is a hardware timer on your motherboard that the operating system can use as a clock source. Modern Windows has several timer sources available (HPET, the ACPI PM timer, and the CPU’s invariant TSC) and chooses among them automatically, usually preferring the efficient invariant TSC.
The crucial point: HPET is a timekeeping source, not a knob that directly sets your input lag. It tells Windows what time it is; it does not, by itself, decide how fast your mouse registers.
Where the “disable HPET” myth came from
Years ago, on some specific hardware and older Windows builds, forcing the platform clock with bcdedit /set useplatformclock true (or disabling HPET in BIOS) occasionally changed DPC latency behavior. A handful of benchmarks circulated, the tweak got copied into a thousand “ultimate gaming” guides, and it calcified into folklore.
Two things make that folklore unreliable today:
- Windows now manages timer sources far better than it did, and usually picks the optimal one already.
- Results were always system-specific — what helped one chipset hurt another.
Why forcing it can hurt on modern Windows
Overriding Windows’ automatic choice is a gamble:
| Action | Likely effect on a modern system |
|---|---|
useplatformclock true (force HPET) | Can raise DPC latency / timing overhead — often worse |
| Disable HPET in BIOS | Usually no benefit; can cause timing quirks |
| Leave on automatic (default) | Windows picks the efficient TSC — recommended |
Forcing HPET as the platform clock makes Windows read a slower, higher-overhead timer more often. On many current systems that is a net negative. Unless you have measured a specific problem that points at the clock source, there is nothing to fix here.
Don’t confuse HPET with timer resolution
This is the single most important distinction in the whole topic. HPET ≠ timer resolution.
- HPET is a hardware clock source Windows selects from. Leave it on auto.
- Timer resolution is how often the Windows scheduler ticks — the interval (e.g. 0.5 ms instead of ~15.6 ms) that applications can request. This genuinely affects frame pacing and responsiveness.
Timer resolution is the lever worth pulling, and you can do it safely and reversibly. See The Ultimate Guide to Timer Resolution for Gaming, and use Tier1Timer to request a fine resolution per-game and revert it on exit.
What actually reduces latency
Skip the HPET roulette and spend your effort where the mechanism is understood and the result is repeatable:
- Fine timer resolution for steady frame pacing — Tier1Timer and the 24H2 timer guide.
- NVIDIA Reflex / AMD Anti-Lag 2 in supported games — Reflex, Anti-Lag 2.
- An FPS cap below refresh to avoid queue and V-Sync latency — Best FPS Cap for Low Latency.
- A correct G-Sync + V-Sync + Reflex setup — the lowest-latency combo.
Then measure your input lag so any change you make is verified, not assumed.
Related guides
- The Ultimate Guide to Timer Resolution for Gaming
- Timer Resolution on Windows 11 24H2: What Changed for Gaming
- NVIDIA Reflex: Should You Turn It On?
- How to Minimize Input Delay for Competitive Gaming
- How to Measure Input Lag
The honest verdict: leave HPET on automatic and stop fiddling with bcdedit timer flags — on modern Windows they rarely help and can quietly make things worse. Put that energy into timer resolution, Reflex or Anti-Lag, a proper FPS cap, and a correct G-Sync setup, and measure the result. Those are the changes your hands will actually feel.
Frequently asked questions
What is HPET and what does it do?
HPET (High Precision Event Timer) is a hardware timer on your motherboard that the OS can use as a clock source. On modern Windows, the OS usually prefers a more efficient platform timer (like the TSC or invariant TSC) and uses HPET only when needed. It is a timekeeping source, not a setting that directly controls input lag.
Should I disable HPET to reduce input lag?
On modern Windows 10 and 11, no — leaving Windows to manage its timer sources automatically is the right default. Forcing HPET off (or on) with bcdedit was an old-forum tweak that produced inconsistent results; on some systems forcing it can actually increase DPC latency or cause timing problems. Unless you have a specific, measured problem, leave it alone.
Is HPET the same as Windows timer resolution?
No, and conflating them is the most common mistake. HPET is a hardware clock source the OS selects from. Timer resolution is how often the Windows scheduler ticks (the interval, like 0.5 ms vs ~15.6 ms), which applications can request. Timer resolution is the one that actually affects frame pacing and responsiveness — and you can tune it safely with a tool like Tier1Timer.
Does forcing 'useplatformclock true' help gaming?
Generally no, and it can hurt. The useplatformclock bcdedit flag forces Windows to use HPET as the platform clock, overriding its automatic choice. On most modern systems this is worse, not better, because Windows already picks the most efficient timer. It is one of the most cargo-culted tweaks on tweak forums and rarely helps.
What should I do instead of fiddling with HPET?
Focus on changes with a real, understood mechanism: a fine Windows timer resolution for steady frame pacing, NVIDIA Reflex or AMD Anti-Lag in supported games, an FPS cap below your refresh rate, and a correct G-Sync + V-Sync setup. These reliably reduce or stabilize latency, unlike HPET toggling.