backtop

Print E-mail del.icio.us 47 comment(s) - last by Skypilota72.. on Aug 23 at 2:04 PM
Improving dual-core compatibility for gaming

AMD has silently released a utility that fixes time stamp counter (TSC) issues with dual-core AMD processors such as the Athlon 64 X2 and Opteron. The AMD Dual-Core Optimizer utility is a driver that synchronizes the time stamp counter on both processor cores and improves game compatibility and performance. Time stamp counter issues occur in older games that are incompatible with multithreading and would run too fast or out of sync.

Issues also occur in newer games and applications that have compatibility issues with processor affinity like Need For Speed: Most Wanted. Affinity issues typically required users to bring up the task manager and set the processor affinity manually or performance would suffer dramatically.

The AMD Dual-Core Optimizer utility could possibly be the rumored “Reverse Hyper-Threading” patch that would improve single thread application and games performance by having dual-core processors show up as a single core processor in applications. AMD has declined to comment on "Reverse Hyper-Threading."

AMD’s Dual-Core Optimizer utility version 1.0 is available from AMD’s website. The utility release notes shows it as being released on March 22nd, 2006 which is strange as AMD has made no mention of the utility publicly.  The utility also installed on Core Duo and Opteron systems.

Comments     Threshold


This article is over a month old, voting and posting comments is disabled
WTF? It works on Intel's Core-Duo?!?
By pcmodem on 7/4/2006 3:10:21 AM , Rating: 2
The article author wrote:
"The utility also installed on Core Duo and Opteron systems.

WTF, AMD is now releasing updates for Intel?



Cheers,
PCM





RE: WTF? It works on Intel's Core-Duo?!?
By Furen on 7/4/2006 3:15:42 AM , Rating: 2
I havent heard of Core Duo (or the Pentium D, for that matter) having the problems mentioned so all it would mean is that the driver does not check for an AMD CPU before installing.


RE: WTF? It works on Intel's Core-Duo?!?
By Griswold on 7/4/2006 3:26:04 AM , Rating: 2
I have seen a P-D box running a game (WoW) at superspeed. It was solved with the /usepmtimer switch in Boot.ini. Intel (at least their netburst stuff) is not immune to the time stamp counter problem with windows and linux.


By Chadder007 on 7/4/2006 1:25:53 PM , Rating: 2
Sorta my situation here...if I have Hyperthreading turned on I have issues with my system.


RE: WTF? It works on Intel's Core-Duo?!?
By Tsuwamono on 7/4/2006 11:50:22 AM , Rating: 2
reverse hyperthreading is an AMD thing man...


RE: WTF? It works on Intel's Core-Duo?!?
By bobdelt on 7/4/2006 12:37:55 PM , Rating: 2
This isn't reverse hyperthreading... man.


RE: WTF? It works on Intel's Core-Duo?!?
By Tsuwamono on 7/4/2006 3:52:49 PM , Rating: 2
said right in the original post thatt he utility could be linked to reverse hyperthreading.


RE: WTF? It works on Intel's Core-Duo?!?
By Tsuwamono on 7/4/2006 3:53:57 PM , Rating: 2
quote:
The AMD Dual-Core Optimizer utility could possibly be the rumored “Reverse Hyper-Threading” patch that would improve single thread application and games performance by having dual-core processors show up as a single core processor in applications. AMD has declined to comment on "Reverse Hyper-Threading."


*cough*


RE: WTF? It works on Intel's Core-Duo?!?
By mertesn on 7/5/2006 3:56:30 AM , Rating: 2
quote:
reverse hyperthreading is an AMD thing man...


What pcmodem was getting at was hyperthreading is an Intel technology. AMD has created a utility to sort of create an abstraction layer for hyperthreading and dual-core processors because currently most games cannot take advantage of either.

I'm surprised Intel didn't beat AMD to the punch on this one. As soon as benchmarks came out that showed a disadvantage in framerates and/or playability issues, they should have released something similar.


By xdrol on 7/10/2006 7:51:36 AM , Rating: 2
HyperThreading is an AMD patent (or what, I don't care the legal mubojumbo). Just they never used it.

Intel and AMD have a cross-lisence agreement (each can use the other's tech after x months), so Intel has adopted it. (Netburst needed it badly BTW.)


By bobdelt on 7/5/2006 5:03:55 PM , Rating: 2
"Could" and "Is" are very different things!

This utility has been out for a while and fixes a bug. This isn't AMD's secret reverse-hyperthreading or every review site on the planet would be doing benches.


RE: WTF? It works on Intel's Core-Duo?!?
By TomaX925 on 7/4/2006 5:35:35 AM , Rating: 2
WHEN you put /usepmtimer into boot.ini THEN "time stamp counter" is used for timing. Since Intels 6xx series this counter always runs with the nominal clock frequency regardless of the power state = no problems.
If a Pentium D system has timer problems I bet it uses an Nforce 4 chipset ?
regards
TEK




RE: WTF? It works on Intel's Core-Duo?!?
By Griswold on 7/4/2006 6:59:41 AM , Rating: 2
quote:
WHEN you put /usepmtimer into boot.ini THEN "time stamp counter" is used for timing.


/usepmtimer forbids windows to use the hardware TSC.

Dont remember if that board had a nf4 chipset, I'd have to ask that guy.


RE: WTF? It works on Intel's Core-Duo?!?
By TomaX925 on 7/4/2006 8:18:56 AM , Rating: 2
Weel I'm not 100% sure, but please read this:
http://www.microsoft.com/whdc/system/CEC/mm-timer....
Do you have further documentation on the /usepmtimer?
Anyway, I had timing problems with a Pentium D that vanished when my NForce4 motherboard went up in smoke (no kidding!). I replaced it with an Intel D945 motherboard that uses a High precision Event Timer.
regards
Tomas


RE: WTF? It works on Intel's Core-Duo?!?
By Griswold on 7/4/2006 9:50:38 AM , Rating: 2
I had not much luck finding further documentation about the /usepmtimer switch at microsoft. The link you provided mentions the PM clock - could be the same and would support what I said: PM timer != TSC.

AMD dualcore's culprit is the TSC-drift and /usepmtimer is the first step to solve the issue - I actually think it has been the only reliable step until the release of this new patch/driver from AMD.

As for the chipset. Could very well be that the Intel Edition NF4 chipset works (too) much like it does on the AMD side with its STPCLK, P- and C-state signals and thus provokes the problem. Cant really comment on that.


RE: WTF? It works on Intel's Core-Duo?!?
By TomaX925 on 7/4/2006 10:31:09 AM , Rating: 2
Personally I think AMD or Nvidia should have informed us more openly a long time ago.
This new AMD patch actually puts in the /usepmtimer into the boot.ini if its not there already. Then it installs a driver to synchronize the TSC's. What would be the point
if the TSC's are disabled?
My information is that /usepmtimer were originally for Intel cpu's with fixed TSC's. It stops the use of a buggy RTC clock in the motherboard. How do I know it to be true when no official explanation exists? I don't.
Anyway, I believe the problem is solved for all AMD users out there, so we should all be happy.

Best regards
Tomas


RE: WTF? It works on Intel's Core-Duo?!?
By Griswold on 7/4/2006 10:59:32 AM , Rating: 2
quote:
Personally I think AMD or Nvidia should have informed us more openly a long time ago.


AMD did comment on the issue a couple months ago and promised improved hardware TSC in the future. No clue if thats already in the current AM2 line or pops up in a later revision.



By TomaX925 on 7/4/2006 11:48:35 AM , Rating: 2
Quote:
AMD did comment on the issue a couple months ago and promised improved hardware TSC in the future.

Well maybe they did, but they did it in such a technical manner that many users are still in the dark.

Lets sum it up:
There is 5 (not 4 as I thought) timers in a PC?
The PIT, the RTC, the APIC, the PM = ACPI timer AND the TSC.
Then both the APIC the ACPI and the TSC's can be buggy.
AMD's new driver must then be for programs that access TSC's directly??
/usepmtimer forces the OS to NOT use the TSC's for housekeeping.

AAARRRGGG
When will the HPET clean up this mess?
best regards
Tomas


By PrinceGaz on 7/4/2006 12:10:13 PM , Rating: 2
Yes, I can confirm it adds /usepmtimer to the boot.ini if it is not already there, because I removed it from mine just before installing the utility to see if it would add it. Sure enough it was there again after installing.


Help a confused newbie.
By Boyo on 7/4/2006 1:51:47 PM , Rating: 2
Is this new optimizer different from the "Hotfix" download that uses the pmtimer in the boot.ini??? I have that downloaded along with a 1.3.2.0 driver. Should I get this download as well........drivers are a confusing thing. Try going to Creative and figure their mess out.




RE: Help a confused newbie.
By Wonga on 7/4/2006 2:10:28 PM , Rating: 2
LOL, if you think Creative's drivers are bad, just wait til you try their RMA process. After 20 days of hearing nothing, I ask the progress with replacing my faulty Zen, only to hear they "don't have any in stock". That strange, cos I could have sworn they made them! After I bit more complaining they offer to "upgrade" me to a Zen Sleek instead. Funny how you have to really kick up a fuss before anything at all gets done. I think that'll be the last time I go Creative. Even their customer feedback page gives you no response...