mathoudebine / mathoudebine/turing-smart-screen-python
CPU Frequency for AMD Ryzen 9 9950X3D calculation wrong
Nobody has claimed this yet.
- Dominant language
- Rich Text Format
- Stars
- 2.3k
- Forks
- 412
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 7
Description
Describe the bug
While the CPU frequency calculation in the Windows Task Manager shows the correct value (i.e. ~4,3 GHz) my Turing Screen shows a value more than 3 times (i.e. ~13.5 GHz, see screenshot below)
Expected behavior
Show the same value (or even just close) for CPU frequency in Task Manager
Screenshots / photos of the Turing screen
Screenshots / photos of Task Manager
Environment:
- Turing 3.5
- turing-smart-screen-python 3.9.1
- LibreHardwareMonitorLib 0.9.4.0
- Windows 11
- Python 3.13.2
- CPU: AMD Ryzen 9 9950X3D
Additional context
I'm a bit unsure if this is a bug with the calculation of the frequency in sensors/sensor_librehardwaremonitor.py or if this is a bug with librehardware in general, so if it is a general bug let me know and I'll open an issue over there
Running test_librehardwaremonitor.py with just the CPU active gives the following output:
Found LibreHardwareMonitorLib 0.9.4.0
Found HidSharp 2.1.0.0
Cpu | AMD Ryzen 9 9950X3D | /amdcpu/0
Load | CPU Core #1 | 55.47968292236328
Load | CPU Core #2 | 11.079681396484375
Load | CPU Core #3 | 11.62559986114502
Load | CPU Core #4 | 12.471681594848633
Load | CPU Core #5 | 11.50783920288086
Load | CPU Core #6 | 11.161602020263672
Load | CPU Core #7 | 11.545598983764648
Load | CPU Core #8 | 11.121922492980957
Load | CPU Core #9 | 11.843198776245117
Load | CPU Core #10 | 11.116802215576172
Load | CPU Core #11 | 11.460476875305176
Load | CPU Core #12 | 11.081600189208984
Load | CPU Core #13 | 55.74143981933594
Load | CPU Core #14 | 11.09887981414795
Load | CPU Core #15 | 11.621761322021484
Load | CPU Core #16 | 12.015998840332031
Load | CPU Core #17 | 11.532801628112793
Load | CPU Core #18 | 11.113601684570312
Load | CPU Core #19 | 11.851519584655762
Load | CPU Core #20 | 11.838722229003906
Load | CPU Core #21 | 16.581762313842773
Load | CPU Core #22 | 14.062082290649414
Load | CPU Core #23 | 11.369598388671875
Load | CPU Core #24 | 11.050880432128906
Load | CPU Core #25 | 14.3596830368042
Load | CPU Core #26 | 14.434557914733887
Load | CPU Core #27 | 11.848962783813477
Load | CPU Core #28 | 11.74464225769043
Load | CPU Core #29 | 11.425280570983887
Load | CPU Core #30 | 11.046398162841797
Load | CPU Core #31 | 52.536964416503906
Load | CPU Core #32 | 11.06112003326416
Load | CPU Total | 15.932262420654297
Load | CPU Core Max | 55.74143981933594
Power | Package | 55.274871826171875
Clock | Core #1 | 3014.641357421875
Factor | Core #1 | 43.0
Power | Core #1 (SMU) | 2.1014654636383057
Voltage | Core #1 VID | 0.14374999701976776
Clock | Core #2 | 3014.641357421875
Factor | Core #2 | 43.0
Power | Core #2 (SMU) | 0.1816699057817459
Voltage | Core #2 VID | 0.14374999701976776
Clock | Core #3 | 3014.641357421875
Factor | Core #3 | 43.0
Power | Core #3 (SMU) | 0.12102515250444412
Voltage | Core #3 VID | 0.14374999701976776
Clock | Core #4 | 3014.641357421875
Factor | Core #4 | 43.0
Power | Core #4 (SMU) | 0.12216544151306152
Voltage | Core #4 VID | 0.14374999701976776
Clock | Core #5 | 3014.641357421875
Factor | Core #5 | 43.0
Power | Core #5 (SMU) | 1.7587387561798096
Voltage | Core #5 VID | 0.14374999701976776
Clock | Core #6 | 3014.641357421875
Factor | Core #6 | 43.0
Power | Core #6 (SMU) | 0.10683926939964294
Voltage | Core #6 VID | 0.14374999701976776
Clock | Core #7 | 3014.641357421875
Factor | Core #7 | 43.0
Power | Core #7 (SMU) | 0.10889387130737305
Voltage | Core #7 VID | 0.14374999701976776
Clock | Core #8 | 3014.641357421875
Factor | Core #8 | 43.0
Power | Core #8 (SMU) | 0.10683926939964294
Voltage | Core #8 VID | 0.14374999701976776
Clock | Core #9 | 4241.5302734375
Factor | Core #9 | 60.5
Power | Core #9 (SMU) | 0.11711227893829346
Voltage | Core #9 VID | 0.14374999701976776
Clock | Core #10 | 4241.5302734375
Factor | Core #10 | 60.5
Power | Core #10 (SMU) | 2.01556396484375
Voltage | Core #10 VID | 0.14374999701976776
Clock | Core #11 | 4241.5302734375
Factor | Core #11 | 60.5
Power | Core #11 (SMU) | 2.5600333213806152
Voltage | Core #11 VID | 0.14374999701976776
Clock | Core #12 | 4241.5302734375
Factor | Core #12 | 60.5
Power | Core #12 (SMU) | 0.11300307512283325
Voltage | Core #12 VID | 0.14374999701976776
Clock | Core #13 | 4241.5302734375
Factor | Core #13 | 60.5
Power | Core #13 (SMU) | 2.7227678298950195
Voltage | Core #13 VID | 0.14374999701976776
Clock | Core #14 | 4241.5302734375
Factor | Core #14 | 60.5
Power | Core #14 (SMU) | 0.9106065034866333
Voltage | Core #14 VID | 0.18125000596046448
Clock | Core #15 | 4241.5302734375
Factor | Core #15 | 60.5
Power | Core #15 (SMU) | 0.11405210942029953
Voltage | Core #15 VID | 0.18125000596046448
Clock | Core #16 | 4241.5302734375
Factor | Core #16 | 60.5
Power | Core #16 (SMU) | 7.1852827072143555
Voltage | Core #16 VID | 0.18125000596046448
Temperature | Core (Tctl/Tdie) | 51.87500762939453
Temperature | CCD1 (Tdie) | 37.125
Temperature | CCD2 (Tdie) | 47.125003814697266
Temperature | CCDs Max (Tdie) | 47.125003814697266
Temperature | CCDs Average (Tdie) | 42.125
Clock | Bus Speed | 70.10794067382812
----------------------------------------------------
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with sensors/sensor_librehardwaremonitor.py and run test_librehardwaremonitor.py using the reported AMD Ryzen 9 9950X3D setup. Compare the reported Clock and Factor values with the displayed CPU frequency and determine whether the calculation or LibreHardwareMonitor data is responsible. Done means the Turing Screen shows a frequency close to Windows Task Manager without breaking the existing sensor test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100