Boot up failure

Deberías tener ciertas habilidades técnicas para resolver este problema, no es sencillo lo mejor sera que lleves tu computadora con un especialista el error que te marca es un error de la memoria del BIOS la encargada de iniciar tu sistema operativo(windows) llévala al técnico.
Suerte.

I am not sure what motherboard you have but the following link will discribe possible causes for your bios beep code:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bph07107

Remove the hard drive and see if you get the same symptom. It should boot, then go into the BIOS and see if it recognizes the RAMs. Re-seat the RAMs if it doesn't boot - if you have two circuit boards - try one at a time. The motherboard can also be your problem.

You should have gone into your Bios pages first.Press F2 whilst booting,learn how to to configure these pages,use the "tab" button to navigate and arrow keys ,Save and exit or restore to factory defaults,learn how to use these pages to enable correct boot sequence--good luck!

Davey Snake!

It seems as if your hard drive has failed or is going to fail. When you hear a clicking noise like that with no CD in the system that is usually what the cause is.

The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Parameters The four parameters that are listed in the message can have three possible meanings. If the first parameter is 1 or 2, or 3 and the third parameter is 0, the parameters have the following definitions.
Parameter Description 1 The lock type that was held (1, 2, or 3) 2 The error status (usually an I/O status code) 3 If Lock Type is 1: the current process

If Lock Type is 2 or 3: 0

4 The virtual address that could not be paged into memory
If the first parameter is 3 (and the third parameter is nonzero) or 4, the parameters have the following definitions.
Parameter Description 1 The lock type that was held (3 or 4) 2 The error status (typically an I/O status code) 3 The address of the InPageSupport structure 4 The faulting address
Otherwise, the parameters have the following definitions.
Parameter Description 1 The address of the page table entry (PTE) 2 The error status (usually an I/O status code) 3 The PTE contents 4 The faulting address

Cause Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:

• 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
• 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
• 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
• 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
• 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).
Another common cause of this error message is defective hardware or failing RAM.
A virus infection can also cause this bug check.
Resolving the Problem Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.
If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.
Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.
Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.
Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.
Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.
Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.
Make sure that the latest Windows Service Pack is installed.
If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error.
Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

Basic Troubleshooting Tips after Installing a New Hard DriveBased on Seagate IDE hard drives.

If you have installed your drive and it does not function properly, perform the following basic checks:

Additional Troubleshooting Tips

If you have performed the preceding basic checks but the problem persists, follow these guidelines for troubleshooting specific cases: 
After you install your new drive, your computer will not boot, and no error message appears on the screen.
The screen remains blank when you power up the system. 
The system does not recognize the drive. 
The dealer partitioned and formatted the drive for you in the store, but the drive does not respond when you install it. 
The system hangs in FDISK or fails to create or save the partition record. 
The system error message, "Drive not Ready," appears. 
The FDISK error message, "No Fixed Disk Present," appears. 
The drive does not format to full capacity. 
The DOS message "Disk Boot Failure," "Non-System Disk" or "No ROM Basic - SYSTEM HALTED" appears. 
The system error message, "HDD controller failure" appears. 
After you install your new drive, your computer will not boot, and no error message appears on the screen.

Check your computer manual or BIOS manufacturer to determine whether your BIOS supports drives that have more than 4,092 cylinders. If your system has this limitation, use the following procedure to configure your computer:

Turn off your computer, open the case, and remove your new drive.

CAUTION: To avoid electrostatic discharge damage to your computer or hard drive, make sure you are well grounded before touching the drive, cable, connector or jumpers.

Move the jumper on the alternate-capacity jumper, as shown in Figure 6. This causes the drive to appear to your BIOS as having a 2.1-Gbyte capacity (4,092 cylinders, 16 heads, 63 sectors per track). You may need third-party partitioning software, such as Disk Manager, to achieve full capacity of the drive. 
Remount your drive in the computer and replace the computer cover. 
Insert a bootable system diskette into drive A and turn on the computer. It should boot from drive A and automatically detect the new drive as a 2.1 -Gbyte drive. 
Insert your DiscWizard diskette into drive A and type A:XDM. Then press ENTER. This runs the Disk Manager program. 
Follow the Disk Manager instructions to install the dynamic drive overlay and to partition and format your new drive to its full capacity. 
After Disk Manager is done, reboot your system. You should see the Disk Manager banner and be able to access the full capacity of your new drive. 

The screen remains blank when you power up the system. 
If the steps listed above do not remedy this problem, try the following: 
Make sure the monitor is plugged in and turned on. 
Check all cards. 
Make sure the video card is seated in its slot and secured with mounting screws. 
Turn off the computer and remove the drive host adapter. If the screen turns on after you reboot, the host adapter may be incompatible or defective. If so, see your dealer. 

The system does not recognize the drive. 
Check all cables. 
Make sure the power supply is adequate for system needs. 
Reboot the computer and listen to make sure the drive motor starts up. If the drive is very quiet, it may be difficult to hear its discs reach operating speed. If the drive motor does not start up, recheck all drive cables. 
Verify that for each drive, a drive-type is listed in the system setup program. 
Try rebooting your computer by pressing the CTRL, ALT and DELETE keys simultaneously. If the drive is recognized after you reboot the system, the computer BIOS test may be completing before the drive is ready. 
One solution is to slow the processor speed during startup. If your computer has a turbo switch, set it to slow speed before turning the computer on. If there is no turbo switch, you may be able to use keyboard commands; see your computer manual for details. After the computer is up and running, return the processor to the fast speed. 
Another solution is to warm-boot your computer after every power-on. 
Check for I/O address conflicts. To isolate the conflict, verify that the drive and host adapter are compatible with your computer. Turn off the computer and remove all the peripheral adapter cards except for the video card and host adapter. If the computer recognizes the drive when you reboot the computer, turn off the computer. Reinstall the other peripheral cards, one at a time, until the conflict reoccurs. After you have isolated the source of the address conflict, you can resolve the conflict by changing the 1/0 address of the peripheral that appears to cause the conflict. 
If Disk Manager has installed the DDO on your hard drive and you have booted directly from a diskette, the information in the boot record for the drive may not have been loaded. Make sure there is no diskette in drive A and reboot. If you want to boot from the diskette, follow the "Booting with a Diskette" instructions under "Advanced Disk Manager Options" on page 20. 

The dealer partitioned and formatted the drive for you in the store, but the drive does not respond when you install it. 
Reboot the computer and make sure the drive spins up. 
Check all cables. 
Make sure the power supply is adequate for system needs. 
Make sure the DOS or Windows version the dealer used to partition and format the drive is the same version you have installed in your computer. If it isn't, see your dealer. 
Verify the drive-type values in the system setup program. You must install the drive using the same drive-type values your dealer used to partition the drive. 
Check for 1/0 address conflicts between peripheral cards. 
Check for viruses. 

The system hangs in FDISK or fails to create or save the partition record. 
Check all cables. 
Your setup system diskette may be corrupted. Try using a backup diskette. 
Make the partitions smaller. 
Change the interrupt jumper setting on the host adapter. 
Some BIOS have a Track 0 protection feature that protects Track 0 from viruses. This may cause FDISK to hang the system. You must disable this feature in the system setup program before you can use FDISK. See your computer reference guide for assistance. Be sure to re-enable this important feature when FDISK is done. 

The system error message, "Drive not Ready," appears. 
Check all cable connections. Make sure pin 1 of the drive is connected to pin 1 of the hard-disc controller or host adapter. 
Make sure the power supply is adequate for system needs. 
Reboot the computer and make sure the drive spins up. 

The FDISK error message, "No Fixed Disk Present," appears. 
Make sure the power supply is adequate for system needs. 
Verify the drive-type values in the system setup program. 
Check for 1/0 address conflicts. 

The drive does not format to full capacity. 
Verify the drive-type values in the system setup program. One of the following problems may have occurred: 
The values may be set with an incorrect translation characteristic. 
You may have entered a parameter value that exceeds the physical capacity of the drive. 
You entered a translation characteristic that does not take full advantage of the drive's capacity. 
The drive's physical specifications exceed the translation limits imposed by the BIOS.

CAUTION: If you change the drive-type values in the system setup program, you must partition and format the drive again. This erases data on the drive. 

If you have partitioned the drive into individual logical drives, you may need to make the partitions smaller to access the full drive capacity. 
If your computer supports LBA mode, you may need to enable LBA mode in the system setup program to access the full capacity of the drive. Refer to your computer's reference guide to find out how to enable LBA. 
Your computer may not support drives that have more than 4,092 cylinders. Follow the instructions on page 25 for After you install your new drive, your computer will not boot, and no error message appears on the screen. 

The DOS message "Disk Boot Failure," "Non-System Disk" or "No ROM Basic - SYSTEM HALTED" appears. 
Reinstall the DOS system files using the DOS SYS utility. 
Check all cables. 
Use FDISK to verify that the primary partition is active. 
Check for viruses. 

The system error message, "HDD controller failure" appears. 
Confirm the jumper settings on the drive. 
Verify the drive-type settings in the system setup program.
If a problem persists, please search for a solution or post a question in our tech support forum in our Help Desk.

Re: Error 983 while using Partition Magic Error 983: "Too many errors found, process halted"
http://service1.symantec.com/SUPPOR...gic&svy=&csm=no

Utilize the following maintenance programs before using Partition Magic:

Description of the Disk Cleanup Tool in Windows XP
http://support.microsoft.com/defaul...2&Product=winxp

How to Perform Disk Error Checking in Windows XP
http://support.microsoft.com/defaul...5&Product=winxp

HOW TO: Analyze and Defragment a Disk in Windows XP
http://support.microsoft.com/defaul...1&Product=winxp

--

Yes, your hard drive may have serious problems. Does the machine have a floppy drive? If so, will it boot to DOS? Or, if you have an XP or linux install CD, will it boot from CD?

Can you hear the hard drive spin up when computer is powered on? Some drives are very quiet, so you might have to put your ear close. Does the drive have an abnormal clicking sound? Western Digital drives were famous for this symptom of failure.

Try swapping the drive into a spare or friend's computer. If the symptoms are nearly identical (no boot), then this points to the drive as failed. Note, that if it does get part way through the boot process, your Operating system (XP, 2000) may blue screen, instead of completely booting. But, if it does get that far, there may be more hope for the drive.

Suggest also you download manufacturer's diagnostic software and run it.

Hard drive failures are very common, some happening within the warranty period or shortly thereafter. This is why backing up your data to CD, flash drive, or other media is so important.

Sounds like bad disk, although 3 beeps sometimes relates to a memory problem on some motherboard bios's. Click Start>run then type'chkdsk' and then Enter, this will run a damage segment diagnosis and repair, if capable.