- Joined
- Sep 3, 2019
- Messages
- 3,974 (1.92/day)
- Location
- Thessaloniki, Greece
| System Name | PC on since March 2025, upgraded from 5900X |
|---|---|
| Processor | Ryzen 7 9700X (March 2025), 150W PPT limit, 85C temp limit, CO -25, +100MHz (up to 5.65GHz) |
| Motherboard | Asrock X870E NOVA, BIOS v3.2, AGESA PI 1.2.0.3a Patch A |
| Cooling | Arctic Liquid Freezer II 420mm Rev7 (Jan 2024) with off-center mount for Ryzen, TIM: Kryosheet |
| Memory | 2x32GB G.Skill Trident Z5 RGB (March2025) 6200MT/s 1.42V CL30-36-36-36-28-64 1T, tRFC:500, Hynix A-D |
| Video Card(s) | Sapphire Nitro+ RX 7900XTX (Dec 2023) 314~467W (370W current) PowerLimit, 1060mV, Adrenalin v25.3.1 |
| Storage | NVMe: 990Pro 2TB(OS 25), 980Pro 1TB(22), 970Pro 512(19) / S-III: 850Pro 1TB(15) 860Evo 1TB(20) |
| Display(s) | Dell Alienware AW3423DW 34" QD-OLED curved (1800R), 3440x1440 144Hz (max 175Hz) HDR400/1000, VRR on |
| Case | Thermaltake Core P8 TG Gaming Full Tower, Fans: 9x140mm + 3x120mm |
| Audio Device(s) | Astro A50 headset |
| Power Supply | Corsair HX750i, ATX v2.4, 80+ Platinum, 93% (250~700W), modular, single/dual rail (switch) |
| Mouse | Logitech MX Master (Gen1) |
| Keyboard | Logitech G15 (Gen2) w/ LCDSirReal applet |
| Software | Windows 11 Home 64bit (v24H2, OSBuild 26100.3775), Install March 2025 |
Indeed the lower core clock only corresponds to active cores (Residency C0)
But power plan also makes a difference in core count activity. How many cores are at “active” (C0) state or “halt/power off” states (C1/C6) at any given moment of any load and how cores react to (new) loads. Especially small and short ones.
You can watch over time the Core residency states and the active core count in HWiNFO.
Also, I can’t say it enough, when using HWiNFO sensor window the setting “Snapshot CPU Polling” must be ON at all times. Otherwise CPU parameters are disturbed when the software is polling values and CPU core states and clocks are messed up.
EDIT
Forgot to clarify and it’s related to what @tabascosauz said, that effective clocks on HWiNFO contains all 3 CPU core states (C0/C1/C6) unlike “regular” core clocks that is based on C0 only.
But power plan also makes a difference in core count activity. How many cores are at “active” (C0) state or “halt/power off” states (C1/C6) at any given moment of any load and how cores react to (new) loads. Especially small and short ones.
You can watch over time the Core residency states and the active core count in HWiNFO.
Also, I can’t say it enough, when using HWiNFO sensor window the setting “Snapshot CPU Polling” must be ON at all times. Otherwise CPU parameters are disturbed when the software is polling values and CPU core states and clocks are messed up.
EDIT
Forgot to clarify and it’s related to what @tabascosauz said, that effective clocks on HWiNFO contains all 3 CPU core states (C0/C1/C6) unlike “regular” core clocks that is based on C0 only.
Last edited:
