F5F Stay Refreshed Hardware Desktop Installation of NVMe SSD still causes delayed boot times.

Installation of NVMe SSD still causes delayed boot times.

Installation of NVMe SSD still causes delayed boot times.

X
xxxLazersxxx
Member
117
08-04-2021, 08:36 PM
#1
Hey there! I'm trying to figure out why my system feels slow when booting up after installing an NVMe SSD. I've checked Task Manager and disabled some apps at startup, adjusted the BIOS to prioritize the SSD, and even reinstalled Windows, but the boot time is still around 12 seconds. My hardware specs are listed, and I'm using Windows 11 on the SSD. Could anyone help identify what might be causing this delay? Thanks!
X
xxxLazersxxx
08-04-2021, 08:36 PM #1

Hey there! I'm trying to figure out why my system feels slow when booting up after installing an NVMe SSD. I've checked Task Manager and disabled some apps at startup, adjusted the BIOS to prioritize the SSD, and even reinstalled Windows, but the boot time is still around 12 seconds. My hardware specs are listed, and I'm using Windows 11 on the SSD. Could anyone help identify what might be causing this delay? Thanks!

L
lonewolf8545
Junior Member
46
08-04-2021, 10:43 PM
#2
This process starts from power-on and completes within 12 seconds after a cold start.
L
lonewolf8545
08-04-2021, 10:43 PM #2

This process starts from power-on and completes within 12 seconds after a cold start.

H
hhwroy
Member
50
08-05-2021, 02:02 AM
#3
Turn on bootlog for better diagnostics. It makes identifying performance issues simpler, though the hardware itself performs well. You can learn how to activate it by checking the documentation available.
H
hhwroy
08-05-2021, 02:02 AM #3

Turn on bootlog for better diagnostics. It makes identifying performance issues simpler, though the hardware itself performs well. You can learn how to activate it by checking the documentation available.

Q
QuietGuy
Junior Member
1
08-14-2021, 11:59 AM
#4
The 12-second time is quite solid, though I doubt it will improve much further. My setup runs at 16 seconds using a 970 evo plus NVMe drive.
Q
QuietGuy
08-14-2021, 11:59 AM #4

The 12-second time is quite solid, though I doubt it will improve much further. My setup runs at 16 seconds using a 970 evo plus NVMe drive.

_
___ducky___
Member
149
08-14-2021, 02:21 PM
#5
In BIOS you can adjust the time splash that shows when starting up. Turn on fast boot even if it doesn’t significantly affect NVME performance.
_
___ducky___
08-14-2021, 02:21 PM #5

In BIOS you can adjust the time splash that shows when starting up. Turn on fast boot even if it doesn’t significantly affect NVME performance.

T
TNTLogicMC
Junior Member
13
08-14-2021, 03:52 PM
#6
My 5900X struggled to run for 12 seconds with a WD Blue SN570 and 32GB DDR4-3200 RAM. It’s frustrating seeing it treated like this. For the sake of this post, I’m upset because my 5900X was forced to boot into an LGA1151 socket. Even worse, the Lenovo M71e I recently updated with an i7-2600 and a modified SATA M.2 feels like it’s being treated unfairly. Oh, the irony! Edited August 9, 2022 by An0maly_76 Updated, more info
T
TNTLogicMC
08-14-2021, 03:52 PM #6

My 5900X struggled to run for 12 seconds with a WD Blue SN570 and 32GB DDR4-3200 RAM. It’s frustrating seeing it treated like this. For the sake of this post, I’m upset because my 5900X was forced to boot into an LGA1151 socket. Even worse, the Lenovo M71e I recently updated with an i7-2600 and a modified SATA M.2 feels like it’s being treated unfairly. Oh, the irony! Edited August 9, 2022 by An0maly_76 Updated, more info

F
FamusLuna
Member
202
08-14-2021, 08:58 PM
#7
I operate about 20 seconds after powering on to log in on a WB 850 1TB... 15 seconds works well. The issue arises when you type your password and it remains active for 15 seconds before showing the desktop.
F
FamusLuna
08-14-2021, 08:58 PM #7

I operate about 20 seconds after powering on to log in on a WB 850 1TB... 15 seconds works well. The issue arises when you type your password and it remains active for 15 seconds before showing the desktop.

S
Spikerex800
Junior Member
36
08-14-2021, 10:32 PM
#8
Most of the boot time is spent by the BIOS checking and setting up hardware. Turning off unnecessary devices and configurations in the BIOS can speed things up—this is what the fast boot feature does, though it’s a BIOS setting rather than a Windows one. The downside is that adding or modifying devices might cause issues during startup. The remaining time comes from Windows loading, which usually takes 3 to 6 seconds. You can slightly reduce this by disabling non-essential startup programs, though it will have little impact since Windows often loads them in the background after the desktop appears. In my experience, a boot from cold to desktop in under 25 seconds is fine.
S
Spikerex800
08-14-2021, 10:32 PM #8

Most of the boot time is spent by the BIOS checking and setting up hardware. Turning off unnecessary devices and configurations in the BIOS can speed things up—this is what the fast boot feature does, though it’s a BIOS setting rather than a Windows one. The downside is that adding or modifying devices might cause issues during startup. The remaining time comes from Windows loading, which usually takes 3 to 6 seconds. You can slightly reduce this by disabling non-essential startup programs, though it will have little impact since Windows often loads them in the background after the desktop appears. In my experience, a boot from cold to desktop in under 25 seconds is fine.

M
Mostok
Member
134
08-16-2021, 07:54 PM
#9
Thanks for the feedback. It's surprising how quickly things run—especially compared to other builds I've set up. The 5-second boot time might be linked to the fresh installation, and enabling bootlog helped me check for issues. The list of loaded and unloaded files looks normal, so it’s hard to pinpoint a specific bottleneck right now.
M
Mostok
08-16-2021, 07:54 PM #9

Thanks for the feedback. It's surprising how quickly things run—especially compared to other builds I've set up. The 5-second boot time might be linked to the fresh installation, and enabling bootlog helped me check for issues. The list of loaded and unloaded files looks normal, so it’s hard to pinpoint a specific bottleneck right now.