It seems there isn't a way to adjust the voltage for the Ryzen 5 3500X in the BIOS settings.
It seems there isn't a way to adjust the voltage for the Ryzen 5 3500X in the BIOS settings.
Hi there. I hope adjusting questions is allowed in this area.
I’m upgrading my computer and plan to use it as a home server for a NAS. The CPU is a Ryzen 5 3500X and the motherboard is an MSI B450M Pro-VDH Max with the newest BIOS installed. Since the NAS only needs basic performance and must run continuously, I’m wondering if I can lower its voltage to cut power use and save on electricity costs. Right now it’s drawing about 80W when idle, and I understand that a slight performance reduction is fine.
I found some tutorials, but in my BIOS the Precision Boost Overdrive option isn’t there—only clock speeds are adjustable. If anyone can guide me on the right steps, I’d really appreciate it.
Here are the images you shared:
https://drive.google.com/file/d/1UtquVxf...sp=sharing
20250630_130221.jpg
drive.google.com
Turn off PBO to check if it reduces your power consumption. Have you experimented with AMD's Ryzen Master and adjusted settings there?
Not challenging the idea of turning off PBO, etc.
But I’ll focus on power usage.
Absolutely in line with aiming to lower power use, though I’d really like to measure the actual savings in watts.
How significant would the performance drop be?
Which NAS server software is currently in place?
Just looking to understand any compromises that might come into play.
The main concern is determining the actual power savings.
Are the adjustments (PBO and others, if any) justified?
What amount of power is consumed when the NAS operates at full capacity (not just idle)?
How long will the NAS remain fully active during a 24-cycle period?
Energy costs are typically charged per kilowatt-hour.
My current electricity invoice displays my kWh rate at $0.12 (USD).
But with additional delivery fees and taxes, the final cost comes to $0.205 per kWh.
Could certain NAS power-saving modifications truly reduce expenses?
= = = =
Once again, everything leans toward energy conservation and its benefits.
I prefer a different strategy.
I recommend beginning by running the NAS in its standard configuration without any power-saving tweaks.
Assess its overall performance and real energy consumption over time.
At the same time, look for other ways to cut energy use—such as replacing some lighting with LED bulbs.
My idea is that the primary goal should be to verify the new NAS functions properly and consistently.
After that, experiment with adjusting power settings. You might find you save energy, or you may not. I’d keep tracking power usage versus performance for a while.
If issues arise, you can revert the changes easily.
It’s likely that any modifications will involve some compromises.
Keep in mind that BIOS updates or OS changes could introduce complications sooner rather than later.
In short: Make sure the NAS is running smoothly first. Then focus on energy efficiency if it still makes sense.
This setup aligns with your expectations. I'll configure it and monitor it for several weeks before adjusting anything.
It's also worth noting whether the configuration includes features for voltage reduction. If not, you might want to explore alternatives like using a lower-power PC if needed.
In fact, the greatest savings come from managing heat output. Automatic PBO settings enable more or full power when required, but they do nothing when CPU usage is low. This also helps maintain top performance and boost levels. For voltage control, using CO (Curve Optimizer) is recommended; it can be found in the PBO section of BIOS. Typical settings range from -10 to -30, but you should experiment carefully—higher values might cause instability at low loads. Besides that, you might want to restrict CPU frequency to a level that suits you. This would also reduce voltage and power, which in turn affects heat output. If a base frequency of 3.6GHz is sufficient, consider keeping it at that or lower.
It seems you made some adjustments and the system didn't respond properly. You had to reset the CMOS to restore functionality, though everything is now working again. You're concerned about making further changes.