Windows 10: Extremely slow boot times, sometimes between 3-5 minutes. Trace files inside.

Hi,

So I recently built a new PC, installed a fresh Windows 10, updated to 1909 and I have extremely slow boot times. Especially on the first boot. The restarts are faster but still slow. Usually stuck on the "Restarting" and "Shutting down" a really long time. Then it is usually stuck on the spinning white circles of windows 10.

Another interesting fact is that it seems to take a long time for Audio and Video drivers to even load. I have a 144hz monitor, but it takes sometimes up to 5 minutes, or longer, for the monitor to switch from 60hz to 144hz on boot. I have tried with two different monitors to that is not the issue itself. Also when I hover over the speaker icon in the tray, I just see "Audio service is not running" for around 4-5 minutes until it loads.

I ran a couple of boot traces. One of them ended up with a BSOD with the message "VIDEO_SCHEDULER_INTERNAL_ERROR". I'm not sure what the reason for that is, I have never seen it before.
----

Here is the first boot trace:

https://www.transfernow.net/aA7BAO042020

Here is the boot trace with the BSOD:

https://www.transfernow.net/fvsNGT042020

Hope anyone can help me out. Would be very appreciated.

---

Specs:

AMD Ryzen 3700x
AMD Radeon 5700 XT
Corsair SF450 V2 Platinum+
Corsair Vengeance LPX 32GB 3200Mhz
Aorus X570 I Pro Wifi
Corsair MP510 480 GB M.2 NvME

submitted by /u/ashba89
[link] [comments]

:)

 

Very slow boot-up time (over three minutes)

Hi,

There was many events that was dropped during the boot trace, but there is enough data to undertake a troubleshooting.





First, the majority of the delay happens in the Session init phase. in this phase the OS primarily load and initialize drivers.

I have identified two suspect drivers:

• NoMachine Hub that causes a boot delay of 12s. Windows try to reload the catalog to check the code integrity for this driver because it's a non-embedded-signed driver. So try to upgrad to the latest version of NoMachine application.

• But the biggest delay is caused by Intel Management Engine driver ( 90 s)

you have the version 11.7.0.1057. There is a newer version available on the Intel website Download Intel® Management Engine Consumer Driver for Intel® NUC Kit NUC7i3DN

Update this driver and see if that help.

Finally take another boot trace.

 

Extremely Slow Boot Time (3 min)

Hi, I recently purchased a laptop with windows 10 x64. The product specifications are these: Star Wars™ Special Edition Notebook - 15-an001na (ENERGY STAR) Product Specifications | HP® Customer Support


It's a HP laptop. The boot up time close to 3 minutes goes like this:

• 40 seconds: the HP logo screen with a loading circle
• then ~2 minutes: black/empty screen with a loading circle
• then comes the log in screen with the time and date
• and after that 20 seconds of the Welcome screen with the loading circle

I also mention that at least 5 minutes after that the disk is at 100%

I tried to disable some services and tasks but it didn't make much of a difference, Glary Utilities tells me there are 171 programs, services, etc running at startup.

I attach a list of them though I know it's huge so I don't ask for someone to go through all of them, but is there a list of what startup programs (9), scheduled tasks (69), plug ins (6), application services (40) and windows services (47) are absolutely mandatory so I can disable the rest? The numbers in brackets refer to the current amount of said services.

Thank you for any help!

 

Extremely Slow Boot Time (3 min)

I would recommend the following actions:

Selectively uninstall any HP bloatware you don't want or need.

Disable all non-essential services (for a test). Here's how:

Go to Start> Run> (type) msconfig.exe

A new window opens. Select the Services tab:




Now, tic the box to hide all MS services:




Now review the non-MS services that remain.

From here you can start to disable services and reboot periodically to see if there is any improvement.
(You can always re-enable them if an issues arises)

However, in the end, you may end up leaving many of them permanently disabled.

Hope this helps,