{"id":161,"date":"2007-05-19T11:11:25","date_gmt":"2007-05-19T16:11:25","guid":{"rendered":"http:\/\/unitstep.net\/blog\/2007\/05\/19\/amd-dual-core-fix-for-games\/"},"modified":"2007-05-19T11:11:45","modified_gmt":"2007-05-19T16:11:45","slug":"amd-dual-core-fix-for-games","status":"publish","type":"post","link":"https:\/\/unitstep.net\/blog\/2007\/05\/19\/amd-dual-core-fix-for-games\/","title":{"rendered":"AMD Dual-Core fix for games"},"content":{"rendered":"

After I built my AMD Athlon X2-based dual-core system last year<\/a>, I started noticing some weird speed issues in certain games. At seemingly random times, the games would speedup and slowdown, making things very jerky and jumpy. This would basically make the game unplayable. It turns out that this is a known<\/a> problem<\/a> and can occur when single-threaded games run on a dual-core system. (So you may even experience these problems on an Intel dual-core system.)<\/p>\n

The solution is nicely outlined in the [H]ard|OCP Forums<\/a>, where it’s aptly known as the “Benny Hill Effect”. Turns out that the problem has to do with power state management issues and how they affect the read time stamp counter instruction (RDTSC), which is used for timing. I followed the guide, and it fixed my problems.
\n
\nThe games that I noticed the timing issues in were NFS:MW<\/abbr>, Rome Total War and GTA<\/abbr> San Andreas. This is by no means a complete list of games that are affected by this issue. Some of my own observations and suggestions for fixing the problem:<\/p>\n