Cannot get computer to boot up.

[usf89]

I have just recently had some problems with my computer and cannot get a straight answer from any stores around here without them asking for money. The first time I noticed there was a problem was whne I would turn on my computer and there would be no output to the screen, no beeping or anything. Then I would press restart and it would usually start up normally when I did that. Now it has gotten worse and the little restart trick doesn't work anymore. It just turns on, fans blow, and no beeps occur. The only card I have in my computer is the video card because my other cards are built into my motherboard, so I took out the video card. Still didn't help, same thing happened. Then I took the mobo out of the case and set it on some cardboard, unhooked all of the drives, leaving in one (brand new) stick of memory, and still nothing new. So, we're down to three things....it's either the mobo, the processor, or the power supply. I don't want to go buy a new processer and mobo if I don't have to, please help!!

AMD Athlon 700mhz
SiS Motherboard Slot A(yes, slot a)
300 watt ATX power supply
brand new memory (and it's the correct type)

[Andrew Leigh]

Hi,

if you put the old Ram back will the PC work? If so then bet your bottom dollar the new Ram is incompatible or that the MOBO is unable to accept a single Ram stick of the size(megs) you are trying to put in.

If not then this is indicative of a POST failure. There is a good write up in the PC Guide site.

Cheers
Andrew

[Wizened Sage]

Hi,
It is possible that the machine will not boot with no drives attached - try reattaching the hard-drive. Ensure the IDE cables are reinserted the correct way around.

[usf89]

Yeah, I tried the old memory and the new, and I tried to boot with everything hooked up. I'll try to find that write up on post problems. Thanks for your help.

[usf89]

Where is the write up on the post problems??

[dquepal]

If there is no initial BEEP, it means that the processor and motherboard are not properly attached, or not comunicating. This can happen for many reasons. For example, in an overclocked system, FSB, or multiplier, or both can result in this type of failure. It can happen too with a BIOS upgrade (BUGGY), or just for hardware physical failure.
Maybe it would be a good idea to check FANS rpm, and to test mobo, and processor in other system, to discard some possibilities.
If you find that nothing seems to fix the problem, and your hardware functions OK in another system, well, you can try this one:
Reset BIOS jumper
Put multiplier mobo jumper in manual, and adjust it to your clock speed

That seemed to work for me with my athlon XP 1800+ and soyo K7VTAPRO system, when it didn´t boot.
Good luck.

PD: about the "reset" button FIX, yeah, I knew that too (It hapenned to me)