Software

Ask something
Question Locked

Win XP Slow Boot

0 helpful
5 replies

by vipergxy

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've been lately having a problem with my winXP system's boot on my Dell Inspiron 9300 laptop. It hangs on the splash screen and takes several minutes to load. Up until a few weeks ago I never had a similar problem. I have checked event viewer and there are no warnings or errors that correspond to the time the splash screen is loading, but some information events that are sourced from bootlog no-loads. I have not yet tried to boot with a /sos command, but it should give me the same info as my bootlog right?

My only thoughts would be that somehow my drivers are conflicting from some recent update that I must not remember (though how I could tell which ones I don't know, I've always been that moron who's too lazy to uninstall outdated drivers when upgrading them) or it's something to do with my svchost crash (which I never did fix, simply disabled automatic update and I'm stuck manually updating, another problem for another time and not likely the cause here). Anyhow I've included my bootlog excerpt (just drivers not loaded) below and will continue to troubleshoot (system scans, reg cleaning, etc.), maybe its time to just wipe windows and do a clean reinstall if I can find my disks.

Loaded driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS <---- Weird that it says loaded and then not loaded........
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Did not load driver \SystemRoot\system32\DRIVERS\kbdhid.sys
Did not load driver \SystemRoot\system32\DRIVERS\serial.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Did not load driver \SystemRoot\system32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Did not load driver \SystemRoot\system32\DRIVERS\ipnat.sys
Did not load driver \??\C:\Program Files\Norton Internet Security\Norton AntiVirus\SAVRTPEL.SYS
Did not load driver \SystemRoot\system32\DRIVERS\Ip6Fw.sys

5 replies

by older mycroft

For all the above non-loaded entries I think you'll find they didn't contribute to your boot delay. Chances are they occurred within a few microseconds of each other.

If any of them are seconds apart, that is more likely to be a contributing factor.

Unfortunately you didn't post the times as they were reported.

What standard is your hard drive in. A full defrag would not be a bad idea at this time.

by vipergxy

yeah my bootlog (just xp's ntblog.txt) doesn't provide time data for each process, and it seems most bootlog programs are for after windows login when it starts services not drivers. Microsoft Bootvis didn't show any major lags though so you're probably right.
As for my hard-drive its an NFTS file system but it when I used MS Disk Defrag analysis it showed that the drive did not need to defrag itself (I try to do it every month or so). I might give it a shot though... any other ideas how I could fix this? I've been through a number of google searches on various forums but no real definitive answer has come up... same applies to my svchost problem (which when I did use a 3rd party boot log showed a 250+ second boot time).

by alphatech9

Sometimes when it says you don't need a defrag, it is lying to you.....

The analyzer allows for some fragmented files to be scattered about, it does not judge which files are the ones that are scattered. I would run a disk clean-up and then a defrag. Also make sure no programs are set to start-up with the OPSYS.

by older mycroft

Access it from Start > Administrative Tools > Event Viewer. (Or something like that - can't remember the path since I tuned mine up).

It'll give the same list but when each item happened.

A 250+ second boot time for a standalone does seem excessive.

This discussion is closed to new replies.