Solved Computer takes about 1.5 minutes to load the desktop + icons

[shadedgrey63]

Granted my computer's now 4-5 years old. I was wondering if anyone has an idea on this. I ran chkdsk, Malwarebytes, and Ccleaner. All were clear but the last, which fixed many things, but I still have the issue. I have minimal programs that run on start-up, so I highly doubt it's that. I analyzed my disc with Windows Defragger, but came back as 0% fragmented. I've been thinking that maybe I need more RAM...or possibly even a new hard drive; I can take care of those if I need to, but is there anything else I can try first?

 

[ignatzatsonic]

You've got plenty of RAM.

How many processes are running in Task Manager after a reboot? Have you looked at the list of non-Microsoft services running after a reboot?

I notice you have a bunch of hard drives listed in your specs.

Do you see any boot time improvement if you disconnect all of those external drives and USB devices?

It took me about 55 seconds to boot with a fast 7200 rpm hard drive and no external devices other than monitor, mouse, and keyboard in the days before I bought an SSD. I have a processor slightly faster than yours. I'd say your boot time is within the normal range.

 

[shadedgrey63]

That is only after the Windows screen, which also displays for a minute or longer. It's been getting worse for a while. It takes 3-5 minutes to fully boot up, and Event Viewer shows errors occur during boot. And I don't have anything connected via USB, other than my mouse/keyboard. I'll check the Task Manager after boot up later.

Edit: I checked, and those "several drives" are built in multimedia card readers, which I haven't used in ages. There are about 23 processes in Task Manager after startup.

 

[shadedgrey63]

I solved this on my own. My computer boots at its normal speed now. I use a Nvidia Graphics Card, and I had *several* recent (around the time I boot up) errors related to NvStreamSvc.exe (which seemingly comes with Nvidia drivers) in my Event Viewer. I decided that must be related, and looked up the file/error. It turns out, disabling that service from running on start up fixed similar problems for some people; I tried it, and it seems to have worked for me.