When I turn my computer on it takes awhile for it to boot up, i
should not though because i have a 2.2 ghz processor and 512mb of ra
and 40GB hardrive. My main problem is that when it turns of fully, I
will run for 4 seconds and then freezes for 4 seconds, runs for
seconds then freezes for 4 seconds, and repeats itself. Does anyon
know what the problem could be? I have reformatted it a few times an
i still get the same problem.

Any help would be appreciated, like what hardware i need to replace..

In article <qP5af.24372$(E-Mail Removed)>,
(E-Mail Removed)lid says...
>When I turn my computer on it takes awhile for it to boot up, it
>should not though because i have a 2.2 ghz processor and 512mb of ram
>and 40GB hardrive. My main problem is that when it turns of fully, It
>will run for 4 seconds and then freezes for 4 seconds, runs for 4
>seconds then freezes for 4 seconds, and repeats itself. Does anyone
>know what the problem could be? I have reformatted it a few times and
>i still get the same problem.

Windows looking for a network?

>Any help would be appreciated, like what hardware i need to replace...
>
>
--
Keith

On Wed, 2 Nov 2005 12:22:10 -0500, Keith <(E-Mail Removed)> wrote:

>In article <qP5af.24372$(E-Mail Removed)>,
>(E-Mail Removed) says...
>>When I turn my computer on it takes awhile for it to boot up, it
>>should not though because i have a 2.2 ghz processor and 512mb of ram
>>and 40GB hardrive. My main problem is that when it turns of fully, It
>>will run for 4 seconds and then freezes for 4 seconds, runs for 4
>>seconds then freezes for 4 seconds, and repeats itself. Does anyone
>>know what the problem could be? I have reformatted it a few times and
>>i still get the same problem.
>
>Windows looking for a network?

Thermal throttling?

ok, what are you guys talking about? lo

On Wed, 02 Nov 2005 22:30:39 +0000, Jdude217 wrote:

> ok, what are you guys talking about? lol

Giving you suggestions to try to solve your problem. My guess (and that's
all one can do when long-distance debugging) is that you have a
misconfiguration, or perhaps hardware, issue with your LAN. This often
causes WinBlows to keep searching for, and timing out on, LAN
configuration during boot.

OTOH, 'tripper is guessing that you have mucked the fansink installation
and the processor is overheating causing it to go into thermal throttling.
Again, these are only guesses, but I don't buy the latter because it
happens right on boot. ...could be wrong though!

--
Keith

On Wed, 02 Nov 2005 16:29:10 GMT, (E-Mail Removed)lid (Jdude217) wrote:

>When I turn my computer on it takes awhile for it to boot up, it
>should not though because i have a 2.2 ghz processor and 512mb of ram
>and 40GB hardrive. My main problem is that when it turns of fully, It
>will run for 4 seconds and then freezes for 4 seconds, runs for 4
>seconds then freezes for 4 seconds, and repeats itself. Does anyone
>know what the problem could be? I have reformatted it a few times and
>i still get the same problem.
>
>Any help would be appreciated, like what hardware i need to replace...

First thing that jumps to my mind is a hard drive that is in the
process of dying. I would recommend downloading the diagnostics
software from your hard drive manufacturer and run them ASAP.

-------------
Tony Hill
hilla <underscore> 20 <at> yahoo <dot> ca

thanks everyone for your suggestions. it cannot be the lan card
because i dont even have one installed or a modem, i talk to u guys
from my job. what i'm thinking is its the processor but thats only a
guess. it is a 1.6 Ghz Northwood overclocked to 2.2Ghz... that is
its stable speed i've checkd into it.. but i guess its just dieing,
ive had it since 2002. but anyways, i think i'm going to go ahead
and buy a new powersupply, bigger harddrive, and a new cpu. lol, who
knows it could be my crappy usb mouse, it sucks.

On Thu, 03 Nov 2005 16:31:53 +0000, Jdude217 wrote:

> thanks everyone for your suggestions. it cannot be the lan card
> because i dont even have one installed or a modem,

Oh, yes it certainly *can* be. That's one of the prime suspects, in fact.
WinBLows may be *looking* for it, but can't initialize it so keeps on
trying.

> i talk to u guys
> from my job. what i'm thinking is its the processor but thats only a
> guess. it is a 1.6 Ghz Northwood overclocked to 2.2Ghz...

Well, sheeit. Why would you do something so silly?

> that is
> its stable speed i've checkd into it.. but i guess its just dieing,
> ive had it since 2002. but anyways, i think i'm going to go ahead
> and buy a new powersupply, bigger harddrive, and a new cpu. lol, who
> knows it could be my crappy usb mouse, it sucks.

--
Keith