Yes, a failing power supply unit can lead to frequent reboots as the computer struggles to get stable power.
Yes, a failing power supply unit can lead to frequent reboots as the computer struggles to get stable power.
Windows 10 pro EVGA SuperNOVA 750 G3 750 watt from 2017 G.SKILL Trident Z Neo (For AMD Ryzen) Series 32GB (2 x 16GB) ASUS AM4 TUF Gaming X570-Plus (Wi-Fi WD_BLACK 1TB SN750 SE NVMe SSD 35GB free Samsung 860 Evo 1GB - 284GB free gtx 1080 ti ftw3 amd ryzen 3900x Dark Rock Pro 4 cooler for cpu) is a powerful build. My problem began a few weeks ago when I had to restart. After hitting restart, it seemed ready to boot but kept restarting again. Eventually, nothing happened. The PC displayed it was still on, the keyboard lights stayed on, but it wouldn’t progress past the login screen. I often had to force a reboot—20 or more times—and finally it landed on the desktop. I was worried because someone suggested it might be the power supply unit, calling it the oldest component in my system from 2017. It’s unsettling when a Windows update forces repeated restarts before it even starts. Could a failing PSU be behind this issue?
It might be possible. If so, it’s likely a faulty capacitor. A brief inspection is needed—remove the PSU cover and check for swollen tops on any capacitors. It could also be a problem on the motherboard, which I encountered a couple of months ago.
It can lead to issues in various ways and might result in serious consequences if it fails completely. Typically, PSU's last longer than five years under regular use, though they still have some wear over time. If you think a replacement is needed, be sure to check if the problem will be resolved before proceeding. By the way, did this start during a Windows update?
It might relate to RAM problems; consider turning off D.O.C.P. to see if it resolves the issue with the 2400mhz memory.
If true, this would clarify a lot about the situation. Windows updates (esp 10 and 11) are often linked to issues like yours. You might want to try installing Windows on another drive to isolate the problem, ensuring your existing HDD/SSD remains intact. This helps determine whether the issue stems from the update itself or a driver conflict, without risking data loss. I suspect it could be related to a compatibility clash between the update and a driver, which has been observed before.