Non-Stop beeping on start up

June 26, 2011 at 12:54:11
Specs: Windows XP
I have a HP Pavilion a1230n computer running Windows XP: here is hte specs.

MY wife was using it one day and she got a blue screen. I came home and restored the pc to factory settings, did the updates and it ran fine for about 2 days, then it went off. now when I start the computer it beeps and never stops, the beeps are about 2 seconds apart, and now my screen says it cannot find a source. can the video card be bad and causing the beeps?

See More: Non-Stop beeping on start up

Report •

Report •

June 26, 2011 at 20:05:37
Pavilions can be either notebook or desktop computers.
Apparently yours is the latter.

Award bios versions, or brand name bios versions based on Award bios versions, can produce a continuous beep pattern like you describe.

Quoting from info at mickliq's first link...

Beep codes for Award BIOS
Most Award post codes are displayed to screen. If a beep code occurs the problem is likely occurring before the system can display video (check the video card or memory).
NOTE: The following codes can vary depending on BIOS version.

Beeps Description
1 short beep POST process completed successfully - normal startup
1 long beep followed by 2 or 3 short beeps Unable to initialize video (to display the post code)
Continuous beeping without pause Serious system related issue such as CPU overheating

If it does it when the computer has had a chance to cool to room temp, then right away when you attempt to boot the computer, it can't be the CPU (processor) overheating.

In my experience, you get a beep pattern like yours from a modern Award bios when there is no ram installed in the mboard, or when the ram has a poor connection in at least one of it's slots.

That's often a beep of about a half second, silence for a half second, a beep of about a half second, silence for a half second, continuously.

Remove the AC power to your computer - unplug it, or switch off the power to it on whatever the cord is connected to.

See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:

Report •
Related Solutions

Ask Question