Changing CPU host speed, system bus speed

[John Doe]

The beat goes on.

Been having some very weird freezing/crashing lately. Yesterday
evening, I lowered the CPU host frequency (same as system bus
speed I guess) from 333 MHz down to 300 MHz. Messed around with
the computer all day but could not get it to crash. Had all sorts
of stuff running, including lots of Internet connections of
various types. Now it is very late in my day. Just ordered a new
power supply in case lowering the system bus speed put less of a
strain on one of the power supply outputs.

While waiting for a new power supply, I further lowered the system
bus speed from 300 MHz down to 266 MHz. Booted into Windows XP
SP3. Before anything except Windows Explorer opened (nothing on
the system tray), my PC froze.

So I guess it is not the power supply.

Immediately after that freeze, as usual the HDD started clicking
continuously, this time for at least 90 seconds until it stopped.

At least I have another lead.
Maybe 332 MHz will work.

 

[John Doe]

While waiting for a new power supply

According to my posting history, I have been using the Antec
TPII-380 since October 2006. The PS I just ordered is an OCZ
OCZ500MXSP ModXStream Pro 500 Watt Power Supply.

 

[RayLopez99]

The beat goes on.

Been having some very weird freezing/crashing lately. Yesterday
evening, I lowered the CPU host frequency (same as system bus
speed I guess) from 333 MHz down to 300 MHz. Messed around with
the computer all day but could not get it to crash. Had all sorts
of stuff running, including lots of Internet connections of
various types. Now it is very late in my day. Just ordered a new
power supply in case lowering the system bus speed put less of a
strain on one of the power supply outputs.

While waiting for a new power supply, I further lowered the system
bus speed from 300 MHz down to 266 MHz. Booted into Windows XP
SP3. Before anything except Windows Explorer opened (nothing on
the system tray), my PC froze.

So I guess it is not the power supply.

Immediately after that freeze, as usual the HDD started clicking
continuously, this time for at least 90 seconds until it stopped.

At least I have another lead.
Maybe 332 MHz will work.

Why not quit while you're ahead? If 300 MHz works, why play around
with other settings?

RL

 

[Paul]

According to my posting history, I have been using the Antec
TPII-380 since October 2006. The PS I just ordered is an OCZ
OCZ500MXSP ModXStream Pro 500 Watt Power Supply.

When you have the TPII-380 out of your computer case,
remove the cover and inspect visually for bad caps.
I lost a True 480 to bad caps, and maybe your power
supply is another ChannelWell design. In mine, it
causes a bad 5V rail.

Paul

 

[GMAN]

According to my posting history, I have been using the Antec
TPII-380 since October 2006. The PS I just ordered is an OCZ
OCZ500MXSP ModXStream Pro 500 Watt Power Supply.

Changing bus speed would not cause your drive to click like that. Its most
likely your drive failing. try downloading this program, HD Sentinel, and
tell us what it says is the health of your drive.

http://www.hdsentinel.com/

Direct link to program
http://www.hdsentinel.com/hdsentinel_free_setup.zip

 

[John Doe]

John Doe wrote:

When you have the TPII-380 out of your computer case, remove the
cover and inspect visually for bad caps. I lost a True 480 to
bad caps, and maybe your power supply is another ChannelWell
design. In mine, it causes a bad 5V rail.

It was examined about six months ago, but anyway... If you suspect
the power supply, how do you explain the thing working at a system
bus speed of 300 MHz and not working at a system bus speed of 266
MHz or 333 MHz? Clearly there is something wrong since 330 MHz is
the default speed that was used for years, but how can it be the
power supply?





--
I did not think it was the power supply, considering the fact that
running Supreme Commander 2 hogwild does not cause crashing. But
having used the 380 W supply for over four years, it should be
replaced anyway. And I can use a modern supply, and a spare
supply since my old computer was recently given up.

 

[John Doe]

Sorry... 333 MHz, not 330 MHz.

 

[John Doe]

Why not quit while you're ahead? If 300 MHz works, why play
around with other settings?

What the **** are you talking about?
--

 

[John Doe]

John Doe wrote:

If your HD is clicking

That was shorthand for "making HDD sounds". Hearing the thing go
for 90 seconds is odd and notable, but maybe that has something to
do with the HDD trying to find itself after Windows freezes, or
doing cleanup work, or whatever.

then that is the mostly reason for your PC locking up at any
stage.

It seems to work perfectly when the system bus speed is changed
back to 300 MHz.

One concern is what a spontaneous reboot might do to the HDD, or
when I get frustrated and start pressing the reset button.

I did order some more stuff (needed for backup or troubleshooting
anyway) including another HDD (Western Digital 750 GB Caviar Green
SATA WD7500AADS), but HDD failure does not explain a particular
system bus speed causing freeze ups.

And then there is the fact that it has never frozen or restarted
spontaneously or produced any other weird error/symptom until
after Windows starts to boot.

At the moment I suspect the motherboard or system memory (RAM).
But replacing the motherboard just for troubleshooting is
difficult here. Maybe removing one or two (of four) memory sticks
is in order. Or maybe wait to do anything until after replacing
the power supply.

 

[Paul]

It was examined about six months ago, but anyway... If you suspect
the power supply, how do you explain the thing working at a system
bus speed of 300 MHz and not working at a system bus speed of 266
MHz or 333 MHz? Clearly there is something wrong since 330 MHz is
the default speed that was used for years, but how can it be the
power supply?

OK, the thing is, when you change bus speed, you need to use
CPUZ to review *all* the results. Both memory and CPU bus
speed, memory timings, may need to be adjusted. The reason
for the checking, is you can't trust the BIOS to do the
right things, when you make adjustments.

Paul

 

[RayLopez99]

What the **** are you talking about?
--

STFU pottymouth. You yourself said your system does not crash at 300
MHz. Then you bitch and moan that it does crash at other settings.
So leave it the fk alone at 300, shiite-->4 brains.

You that stupid? I guess so.

RL

 

[John Doe]

OK, the thing is, when you change bus speed, you need to use
CPUZ to review *all* the results. Both memory and CPU bus speed,
memory timings, may need to be adjusted. The reason for the
checking, is you can't trust the BIOS to do the right things,
when you make adjustments.

Hopefully that is correct and the only thing left to clean up.
Will find out later. Thanks.