• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
oskingen

Long startup boot time

33 posts in this topic

Hi, I have vista sp1, no application at startup expect kaspersky antivirus, some services disabled, disk defragmented. Normally it take 3-4 loading bar but now i pass to 18 loading. My configuration is still the same.

Where can i find the issue ? what can be the cause ? It's one thing i can not understand. If you know something please help

0

Share this post


Link to post
Share on other sites
Hi, I have vista sp1, no application at startup expect kaspersky antivirus, some services disabled, disk defragmented. Normally it take 3-4 loading bar but now i pass to 18 loading. My configuration is still the same.

Where can i find the issue ? what can be the cause ? It's one thing i can not understand. If you know something please help

Well, as far as I know it happens mostly because of some driver. In my case they were nividia drivers. So I adopted laptop2video nividia drivers and startup is faster.

I hope it hellps

0

Share this post


Link to post
Share on other sites

yeah i understand but when i install my drivers it's fine, the problem happened maybe 3 weeks after my install

0

Share this post


Link to post
Share on other sites

Hard to say, but it's usually driver-related. You could use Process Monitor to monitor the boot log and then analyze it once rebooted to see what is happening during boot. Vista also has boot logging you can enable, although I've found that to be less than helpful in most cases (which is why I suggest process monitor instead).

0

Share this post


Link to post
Share on other sites

Thank, i'll take a look

0

Share this post


Link to post
Share on other sites

take a look into the event log under "Application and service protocols"->Microsoft->Windows-> DiagnosticsPerformance you can filter for log messages about slow startup and shut down causes.

0

Share this post


Link to post
Share on other sites
take a look into the event log under "Application and service protocols"->Microsoft->Windows-> DiagnosticsPerformance you can filter for log messages about slow startup and shut down causes.

Thank man!

0

Share this post


Link to post
Share on other sites

I'm not familiar with event viewer. I did what you suggest. for example in the picture below. where can i determine exactly the cause of the problem because i can see a long degradation time but i don't know what is it

post-172411-1210284390_thumb.jpg

Edited by hannubys
0

Share this post


Link to post
Share on other sites

If you look in \Windows\system32\GroupPolicyUsers, do you have any files or folders in there?

0

Share this post


Link to post
Share on other sites
If you look in \Windows\system32\GroupPolicyUsers, do you have any files or folders in there?

Nothing inside

0

Share this post


Link to post
Share on other sites

your best bet is to use Process Monitor, it will give you an excellant understanding of what is happening when your machine boots up

0

Share this post


Link to post
Share on other sites
If you look in \Windows\system32\GroupPolicyUsers, do you have any files or folders in there?

Nothing inside

OK, so please download process monitor and get a boot log. Once you reboot, open process monitor and save the log as a .pml file (the default), and then compress it and put it somewhere we can all look at it :).

0

Share this post


Link to post
Share on other sites

Ok, I did that. I put the file here. I appreciate your help because i'm not able so far to understand the cause.

log file

Edited by hannubys
0

Share this post


Link to post
Share on other sites

this is Superfetch. It load a lot of files into the RAM so that you can start programs much faster. Try to disable Superfetch temporary and restart your PC to test if it starts faster.

0

Share this post


Link to post
Share on other sites

I use this app. DTWEAK Pro. It's a free trail, it'll do disk cleanup and defrag, registry cleanup and defrag, check hard drive health, and so you a list of all things running at bootup. I ran the Vista ver. on my computer and it helped a little. But of course the only thing to help Vista is XP. :lol:

0

Share this post


Link to post
Share on other sites
this is Superfetch. It load a lot of files into the RAM so that you can start programs much faster. Try to disable Superfetch temporary and restart your PC to test if it starts faster.

I tried this too. even with superfetch disable. it's the same. my drive is clean, defragmented.

tell me if i have to delete also all files in Windows\Prefetch folder.

Edited by hannubys
0

Share this post


Link to post
Share on other sites

This happens to me too, at beginning vista loads faster but after some time booting slows a lot. don´t know why.

0

Share this post


Link to post
Share on other sites

According to this, we go from the initial call into starting smss.exe at 10:26:11 to winlogon.exe starting to begin processing for the "Welcome" screen at 10:26:23 (12 seconds), and almost all of the time between is csrss.exe parsing the registry hives that are being loaded (this does take time, so if your registry gets "large" over time, booting WILL be slower). Winlogon takes ~1second to get to it's LSA call to be ready to accept credentials, and from there I see lsass.exe and wininit.exe starting up (meaning we're loading the security subsystem) and then services.exe kick in to start up the "delayed start" services (at approximately 10:26:26), and then the logonui.exe begins (to actually display the Welcome page). From there, we go through svchost parsing the power settings and event logging, and then we start processing group policy extensions at 10:26:36 (10 seconds later). This takes less than a second, and I see you started to get a desktop (explorer.exe) at 10:26:37, and from there everything appears to be working swimmingly.

Therefore, it appears that we're parsing the registry hives for power and service start information where the largest delay is, so perhaps this is either registry bloat, or a driver that's causing the delay? It's not obvious here, and the event log stating that policy processing caused the delay is not entirely accurate - we weren't able to process policies until the registry and power scheme checks completed, and those are the things that are taking most of the boot time you would notice...

0

Share this post


Link to post
Share on other sites

yeah and i'm not able to diagnostic this. i don't know what to do. I'll make some tests. the thing strange is that i installed all my softwares, drivers the same day because i use a script to make this in silent install and the problem appeared 2 weeks later.

Edited by hannubys
0

Share this post


Link to post
Share on other sites
yeah and i'm not able to diagnostic this. i don't know what to do. I'll make some tests. the thing strange is that i installed all my softwares, drivers the same day because i use a script to make this in silent install and the problem appeared 2 weeks later.

From your problem description and the procmon log, your box spends the most time during boot scanning the registry (not sure why). Have you added or modified any software since you built the box?

We will probably have to break out the more advanced tools to get this:

1. Download and install the Windows Performance Tools Kit (x64 package for 64 bit) - choose the "complete" option during install

2. Open a command prompt, and type the following command:

"xbootmgr -trace rebootCycle -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP"

replace C:\TEMP with any temp directory on your machine as necessary to store the output files

This will reboot your box. Once it does, log back in and once the countdown time finishes, you should now have some files in C:\TEMP. I'm interested in the .cab file, specifically.

0

Share this post


Link to post
Share on other sites
yeah and i'm not able to diagnostic this. i don't know what to do. I'll make some tests. the thing strange is that i installed all my softwares, drivers the same day because i use a script to make this in silent install and the problem appeared 2 weeks later.

From your problem description and the procmon log, your box spends the most time during boot scanning the registry (not sure why). Have you added or modified any software since you built the box? If not, let me know.

what do you mean by built the box? (i'm french). and no, i didn't add or modify any software.

0

Share this post


Link to post
Share on other sites

Well, I won't get into the debate between French and French-Canadian since you may actually be from France, but I do have something you can try - we will probably have to break out the more advanced tools to get this:

1. Download and install the Windows Performance Tools Kit (x64 package for 64 bit) - choose the "complete" option during install

2. Open a command prompt, and type the following command:

"xbootmgr -trace rebootCycle -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP"

replace C:\TEMP with any temp directory on your machine as necessary to store the output files

This will reboot your box. Once it does, log back in and once the countdown time finishes, you should now have some files in C:\TEMP. I'm interested in the .cab file, specifically.

0

Share this post


Link to post
Share on other sites
what do you mean by built the box?
"Box" in this case means "computer", without the screen, so the housing and all what´s inside.
0

Share this post


Link to post
Share on other sites

Well, I speak in software terms unless I'm in the hardware forums, so in this case I do actually mean "installed Windows+apps" == built the box.

0

Share this post


Link to post
Share on other sites
Well, I speak in software terms unless I'm in the hardware forums, so in this case I do actually mean "installed Windows+apps" == built the box.

I installed the software et launch the command.

here is the link .cab file

yeah i'm from france :thumbup

Edited by hannubys
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.