XP pro boot problems- pauses before desktop for 90 seconds

[Tyson82]

This is just a recently acquired problem, although I cant remember exactly when it started or think of anything that might have casued it.


My boot time has become ungodly long. System boots fine until I get the wallpaper, then the system hangs for 100 seconds.

I ran Microsoft's Bootvis to try to get a full boot trace, it shows absolutely no disk activity from vsmon.exe to nvraidservice.exe 100 seconds later.

Unfortunately Bootvis won't trace the driver delay, nor will it run the optimization option.

I have run AVG, Ad-Aware, Spybot, and Zone Alarm's spyware detection prog. Ive defragged the page file, the registry, run registry cleaners, and hard drive tests.

I have found nothing out of the ordinary. I used 'What's Running?' to check out the drivers in memory, removed a couple of things, but nothing of any consequence.

Also, removed and reinstalled shipset and video drivers.

Any idea is welcome. Obviously Im overlooking something, just don't know what.

Thx in advance

 

[pcgeek11]

I've seen network drivers causing these kinds of delays. Check the network.

pcgeek11

 

[Cr0nJ0b]

I've also seen this type of lag when I have a CD or DVD in the drive as the system tries to scan for data.

Basically, you need to think about anything that the computer needs to connect to before starting up. Like mapped drives, virtual drives etc...anything that would normally be quick to look up might be slow. eg., a virtual drive that isn't working properly...the system thinks it's there, and keeps retrying, but can't get a link to it.

 

[Tyson82]

hmm. thanks for the replies.

Im not showing any network component problems in device manage. And reinstalling the chipset drivers should have taken care of that, I would have thought anyway.


And Ive made sure there is no media in my drives, flash drives are unplugged, etc. The odd thing is that there is no activity at all according Bootvis. No CPU activity, no disk activity.

 

[greylica]

No, he is talking about a DHCP delay to aquire the adress. This problem can be caused too with problems in the cache of the processor, ECC errors may cause the problems and until your processor is up with the kernel fully running, nothing happens. I see that you overclock your system, Lower the overclock to standard paramenters, and make a full test with memtest to see if nothing is wrong. If nothing is wrong, when Windows starts for the first time, verify if in the task manager there is an kernel dump file running (Sorry I cannot remember the name now, I am a happy linuxer ) . This indicates that your system was unstable.

 

[coupland]

Sounds like network to me too. Any mapped network drives that can't reconnect? Massive group policies coming down from a domain controller? Roaming profiles? Everything could be working just fine and it could still be network-related while your system is trying to access a resource that's not there or doing massive data transfers in the background. If the machine isn't a member of a domain disable the NIC, reboot, and just see if things are snappy again. That would narrow it down.

 

[Tyson82]

Ive got the onboard NIC enabled, but I havent had a cable connnected in over year.

Oh and my profile is inaccurate, my overclock is currently minimal, only at 1.89. But I will try your suggestion greylica.

 

[Tyson82]

uninstalling Nvidia Network Access Manager didn't help. Neither did disabling the onboard NIC in BIOS.

Any other ideas?

 

[Tyson82]

anyone?

 

[EvilRage]

Same behavior in safe mode?

Also, have you tried unplugging all peripherals not necessary for the PC's operation? Only leave keyboard mouse and monitor plugged in. And hell, if it still does it, try without a keyboard or mouse too. I had a bootup problem once caused by an HP Printer being plugged in while the PC was booting, have to wait until it's completely in Windows to plug it in now.