Disabling HPET to Reduce Micro-Stutter in Games: Does It Actually Help?

HPET (High Precision Event Timer) is a hardware timer that Windows uses for scheduling and timing operations. Disabling it is a common gaming optimization tip, but whether it actually helps depends heavily on your CPU and system. Here’s the full picture.

What HPET does and why disabling it matters for gaming

HPET provides very high precision timing to the OS – more precise than the older TSC (Time Stamp Counter) or ACPI PM timers. In theory that’s good. In practice, accessing HPET introduces some CPU overhead, and on certain processors the precision advantage is offset by latency introduced in the timing calls.

For gaming, consistent frame timing matters more than raw FPS. If HPET is causing uneven timer intervals, it can manifest as micro-stutter – frames arriving inconsistently even if the average FPS looks fine.

The benefit of disabling HPET is most commonly reported on older Intel CPUs (pre-10th gen) and AMD Ryzen systems. On modern Intel 12th gen+ systems, the impact is minimal because those CPUs have their own high-precision timers that are faster than HPET.

Method 1: Device Manager

  1. Right-click Start > Device Manager
  2. Click View > Show hidden devices
  3. Expand “System devices”
  4. Find “High precision event timer”
  5. Right-click > Disable device
  6. Confirm and restart

This is the simplest method and easily reversible.

Method 2: Command Prompt

Open Command Prompt as administrator and run:

bcdedit /deletevalue useplatformclock

Then restart. This removes the explicit HPET usage instruction from the boot configuration.

To re-enable later: bcdedit /set useplatformclock true

Method 3: BIOS setting

Some motherboards have an HPET option directly in BIOS/UEFI settings, usually under Advanced > PC Health Status or Advanced Chipset settings. Disabling it here is the most complete approach as it prevents the OS from accessing HPET at all.

Should you actually do this?

Results vary significantly by system. The best approach is to benchmark before and after – run a game with a frame time capture tool (CapFrameX is free and good for this) and compare frame time consistency, not just average FPS. If 99th percentile frame times improve, it helped. If not, re-enable it.

Modern systems (Intel 12th gen+, recent Ryzen) are unlikely to see meaningful improvement. Older systems are more likely candidates.

Here’s a video walking through all three methods with context on which systems benefit most:

the benchmark before and after approach is the right call. too many gaming optimization guides tell you to do something without any way to verify it helped. capframex capturing frame times before and after gives you actual data. did the 99th percentile frame time improve? did it get worse? you’ll know rather than guessing.

The Device Manager method is the easiest to test and reverse. Disable it, play for a session, re-enable if you notice no difference or if anything feels worse. The bcdedit command and BIOS options are more thorough but the Device Manager path is sufficient for testing whether HPET is relevant to your specific system.

The CPU generation dependency is important context. Blanket “disable HPET for better gaming” advice was more relevant five years ago. On a 13th or 14th gen Intel system the TSC is already more accurate than HPET and disabling HPET has essentially no effect. Applying every optimization tip you find without checking relevance is a waste of time.

Frame time consistency is the right metric to focus on for stutter. Average FPS can look identical while frame times are wildly inconsistent, which is what you actually experience as stuttering. A game running at “60fps” where frames arrive at 8ms, 25ms, 8ms, 20ms feels much worse than one where every frame takes 16ms.

The BIOS option for HPET is worth knowing about as the most complete approach. If your motherboard exposes it, disabling at the BIOS level means the OS never even sees the timer, which is cleaner than disabling it in Device Manager while it’s still technically present in the hardware inventory.