Its like grasping at straws to find a solution and trying to paint WG in some angelic light. They introduced a patch before which crashed with nvidia drivers, now they released a patch which is lagging on ms and again the MS lag is coming from TELIA and WG SERVER NODES.

It has nothing to do with overclocking. PERIOD.

WG introduced a patch -> ms issue happens -> systems are the same as previous patch -> only change is WoT patch.

Overclocking only becomes a issue to a computer system when : -

A. you don’t know what your doing and put it past the required level and the system crashes
B. The hardware is incapable of decent level of overclocking
C. You don’t have adequate cooling to run overclocking.

Also, to point out, there is plenty of WoT players who have no form of overclocking and are still getting the ms spikes, so its not overclocking, its what I said above, the Telia ms nodes having 100+ ms spikes and WG’s nodes having a 30-60% packet loss on evenings when userbase is over the 80k mark.

MS lag was introduced with 8.8 PATCH, WG has created the problem, NOT THE END USER.

Users computers all haven’t suddenly become overclocked or problematic after one event: 8.8 PATCH.

FYI, the EC Sensor is detecting your fan speeds on your CPU, if you disable that your computer cannot regulate the fan speed on your CPU, so in essence switching that off will lead to your computer melting because your not suppose to switch the damn thing off.

Following internet advice from a email is a big no-no. Don’t do it its stupid.

It would display Live TV with a slight shudder that most people didn’t notice but annoyed me.
Someone suggested it might be a timing issue. I found an app that would tell me how accurate the PC was keeping high resolution timing. And sure enough it was something like 0.003 of a second out.

in THIS case removing the overclock resolved the issue. Also in the Bios there is some thing about using alternate timing which was also worth while investigating.

I ran the same test on another machine that was highly over clocked and it didn’t experience the issue. Both were Gigabyte boards. The other cool thing about the app is you could run it and it would report back the ability for your machine to playback content smoothly as many drivers and what not request for resources.

We need to remember on windows nothing happens in real time everything gets put in a request queue (So we can multi task) So it’s highly possible that some driver or anything is causing WOT to have to wait a fraction of a second for resources.

http://www.change.org/petitions/wargaming-net-solve-the-problem-of-lag

Overclocking doesn’t effect your latency ingame, your ISP, connection, your routing to the servers and how there load is at that timepoint is what effects latency.

The facts ladies and gentlemen is that Telia, a ISP in europe is causing a 100ms hop on 4 nodes, further to this when the evening rolls in WG’s server nodes are suffering a 30-60% packet loss.

THIS HAS NOTHING TO DO WITH OVERCLOCKING.

That sunk in yet?

Its routing and server load. Its Telia’s and WG’s issue, not users computers which worked perfectly fine with 8.7 and magically suddenly have issues with 8.8 PATCH CODE WORK, which conviently then requires you to disable your overclocking which worked fine in previous patch?

Please.

Talk about horse ****.

I’m not saying that disabling the sensor fixes all problems in WoT, I still have ocasionall red blips, but in my case it made the game playable for me again.

Good luck everyone