Blur Busters Forums

Hyote wrote: ↑

01 Jan 2026, 13:38

Games call for their own timer resolution. Again, educate yourself on the topic if you want correct answers. I know only one or two things about this but I am 100% sure that using timer resolution does more harm than good for latency and performance whether it's Windows 10 or 11. Windows has like 15 timers and you don't have to make comparisons between every single one of them and assume that all of them need to be lowered like this. Also the 2 ms is rather funny because as I remember, the actual example is that if it is called faster, then it does double the work, meaning the same thing I kept repeating until now. It's nothing than a resource hog. But again if it improves your game, then good.

• Latest Updates: FACEIT Optimization: A new guide on how to fix Faceit "graininess" (input lag) caused by hidden Windows processes and driver conflicts.

• Quick Start (v3.x)

• Troubleshooting: How to identify and fix Lags & Stutters (v3.x).

• Tuning Guide: Detailed config descriptions and the "Golden Rule" of balancing Duty vs. SpinGuard (v3.x).

• Application Philosophy: Describe how and why application works (v3.x).

• How to achieve better system responsiveness natively (without using my app)

• The "Account Voodoo": An analysis of why playing CS2 on the same computer—but with different Steam accounts—can feel completely different in terms of hitreg.

soul4kills wrote: ↑

01 Jan 2026, 14:49

Hyote wrote: ↑

01 Jan 2026, 13:38

Games call for their own timer resolution. Again, educate yourself on the topic if you want correct answers. I know only one or two things about this but I am 100% sure that using timer resolution does more harm than good for latency and performance whether it's Windows 10 or 11. Windows has like 15 timers and you don't have to make comparisons between every single one of them and assume that all of them need to be lowered like this. Also the 2 ms is rather funny because as I remember, the actual example is that if it is called faster, then it does double the work, meaning the same thing I kept repeating until now. It's nothing than a resource hog. But again if it improves your game, then good.

See, i think you're confused. The game can get the lowest possible timer it wants and operate at that the QPC interval all it wants. This is the part you're over looking. When my mouse sends an interrupt and system timer resolution is at 15ms. Well my mouse input is buffered by the system timer resolution to process that and send that info to the game. This is where input lag latency comes from.

Why even have a dynamic system timer if the 10mhz QPC exists. It's to buffer requests to the cpu for certain tasks so it doesn't get overloaded. Also helps with power savings as well.

edit: and I'm confused by what you mean by double the work. That comment makes me think you don't understand my goal here. I have a 5900x, and double the work is a bad thing? Yes, i want it to do double the work, it has no effect on the GPU. My 5900x is only being utilized 5% when gaming. How is double the work a bad thing? It's what I'm trying to do, take advantage and put my CPU to work so that my computer is more responsive when gaming. Once I'm done, I put my computer back into power saver mode and close islc.

Hyote wrote: ↑

09 Jan 2026, 18:43

soul4kills wrote: ↑

01 Jan 2026, 14:49

Hyote wrote: ↑

01 Jan 2026, 13:38

Games call for their own timer resolution. Again, educate yourself on the topic if you want correct answers. I know only one or two things about this but I am 100% sure that using timer resolution does more harm than good for latency and performance whether it's Windows 10 or 11. Windows has like 15 timers and you don't have to make comparisons between every single one of them and assume that all of them need to be lowered like this. Also the 2 ms is rather funny because as I remember, the actual example is that if it is called faster, then it does double the work, meaning the same thing I kept repeating until now. It's nothing than a resource hog. But again if it improves your game, then good.

See, i think you're confused. The game can get the lowest possible timer it wants and operate at that the QPC interval all it wants. This is the part you're over looking. When my mouse sends an interrupt and system timer resolution is at 15ms. Well my mouse input is buffered by the system timer resolution to process that and send that info to the game. This is where input lag latency comes from.

Why even have a dynamic system timer if the 10mhz QPC exists. It's to buffer requests to the cpu for certain tasks so it doesn't get overloaded. Also helps with power savings as well.

edit: and I'm confused by what you mean by double the work. That comment makes me think you don't understand my goal here. I have a 5900x, and double the work is a bad thing? Yes, i want it to do double the work, it has no effect on the GPU. My 5900x is only being utilized 5% when gaming. How is double the work a bad thing? It's what I'm trying to do, take advantage and put my CPU to work so that my computer is more responsive when gaming. Once I'm done, I put my computer back into power saver mode and close islc.

Since I don't want to start learning reverse engineering, I'll try asking if dpclat.exe works if active monitoring is stopped. I won't defend or attack the claim of it doing anything for system timers but there does seem to be some kind of a difference even on Windows 10 22H2.

Slender wrote: ↑

10 Jan 2026, 07:29

Hyote wrote: ↑

09 Jan 2026, 18:43

soul4kills wrote: ↑

01 Jan 2026, 14:49

Hyote wrote: ↑

01 Jan 2026, 13:38

Games call for their own timer resolution. Again, educate yourself on the topic if you want correct answers. I know only one or two things about this but I am 100% sure that using timer resolution does more harm than good for latency and performance whether it's Windows 10 or 11. Windows has like 15 timers and you don't have to make comparisons between every single one of them and assume that all of them need to be lowered like this. Also the 2 ms is rather funny because as I remember, the actual example is that if it is called faster, then it does double the work, meaning the same thing I kept repeating until now. It's nothing than a resource hog. But again if it improves your game, then good.

See, i think you're confused. The game can get the lowest possible timer it wants and operate at that the QPC interval all it wants. This is the part you're over looking. When my mouse sends an interrupt and system timer resolution is at 15ms. Well my mouse input is buffered by the system timer resolution to process that and send that info to the game. This is where input lag latency comes from.

Why even have a dynamic system timer if the 10mhz QPC exists. It's to buffer requests to the cpu for certain tasks so it doesn't get overloaded. Also helps with power savings as well.

edit: and I'm confused by what you mean by double the work. That comment makes me think you don't understand my goal here. I have a 5900x, and double the work is a bad thing? Yes, i want it to do double the work, it has no effect on the GPU. My 5900x is only being utilized 5% when gaming. How is double the work a bad thing? It's what I'm trying to do, take advantage and put my CPU to work so that my computer is more responsive when gaming. Once I'm done, I put my computer back into power saver mode and close islc.

Since I don't want to start learning reverse engineering, I'll try asking if dpclat.exe works if active monitoring is stopped. I won't defend or attack the claim of it doing anything for system timers but there does seem to be some kind of a difference even on Windows 10 22H2.

it is hard to open latency moon (kernel timer mode) and check it?

Hyote wrote: ↑

10 Jan 2026, 08:54

Slender wrote: ↑

10 Jan 2026, 07:29

Hyote wrote: ↑

09 Jan 2026, 18:43

soul4kills wrote: ↑

01 Jan 2026, 14:49

See, i think you're confused. The game can get the lowest possible timer it wants and operate at that the QPC interval all it wants. This is the part you're over looking. When my mouse sends an interrupt and system timer resolution is at 15ms. Well my mouse input is buffered by the system timer resolution to process that and send that info to the game. This is where input lag latency comes from.

Why even have a dynamic system timer if the 10mhz QPC exists. It's to buffer requests to the cpu for certain tasks so it doesn't get overloaded. Also helps with power savings as well.

edit: and I'm confused by what you mean by double the work. That comment makes me think you don't understand my goal here. I have a 5900x, and double the work is a bad thing? Yes, i want it to do double the work, it has no effect on the GPU. My 5900x is only being utilized 5% when gaming. How is double the work a bad thing? It's what I'm trying to do, take advantage and put my CPU to work so that my computer is more responsive when gaming. Once I'm done, I put my computer back into power saver mode and close islc.

Since I don't want to start learning reverse engineering, I'll try asking if dpclat.exe works if active monitoring is stopped. I won't defend or attack the claim of it doing anything for system timers but there does seem to be some kind of a difference even on Windows 10 22H2.

it is hard to open latency moon (kernel timer mode) and check it?

That is not the one I meant, I thought it was about the fixed 10 MHz QPC timer.

Slender wrote: ↑

10 Jan 2026, 09:32

Hyote wrote: ↑

10 Jan 2026, 08:54

Slender wrote: ↑

10 Jan 2026, 07:29

Hyote wrote: ↑

09 Jan 2026, 18:43

Since I don't want to start learning reverse engineering, I'll try asking if dpclat.exe works if active monitoring is stopped. I won't defend or attack the claim of it doing anything for system timers but there does seem to be some kind of a difference even on Windows 10 22H2.

it is hard to open latency moon (kernel timer mode) and check it?

That is not the one I meant, I thought it was about the fixed 10 MHz QPC timer.

1803 still work for new rtx.
also, try acpi timer, it smooth for me like wow.

Hyote wrote: ↑

10 Jan 2026, 12:39

Slender wrote: ↑

10 Jan 2026, 09:32

Hyote wrote: ↑

10 Jan 2026, 08:54

Slender wrote: ↑

10 Jan 2026, 07:29

it is hard to open latency moon (kernel timer mode) and check it?

That is not the one I meant, I thought it was about the fixed 10 MHz QPC timer.

1803 still work for new rtx.
also, try acpi timer, it smooth for me like wow.

lol, most browsers dropped support for that build by now but I think for the timers, I still got the best results with HPET off in BIOS+Win
bcdedit /set useplatformclock false
bcdedit /set useplatformtick true
This supposedly uses the PMT timer.
I use legacy settings for almost everything, even Windows 11.

Slender wrote: ↑

10 Jan 2026, 12:46

Hyote wrote: ↑

10 Jan 2026, 12:39

Slender wrote: ↑

10 Jan 2026, 09:32

Hyote wrote: ↑

10 Jan 2026, 08:54

That is not the one I meant, I thought it was about the fixed 10 MHz QPC timer.

1803 still work for new rtx.
also, try acpi timer, it smooth for me like wow.

lol, most browsers dropped support for that build by now but I think for the timers, I still got the best results with HPET off in BIOS+Win
bcdedit /set useplatformclock false
bcdedit /set useplatformtick true
This supposedly uses the PMT timer.
I use legacy settings for almost everything, even Windows 11.

@ :talking about qpc 10mhz
@ -give advice for good working build with old timer
@: talking aboud browser