zqhong / ryzentuner Goto Github PK

A tool that supports adjusting the power limit of Ryzen mobile processors and the QoS level and priority of Windows processes

License: MIT License

C# 99.42% Makefile 0.58%

power-management ryzen energystar ryzenadj

ryzentuner's Introduction

RyzenTuner

English | 简体中文

RyzenTuner provides a GUI interface to easily adjust the power limit of Ryzen mobile processors, and also supports adjusting the QoS level and priority of Windows processes, thereby improving battery life and reducing fan noise.

Feature

Automatic Mode

Different working modes (standby/balance/performance) are automatically selected according to different conditions such as plug-in/battery/night/active time.

Description of working mode:

Standby mode: in the lowest energy consumption state, can only deal with ultra-low load work
Balanced Mode: The state with the highest energy consumption ratio, to deal with sudden tasks, such as opening web pages, Photoshop
Performance Mode: for scenarios that require high performance, such as compiling software, playing large games, rendering, etc.

Usage

You can directly go to Release to download the compiled program and use it.

FAQ

How to modify the power of other modes such as standby mode

Close RyzenTuner. Open the RyzenTuner.exe.config file and modify the corresponding parameters. For example, SleepMode is the sleep mode, modify the value in it.

Example: Change sleep mode from 1 W to 2 W

Before update

<setting name="SleepMode" serializeAs="String">
    <value>1</value>
</setting>

After update

<setting name="SleepMode" serializeAs="String">
    <value>2</value>
</setting>

Give a Star! ⭐

If you like or are using this project, please give it a star. Thanks!

Dependent project

Archeb/RyzenTuner: Developed based on this project
FlyGoat/RyzenAdj: Ryzen mobile processor power management tool
imbushuo/EnergyStar: Windows process scheduling, may have the effect of increasing battery life (not tested)
LibreHardwareMonitor: Get hardware information
dahall/Vanara: A set of .NET libraries that wraps many PInvoke calls to Windows native APIs

Thanks to the projects and authors listed above.

License

RyzenTuner is licensed under MIT.

ryzentuner's People

Contributors

Stargazers

Watchers

Forkers

tennython resource-archive sccbhxc sigpending xuning2 lyk082401

ryzentuner's Issues

Silent Start 静默启动

在打开 RyzenTuner 后，自动进入托盘模式，不显示用户界面，这样方便点

On exit reset changes

Issue:
When exiting the application I am not told the original tdp of the system nor is it reset.

How to fix:
When exiting reset the values to original state

Suggestion: 增加设置选项

希望能在设置里增加一个开机隐藏式（直接进托盘，不显示主界面）的自启动选项（例如，Ryzen Controller的隐藏式启动加上自己设置一个taskschedule里面的任务）
希望能在设置里增加一个选择是否显示托盘图标的选项（但是我不清楚能否实现，例如IDM那种）

建议新增“开机启动”的设置项

建议增加开机自启动的配置项，可以先实现个简单的，比如搞个快捷方式到“启动”目录。

建议：添加恢复系统默认功耗与电源调度策略的选项

如题，希望能增加一个一键恢复系统默认功耗与电源调度策略的选项

可能的bug反馈&建议新增温度调控选项

我的笔记本是 hp envy 13 x360 2018款，cpu 2500u，我在三种模式下跑了stress fpu，结果如下：
1.手动27w

2.手动26w

3.性能26w

可以看到，只有手动27w情况下，cpu温度突破了笔记本自身限制的70℃，达到期望的90℃，其他则完全没有突破70℃，这算是个bug？
另外，希望增加调整温度的选项，让用户自行决定可以达到的最高温度

redmibook pro15 6800H 开省电模式（限制功率10w）时，过几分钟后系统会卡住

托盘图标右键勾选样式错误及显示逻辑问题

Windows 11 最新版下托盘图标右键的勾选样式有问题：

然后此时我点击“自动模式”，就没有任何一项勾选了，但实际上这些选项是单选的。

启动失败，提示init ryzenadj failed

系统信息：win11 22H2
处理器：AMD 6800H

RyzenTuner.exe 导致系统蓝屏

电脑型号：惠普战X 锐龙版（HP EliteBook 865 16 inch G9）
CPU：AMD Ryzen 7 Pro 6850HS
GPU：AMD Radeon(TM) Graphics
系统版本：Windows 11 22H2 Build 22621
蓝屏场景：一直使用自带的性能模式（26W），energy star 和保持唤醒均未勾选。出现过两次蓝屏，第一次是在未插电状态下休眠唤醒后打开 Chrome 访问网页不到半分钟卡屏，随后蓝屏。第二次为插电盒盖睡眠时蓝屏。第一次蓝屏代码为 CLOCK_WATCHDOG_TIMEOUT_IDLE_THREAD_INVALID_CONTEXT，第二次蓝屏时不在电脑旁且转储出错，无法得知蓝屏代码。测试过退出 RyzenTuner 后睡眠和休眠均不会出现蓝屏
蓝屏 dump 文件详情：

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 000000000000000c, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffbb80f51d1180, The PRCB address of the hung processor.
Arg4: 0000000000000006, The index of the hung processor.

Debugging Details:
------------------

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1827

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 3018

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

Key  : Analysis.Init.CPU.mSec
Value: 312

Key  : Analysis.Init.Elapsed.mSec
Value: 10236

Key  : Analysis.Memory.CommitPeak.Mb
Value: 100

Key  : Bugcheck.Code.DumpHeader
Value: 0x101

Key  : Bugcheck.Code.Register
Value: 0x101

Key  : Dump.Attributes.AsUlong
Value: 1808

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key  : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage
Value: 0

FILE_IN_CAB: 102422-15078-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

BUGCHECK_CODE: 101

BUGCHECK_P1: c

BUGCHECK_P2: 0

BUGCHECK_P3: ffffbb80f51d1180

BUGCHECK_P4: 6

FAULTING_PROCESSOR: 6

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RyzenTuner.exe

STACK_TEXT:
ffffbb80f53f09a8 fffff80118276006 : 0000000000000101 000000000000000c 0000000000000000 ffffbb80f51d1180 : nt!KeBugCheckEx
ffffbb80f53f09b0 fffff80118022f74 : 0000000df1750f07 0000000df1750f07 000000000005d922 0000000000000000 : nt!KeAccumulateTicks+0x252106
ffffbb80f53f0a10 fffff80118022e56 : 0000000000000010 0000000000000000 ffffbb80f53d6180 0000000df16fc700 : nt!KiUpdateRunTime+0xf4
ffffbb80f53f0bd0 fffff8011802107e : 0000000000000000 ffffbb80f53d6180 ffffffffffffffff 0000000000000000 : nt!KiUpdateTime+0x13e6
ffffbb80f53f0e90 fffff8011802088a : fffff80118a5fe40 ffffa90c743a4a70 ffffa90c743a4a70 0000000000000000 : nt!KeClockInterruptNotify+0x3de
ffffbb80f53f0f40 fffff80118145f6e : 0000000df2b10f35 ffffa90c743a49c0 ffffbb80f53d6180 0000000000000000 : nt!HalpTimerClockInterrupt+0x10a
ffffbb80f53f0f70 fffff80118229d1a : fffff4865c90f990 ffffa90c743a49c0 0000000000000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x19e
ffffbb80f53f0fb0 fffff8011822a2e7 : ffffa90c879cc0c0 fffff801180bc17c ffffa90c879cc0c0 0000000000000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff4865c90f910 fffff8011823a8bd : 0000000000000550 ffffa90c879cc0c0 0000000000000000 000001e532cd1098 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff4865c90faa0 00007ffb7300ee54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceUser+0xbb
000000b05a79e428 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`7300ee54

SYMBOL_NAME: nt!KeAccumulateTicks+252106

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.674

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 252106

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_IDLE_THREAD_INVALID_CONTEXT_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b37ea922-6ea8-0080-e849-451291ca96f3}

Followup: MachineOwner
---------