F5F Stay Refreshed Hardware Desktop PC will start only with Windows 11 after clearing the CMOS battery.

PC will start only with Windows 11 after clearing the CMOS battery.

PC will start only with Windows 11 after clearing the CMOS battery.

Pages (2): 1 2 Next
A
AaronBladez
Junior Member
49
03-11-2021, 12:41 PM
#1
I've just assembled a brand new PC. All parts are original. I installed Windows 11 Pro without any problems, and the first boot was also smooth. Recently, I've observed that whenever I power on or restart my PC, it immediately switches to BIOS and fails to boot into Windows. If I turn off the power and hold the power button for about ten seconds before turning it back on, it boots directly into Windows as if nothing happened. When it enters BIOS, it displays a 0 bootable devices list, but after clearing the CMOS, does it change? Also, in the BIOS, my M.2 drive showing the OS appears there. Anyone know what's going on? I'm really confused.

System details: Windows 11 Pro (latest), media creation tool downloaded and updated, CPU Ryzen 9 9950x3d, GPU RTX 5090, motherboard Gigabyte Aorus B850 Elite WIFI7, RAM 64GB Corsair Vengance (4 x 16GB), power supply Corsair H1500i (2025 model), M.2 drives Samsung 990 Pro 1TB and Samsung 990 EVO Plus 4TB (for games), with monitors, keyboard, mouse, and headset connected. Network is hard wired at 1Gb/s.
A
AaronBladez
03-11-2021, 12:41 PM #1

I've just assembled a brand new PC. All parts are original. I installed Windows 11 Pro without any problems, and the first boot was also smooth. Recently, I've observed that whenever I power on or restart my PC, it immediately switches to BIOS and fails to boot into Windows. If I turn off the power and hold the power button for about ten seconds before turning it back on, it boots directly into Windows as if nothing happened. When it enters BIOS, it displays a 0 bootable devices list, but after clearing the CMOS, does it change? Also, in the BIOS, my M.2 drive showing the OS appears there. Anyone know what's going on? I'm really confused.

System details: Windows 11 Pro (latest), media creation tool downloaded and updated, CPU Ryzen 9 9950x3d, GPU RTX 5090, motherboard Gigabyte Aorus B850 Elite WIFI7, RAM 64GB Corsair Vengance (4 x 16GB), power supply Corsair H1500i (2025 model), M.2 drives Samsung 990 Pro 1TB and Samsung 990 EVO Plus 4TB (for games), with monitors, keyboard, mouse, and headset connected. Network is hard wired at 1Gb/s.

M
maxiionita
Member
172
03-11-2021, 01:27 PM
#2
Update your update with complete hardware details and operating system specifics. Provide the power supply information, including PSU make, model, wattage, age, and condition. List all connected peripherals. Specify whether the network is wired or wireless. Mention how you are clearing CMOS.
M
maxiionita
03-11-2021, 01:27 PM #2

Update your update with complete hardware details and operating system specifics. Provide the power supply information, including PSU make, model, wattage, age, and condition. List all connected peripherals. Specify whether the network is wired or wireless. Mention how you are clearing CMOS.

S
Savannah010204
Junior Member
4
03-18-2021, 02:22 AM
#3
What iso was used to generate the installer stub? How does it automatically go to the BIOS? Typically, the system displays the startup splash screen by default unless the option is turned off, in which case no OS is detected and it prompts for a reset followed by DEL to enter setup.
S
Savannah010204
03-18-2021, 02:22 AM #3

What iso was used to generate the installer stub? How does it automatically go to the BIOS? Typically, the system displays the startup splash screen by default unless the option is turned off, in which case no OS is detected and it prompts for a reset followed by DEL to enter setup.

C
CreepAssassin
Member
50
03-19-2021, 03:57 PM
#4
Consider turning off Secure Boot too.
C
CreepAssassin
03-19-2021, 03:57 PM #4

Consider turning off Secure Boot too.

A
Anson1108
Member
102
03-21-2021, 08:50 AM
#5
I've made the necessary adjustments as requested. I've cleared it by unplugging it, keeping the power button pressed for ten seconds or more before restoring it.
A
Anson1108
03-21-2021, 08:50 AM #5

I've made the necessary adjustments as requested. I've cleared it by unplugging it, keeping the power button pressed for ten seconds or more before restoring it.

A
Avollon
Junior Member
21
03-21-2021, 10:49 AM
#6
I began the week using the Windows Media Creation tool, and I think it’s the most recent version. (Sorry, I’m not entirely sure)
It proceeds to the splash screen before BIOS but then continues to BIOS where it’s meant to boot into Windows.
A
Avollon
03-21-2021, 10:49 AM #6

I began the week using the Windows Media Creation tool, and I think it’s the most recent version. (Sorry, I’m not entirely sure)
It proceeds to the splash screen before BIOS but then continues to BIOS where it’s meant to boot into Windows.

L
LeClecle
Junior Member
2
03-21-2021, 03:12 PM
#7
Fast boot is completely turned off right now, but I'm going to attempt disabling secure boot to check. Appreciate the idea, I'll update you once I've tried it.
L
LeClecle
03-21-2021, 03:12 PM #7

Fast boot is completely turned off right now, but I'm going to attempt disabling secure boot to check. Appreciate the idea, I'll update you once I've tried it.

R
Rantruffs
Member
59
03-21-2021, 05:16 PM
#8
Not any regional variation just from the ms page. So perhaps I should download the multi edition iso separately and use Rufus to create a stub to rule it out. It seems similar to what happens if the iso is outdated and older drivers can't recognize newer hardware. Though I wouldn't expect the media creation tool to download an outdated iso if everyone's using it and it was somehow incorrect, there would be many complaints. Otherwise, why shouldn't secure boot work? Windows 11 is built for secure booting. Still, a new interesting Windows 11 boot bug is one of the most exciting developments in years. If that isn't it, maybe updating the MBOO bios would help. Still, you have 990pro drives as the other person did, who used a regional iso for the setup installer. *If that also seems confusing, I'd recommend reaching out to Samsung support for more information. They might have encountered this issue before.*
R
Rantruffs
03-21-2021, 05:16 PM #8

Not any regional variation just from the ms page. So perhaps I should download the multi edition iso separately and use Rufus to create a stub to rule it out. It seems similar to what happens if the iso is outdated and older drivers can't recognize newer hardware. Though I wouldn't expect the media creation tool to download an outdated iso if everyone's using it and it was somehow incorrect, there would be many complaints. Otherwise, why shouldn't secure boot work? Windows 11 is built for secure booting. Still, a new interesting Windows 11 boot bug is one of the most exciting developments in years. If that isn't it, maybe updating the MBOO bios would help. Still, you have 990pro drives as the other person did, who used a regional iso for the setup installer. *If that also seems confusing, I'd recommend reaching out to Samsung support for more information. They might have encountered this issue before.*

O
opticgunship
Posting Freak
815
03-21-2021, 06:20 PM
#9
The Media Creation Tool was installed using the most recent BIOS version, according to the Gigabytes website. This was the initial update after setting up Windows.
O
opticgunship
03-21-2021, 06:20 PM #9

The Media Creation Tool was installed using the most recent BIOS version, according to the Gigabytes website. This was the initial update after setting up Windows.

B
Blureux
Posting Freak
797
03-21-2021, 07:03 PM
#10
This motherboard?
https://download.gigabyte.com/FileList/M...1003_e.pdf
Verify that I found the applicable User Manual.
Because this is a new build work thorough the User Manual page by page to double check everything including BIOS instructions.
Pay close attention to all fine print - even in diagrams. Go online when suggested to look for updated information.
Power down, unplug, open the case. Carefully verify by sight and feel that all connectors, cards, RAM, jumpers, and case connections are correct and fully and firmly in place.
No one wants to force anything - especially with a new build. So what seems to be fully in place may not be.
You may need to unplug/replug or disconnect/reconnect a few times. Then all of a sudden something just seems to connect much more smoothly and securely.
Take a few minutes and check accordingly.
= = = =
Clear CMOS per Paragraphs 19/20 on numbered Pages 30 and 31.
Take a closer look that the default BIOS settings thereafter.
Consider a new CMOS battery just as a matter of elimination,
= = = =
Splash screen: At the next sucessful boot take a look in Reliability History/Monitor and Event Viewer.
Either one or both tools may be capturing some error code, warning, or even an information just before or aT the time the build reverts back to booting.
B
Blureux
03-21-2021, 07:03 PM #10

This motherboard?
https://download.gigabyte.com/FileList/M...1003_e.pdf
Verify that I found the applicable User Manual.
Because this is a new build work thorough the User Manual page by page to double check everything including BIOS instructions.
Pay close attention to all fine print - even in diagrams. Go online when suggested to look for updated information.
Power down, unplug, open the case. Carefully verify by sight and feel that all connectors, cards, RAM, jumpers, and case connections are correct and fully and firmly in place.
No one wants to force anything - especially with a new build. So what seems to be fully in place may not be.
You may need to unplug/replug or disconnect/reconnect a few times. Then all of a sudden something just seems to connect much more smoothly and securely.
Take a few minutes and check accordingly.
= = = =
Clear CMOS per Paragraphs 19/20 on numbered Pages 30 and 31.
Take a closer look that the default BIOS settings thereafter.
Consider a new CMOS battery just as a matter of elimination,
= = = =
Splash screen: At the next sucessful boot take a look in Reliability History/Monitor and Event Viewer.
Either one or both tools may be capturing some error code, warning, or even an information just before or aT the time the build reverts back to booting.

Pages (2): 1 2 Next