Page 1 of 1

Drivers for a CPU. Why wasn't I told?

Posted: 2007-04-26 06:21pm
by Darth Wong
Seriously, who knew you had to install drivers for a CPU? That's a new concept for me, so when I installed an Athlon64 3800+ X2 dual-core CPU, I naturally assumed I could just run with it. This led to a week of frustration as I couldn't figure out why the timing on Rome: Total War was wonky as hell. Turned out that you need to install the AMD CPU driver and "dual core optimizer" to solve that problem, and that there's a whole class of games which suffers from it because of the way they synchronize with the system clock in a dual-core system.

Did everyone else already know this? Was I the last person to get the telegram?

Re: Drivers for a CPU. Why wasn't I told?

Posted: 2007-04-26 06:28pm
by Vohu Manah
Darth Wong wrote:Seriously, who knew you had to install drivers for a CPU? That's a new concept for me, so when I installed an Athlon64 3800+ X2 dual-core CPU, I naturally assumed I could just run with it. This led to a week of frustration as I couldn't figure out why the timing on Rome: Total War was wonky as hell. Turned out that you need to install the AMD CPU driver and "dual core optimizer" to solve that problem, and that there's a whole class of games which suffers from it because of the way they synchronize with the system clock in a dual-core system.

Did everyone else already know this? Was I the last person to get the telegram?
Honestly, that is news to me too. What the hell?

Posted: 2007-04-26 06:34pm
by DaveJB
For whatever reason, it's only AMD's dual-core chips that have this issue. Intel's dual/quad-core chips have never suffered this problem, which is likely why it remains a somewhat obscure issue, even two years later.

Posted: 2007-04-26 06:43pm
by phongn
Yeah, I've known about this for some time. For more details, MSDN has an overview on the issue.

Posted: 2007-04-26 08:16pm
by Uraniun235
A couple of my friends had problems with this and it took them quite awhile to figure out what the problem was. I wouldn't have known about it if I hadn't already seen threads about this very issue on another tech forum I frequent.

Posted: 2007-04-26 08:30pm
by Resinence
Intel's dual/quad-core chips have never suffered this problem
Wrong.
There is a microsoft patch to address timing issues with intel Dual Cores (I had to use it to fix gaming performance on my rig), and you have to use /pmtimer just like the AMD's. There is also intel optimised INF's (Drivers). Though the issue is slightly different, intel dual core CPU's also need "hotfixes" to reach maximum performance and prevent the rubberbanding effect from incorrect timings. Don't forget to scroll down and do the performance state registry fix, and to add /pmtimer (also explained).

edit: For more info go Here
edit2: That hotfix is NOT for AMD's, don't blame me if you didn't listen and fuck up your PC. Use the AMD stuff, this is for intels.