Tweaking boot time (classpnp.sys?)

[Echo147]

I'm looking for ways to reduce my reboot time (102 seconds according to this script). I've pruned BIOS routines and startup items, which leaves the bit in the middle.

I realise on HDDs (3 x F3s in RAID0; 6.1 WEI; 350MB/s sequentials) I'll never see the sub-60 second reboot times of SSDs, but I get the feeling Windows is dithering when it hits classpnp.sys (the last driver I see loading).

Since \Windows\ntbtlog.txt has no time stamps I'm testing with safe mode so I can watch the drivers as they load. Everything up to classpnp has no delay, loading about 10 per second, but after this final driver there's ~35 seconds of no HDD activity before a black screen then welcome screen.

Short of unplugging loads of hardware, is there a way I can analyse what it's doing?

Cheers

 

[cluberti]

Normally I wouldn't just link to a site outside of sevenforums, but this is not a shameless plug - there's a very good thread on MSFN's forums on how to use xperf to trace boot time issues (amongst other things) here that you might want to have a look at.

 

[Digerati]

Your computer boots in less than 2 minutes and you are complaining? Why? There's nothing wrong with 102 seconds, especially with a RAID. And besides, longer boot times are no indication of system performance once the system is booted - and that's where it counts.

 

[Echo147]

Normally I wouldn't just link to a site outside of sevenforums, but this is not a shameless plug - there's a very good thread on MSFN's forums on how to use xperf to trace boot time issues (amongst other things) here that you might want to have a look at.

Thanks for that, some very detailed info it spits out!

Your computer boots in less than 2 minutes and you are complaining? Why? There's nothing wrong with 102 seconds, especially with a RAID. And besides, longer boot times are no indication of system performance once the system is booted - and that's where it counts.

Doesn't everyone here (this section at least!) strive to get 7 running best as possible? Even when I briefly had an SSD (RealSSD 256GB - died on day 1) it was a disappointing 89 seconds, up to triple the time of some of these times.

 

[cluberti]

Wow. I've got a rather "old" setup (admittedly 2x WD Raptor 10K 74GB drives for the OS) that boots in ~45 seconds, from right after the POST to usable desktop. 102 seconds is a long time, even for a single-drive system - sounds like either your filesystem isn't configured for the correct cluster size, or you have a ton of boot drivers, or services starting automatic, etc. 102 seconds isn't "bad", but it's not good either.

 

[Digerati]

Doesn't everyone here (this section at least!) strive to get 7 running best as possible?

"Running" yes, but boot times is not an indication of performance! And it is immaterial once the system boots completely. And I disagree with cluberti's comment that 102 is not good. Once again you are setting up a RAID during boot and that is a big thing. Also we don't know what else you are loading at start - and that depends entirely on your specific hardware configuration. Many systems take 3 or 4 minutes or longer to fully boot and load up everything at start.

Once again, performance after the full boot is the key factor in determining system performance. After all, most people only boot once a day, if that.

 

[flez]

. Once again you are setting up a RAID during boot and that is a big thing. .

Is the raid not in hardware, most motherboards have onboard raid these days, my raid needs nothing, its even visible from a cd boot.

 

[Digerati]

my raid needs nothing

Not true! It is setup in the BIOS and is loaded every time it boots.

 

[Echo147]

It does add 10-15s to my boot time, not much I can do about that.

 

[madtownidiot]

IMHO, if it takes more than one minute to boot after POST, either something is wrong or there are too many processes running at startup. I have yet to see a system capable of running 7 that I couldn't tweak to boot in less than a minute without reducing any of it's functionality

 

[CarlTR6]

Doesn't everyone here (this section at least!) strive to get 7 running best as possible?

"Running" yes, but boot times is not an indication of performance! And it is immaterial once the system boots completely. And I disagree with cluberti's comment that 102 is not good. Once again you are setting up a RAID during boot and that is a big thing. Also we don't know what else you are loading at start - and that depends entirely on your specific hardware configuration. Many systems take 3 or 4 minutes or longer to fully boot and load up everything at start.

Once again, performance after the full boot is the key factor in determining system performance. After all, most people only boot once a day, if that.

+1. Well said.

 

[Digerati]

or there are too many processes running at startup.

Now wait! What's to say "too many"? And what's to say a lot is "bad"? Many folks have cameras, card readers, external drives, printers, email programs, PDA devices, various security programs including AV, AS, FW programs, HW monitors, special mouse and keyboard programs, dual monitors, networked/mapped drives, etc. that start at boot. I say again, as long as the system is running fine once it is fully booted, then a long (3 - 4 minutes) boot time does not indicate a "problem". Some XP systems can take 5 - 6 minutes to boot, then run great all day long.

There is no harm in having many processes run at startup as long as you have the resources (namely RAM) to support them after the boot is complete.

 

[Laker]

I'm new here and am puzzled why someone would want to wait up to 4 minutes for their system to boot. FYI - my normal boot time 23 seconds as timed by program boottimer.exe. And no it is not an ssd. It's a 5400 RPM HDD (WD2500BEVS).

I'll admit though, I am not well versed with Raid configurations. I just can't imagine troubleshooting program or driver issues with that long of a boot time. I'd pull my hair out. Wait, can't I'm already bald. LOL.

How much time does this add to a single system hdd setup?

 

[logicearth]

How much time does this add to a single system hdd setup?

RAID is for multi-drive systems.

 

[Laker]

logic - sorry I didn't make my question clearer. When comparing single hdd to multi-hdd setup (Raid), how much time does the Raid configuration add?

 

[Digerati]

I'm new here and am puzzled why someone would want to wait up to 4 minutes for their system to boot.

Nobody said that! But what I did say, and what I am saying again is that boot times is NOT an indication of performance.

 

[Laker]

Originally Posted by Digerati
Nobody said that! But what I did say, and what I am saying again is that boot times is NOT an indication of performance.

Digerati - please don't take offence but my question of why someone would want to wait up to 4 minutes for their system to boot was taken from your quote.

"Many systems take 3 or 4 minutes or longer to fully boot and load up everything at start."

Did I misunderstand your meaning? Again I have little experience with RAID set ups but am posing questions to have a better understanding. Does a raid set up add significant time to the booting of an Win7 OS? If so how much time... 10, 30, 60 seconds?

I am having a hard time getting around the aggravation that even a 2+ minute reboot would pose while troubleshooting a system let alone your mentioned 3-4 minutes.

 

[pparks1]

Hmmmm.....my Western Digital Caviar blue 500GB in my desktop computer at work boots into Windows 7 in about 40 seconds. But then, I also don't install a lot of software and such...only what I need. Do you have a lot of stuff installed on your hard drives?

 

[Digerati]

Originally Posted by Digerati
Nobody said that! But what I did say, and what I am saying again is that boot times is NOT an indication of performance.

Digerati - please don't take offence but my question of why someone would want to wait up to 4 minutes for their system to boot was taken from your quote.

"Many systems take 3 or 4 minutes or longer to fully boot and load up everything at start."

Did I misunderstand your meaning?

No offense taken but you did, and still are twisting the meaning of my words around. You say you took it from my quote but I NEVER said or implied that anyone wants to wait for anything! The fact is, most computer users would prefer instant on, if possible, and would rather not wait at all.

So again, I am not speaking about desires. I am merely stating, again, that long boot times is not an indication of performance.

 

[Laker]

Yes, you have stated your point several times now. I did not nor am I attempting to "twist the meaning of your words".

I am attempting to understand whether a raid set up add significant time to the booting of a Windows 7 OS? If so how much time... 10, 30, 60 seconds? Would you be willing to provide an answer?