Solving High Voltages and Clockspeeds in Ryzen 3rd Gen, Study Guides, Projects, Research of Advanced Computer Architecture

Why software monitoring tools report unexpectedly high voltages and clockspeeds in 3rd gen ryzen processors. The root cause is identified as certain popular applications making frequent requests for high performance and power state from the processor. The document also introduces uefi cppc2, a new capability in 3rd gen ryzen processors that puts the processor firmware in charge of clockspeed selections. A solution through a new amd chipset driver that relaxes the processor's sensitivity level to boost requests while running desktop apps.

Typology: Study Guides, Projects, Research

2021/2022

Uploaded on 09/27/2022

gilian
gilian 🇬🇧

4.6

(11)

228 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Hello! Over the past few weeks, your reports were instrumental in assisting us to root cause why
software monitoring tools were reporting unexpectedly high voltages and clockspeeds at the Windows
desktop. We now have a comprehensive update to share with you on this topic. We also have some
good news for Destiny 2 players!
ROOT CAUSE ANALYSIS
Our analysis indicates that certain pieces of popular software, which are widely considered to be “low
CPU load” applications, frequently make indirect requests for the highest performance and power state
from the processor. These everyday applications include popular browsers, chat applications,
monitoring tools, mouse/keyboard utilities, fan and AIO controllers, driver background services, and
more.
Concurrently, 3rd Gen Ryzen™ Processors include a new capability called Collaborative Power and
Performance Control (“UEFI CPPC2”). This puts the processor firmware in charge of its own clockspeed
selections at all times, and such selections may be done as rapidly as one millisecond (1ms).
Let’s add it up: If a system is running many of these “low-load-but-not-really” applications at the same
time, and the CPU is designed to be more responsive than ever, then the CPU may repeatedly interpret
their combined activity as a frequent need for boost. The stage is set for some curious behavior.
Taking a look with an oscilloscope, you can observe the frequencies and voltages rapidly bouncing
between low and high conditions hundreds of times per second (Figure 1 below)far faster than any
software monitoring tool can observe. The result: software monitoring tools may report that the
processor is “stuck” in a high state.
Figure 1: This diagram shows 283ms of time elapsed between orange circles A and B in the chart. You can see the processor
(jagged line) voltage rapidly bouncing between 1.072V and 1.464V--dozens of times in just a quarter second. The desktop
applications (chat, browser, game launcher) running on this system are collectively making rapid boost and idle requests.
As users add additional background tools and services to the system, this issue can exacerbate. Given
that many enthusiasts often keep a monitoring tool, browser, chat app, and peripheral utility open at all
times, it becomes relatively easy to encounter the conditions we’re describing.
Bottom line: Many tasksgaming, video, browsing, word processingdeserve high responsiveness
from the processor. There are also clear power efficiency benefits to treating workloads with high
frequencies (race-to-idle). But it is also totally fair to say that there can be too much of a good thing.
pf3
pf4

Partial preview of the text

Download Solving High Voltages and Clockspeeds in Ryzen 3rd Gen and more Study Guides, Projects, Research Advanced Computer Architecture in PDF only on Docsity!

Hello! Over the past few weeks, your reports were instrumental in assisting us to root cause why software monitoring tools were reporting unexpectedly high voltages and clockspeeds at the Windows desktop. We now have a comprehensive update to share with you on this topic. We also have some good news for Destiny 2 players!

ROOT CAUSE ANALYSIS

Our analysis indicates that certain pieces of popular software, which are widely considered to be “low CPU load” applications, frequently make indirect requests for the highest performance and power state from the processor. These everyday applications include popular browsers, chat applications, monitoring tools, mouse/keyboard utilities, fan and AIO controllers, driver background services, and more. Concurrently, 3 rd^ Gen Ryzen™ Processors include a new capability called Collaborative Power and Performance Control (“UEFI CPPC2”). This puts the processor firmware in charge of its own clockspeed selections at all times, and such selections may be done as rapidly as one millisecond (1ms). Let’s add it up: If a system is running many of these “low-load-but-not-really” applications at the same time, and the CPU is designed to be more responsive than ever, then the CPU may repeatedly interpret their combined activity as a frequent need for boost. The stage is set for some curious behavior. Taking a look with an oscilloscope, you can observe the frequencies and voltages rapidly bouncing between low and high conditions hundreds of times per second (Figure 1 below)—far faster than any software monitoring tool can observe. The result: software monitoring tools may report that the processor is “stuck” in a high state. Figure 1 : This diagram shows 283ms of time elapsed between orange circles A and B in the chart. You can see the processor (jagged line) voltage rapidly bouncing between 1.072V and 1.464V--dozens of times in just a quarter second. The desktop applications (chat, browser, game launcher) running on this system are collectively making rapid boost and idle requests. As users add additional background tools and services to the system, this issue can exacerbate. Given that many enthusiasts often keep a monitoring tool, browser, chat app, and peripheral utility open at all times, it becomes relatively easy to encounter the conditions we’re describing. Bottom line: Many tasks—gaming, video, browsing, word processing—deserve high responsiveness from the processor. There are also clear power efficiency benefits to treating workloads with high frequencies (race-to-idle). But it is also totally fair to say that there can be too much of a good thing.

THE IMMEDIATE SOLUTION

Immediately available for download, a new AMD chipset driver (version 1.07.29.xxx ) is designed to relax the processor’s sensitivity level to boost requests while running desktop apps like those described above. It will modify the processor’s behavior in two key ways:

  1. We will be adjusting the sensitivity of CPPC2. If you are running the Windows 10 May 2019 Update, 3rd Gen Ryzen processors will now use traditional 15ms clock selection intervals when at idle or low load. This has the effect of filtering many of these short-lived or undesirable boost requests, enabling the processor to be more dormant when the workloads are light.
  2. We will also be adjusting how the processor behaves in low or idle workloads. If a processor core is not power gated and sleeping, the processor core will sit at 99% of base clock for low or idle workloads. For example: an AMD Ryzen™ 7 3700X base clock is 3600MHz, so you would see “idle” frequencies around 3564MHz ± 0.08%. This 99% value keeps the active core on a razor’s edge so that your non-trivial applications can easily trigger CPU boost. While boosted, the processor will still control frequency selection in 1ms intervals. These changes are implemented in Chipset Driver 1.07.29 , available for download now. The chipset driver installer will automatically install and enable a new AMD Ryzen™ Balanced power plan for all 3rd Gen AMD Ryzen customers. Users of any other Ryzen™ CPU will not receive, and do not need, this plan. Altogether, this new power plan is designed to make the processor more relaxed when the loads are intermittent or light (Figure 2 below), without taking away from the processor’s ability to respond to sustained workloads like games and content creation. It should have the effect of solving the voltage and frequency behaviors you’ve reported to us over the past few weeks. We truly appreciate your reports and messages, as they were instrumental in diagnosing and resolving this issue. Figure 2 : AFTER the new power plan, the same 28 3 ms time window shows a dramatically different behavior for the same application(s). Expected 1. 464 V peaks now only last for about 25ms, suggesting there was a brief and bursty workload that ended and allowed for idle. You can also see valleys in the chart of 168mV, suggesting the CPU was broadly power gating at these times. And, most importantly, you see general residency around 1.072V suggesting the cores are awake but handling light workloads.

SEE FOR YOURSELF

A new build of AMD Ryzen Master (version 2.0. 1 .12 33 ) is also available for download today, and it takes all of the above changes into account. If you’re new to this utility: Ryzen™ Master is our first-party monitoring and tuning application that can help you observe the behavior of your PC and, if desired, tweak the performance as well. In addition, the tool has been refined with two critical changes concerning voltage and temperature monitoring. For temperatures:

  • OLD BEHAVIOR: Report the highest temp (“instantaneous temperature”) of any sensor in the whole CPU, no matter how isolated or brief. This approach overstated the prevalence and significance of fleeting peaks, which artificially inflated temperature reports by up to 30°C above the true silicon conditions.
  • NEW BEHAVIOR: Report a short-duration rolling average of all temp sensors in the chip. This model will give you a holistic view of what the processor is doing across cores, cache, bus interfaces, etc. It’s the closest any software monitoring tool can come to portraying the true thermal conditions of the chip, and it’s the same model our own Precision Boost 2 algorithm uses to make temperature-related boost decisions. For voltage:
  • OLD BEHAVIOR: Report the highest transient voltage in the whole CPU, no matter how isolated or brief. This, too, overstated the prevalence and significance of fleeting peaks, which artificially inflated voltage reports by as much as 800mV.
  • NEW BEHAVIOR: Report the average voltage requested of the regulators, which presents a “whole chip” view that factors in sleeping cores, idle cores, and active cores. This is the closest any software monitoring tool can come to portraying the true electrical conditions of the chip, and it’s the same model our own Precision Boost 2 algorithm uses to make electrical-related boost decisions. Altogether, this version of AMD Ryzen Master will give you an accurate view of what your 3rd^ Gen AMD Ryzen Processor is doing, using the same sources and methods utilized by our on-chip firmware and internal monitoring tools. ADDITIONALLY: We also intend to release new developer documentation that enables third-party tools to take the same measurements, so you can continue to rely on your favorite third-party apps after they’re updated. We will be contacting utility vendors directly with more details when the documentation is ready.

GOOD NEWS FOR DESTINY™ 2 PLAYERS

Destiny 2 Players with 3rd^ Gen AMD Ryzen™ systems can also get back into the game! Customers who install chipset driver version 1.07.29 (or later) can once again take the fight to the Red Legion. This driver contains a beta solution for Destiny 2, which resolves an issue where users were unable to launch the game. A more comprehensive fix will be deployed in BIOS updates for Socket AM4 motherboards in order to address other software affected by the same underlying issue. Motherboard BIOSes based on AGESA 1003ABB will contain this update.

GOING FORWARD

Once again: we genuinely appreciate the time, reports, and collaboration from the enthusiast community on the topics in this blog. You were a critical piece of our effort to understand and develop solutions. But we’re not finished! Successive AGESA releases are already in development and, as we near release, we’ll continue to use this format to keep you apprised of features and timelines. And, on a final note, new BIOSes based on the impending AGESA 1003ABB will also resolve the “Event 17, WHEA-Logger” warnings in the Windows Event Log. These warnings indicate that the system successfully corrected a trivial error in a data packet sent between two PCI Express® devices. PCIe devices can transmit thousands of packets per second, and it is typical for a few of them to require a correction or retry. As such, it is customary to suppress these unhelpful/routine messages in the log to limit the error reporting scope to errors that require attention and action. AGESA 1003ABB will make that change. If you have questions, comments, or concerns about any of the changes described in this blog, please do not hesitate to open an online service request at AMD.com.