TWEAK: Enable HPET (in BIOS and OS) for better performance and FPS


Recommended Posts

Hi guys, I could not resist joining this forum to add my two cents. HPET made me go nutz, too.

 

 

HPET on/off making a significant difference is definitely NOT snake oil.

 

 

On my previous Win 7 build (DAW only), disabling HPET in BIOS & OS resulted in a DPC latency of comfortable 2 - 4 micro seconds. Before that, the latency rarely ever dropped below 130 micro seconds, which already has been quite good regarding the 270 which I?ve had before I got rid of my nvidia card and its crappy drivers.

 

Not only there were no more drop outs (at reasonable buffer sizes), the whole system was much more responsive. The negative result was that my ASIO load meter got more "nervous/sensitive". Means that the meter in Cubase jumped up and down more than before when it was slightly higher but also more stable.

 

I?ve dealt quite a while with the HPET thing and have come to the conclusion, that HPET is neither the "best timer" nor the worst. Computers are not interested in having the timer "ring" every 1000 or 976 or whatever when. They have no personal preference and don?t care about the output. Just about the processing itself. So the important thing is to have as many timers as possible as this means more potential moments to generate interrupts.

 

["...interrupts can be missed if the target time has already passed"]  the wiki link

 

Enabling HPET & using "bcdedit..... true" to force Windows to use only one timer seems absurd. More

 

Just think of it as drinking in a bar where two out of three waitresses have been fired and the one who?s left may be extremely punctual at appearing only once per hour. One of the former waitresses (which meanwhile are unemployed and hungry) could have come your way already 45 minutes after your last beer order. That?s when you were supposed to generate that one interrupt to quench your thirst.

 

I am aware that there has to be some kind of down side to it. Otherwise, nVidia would not set their drivers to strictly induce a latency of 255 micro seconds instead of matching it with the PCI Latency Setting found in BIOS. Maybe this allows a more stable framerate (not a faster one!), like slaves on a galley working their paddles to the decent but steady beat of the drummer. Less strokes, but more load per stroke.

 

While its benefits/disadvantages depend on each single person?s needs, its influence on the computer at the bare system level has to be clearly explainable. There is no place for "every setup is different, so this function does whatever its wants to do", computers don?t work this way.

 

For me, disabling it much more serves my needs as constantly keeps my snake oiled.

 

 

Cheers from Germany

 

'Nuff said.

thread is 2 years old, still not a single proof or evidence that this works.

 

on the contrary, all the claims that this works makes me wonder what's the purpose of deceiving people into this?

thread is 2 years old, still not a single proof or evidence that this works.

 

on the contrary, all the claims that this works makes me wonder what's the purpose of deceiving people into this?

Personally, I think it is just the placebo effect instead of subterfuge in many cases. The wintimertest results are enough to convince folks that it must improve speed objectively everywhere. We aren't immune to such things by any means either. We might defrag an HDD and perceive the same thing to be honest. Tricks of the mind. It's similar to people who listen to uncompressed audio (versus XYZ compressed audio) and claim they can hear a difference, yet double blind studies show otherwise. Expectations are everything, huh?

It's similar to people who listen to uncompressed audio (versus XYZ compressed audio) and claim they can hear a difference, yet double blind studies show otherwise. Expectations are everything, huh?

 

well, i can listen to 128kbps audio file and find differences from the same uncompressed format; 320kbps, not so well. Buy i agree with you, even a defrag can make a subtle difference so this is more a placebo effect then anything.

  • Like 1

well, i can listen to 128kbps audio file and find differences from the same uncompressed format; 320kbps, not so well. Buy i agree with you, even a defrag can make a subtle difference so this is more a placebo effect then anything.

Well 128kbps is the questionable line afaik (or 192kbps -- depending on the compression algorithm). It's the higher bit rates where you can't perceive in double blind tests, yet, people claim otherwise.

Well 128kbps is the questionable line afaik (or 192kbps -- depending on the compression algorithm). It's the higher bit rates where you can't perceive in double blind tests, yet, people claim otherwise.

 

well, considering that when i was learning Java i made a small audio program that i could insert two filters:a low-pass and a high-pass; learned pretty quickly i was going to become deaf more faster then i expected lol

How do I disable it?

Can't find it in my bios....

I have a hp laptop.

Help!

 

You don't, If your computer came with Windows, it's already optimized for the hardware.

But it should be in bios!

Why is it not?

Your laptop is probably too new (pretty sure mine doesn't have it either). The only good reason to have the option in the bios was during the early years when the actual hardware implementations weren't well tested or supported.

Your laptop is probably too new (pretty sure mine doesn't have it either). The only good reason to have the option in the bios was during the early years when the actual hardware implementations weren't well tested or supported.

Do you know any other method that reduces lag and improves gaming?

Do you know any other method that reduces lag and improves gaming?

Well you can still force only HPET in Windows (as was outlined here in the first post) using step 2 if your laptop supports it (you just can't turn it off/on in the bios). Note, I am not saying this will improve your performance (I don't believe it will).

Well you can still force only HPET in Windows (as was outlined here in the first post) using step 2 if your laptop supports it (you just can't turn it off/on in the bios). Note, I am not saying this will improve your performance (I don't believe it will).

Can't find that 2nd step... :(

For many years already my HD never scream.  After turn this on:

bcdedit /set useplatformclock true

 

I heard my hard drive screaming.  I mean it has never make any noise before.  So yeah I think I will need to get a new hard drive to back up my data soon and then get back to it's original setting... not turning on the HPET that is.

  • 3 weeks later...

HardBag (or anyone else here),

 

How do I check the BCD on what's the current setting of useplatformclock, before making any changes to the BCD?

 

BTW, I have checked my system to see if Invariant TSC is supported or not. Says it's supported.

So does that mean I don't need to edit my BCD?

 

For those who don't know how to check, here's how:

 

1. Open AIDA64 -> Motherboard -> CPUID
2. Look for the field "Invariant Time Stamp Counter", and check whether it's supported or not.

 

HardBag (or anyone else here),

 

How do I check the BCD on what's the current setting of useplatformclock, before making any changes to the BCD?

 

BTW, I have checked my system to see if Invariant TSC is supported or not. Says it's supported.

So does that mean I don't need to edit my BCD?

 

For those who don't know how to check, here's how:

 

1. Open AIDA64 -> Motherboard -> CPUID
2. Look for the field "Invariant Time Stamp Counter", and check whether it's supported or not.

 

For the first question: type 'bcdedit' on the command line. 'useplatformclock' will appear under the Windows Boot Loader section if it set.

 

For the second question: the TSC is completely separate from the HPET timer. See: http://en.wikipedia.org/wiki/Time_Stamp_Counter. The invariant version of the TSC is an updated version of the TSC on newer processors:

 
17.13.1 Invariant TSC

The time stamp counter in newer processors may support an enhancement, referred to as invariant TSC. 

Processor?s support for invariant TSC is indicated by CPUID.80000007H:EDX[8]. 

 

The invariant TSC will run at a constant rate in all ACPI P-, C-. and T-states. This is the architectural behavior 
moving forward. On processors with invariant TSC support, the OS may use the TSC for wall clock timer services 
(instead of ACPI or HPET timers). TSC reads are much more efficient and do not incur the overhead associated with 

a ring transition or access to a platform resource.

 

--

http://www.intel.com/content/www/us/en/architecture-and-technology/64-ia-32-architectures-software-developer-vol-3b-part-2-manual.html

Look what I found:  useplatformclock [ yes | no ]

Forces the use of the platform clock as the system's performance counter.

Note  This option should only be used for debugging.

http://msdn.microsoft.com/en-us/library/windows/hardware/ff542202(v=vs.85).aspx

  • 1 month later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Most of the stuttering can easily be fixed by generating a PSO cache and compiling every shader before loading the game, it's up to the developer to set it up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!