XP startup time sometime very slow

[asperamanca]

Hello all,

I have installed XP prof to a new computer, and often it boots in about
the time I would expect (maybe 30-40 seconds from end of bios screen to
desktop).
Sometimes however, the boot time is twice to three times as long. The
boot GUI shows, and the "progress indicator" (or whatever you want to
call it) moves, but there doesn't seem to be much HD activity. Then,
after a while, HD flickers again, and then it's only a few seconds to
the desktop.
The installation is pretty bare right now, with mostly the default
windows services running, graphics and mainboard drivers are installed,
and Virus Scan Enterprise is up and running.
I also have a workgroup, and have defined some shares.

Any ideas where I might start looking?

Thanks in advance!

Robert

 

[Alias]

Hello all,

I have installed XP prof to a new computer, and often it boots in about
the time I would expect (maybe 30-40 seconds from end of bios screen to
desktop).
Sometimes however, the boot time is twice to three times as long. The
boot GUI shows, and the "progress indicator" (or whatever you want to
call it) moves, but there doesn't seem to be much HD activity. Then,
after a while, HD flickers again, and then it's only a few seconds to
the desktop.
The installation is pretty bare right now, with mostly the default
windows services running, graphics and mainboard drivers are installed,
and Virus Scan Enterprise is up and running.
I also have a workgroup, and have defined some shares.

Any ideas where I might start looking?

Thanks in advance!

Robert

Check your power supply.

Alias

 

[asperamanca]

Check your power supply.

Alias

In what way should I check my power supply? I haven't had any trouble
that I would point to the power supply (inexplicable crashes while both
CPU and GPU are running flat out, or, for that matter, any instability
while XP is actually running).

Robert

 

[Alias]

In what way should I check my power supply?

Replace it with a known good one or use a voltage meter.

I haven't had any trouble
that I would point to the power supply (inexplicable crashes while both
CPU and GPU are running flat out, or, for that matter, any instability
while XP is actually running).

Robert

I had the same problem you have and replacing the power supply fixed it.
After I removed it, I opened it and it was full of dust.

Alias

 

[asperamanca]

Additional info:
I've just run BootVis and tested the bootup performace. According to
this MS-Tool, the computer does absolutely...nothing for about 110
seconds.

 

[Depresion]

Hello all,

I have installed XP prof to a new computer, and often it boots in about
the time I would expect (maybe 30-40 seconds from end of bios screen to
desktop).
Sometimes however, the boot time is twice to three times as long. The
boot GUI shows, and the "progress indicator" (or whatever you want to
call it) moves, but there doesn't seem to be much HD activity. Then,
after a while, HD flickers again, and then it's only a few seconds to
the desktop.
The installation is pretty bare right now, with mostly the default
windows services running, graphics and mainboard drivers are installed,
and Virus Scan Enterprise is up and running.
I also have a workgroup, and have defined some shares.

Any ideas where I might start looking?

Thanks in advance!

It could be that windows is looking for networked resources (shared printers and
drives on another computer) or some other hardware taking a long time to
respond. Try removing some hardware part by part (or disabling it in the bios)
and try a few boots to see if things get better with one component missing.

 

[asperamanca]

It could be that windows is looking for networked resources (shared printers and
drives on another computer) or some other hardware taking a long time to
respond. Try removing some hardware part by part (or disabling it in the bios)
and try a few boots to see if things get better with one component missing.

Difficult, since it happens only on occassion. So I can't say for sure
it the change I made made any change, so to spieak ;-)

I'm currently completely re-installing XP, since I had a few other
problems as well, so I'll see how it works then

 

[asperamanca]

The power supply is brand new and top quality...but if it still occurs
after the re-install, it's something to check. Thanks

 

[Alias]

The power supply is brand new and top quality...

Made in China?

but if it still occurs
after the re-install, it's something to check. Thanks

I may also be other hardware.

Alias

 

[asperamanca]

Well, what isn't made in China, nowadays?
I'm pretty much aware that bad hardware can do bad things. It was worse
with Win95/98 than it is with XP, but software can only do so much.

 

[Alias]

Well, what isn't made in China, nowadays?

My point is just because it's new doesn't mean it's in good shape. I
have had to return "brand new" hard drives and motherboards that were
defective "out of the box". I asked a supplier and they told me that 3
out of 100 motherboards arrive defective.

I'm pretty much aware that bad hardware can do bad things. It was worse
with Win95/98 than it is with XP, but software can only do so much.

It's your computer but if it were mine, I'd be checking the hardware,
not the software.

Alias

 

[asperamanca]

You have a point, but there's only so much I can check without actually
opening it and digging out some electronic equipment. The voltage
levels (that the mainboard displays) seem OK, and from the outside it
looks fine. If the problems persist after I've tried everything on the
software side, I can go to the shop and ask they check it. But they
tend to charge money if they find it's returned but was in good shape.

 

[asperamanca]

I have a hunch..I disabled AMD's Cool'n Quiet in the BIOS, and didn't
have the problem ever since...so far. Does anyone else know whether
this might be the reason?

 

[Alias]

I have a hunch..I disabled AMD's Cool'n Quiet in the BIOS, and didn't
have the problem ever since...so far. Does anyone else know whether
this might be the reason?

When I had the problem, weeks would go by without incident. Then, out of
the blue, it would start happening again. Hardware is hard to
troubleshoot and the only thing you can do to be sure is to swap with
known good hardware to find the culprit.

Alias