F5F Stay Refreshed Power Users Overclocking I experience increased online latency when I overclock my CPU.

I experience increased online latency when I overclock my CPU.

I experience increased online latency when I overclock my CPU.

T
Tia0007
Member
Find
59
10-12-2025, 02:02 AM
#1
Hi again.
I’m facing some unusual issues lately. I won’t make it too long, so here’s a brief summary. My MSI P31 card doesn’t overclock much beyond what the BIOS allows, maybe not at all. I adjusted the chipset, memory, and CPU voltages, and now I handle the overclocking part in Windows using the SET FSB tool. Because of the chipset limits, I can get speeds from 333MHz up to 364MHz, which is fine. Even with weak CPU or memory overclocking, my online ping stays lower (less latency). Whether I play a game or ping a server, with no overclock I get 31-33ms latency, but with overclock it jumps to 39-45ms. I’ve tested this several times and the overclock seems to be the main cause. Since I can change the settings in Windows, I can see how lowering the FSB improves ping and reduces latency. The opposite happens when I raise the FSB. This is quite strange. Please help me, and let me know what I should do. I want faster CPU speeds and lower ping times—both are important for my Dota 2 game. I’m using a 4G LTE USB modem. Thanks!
Reply
Reply
T
Tia0007
10-12-2025, 02:02 AM #1

Hi again.
I’m facing some unusual issues lately. I won’t make it too long, so here’s a brief summary. My MSI P31 card doesn’t overclock much beyond what the BIOS allows, maybe not at all. I adjusted the chipset, memory, and CPU voltages, and now I handle the overclocking part in Windows using the SET FSB tool. Because of the chipset limits, I can get speeds from 333MHz up to 364MHz, which is fine. Even with weak CPU or memory overclocking, my online ping stays lower (less latency). Whether I play a game or ping a server, with no overclock I get 31-33ms latency, but with overclock it jumps to 39-45ms. I’ve tested this several times and the overclock seems to be the main cause. Since I can change the settings in Windows, I can see how lowering the FSB improves ping and reduces latency. The opposite happens when I raise the FSB. This is quite strange. Please help me, and let me know what I should do. I want faster CPU speeds and lower ping times—both are important for my Dota 2 game. I’m using a 4G LTE USB modem. Thanks!

Reply
Reply
M
MAZ531
Member
Find
164
10-12-2025, 04:31 PM
#2
I discovered a fix on forum overclock.net. The Windows clock/timer was incorrect. The PC started with default BIOS settings but was later overclocked. This caused confusion for Windows. Using WinTimerTester and a command line in CMD resolved the issue.
Reply
Reply
M
MAZ531
10-12-2025, 04:31 PM #2

I discovered a fix on forum overclock.net. The Windows clock/timer was incorrect. The PC started with default BIOS settings but was later overclocked. This caused confusion for Windows. Using WinTimerTester and a command line in CMD resolved the issue.

Reply
Reply
M
Masupa
Member
Find
59
10-12-2025, 08:15 PM
#3
If you lower your FSB below 333Mhz, it might indicate an issue with the FSB and southbridge not syncing properly, which is likely to occur on this platform. A higher ping after reducing the FSB suggests this problem is present.
Reply
Reply
M
Masupa
10-12-2025, 08:15 PM #3

If you lower your FSB below 333Mhz, it might indicate an issue with the FSB and southbridge not syncing properly, which is likely to occur on this platform. A higher ping after reducing the FSB suggests this problem is present.

Reply
Reply
F
Featherclaw
Junior Member
Find
12
10-13-2025, 04:19 AM
#4
I discovered a fix on forum overclock.net. The Windows clock/timer was incorrect. The PC started with default BIOS settings but was later overclocked. This caused confusion for Windows. Using WinTimerTester and a specific command in CMD resolved the issue.
Reply
Reply
F
Featherclaw
10-13-2025, 04:19 AM #4

I discovered a fix on forum overclock.net. The Windows clock/timer was incorrect. The PC started with default BIOS settings but was later overclocked. This caused confusion for Windows. Using WinTimerTester and a specific command in CMD resolved the issue.

Reply
Reply