Computer not booting up right after CPU overclock

[Hamel]

Yay for stupid bullshit

I clocked the CPU from the default 200mhz to 232. When I booted up, no signal went to the monitor, and no power went to the keyboard and mouse. The video card and cpu fans were still working so I'm guessing that nothing was fried. When I reset the computer, it gives long, loud beeps that don't stop unless I boot with the power button.

My mobo is an ECS 755-A2 V1.0
Processor is athlon64 3000+

[Crayz9000]

Do a BIOS CMOS clear. There should be a jumper on the motherboard; if there is none, simply pull the battery out for a few minutes.

Oh, and by the way, why did you get an ECS motherboard? They have a very poor reputation for reliability.

[Hamel]

Do a BIOS CMOS clear. There should be a jumper on the motherboard; if there is none, simply pull the battery out for a few minutes.

Oh, and by the way, why did you get an ECS motherboard? They have a very poor reputation for reliability.

I've never heard anything of the sort, though my "research" on the board was limited to a few searches through HardOCP's forums.

Thanks, I'll try to locate the jumper or the battery.

Edit: lol, it worked

[Ace Pace]

Do a BIOS CMOS clear. There should be a jumper on the motherboard; if there is none, simply pull the battery out for a few minutes.

Oh, and by the way, why did you get an ECS motherboard? They have a very poor reputation for reliability.

I've never heard anything of the sort, though my "research" on the board was limited to a few searches through HardOCP's forums.

Thanks, I'll try to locate the jumper or the battery.

Edit: lol, it worked

Leave HardOCP alone except for cooling reviews, put that site down.

Everytime you OC, do it by around 3MHZ, load up windows, and run a full stress test, consisting of any and all benchsmarks you have for around 30 minutes straight, only then OC more.

Yes, its time consuming, but its the only way your garunteed to know if its going to burn.

[MKSheppard]

I clocked the CPU from the default 200mhz to 232.

Can I say it? You're a moron for overclocking. You've gained a marginal
speed increase for a much higher percentage of blowing your box to shit.

[DaveJB]

Can I say it? You're a moron for overclocking. You've gained a marginal speed increase for a much higher percentage of blowing your box to shit.

That's a bit of an overstatement. Generally, an FSB overclock won't kill your system, unless you're using a poor mobo and/or PSU. It's when you start playing with the CPU's voltage and high-end cooling kit that you risk frying your system.

Of course, given that you could take the money from expensive overclocking gear and just buy a faster CPU, it does tend to render the whole exercise pointless.

[Ace Pace]

Can I say it? You're a moron for overclocking. You've gained a marginal
speed increase for a much higher percentage of blowing your box to shit.

If you have a slow PC (and I mean really slow, like 1GHZ), OCing is a perfect way of extending its life time another few months while saving up for an upgrade.

But your right, OCing for OCings sake is stupid.

[Admiral Valdemar]

Was 32MHz really going to make any difference?

[Ace Pace]

Was 32MHz really going to make any difference?

I'm assuming he's talking about the FSB, where thats multiplied by the CPU's multiplier to reach the final clockspeed.

Since he's talking about his AMD 64-bit CPU, that would give him a nice preformance boost, probebly on the order of 100MHZ.

[Admiral Valdemar]

I'm assuming he's talking about the FSB, where thats multiplied by the CPU's multiplier to reach the final clockspeed.

Since he's talking about his AMD 64-bit CPU, that would give him a nice preformance boost, probebly on the order of 100MHZ.

That makes sense. I wondered why an AMD 3000+ would have such a piss poor clockspeed.

[Ace Pace]

That makes sense. I wondered why an AMD 3000+ would have such a piss poor clockspeed.

Its not possible for a modern AMD to come down to 200MHZ, even a 50FSB would be first doubled to 100, then multiplied by (I THINK) 14.

If anyone has AMD's multiplier listing, I would be thankful.

[Sokartawi]

AMD Athlon XP 1500+ 1333MHz 256KB L2 cache 133MHz FSB 10x multiplier Palomino core

AMD Athlon XP 1600+ 1400MHz 256KB L2 cache 133MHz FSB 10.5x multiplier Palomino core

AMD Athlon XP 1700+ 1466MHz 256KB L2 cache 133MHz FSB 11x multiplier Palomino, Thoroughbred-A or Thoroughbred-B cores

AMD Athlon XP 1800+ 1533MHz 256KB L2 cache 133MHz FSB 11.5x multiplier Palomino, Thoroughbred-A or Thoroughbred-B cores

AMD Athlon XP 1900+ 1600MHz 256KB L2 cache 133MHz FSB 12x multiplier Palomino, Thoroughbred-A or Thoroughbred-B cores

AMD Athlon XP 2000+ 1667MHz 256KB L2 cache 133MHz FSB 12.5x multiplier Palomino, Thoroughbred-A or Thoroughbred-B cores

AMD Athlon XP 2100+ 1733MHz 256KB L2 cache 133MHz FSB 13x multiplier Palomino, Thoroughbred-A or Thoroughbred-B cores

AMD Athlon XP 2200+ 1800MHz 256KB L2 cache 133MHz FSB 13.5x multiplier Thoroughbred-A or Thoroughbred-B cores

AMD Athlon XP 2400+ 2000MHz 256KB L2 cache 133MHz FSB 15x multiplier Thoroughbred-B core

AMD Athlon XP 2500+ 1833MHz 512KB L2 cache 166MHz FSB 11x multiplier Barton core AMD

Athlon XP 2600+ 2133MHz 256KB L2 cache 133MHz FSB 16x multiplier Thoroughbred-B core

AMD Athlon XP 2600+ 2083MHz 256KB L2 cache 166MHz FSB 12.5x multiplier Thoroughbred-B core

AMD Athlon XP 2600+ 1917MHz 512KB L2 cache 166MHz FSB 11.5x multiplier Barton core

AMD Athlon XP 2700+ 2166MHz 256KB L2 cache 166MHz FSB 13x multiplier Thoroughbred-B core

AMD Athlon XP 2800+ 2250MHz 256KB L2 cache 166MHz FSB 13.5x multiplier Thoroughbred-B core

AMD Athlon XP 2800+ 2083MHz 512KB L2 cache 166MHz FSB 12.5x multiplier Barton core

AMD Athlon XP 3000+ 2166MHz 512KB L2 cache 166MHz FSB 13x multiplier Barton core

AMD Athlon XP 3000+ 2100MHz 512KB L2 cache 200MHz FSB 10.5x multiplier Barton core

AMD Athlon XP 3200+ 2200MHz 512KB L2 cache 200MHz FSB 11x multiplier Barton core

AMD Athlon XP 3200+ 2333MHz 512KB L2 cache 166MHz FSB 14x multiplier Barton core

Edit:

Also found a list here, which non Athlon-XP processors, but it's incomplete for the new ones.

http://encyclopedia.thefreedictionary.c ... processors

I probably have a complete list of this on my other PC but it's too late and I'm not going downstairs to fetch it.

[phongn]

Alas, Hamel has an AMD64 processor

[Glocksman]

My XP 2100 Tbred A with Vantec Aeroflow cooler has been running fine at 1992 Mhz (12*166) for over a year. The computer reports it as a XP 2400 because of the bus speed increase. If I take it much higher, I get lockups and crashes, but it's rock solid at 166 FSB.

Previously I had an Abit BM6 which originally ran a Celeron 466, When it began to get a little long in the tooth, I bought a 533 Celeron A and ran it at 100 Mhz bus which gave me an 800 Mhz machine for the expenditure of $90.

Moderate OC'ing is a way to the increase performance/price ratio.

[Hamel]

I can't overclock one iota without the system getting unstable, freezing, and rebooting suddenly. Retarded.

[Hamel]

Christ, the system is even unstable WITHOUT cpu overclocking. It'll freeze while playing FarCry, requiring a restart. The system reboots itself the very second I load up a visualisation in Winamp 5. The Doom 3 demo will freeze for around a minute at times. WTF. I'm guessing this is the mothetboard being a cunt?

[phongn]

ECS has horrible quality control. Try RMAing it.

[Glocksman]

Did you use known good RAM?
I've seen machines behave like that when the RAM is substandard.

Also, is your power supply beefy enough?

[Hamel]

Did you use known good RAM?
I've seen machines behave like that when the RAM is substandard.

Also, is your power supply beefy enough?

3200 Corsair Value Select RAM, and a 350W power supply. Should be fine.

[Glocksman]

Sounds OK, then.
What video card are you running?
The reason I ask is that the one thing in common the problems you listed have is that they're all video related.

Does it crash when you run SETI or some other processor intensive app as a burn in program?

It's probably the mobo, but it couldn't hurt to (re)install the latest chipset drivers and then the video drivers.

[Hamel]

BFG 6800OC. I've had the official 61.xx drivers give me blue screens before so I only use unofficial or beta drivers. Overclocking a vidcard has never, ever caused a crash for me.

[Tech^salvager]

It may be the PSU isn't running power at adequate level. What type of PSU? Do you any other PSU's? to test it with? Do you know what the 12v and 5v rail are reporting in the bios?

[Ace Pace]

BFG 6800OC. I've had the official 61.xx drivers give me blue screens before so I only use unofficial or beta drivers. Overclocking a vidcard has never, ever caused a crash for me.

And there we have it, unless its a great motherboard and a quality PSU, never try running a top level card on that kind of power, a 480W is reccomended unless its a real top of the line Antec TruePower.

[Hamel]

Errrrrrrrr..... The recommended PSU specs for 6800s are way overblown. There are people running GTs with PSUs below 400W without issue.

If that's truly the problem then fine, but it smells fishy.

[Glocksman]

Depends upon who made the PSU.
Antecs, Sparkles, Heroichis, etc are decent units.
Anything made by Deer is suspect no matter what the PSU's rating is.

Can you borrow a PSU from a friend and temporarily swap out the supply?
Or you could go buy an Antec from Best Buy and return it if it doesn't fix the problem.