The PC requires a two-minute power-off period before it will start up.
The PC requires a two-minute power-off period before it will start up.
My PC, after years of use, now keeps restarting itself unless I cut power for two minutes. After turning it on, everything works properly, and rebooting is also smooth.
I rebuilt it in 2015 (everything new at that time):
Processor: Intel Core i7-4790k quad-core 4.0GHz
Cooler: Kotetsu SCKTT-1000
Memory: 4x GSKILL Ripjaws X Series 4GB DDR3 1600MHz
Storage: 2x Samsung 850 EVO 250GB, 1x Samsung 860 EVO 1TB (only one 850 was installed initially)
Power supply: Seasonic SS-520FL 520W ATX12V Fanless
Graphics card: EVGA GTX 960 2GB
Case: Fractal Design Define R5
Operating system: Windows 10 Pro
BIOS version: 0501
Monitors: ASUS VX238H, LG 27UD58-B
It functioned well for about eight years, but after moving my desk to another room, it would only boot at 5%. Returning to the original space didn’t help. I tried some basic fixes like changing the CMOS battery, but nothing worked. Eventually, I suspected a possible damage to the motherboard. I kept my case sealed, used surge protectors in both rooms, but I wasn’t sure what would happen.
I also had a laptop, so I stopped using the desktop.
Last week I attempted again. This time it booted occasionally, and I could pinpoint exact steps that caused the issue. Even though I’m now living elsewhere, I don’t think the problem changed—my troubleshooting wasn’t thorough enough before.
Here’s what consistently happens:
- Reboot from Windows or MX Linux live USB or BIOS: Boots normally
- Shut down (via Windows start menu, MX Linux live USB, or case power button), wait any time, then start: Endless cycle
- Unplug, wait 10 seconds or less, then plug back in: Cycle restarts automatically without me initiating it
- Unplug, wait 1 minute or less, then plug back in, then start: Endless cycle
- Unplug, wait over 2 minutes, then plug back in, then start: Boots normally
Terms:
“Start” = Press power button on case
“Unplug” = Disconnect from power using the switch on the PSU after experiencing the endless cycle
“Replug” = Turn on the switch on the PSU
“Endless cycle” = CPU cooler runs and case power LED lights, then turns off after 1 second; repeats indefinitely. Disconnecting is the only way to stop it.
Notes:
- The endless cycle happens even when everything except the CPU, cooler, RAM, case, keyboard, and monitor is unplugged.
- During last week’s troubleshooting, I replaced the CMOS battery and reset it. Before that, a 1-minute power cut was enough to stop the cycle. Now, that duration isn’t enough. Not sure if that helps.
I can still use the computer, but I prefer knowing what’s wrong.
What could be wrong?
Is there a fix?
If I choose not to fix it now, could it worsen or cause other problems? Or might the issue stay the same?
I’m open to suggestions and any insights, especially if I can test them myself! Thanks in advance!
Check for any error notifications, alerts, or informational logs in the Reliability History/Monitor or Event Viewer.
Here are the key points rephrased while keeping the original meaning and structure:
- I should note that the system has been disconnected from all networks, which has caused many errors, though some were omitted.
- For most of the incidents, I shortened certain details for clarity, but they can be provided again if needed.
- After reading your message, I checked whether these occurrences would repeat. I powered down around 4:06 pm today. The brief period without power wasn’t sufficient to stop the Endless Cycle; even five minutes didn’t work. I resumed after about ten minutes of being unplugged. Since then, none of the events listed have occurred.
Reliability History
- Critical incidents were recorded on 1/18, 1/20, and 1/24 indicating an improper shutdown of Windows.
- There was also a report on 1/23 about the Spooler SubSystem App ceasing to function.
- The event on 1/24 likely matches the last time I powered on the system before today’s shutdown.
- RH logs several hardware issues under Windows in "Problem Reports," but the most recent one was on 8/28/2021. The last successful boot was on 9/17/2021, with unclear details.
Event Viewer
- Multiple unusual events appeared in Event Viewer:
- Boot or system-start drivers failed to load (e.g., dam).
- Kernel-PnP warnings about driver failures for specific devices.
- Connectivity issues marked as disconnected.
- An unexpected shutdown on 1/23/2026 at 11:37:34 AM, noted as unusual.
- A critical kernel power event indicating a reboot without a clean shutdown.
- Warnings about corrupted Brave extensions (related to GreaseLion).
- Information events showing ExpressVPN receiving unsupported POWEREVENT control and another that it would handle.
- Around 4:06 pm today, after initiating the shutdown, the system entered sleep, resumed shortly afterward—this behavior wasn’t typical for other days.
- On 9/17/2021, before the system failed for years, there was an error with the HDAUDIO device starting (driver hdaudio.inf).
- A warning about updating drivers from version 0x0006003300140002 to 0x0006004b00230049 was logged.
Let me know if you need further clarification.
Before changing the CMOS battery, each time I started up I encountered the American Megatrends error displaying a message requiring an update. (I might have left some devices connected to the MB without power, unsure if that contributed.) From that interface, whenever I accessed the BIOS, I chose the default settings option and saved, but it consistently reported no changes. Eventually, after replacing the battery, I realized I hadn’t updated the system time—repeatedly set to 00:00:00 on January 1, 2009 during BIOS entry—and I also updated it before saving. That resolved the issue.
More errors and diverse mistakes indicate a weakening and deteriorating power supply unit. An 8-year-old PSU is almost certainly beyond its intended lifespan. Keep in mind that PSUs deliver various voltages (3.3, 5, and 12) to different system parts. This means some elements might function normally while others face difficulties due to insufficient power. Two actions are recommended:
1) Make sure all crucial information is saved at least twice in separate locations far from the affected system. Check that these backups can be retrieved easily.
2) Replace it with a known functional PSU—preferably at least 700 Watts. Test if the issues improve or disappear, using only the original cables.
The PSU plays a vital role and must be highly dependable.