AMD Dual Core problems?

X

XFs

New Member
When people talk about Dual Core problems,
they talk about AMD Dual Core. Right?

I'm staying away from Intel Dual Core CPUs,
but they never had any problems. Right?
 
Ok for one, you dont need 3 threads. For 2, alot of cpus have problems, i dont thinks its AMD specifically, i havent had one problem with my X2 and it overclocks like a demon. So no, its not just AMD.
 
When new case sees problems with a dual core model cpu the most common advice given for correction is to update the bios on a new board. Many boards will simply not support the faster models without the newer revision.
 
The AMD dual core has several problems actually. If you do a search you will find them. One of the most notable is the need for a patch to make the dual core run properly.

There's nothing that can't be fixed with a little bit of due diligence that I know of.
 
Microsoft developed a hotfix for multiple processor boards(boards with two not one cpu) that is intended for use when you see drastic performance losses. The article is seen at http://support.microsoft.com/?id=896256

How to disable the new performance state policy behavior

loadTOCNode(3, 'moreinformation');Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

After you install the hotfix that is described in this article, you may use registry settings to disable the new performance state policy behavior. To do this, follow these steps: 1.Click Start, click Run, type regedit, and then click OK.2.Right-click HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager, point to New, and then click Key.3.Type Throttle for the new key name.4.Right-click Throttle, point to New, and then click DWORD Value.5.Type PerfEnablePackageIdle for the value name.6.Right-click PerfEnablePackageIdle, and then click Modify.7.In the Value data box, type 0. Make sure that Hexadecimal is selected in the Edit DWORD Value dialog box, and then click OK.

Note You can type 1 in the Value data box to enable the new performance state policy behavior.8.Quit Registry Editor.
 
StrangleHold said:
As fas as I know thats for Dual processors not dual cores
Click to expand...

Read it carefully now.
Windows XP SP2 Dual Core Performance FixPosted by: Chris_Tom on Friday, October 07, 2005 - 10:35 AM
Microsoft has released a hotfix to improve performance on dual core systems. It fixes a possible decrease in performance during demand based switching. Cool 'n Quiet must be enabled for the fix to work, and Microsoft will only send you the hot fix if you have been experiencing the problem. The issue is how do you know if you are or not? AMD told me this can have an impact on some games although I've not heard of any problems, and my main gaming system is an Athlon 64 X2 3800+ at the moment. Here are some additional details. Possible decrease in performance during demand-based switching
Demand-based switching refers to the changing of ACPI processor performance states in response to system workloads. For example, demand-based switching can change voltage and frequency in response to system workloads. Windows XP processor power management implements demand-based switching through the Adaptive processor throttling policy. The Adaptive processor throttling policy dynamically and automatically adjusts the processor current performance state in response to the computers CPU use. The Adaptive processor throttling policy works without user intervention.

If you run Windows XP on a computer that has multiple processors, single-threaded workloads may move across available CPUs. This migration behavior is a natural artifact of how Windows schedules work across available CPU resources. However, if a computer is running with the Adaptive processor throttling policy, this thread migration may cause problems. For example, the Windows kernel power manager may not be able to correctly calculate the optimal target performance state for the processor. This problem occurs because the individual logical or physical processor core may appear to be less busy than the processor package actually is. On performance benchmarks that use single-threaded workloads, this artifact may become evident in the following ways:
• Decreased performance
• A high degree of variance between successive runs of the same benchmark tests
The hotfix that is described in this article includes changes to the kernel power manager. These changes make it possible to track CPU use across the processor package. This tracking helps calculate an increased target performance state.

Note This solution favors performance gains over power savings. Although benchmark performance scores may improve, battery life could be negatively affected. Therefore, this kernel policy change must be enabled in the registry to allow for maximum flexibility.
I would be interested to know if this actually effected anyone out there.

http://www.amdzone.com/modules.php?...=article&sid=3951&mode=thread&order=0&thold=0

This is only one original reference to using the same hotfix for dual cored models seen in late 2005. http://support.microsoft.com/?id=896256
 
There may or may not be a registry edit for the 64bit version that is different for the one seen there. If you see the same values in the 64bit version this could be trried there. The fix there is shown as applying to
APPLIES TO

•Microsoft Windows Server 2003, Standard x64 Edition•Microsoft Windows Server 2003, Enterprise x64 Edition•Microsoft Windows XP Service Pack 2, when used with: Microsoft Windows XP Home Edition Microsoft Windows XP Professional•Microsoft Windows XP Tablet PC Edition 2005

This was the only article ever seen on a special reg edit for correcting performance problems. MSDN may have one for the 64bit version buried deep in there somewhere. Generally when moving up from a single to dual cored cpu a download of the latest bios version sees something like this corrected. The newer version offers the support for the higher end model cpus.
 
That reg edit is also applied to systems running dual cored cpus as well as dual processor boards. Microsoft published that article when problems were first being seen with newer dual cored models. This is only applied when performance problems are seen. Updated bios revisions have now improved support for the X2s, FX60, and dual cored Opteron models.
 
PC eye said:
That reg edit is also applied to systems running dual cored cpus as well as dual processor boards. Microsoft published that article when problems were first being seen with newer dual cored models. This is only applied when performance problems are seen. Updated bios revisions have now improved support for the X2s, FX60, and dual cored Opteron models.
Click to expand...

Note This problem also applies to x64-based versions of Microsoft Windows Server 2003. However, this article and its associated private hotfix ((are not intended to resolve timing problems in games and other applications that run on AMD dual-core)) computers.
 
StrangleHold said:
Note This problem also applies to x64-based versions of Microsoft Windows Server 2003. However, this article and its associated private hotfix ((are not intended to resolve timing problems in games and other applications that run on AMD dual-core)) computers.
Click to expand...

Computers that are running Windows XP Service Pack 2 and that are equipped with multiple processors that support processor power management features may experience decreased performance

Article ID:896256Last Review:August 11, 2006Revision:4.0

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

http://support.microsoft.com/kb/256986/ Description of the Microsoft Windows registry

On This Page


SYMPTOMS

Computers that are equipped with multiple processors that support processor power management features, such as Advanced Configuration and Power Interface (ACPI) processor performance states, require Microsoft Windows XP Service Pack 2 (SP2). Additional updates are available to optimize performance and behavior on computers that are running Windows XP SP2. Without these updates, computers that are equipped with these power management-capable, mobile, dual-core processors may experience decreased performance or unexpected behavior.

Note This problem also applies to x64-based versions of Microsoft Windows Server 2003. However, this article and its associated private hotfix are not intended to resolve timing problems in games and other applications that run on AMD dual-core computers. For more information about performance issues on dual-core computers, click the following article number to view the article in the Microsoft Knowledge Base:

http://support.microsoft.com/kb/909944/ Game performance may be poor on a Windows XP-based computer that is using a dual-core processor

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows XP service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. Prerequisites

loadTOCNode(3, 'resolution');No prerequisites are required. Restart requirement

loadTOCNode(3, 'resolution');You must restart the computer after you apply this hotfix. Hotfix replacement information

loadTOCNode(3, 'resolution');This hotfix does not replace any other hotfixes. File information

loadTOCNode(3, 'resolution');The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Version Size File name--------------------------------------------------------------28-Sep-2005 23:35 5.1.2600.2765 134,272 Halmacpi.dll 29-Sep-2005 00:02 5.1.2600.2765 2,136,064 Ntkrnlmp.exe 28-Sep-2005 23:35 5.1.2600.2765 2,057,344 Ntkrnlpa.exe 28-Sep-2005 23:35 5.1.2600.2765 2,015,744 Ntkrpamp.exe 29-Sep-2005 00:04 5.1.2600.2765 2,180,096 Ntoskrnl.exe 28-Sep-2005 23:32 5.1.2600.2765 30,720 Arpidfix.exe

STATUS

loadTOCNode(1, 'status');Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

loadTOCNode(1, 'moreinformation');Windows XP SP2 is required on computers that have multiple CPUs that support ACPI processor performance states. This requirement includes computers that support the following items: •Multiple physical sockets•Multiple-core designs•Multiple logical threads, such as Intel hyper-threading technologyBecause Windows XP was not originally designed to support performance states on multiprocessor configurations, changes are required to correctly realize this support on multiprocessor systems. Windows XP Service Pack 2 includes the required changes to the kernel power manager. These changes make sure that Windows XP correctly functions on multiprocessor systems with processor performance states.

This hotfix also addresses the following issues on computers that have multiple processors that support processor performance states: •A possible decrease in performance on single-threaded workloads when processor performance states are using demand-based switching.•The synchronization of the processor Time Stamp Counter (TSC) registers across processors when you use the ACPI Power Management timer on multiprocessor systems. •ACPI C-state promotion and demotion issues in the kernel power manager.
Hotfix details

loadTOCNode(2, 'moreinformation');Possible decrease in performance during demand-based switching

loadTOCNode(3, 'moreinformation');Demand-Based Switching (DBS) is the use of ACPI processor performance states (dynamic voltage and frequency scaling) in response to system workloads. Windows XP processor power management implements DBS by using the adaptive processor throttling policy. This policy dynamically and automatically adjusts the processor’s current performance state in response to system CPU use without user intervention.

When single-threaded workloads run on multiprocessor systems that include dual-core configurations, the workloads may migrate across available CPU cores. This behavior is a natural artifact of how Windows schedules work across available CPU resources. However, on systems that have processor performance states that run with the adaptive processor throttling policy, this thread migration may cause the Windows kernel power manager to incorrectly calculate the optimal target performance state for the processor. This behavior occurs because an individual processor core, logical or physical, may appear to be less busy than the whole processor package actually is. On performance benchmarks that use single-threaded workloads, you may see this artifact in decreased performance results or in a high degree of variance between successive runs of identical benchmark tests.

This hotfix includes changes to the kernel power manager to track CPU use across the processor package. These changes enable visibility into the true activity level of a CPU complex and therefore help correctly calculate an increased target performance state.

Note This solution favors performance gains over power savings. Although benchmark performance scores may improve, battery life could be negatively affected. Accordingly, this kernel policy change may be disabled by a registry key to allow for maximum flexibility. How to disable the new performance state policy behavior

loadTOCNode(3, 'moreinformation');Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

After you install the hotfix that is described in this article, you may use registry settings to disable the new performance state policy behavior. To do this, follow these steps: 1.Click Start, click Run, type regedit, and then click OK.2.Right-click HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager, point to New, and then click Key.3.Type Throttle for the new key name.4.Right-click Throttle, point to New, and then click DWORD Value.5.Type PerfEnablePackageIdle for the value name.6.Right-click PerfEnablePackageIdle, and then click Modify.7.In the Value data box, type 0. Make sure that Hexadecimal is selected in the Edit DWORD Value dialog box, and then click OK.

Note You can type 1 in the Value data box to enable the new performance state policy behavior.8.Quit Registry Editor. Correct TSC synchronization

loadTOCNode(3, 'moreinformation');On some operating systems, the processor TSC may change the rate at which it counts. Additionally, the processor TSC may stop counting when specific processor power management features are used. On computers that have multiple processors, the TSC is typically the operating system hardware timer that supports calls to the kernel KeQueryPerformanceCounter function. When TSC does not increment monotonically, system components that use the kernel KeQueryPerformanceCounter function may not work correctly. To address this problem, Microsoft makes it possible for the ACPI Power Management Timer to be used as the operating system timer that supports the kernel KeQueryPerformanceCounter function. However, some programs may directly access the TSC by bypassing the Windows timer APIs. The multiple-processor Hardware Abstraction Layer (HAL) makes sure that the TSC registers on all processors on a multiple-processor computer remain closely synchronized. Therefore, access by system software that may be directed to different processors does not return different results. This change makes sure that the multiple-processor HAL continues to correctly synchronize the TSCs across all processors on a computer, even if the ACPI power management timer is used as the operating system hardware timer. Correct C-state promotion and demotion

loadTOCNode(3, 'moreinformation');This change corrects issues in the kernel power manager to correctly handle processor ACPI C-state promotion and demotion on multiprocessor systems.

MORE INFORMATION

For more information about a related topic, click the following article number to view the article in the Microsoft Knowledge Base: 835730

(http://support.microsoft.com/kb/835730/) Sound may play slowly or music may not play continuously in Windows XP or Windows 2000
For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base: 824684

(http://support.microsoft.com/kb/824684/) Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.


APPLIES TO

•Microsoft Windows Server 2003, Standard x64 Edition•Microsoft Windows Server 2003, Enterprise x64 Edition•Microsoft Windows XP Service Pack 2, when used with: Microsoft Windows XP Home Edition Microsoft Windows XP Professional•Microsoft Windows XP Tablet PC Edition 2005
 
That's what it was originally intended for prior to AMD coming out with dual core cpus. Intel is bound to see some issues with their Core 2 duos now out. When XP first came out upto SP2 no one had a dual core cpu. Several articles that came out in late '05 and early '06 point to the registry mod here as a means to solve performance losses seen overall on XP systems.
 
You must log in or register to reply here.
Back
Top