Can reducing the CPU voltage affect Windows 10 stability?
Can reducing the CPU voltage affect Windows 10 stability?
So I decided to undervolt my i9-14900k by -0.050v in the bios settings. Also my XMP profile was disabled so I could increase my RAM from 4800mt to 6000mt
Now I have gamed for days. I have ran multiple CPU and system stress tests across various programs. I let unigine heaven run overnight on extreme..
Not a single problem. Not a single stutter, crash, BSOD and my CPU hovers in the 33c at idle to 65c at gaming, GPU at 40c idle to 55c gaming. My CPU actually dropped 5 degress after the undervolt.
But here's the thing. While sitting idle in the Windows 10 environment doing barely nothing, the system locks up forcing me to reset.
Why no problems under extreme stress with gaming, but problems when doing nothing at the Desktop?
My setup at time of this post:
|| CPU: Intel 14900k || GPU: evga 3080 XC3 Ultra Hybrid || MB: Gigabyte z490 UD AC || RAM: 2 x 32GB 6000mhz DDR5 SDRAM || Samsung EVO 970 Plus 2TB || Dell S2417DG Monitor || Soundblaster AE-7 || Phanteks Eclipse p600s Case || be Quiet! Dark Rock Slim CPU Cooler || Corsair AX1600i PSU || 7 Fans total in system ||
"Can undervolting your CPU cause Windows 10 instability?" Yes.
There is no guarantee a chip will run stably at settings the manufacturer hasn't sold them to work at regardless what one may read or watch online. Integrated circuits, while repeatably reliable, still have ranges in quality and tolerance.
Intel has even run afoul of the reality that chips run without end-user scrutiny of default voltage settings set by motherboard manufacturers, may degrade in short order.
It's simple to test, really. If your system was stable before you tinkered with the settings, undo one of them. Start by undoing your undervolt. If your system stops behaving in an unstable manner when idling at the Windows Desktop, that's the most likely candidate for the unwanted behavior.
When undervolting, pick a target. If instability is witnessed afterward, dial back your target undervolt. The goal is to walk the setting from unstable to stable until you find what your particular chip will tolerate.
Why would your chip have issues at idle instead of under load? Chips often use the equivalent of voltage tables. Different amounts of work being done by the chip will require different voltages to remain stable. Does your undervolt apply to just a single entry in the table or is it an offset for the entire range the chip will operate at? It's possible your chip does not need the maximum voltage given at the top end of the table, but when workload reduces and allows for idle voltages, your offset now falls below the minimum threshold needed for your particular chip.
Thank you for the update. I believe the issue might be related to a problem with the USB ports during wake-up. By moving my mouse and keyboard to the 2.1 ports, I haven't experienced any lockups. Also, for the first time, I replaced the HDD on the new motherboard without reinstalling Windows, and it's functioning well. I'm curious if there could be a driver conflict with the USB hub or if the ports have some damage.
Drivers on their own are rarely the main problem these days, especially with newer Windows versions. Since Windows typically includes drivers from various manufacturers along with its own standard ones, almost every common part has support. However, the real issue often lies in the registry settings and instructions—sometimes it tells Windows to load ASUS MMO drivers, but if you have an MSI MMO, it can't apply the right drivers, opting instead for generic ones. This leads to poor performance or compatibility problems, especially when MSI uses more proprietary solutions. It's like a series of small issues.
Hypothetically, older BIOS or USB drivers work fine with versions like BT or USB 3.0. But you won’t find the speeds or power delivery capabilities you expect from newer releases. If your device requires USB 2.0, you might encounter glitches, slow charging, or other minor issues.
Many users don’t notice these small problems—they usually appear as minor log warnings instead of critical errors or crashes. Sometimes a 144Hz monitor shows up as a generic display and only renders at 120Hz, unless you check the system specifications carefully to confirm it’s displaying the full resolution.
Drivers might or might not be the problem, and although a switch between Windows installations on different hardware usually helps, it doesn’t always resolve the issue. If you’re worried, checking the Windows Device Manager for any errors could give you some clarity.
USB drivers are quite standard and come from Windows unless you’re using more advanced software. Your explanation seems clear, but it’s hard to say exactly which ports were involved based on your description.
I’m not sure about the specific ports you’re referring to when you say:
"I moved my mouse and keyboard to the 2.1 ports and I haven't had a single lockup since."
You didn’t mention which ports your keyboard and mouse were connected to before, which makes it hard to pinpoint exactly where the change happened. According to the Gigabyte z790M Aorus Elite AX ICE manual, you have:
- 1 x USB 3.2 Gen 2x2 Type-C
- 1 x USB 3.2 Gen 2 Type-A
- 4 x USB 3.2 Gen 1 Type-A
- 4 x USB 2.0/1.1 ports
Since the USB 3.2 Gen 2x2 port is controlled directly by the CPU, any issues with undervolting could affect it. The other ports are managed by the chipset, so I wouldn’t focus there unless instability appears.
However, if your USB ports caused system problems during use, I’d be concerned. Is the undervolt setting stable? Have you checked if your CPU ran in idle states after moving USB devices? Trying to revert one or both USB connections back to their original ports might help confirm the cause.
While I can’t rule out the undervolt issue entirely, it’s also possible the USB connection is the culprit. You’re not sure yet, but running a memory test could be useful. Use Windows’ built-in Memory Diagnostic tool and see if it detects any errors. Even if it fails, it won’t necessarily mean the RAM is bad—it might just be misconfigured.