Windows · AMD Ryzen monitoring and tuning
Private repo · coming soonZenStation
Tuning a Ryzen usually means having several programs open. ZenStation puts them in one window: clocks, temperatures, power, memory timings, power limits, Curve Optimizer, P-states and a stress test.
Nothing it writes to the processor is permanent. After a restart the BIOS values are back. From the Memory page you can send your running timings to the shared timings page.
Application screenshots
Select a screenshot to enlarge it.
CPU view
A web preview based on the current CPU layout, using sample values. It includes the effective clock and core power columns updated on 6 October 2026.
Appearance and settings
An application development screenshot showing language, theme and refresh settings.
Sensor view
The actual WPF sensor control; sensor values in this development screenshot are sample data.
CPU compatibility
Processor identification, sensors, memory reading and tuning support are evaluated separately. Recognizing a CPU does not mean every feature is supported; physical validation is not complete for all devices.
| CPU / platform | Validation | Coverage |
|---|---|---|
| Ryzen 5 3400G · Picasso | Local validation | DDR4 and monitoring; tested tuning operations have device-specific records. |
| Early Ryzen / Zen+ · Matisse / Vermeer | Source and test coverage | DDR4, cores/CCDs and desktop limits; availability varies by model. |
| Raphael / Granite Ridge · X3D | Source and test coverage | DDR5, SVI3 and version-specific PM fields; X3D tuning is evaluated separately. |
| Raven / Picasso / Dali · Renoir / Lucienne / Cezanne | APU coverage | Desktop/mobile packages, memory and power limits are evaluated separately. |
| Rembrandt / Phoenix / Hawk Point | Mobile coverage | PM versions and iGPU fields vary by model. |
| Dragon Range / Fire Range HX | Further validation needed | Shared desktop silicon does not validate every mobile tuning operation. |
| Strix / Krackan / Strix Halo | Development and test coverage | PM sizes, topology and memory maps need device-specific validation. |
Report a bug
Describe the issue in a few steps. Your CPU model and app version help me understand which device is affected.
What's in it
- Overview: core clocks, temperature, voltage, power and limits
- Sensors: CPU, graphics card, motherboard, drive and memory sensors in one list
- Memory: DDR4/DDR5 timings, impedances, SPD, latency and bandwidth test
- CPU tuning: PBO limits, Curve Optimizer, P-states and profiles
- Graphics: temperatures, clocks and power, memory chip temperatures on NVIDIA
- Fans: a curve or a fixed speed
- Stability: stress test and WHEA hardware errors
- Game overlay: FPS and the sensors you pick
Built on
ZenStates-Core (opens in a new tab) (irusanov), LibreHardwareMonitor (opens in a new tab) and PawnIO (opens in a new tab) (namazso). The full list is on the app's About page.
Technical notes
Problems, data sources and measurement methods from developing ZenTimings and ZenStation.
DDR5 · APOB
Reading tCCD_L from APOB
Reading the tCCD_L family in the ZenTimings fork: memory-controller registers, APOB data and layouts that change with BIOS versions.
2 min read
Read the articleRyzen · SMU
Ryzen sensors: similar labels, different measurements
ZenStation sensor notes: SMU PM versions, clock and voltage sources, sampling differences and a local Ryzen 5 3400G comparison.
2 min read
Read the articleRAM · Benchmark
What does a memory benchmark measure?
Latency, bandwidth, caches, working sets and repeatability in the ZenTimings and ZenStation memory benchmarks.
2 min read
Read the article