bootup freezing

[erjin999]

I had this issue on my cheap work computer, where it would startup and then after aout 1-2 seconds shut down. It was due to a cheap power supply, and was made worse by changing the FSB on the mobo from 100Mhz to 133 Mhz and back. In the end I changed the power supply and its been ok since then, but I havent fiddled with the FSB anyway since then.

Certainly the easiest way to work it out would be get/steal/borrow a power supply, but not a ultra cheapy one.

[neonext]

i'll be picking one up tomorrow, hopefully it works. My old one was 300W so I am going to get one that is the same wattage. IIRC that is the important thing

[neonext]

well, it seems the new power supply has solved the power-related problems, such as the system not turning on and the system shutting off on its own, but i still cant get the startup screen to show. while i was working on it, i took a close look at my cpu and near the core it is black on both sides, with a discoloring on most of the inner part of the chip. i'm thinking that i burnt the chip too much with that old fan :(

no beeping or anything when i try to start up, no power led either. it looks like it's been narrowed down to either the cpu or the m/b, so i'm wondering... if you had a faulty cpu, would the power led not light up? should i just try to replace the cpu, or could it still be a problem with the m/b?

[erjin999]

I think it does power up even with a faulty cpu. Powers up then down again quite quickly. Many times I have cooked cpus (when I was really hungry :P) and once it took the mobo with it.

[neonext]

what should i do then? just upgrade to a new cpu/mobo combo and be done with it?

[erjin999]

Erm, if you are not going to go up a level with your upgrade, as in get the same kind, then get a cpu, test it, if it doesnt work, then get the mobo. If you are going to upgrade a level then first be totally certain that it is the cpu and the mobo. Can you not borrow a friends chip to test ?

[neonext]

not really... cant think of anyone with something AMD, let alone Athlon

[desert_storm]

I didn't read everything that was said.  But i had the same problem, or something close to it.  they way I fixed it was entering BIOS and restoring all the defults.