


Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
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
1 / 4
This page cannot be seen from the preview
Don't miss anything!



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!
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.
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:
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:
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.
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.