Brutally slow startup

Toggle sidebar Toggle sidebar
E

eutherin

Distinguished
Jul 13, 2011
14
0
18,510
Hi, after logging in to my computer it takes about 10-15 minutes before I can actually begin to open things, say explorer, etc.
The only things I have set to start on boot are my monitors AV and cooling system
(Coretemp, AVG, NZXT Kraken control)
It sits at ~0% resources used during this whole time, so it's not seeming like it's overloaded.
The pc is all fairly new as well. (Less than a year old)
Does anyone have any ideas as to how I can fix this?

To clarify:
I have an old hard drive, I'm going to try replacing that.
I can log in but if i open programs(Chrome, Recycle bin, etc.) it will take 10-15 min to open.
After about half an hour the issue goes away.
 
Solution
J
I answered a similar post on this forum. I had a similar problem although my hard drive isn't old...
The key to finding out what's going on is to use xbootmgr (from a dos command). This does a reboot, and logs everything that's going on. When the computer is done rebooting, you can go in the windows\system32 folder, and see the trace, and usually this will tell you what's going on. Specificall, you run: xbootmgr -trace boot -verboseReadyBoot
In my case, it was a prefetch issue: the trace showed that superfetch was missing every read, and that can completely kill your startup time. Mine was about 500s from start to finish! I fixed the prefetch issue (I had several issues, the defrag service was disabled, and the prefetch service was on...
Sort by date Sort by votes
E

eutherin

Distinguished
Jul 13, 2011
14
0
18,510

I log in without delay, but then if i double click say recycle bin, it will be 10 minutes before that window opens.

 
Upvote 0 Downvote
E

eutherin

Distinguished
Jul 13, 2011
14
0
18,510

It's pretty much the vital stuff,
19rv0t8.png
 
Upvote 0 Downvote
J

jeanl

Reputable
Feb 27, 2014
3
0
4,520
I answered a similar post on this forum. I had a similar problem although my hard drive isn't old...
The key to finding out what's going on is to use xbootmgr (from a dos command). This does a reboot, and logs everything that's going on. When the computer is done rebooting, you can go in the windows\system32 folder, and see the trace, and usually this will tell you what's going on. Specificall, you run: xbootmgr -trace boot -verboseReadyBoot
In my case, it was a prefetch issue: the trace showed that superfetch was missing every read, and that can completely kill your startup time. Mine was about 500s from start to finish! I fixed the prefetch issue (I had several issues, the defrag service was disabled, and the prefetch service was on delay start), and ran xbootmgr -trace boot -prepsystem -verbosereadyboot (this reboots the computer 6 times, taking notes of what memory needs to be loaded, then at the end uses defrag to layout everything sequentially so the prefetcher grabs everything in one shot the next time you boot).
This lowered the boot time to about 1 minute (along with delaying some services).
But even if your problem isn't prefetch, using xbootmgr will show you what's going wrong.

Another thing that could help you with an old drive is ReadyBoost. Look up the entry in wikipedia, it actually explains better than most posts I've seen on the net. For an old drive that has a very long seek time, it usually helps a lot to user Readyboost. You plug in a USB memory stick, or an sdcard, and the system uses that as a cache (flash memory has very fast "seek" time but not very high throughput). But better yet of course would be to switch your drive if it's very slow.

Jeanl
 
Upvote 0 Downvote
Solution
E

eutherin

Distinguished
Jul 13, 2011
14
0
18,510

Ill give it a try sometime if it ever comes back, i just wiped it.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom