mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Ryzen 5000 High Voltage #11369
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#11369
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @crashburn162 on GitHub (Dec 6, 2020).
Please provide the following information
qBittorrent version and Operating System
Qbittorrent 4.3.1/4.3.0 Windows Pro 1909
If on linux, libtorrent-rasterbar and Qt version
(type here)
What is the problem
Hi,
So I've been using qbittorrent for a long time now my previous CPU was Ryzen 7 1700 everything worked great there. I got a Ryzen 5900X the other day and the problem I have is whenever qbittorrent is opened the Precision Over Boost detects it as some high priority program and pumps the voltage of the cpu to 1.46-1.47 all cores which leads to 50 degrees celsius idle temps it doesn't matter if I am uploading or downloading anything. I've tried making the I/O Thread count higher or lower doesn't affect it. I've tried putting the priority of the program in windows to low doesn't work. I don't know if this issue can be solved by changing the code of the program or it will be resolved in Precision Boost 2.0 which should come to AMD processors this month in form of motherboard firmware. I am open to suggestion for a work around if anyone got one :)
What is the expected behavior
Steps to reproduce
Need to have a ryzen 5000 CPU
Extra info(if any)
(type here)