F5F Stay Refreshed Hardware Desktop The PC fails to start during the initial cold boot attempt, yet manages to boot after being powered off and restarted.

The PC fails to start during the initial cold boot attempt, yet manages to boot after being powered off and restarted.

The PC fails to start during the initial cold boot attempt, yet manages to boot after being powered off and restarted.

J
JromHD
Junior Member
2
07-17-2022, 08:23 AM
#1
Hello, I've been experiencing this issue with my PC for about a month now after setting up a dual-boot configuration with Windows 11 and Linux Mint. Every morning when I power on, the system starts all components properly—fans spin, peripherals get power, and the GPU indicator lights up—but it fails to boot. The monitor doesn’t show any boot signal, and there’s no output. When I turn it off and back on, everything works fine.

Details about my setup:
- CPU: AMD Ryzen 5 5500
- GPU: AMD Radeon RX 580
- Motherboard: MSI B550M PRO-VDH WI-FI
- RAM: 2x8GB at 3200MHz (Gaming DDR4)
- Power Supply: Toughpower GX2 80+ Gold 600W
- SSD: TEAMGROUP MP33 1TB SLC Cache 3D NAND TLC NVMe 1.3 PCIe Gen3x4 M.2 2280 (Windows 11) & Crucial MX500 500GB 3D NAND SATA
- Case: Zalman S2 ATX Mid Tower
- Monitor: Viotek GFV22CB 22-inch 144Hz

I've tried clearing CMOS, checking cables, reseating RAM, and even using different boot orders. Fast startup and hibernation are disabled in Windows 11, and the problem persists whether Secure Boot is enabled or not. It happens even when GRUB’s OS probing is turned on or off. Linux Mint was set as the first boot option, but I’m planning to switch it to Windows 11 for testing purposes tomorrow.

I’m running out of ideas and want some guidance before things get worse. It doesn’t look like a critical hardware failure, but the unexpected behavior is unsettling.
J
JromHD
07-17-2022, 08:23 AM #1

Hello, I've been experiencing this issue with my PC for about a month now after setting up a dual-boot configuration with Windows 11 and Linux Mint. Every morning when I power on, the system starts all components properly—fans spin, peripherals get power, and the GPU indicator lights up—but it fails to boot. The monitor doesn’t show any boot signal, and there’s no output. When I turn it off and back on, everything works fine.

Details about my setup:
- CPU: AMD Ryzen 5 5500
- GPU: AMD Radeon RX 580
- Motherboard: MSI B550M PRO-VDH WI-FI
- RAM: 2x8GB at 3200MHz (Gaming DDR4)
- Power Supply: Toughpower GX2 80+ Gold 600W
- SSD: TEAMGROUP MP33 1TB SLC Cache 3D NAND TLC NVMe 1.3 PCIe Gen3x4 M.2 2280 (Windows 11) & Crucial MX500 500GB 3D NAND SATA
- Case: Zalman S2 ATX Mid Tower
- Monitor: Viotek GFV22CB 22-inch 144Hz

I've tried clearing CMOS, checking cables, reseating RAM, and even using different boot orders. Fast startup and hibernation are disabled in Windows 11, and the problem persists whether Secure Boot is enabled or not. It happens even when GRUB’s OS probing is turned on or off. Linux Mint was set as the first boot option, but I’m planning to switch it to Windows 11 for testing purposes tomorrow.

I’m running out of ideas and want some guidance before things get worse. It doesn’t look like a critical hardware failure, but the unexpected behavior is unsettling.

K
kelusky101
Member
181
07-23-2022, 05:16 AM
#2
It's a possibility that the switching power supplies support multiple rails, such as 3.3V, 5V, and +/- 12V. Certain rails need to operate under light load before they become stable, which involves a sensor. If a rail isn't stable, it can delay the system start-up. It's possible that one rail fails during a cold boot, though the exact cause remains unclear. Stability could depend on factors like power load conditions or internal components within the supply. Analyzing this would require costly equipment, but signs suggest a failing capacitor might be at play. Electrolytic capacitors degrade over time, often not charging properly when the system starts up cold. This temperature shift could help the rail stabilize after a restart. Most likely, the issue lies with the power supply itself. If your power source is weak or unstable ("brown out"), it can also lead to instability even in a functioning supply. The probability seems higher that one of the capacitors is malfunctioning.

The CMOS battery might be outdated and prone to memory errors. When the system powers off completely, a faulty battery could cause data corruption. This situation resembles a power supply failure, as a bad capacitor can trigger similar symptoms. Usually, a reboot is needed after adjusting the BIOS settings, making it hard to pinpoint whether the issue stems from another problem or a reset of the CMOS. I generally believe the power supply is more likely responsible, though other factors could contribute. Both batteries and capacitors have a chance of failing.
K
kelusky101
07-23-2022, 05:16 AM #2

It's a possibility that the switching power supplies support multiple rails, such as 3.3V, 5V, and +/- 12V. Certain rails need to operate under light load before they become stable, which involves a sensor. If a rail isn't stable, it can delay the system start-up. It's possible that one rail fails during a cold boot, though the exact cause remains unclear. Stability could depend on factors like power load conditions or internal components within the supply. Analyzing this would require costly equipment, but signs suggest a failing capacitor might be at play. Electrolytic capacitors degrade over time, often not charging properly when the system starts up cold. This temperature shift could help the rail stabilize after a restart. Most likely, the issue lies with the power supply itself. If your power source is weak or unstable ("brown out"), it can also lead to instability even in a functioning supply. The probability seems higher that one of the capacitors is malfunctioning.

The CMOS battery might be outdated and prone to memory errors. When the system powers off completely, a faulty battery could cause data corruption. This situation resembles a power supply failure, as a bad capacitor can trigger similar symptoms. Usually, a reboot is needed after adjusting the BIOS settings, making it hard to pinpoint whether the issue stems from another problem or a reset of the CMOS. I generally believe the power supply is more likely responsible, though other factors could contribute. Both batteries and capacitors have a chance of failing.

M
MrKiwiism
Member
236
07-24-2022, 07:51 AM
#3
Welcome to the forums, newcomer! When setting up a dual boot, please adhere to these instructions. This approach has worked before with the previous Windows version: install Windows first, then add Linux without erasing your existing drive. How recent is your PSU? Regarding your BIOS, does the time keep resetting? If yes, it may indicate a low battery in the CMOS or a grounding problem at home.
M
MrKiwiism
07-24-2022, 07:51 AM #3

Welcome to the forums, newcomer! When setting up a dual boot, please adhere to these instructions. This approach has worked before with the previous Windows version: install Windows first, then add Linux without erasing your existing drive. How recent is your PSU? Regarding your BIOS, does the time keep resetting? If yes, it may indicate a low battery in the CMOS or a grounding problem at home.

W
woodskill137
Member
60
07-24-2022, 08:14 AM
#4
Thank you for the friendly greeting!
The build is just over a year old now, and it's still functioning properly, including the time reset.
W
woodskill137
07-24-2022, 08:14 AM #4

Thank you for the friendly greeting!
The build is just over a year old now, and it's still functioning properly, including the time reset.

J
janrooijen
Member
205
08-01-2022, 05:56 AM
#5
That would definitely be a puzzling situation. It seems unlikely, but it’s worth considering whether one or both SSDs might be involved in the problem.
J
janrooijen
08-01-2022, 05:56 AM #5

That would definitely be a puzzling situation. It seems unlikely, but it’s worth considering whether one or both SSDs might be involved in the problem.

O
omniclean
Member
192
08-03-2022, 01:19 AM
#6
Disk issues can occur, yet the SMART tests indicated everything was fine. It seems there might be another cause. "Odds" is a suitable term for expressing a probability based on experience, though it remains uncertain.
O
omniclean
08-03-2022, 01:19 AM #6

Disk issues can occur, yet the SMART tests indicated everything was fine. It seems there might be another cause. "Odds" is a suitable term for expressing a probability based on experience, though it remains uncertain.

D
Draker59
Member
126
08-03-2022, 04:23 AM
#7
I just made a minor update:
My PC has worked well for the last couple of days after setting Windows as the first boot choice. Of course, the problem has been sporadic (I went almost a week without it happening before), so I might have just been lucky, but I thought it worth noting.
D
Draker59
08-03-2022, 04:23 AM #7

I just made a minor update:
My PC has worked well for the last couple of days after setting Windows as the first boot choice. Of course, the problem has been sporadic (I went almost a week without it happening before), so I might have just been lucky, but I thought it worth noting.