CPU overclocking >>> Timers Off

[Coldfire]

This has nothing to do with overclocking. It's a known issue and it's most likely caused by client/servers async data. The exact problem is hard to determine though as it happens too rarely.

[Rutelor]

this is due to memory leaks... after a few days I notice the same thing on my computer, a simple logout and log back in seems to fix this.. so if you have been logged in for days and going to a dungeon, do a quick logout and login.

This has nothing to do with overclocking. It's a known issue and it's most likely caused by client/servers async data. The exact problem is hard to determine though as it happens too rarely.

Much as I appreciate your responses to my query above, Coldfire and Auctiongirl, I have to insist that my issue (I'm not commenting about the one that afflicts you, Auctiongirl) is directly correlated to overclocking. I have set my overclocking up, and back down to zero, repeatedly, during the last few days, and the results of the experiment are unvarying and consistent: Every time CPU overclocking is on, the timers (action cool-down counters as well as guildleve timers) are off by a significant amount of time; every time overclocking is turned off, the timers regain their accuracy. Simple and plain.

Furthermore, the time differential (the period by which timers are off) consistently matches the percentile of the overclocking. So, for instance, if I overclock my CPU by 15%, a one minute timer will be off by 9 seconds, every time.

[Coldfire]

Maybe you get 60fps when overclocking and ~50fps when not.

[Hazmatyre]

Much as I appreciate your responses to my query above, Coldfire and Auctiongirl, I have to insist that my issue (I'm not commenting about the one that afflicts you, Auctiongirl) is directly correlated to overclocking. I have set my overclocking up, and back down to zero, repeatedly, during the last few days, and the results of the experiment are unvarying and consistent: Every time CPU overclocking is on, the timers (action cool-down counters as well as guildleve timers) are off by a significant amount of time; every time overclocking is turned off, the timers regain their accuracy. Simple and plain.

Furthermore, the time differential (the period by which timers are off) consistently matches the percentile of the overclocking. So, for instance, if I overclock my CPU by 15%, a one minute timer will be off by 9 seconds, every time.

I got the same issue a few days after the patch came out, but the issue lasted only for that particular day. I haven't noticed anything else after that. I overclocked my quad core Intel processor from 2.8ghz to 3.4ghz.