My computer refuses point blank to start up - what's the problem?

My computer was working perfectly yesterday, and when I come to switch it on today - nothing. It won't even boot up and the screen is blank. I hear 10 annoying beeps (2, a brief pause, and then another 8). What can be the problem?

Over the past 6 months, my computer has been having a few problems - but nothing to write home about. What used to happen was that when I switched it on sometimes it would'nt boot up, so I just switched it off at the back, switched it back on, press the power button on again, and it would boot up as sweet as a nut. NOW though, it won't even boot up at all. What can this all mean?

My computer symptons:

- Blank screen
- Does not boot
- LED's are on
- Power supply seems to work (CD-ROM opens on request, etc.)
- Approx. 10 beeps (American Megatrends format)

My PC Specifications:

- Windows XP
- Socket A motherboard
- 40GB Hard-drive
- 500MB Ram
- ATI Radeon GC

What does all this mean? A new motherboard? I doubt it is the graphics card beacause I have never had a problem with it. Could it be the ram?

PLEASE, somebody help me, it could not have come at a worse time.

AMI bios uses continuous beeps for errors. That might indicate that the 2-8 you hear is two errors? If so that would be 2beeps=memory parity error, 8beeps=video memory error. Both could be due to bad memory. Try each stick that you have individually in each slot. If that doesn't work, try a new stick (borrow one if you can). After that, try a new video card.
If the beeps are 10 continuous beeps, its a CMOS checksum error and indicates a mobo problem.

By "Stick", you mean the RAM, right?



And if is it a motherboard problem, I would be forced to replace it a with a new one...?

Thanks, for your help, appreciate it.

Stick=RAM, yes.
The first thing I'd try for the mobo error would be a new CMOS battery. That might fix things quick and easy. Before doing any replacement of the mobo or anything, try new power supply, different video card, etc to make sure nothing else could be causing the problem indirectly.