AMD and Microsoft have officially released fixes to address the reduced performance of compatible AMD processors when running Windows 11. The first issue related to L3 cache latency has been fixed courtesy of a new Windows 11 software update (KB5006746), while the issue pertaining to threads not being properly scheduled on a CPU’s fastest core has been addressed with a new chipset driver package (3.10.08.506). Links to the changelog for KB5006746 and AMD’s new drivers may be found below.
Per AMD’s updated “Windows 11 Performance Variation in Certain Applications on Compatible AMD Processors” support document:
Issue 1: Measured and functional L3 cache latency may increase for some applications.
- A Windows 11 software update is now available to address this issue under Microsoft Knowledgebase ID 5006746.
- More information on downloading and installing this update can be obtained under Microsoft article KB5006746.
- Systems with this update applied will enumerate KB5006746 in the Control Panel Programs Programs and Features Installed Updates interface.
Issue 2: UEFI CPPC2 (“preferred core”) may not preferentially schedule threads on a processor’s fastest core.
- An AMD Chipset Driver package is now available to address this issue under version 3.10.08.506.
- Systems with this update applied will report AMD Chipset Software 3.10.08.506 (or newer) within the Apps & Features interface of Windows 11.
- In addition:
- For AMD processors with the “Zen 3” architecture: Systems configured with AMD Chipset Driver 3.10.08.506 (or newer) should report version 188.8.131.52 (or newer) for the AMD.Power.Processor.Settings entry in the Windows 11 Provisioning Packages interface.
- For AMD processors with the “Zen+” or “Zen 2” architectures: Systems configured with AMD Chipset Driver 3.10.08.506 (or newer) should have the AMD Ryzen™ Balanced power plan selected and active in the Control Panel Power Options interface.
AMD goes on to confirm that these fixes fully resolve the performance impacts that users of compatible AMD processors might have been experiencing in certain applications when running Windows 11 build 22000.194