- Joined
- Sep 3, 2019
- Messages
- 3,027 (1.75/day)
- Location
- Thessaloniki, Greece
| System Name | PC on since Aug 2019, 1st CPU R5 3600 + ASUS ROG RX580 8GB >> MSI Gaming X RX5700XT (Jan 2020) |
|---|---|
| Processor | Ryzen 9 5900X (July 2022), 150W PPT limit, 79C temp limit, CO -9~14 |
| Motherboard | Gigabyte X570 Aorus Pro (Rev1.0), BIOS F37h, AGESA V2 1.2.0.B |
| Cooling | Arctic Liquid Freezer II 420mm Rev7 with off center mount for Ryzen, TIM: Kryonaut |
| Memory | 2x16GB G.Skill Trident Z Neo GTZN (July 2022) 3600MHz 1.42V CL16-16-16-16-32-48 1T, tRFC:288, B-die |
| Video Card(s) | Sapphire Nitro+ RX 7900XTX (Dec 2023) 314~465W (390W current) PowerLimit, 1060mV, Adrenalin v24.5.1 |
| Storage | Samsung NVMe: 980Pro 1TB(OS 2022), 970Pro 512GB(2019) / SATA-III: 850Pro 1TB(2015) 860Evo 1TB(2020) |
| Display(s) | Dell Alienware AW3423DW 34" QD-OLED curved (1800R), 3440x1440 144Hz (max 175Hz) HDR1000, VRR on |
| Case | None... naked on desk |
| Audio Device(s) | Astro A50 headset |
| Power Supply | Corsair HX750i, 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 (v23H2, OSB 22631.3155) |
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:
