Windows 2000 keeps on rebooting and showing message ...cannot find hive....pls help

found this on net
STOP: 0x00000073 (parameter, parameter, parameter, parameter) CONFIG_LIST_FAILED
Explanation: This is a Windows 2000 Executive character-mode STOP message. It indicates the system configuration link list failed. One of the core system hives is corrupted or unreadable, or some critical Registry keys and values are not present.
User Action: If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.

backup the current hive file, and copy the hive file from repair folder to the config folder, that would solve the problem

this problem is BIOS problem not in a windows operating system, pls contact your Compaq service center. Compaq only solve this problem.

use registry cleaning softwares or repair your operating system

If u have 2 ram in 1 computer memoryh frequence
conflict betwwen each other if both r differ.
So cheange yhour ram and check both rammeoroy frequence are same .

BAD_POOL_CALLER is a stop error message that is caused because of problems with the memory management.

There is a list of more than thirty such causes that can give you this error message. If the stop error is consistent every time the system is rebooted, the following method will be effective in solving the problem:
* The hardware and RAM should be checked initially.
* Boot the system once again using the OS setup CD, or use a boot setup that has a GUI like BartPE.
* With RunScanner it is possible to use a memory test tool.
* Select a single account
* If all the accounts open then the system registry hive might be the problem.
* Locate the hive damaged and rename it, do not delete it.
* Create another hive from the backup or from the restore point.
* Initially uses the latest one and keep checking the restore points that come later.
* Avoiding harvesting any replacement hives from the hard drive booted Windows.
* After which compare the hives for differences.

This is one of the ways of fixing BAD_POOL_CALLER errors. Another method is to reinstall the OS but occasionally shows a disk read error or an error on the same lines. Switching the computer off for a minute or more and then switching it on can solve it since the error is only a slight glitch in the system operation.
The BAD_POOL_CALLER is seen for the first time after installing a hardware or software it is recommended that the computer be restarted. If it doesn’t solve the problem, the installation of the hardware or software should be checked for corrections. If the problem persists the installed hardware and software should be disabled, and the BIOS memory options like caching or shadowing should be disabled too.
The safe mode can be used as well to remove or stop components.
To enable the safe mode just press F8 when the machine is being restarted and select it from the Advance Startup options and correct the problem. The installation of the graphics card is another reason the BAD_POOL_CALLER error shows up. A simple reinstallation of the driver can solve the problem.
Microsoft has also acknowledged that the BAD_POOL_CALLER Stop 0xC2 error pops up when trying to print a document that contains a corrupt font.
A hot fix is available at www.support.microsoft.com

do it


1.




Use the Windows 2000 CD-ROM or the Windows 2000 Startup disk to start the computer. 2. When you see the "Welcome to Setup" message, press R for "repair." 3. Press C to run the Recovery Console tool. 4. Select the installation that you want to repair. 5. Type the administrator password.

If the computer is a domain controller, type the password for Directory Services Restore Mode when you are prompted to do so.For additional information about the Recovery Console tool, click the article numbers below to view the articles in the Microsoft Knowledge Base: 239803 (http://support.microsoft.com/kb/239803/EN-US/) How to Change the Recovery Console Administrator Password on a Domain Controller 223301 (http://support.microsoft.com/kb/223301/EN-US/) Protection of the Administrator Account in the Offline SAM 6. At the Recovery Console command prompt, type the following commands, pressing ENTER after you type each command: cd system32\config
ren system system.old
ren system.alt systemalt.old 7. If you have run the Emergency Repair Disk Wizard from Windows Backup and Recovery tools, copy the backup of the System hive from the %SystemRoot%\Repair\Regback folder.

If you have not run the Emergency Repair Disk Wizard, copy the default System hive from the %SystemRoot%\Repair folder.

IMPORTANT: You need to restore the most recent copy of the System hive. You also need to reinstall any hardware device drivers or programs that run as services that you installed since the last time that you updated your Emergency Repair Disk.

To copy the default System hive, type the following command, and then press ENTER: copy c:\winnt\repair\system c:\winnt\system32\config To copy the System hive that was backed up the last time that you ran the Emergency Repair Disk Wizard, type the following command, and then press ENTER: copy c:\winnt\repair\regback\system c:\winnt\system32\config 8. At the command prompt, type exit, and then press ENTER to restart your computer.

Here is the solution right from Microsoft.

 

SYMPTOMS
When you try to start or restart your Windows XP-based computer, you may receive one of the following error messages:

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SOFTWARE

Stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or alternate

CAUSE
This issue can occur if the System or Software hive for the Windows XP installation is missing or damaged.

RESOLUTION
To resolve this issue, use one of the following methods.

Use the Recovery Console Tool
To restore a damaged registry hive, use the Recovery Console to restore the backup copy of the hive from the Repair folder. The Repair folder contains a copy of the system's registry hives that were created after the first successful startup of Windows XP.

WARNING : Although data should not be affected by the following procedure, you may need to restore changes you previously made to programs or system settings since the first time you successfully started Windows XP.

To replace the damaged registry hive and restore the backup copy of the hive from the Repair folder: Start your computer to the Recovery Console.

Determine if the file that is mentioned in the "Symptoms" section of this article is present, and if it is, rename it:

In Recovery Console, change to the c:\Windows folder.

Type cd sytem32\config , and then press ENTER.

Type dir system , and then press ENTER.

If you cannot run the preceding command successfully (because the file is missing), skip to step 3. If you can run the preceding command successfully, type ren system system.bak , and then press ENTER.

NOTE : If the message that you received referred to the software file, replace "system" with "software" in the preceding command. For example, you would type ren software software.bak (instead of ren system system.bak ), and then press ENTER.

Type copy c:\windows\repair\system , and then press ENTER.

NOTE : If the message that you received referred to the software file, replace "system" with "software" in the preceding command. For example, you would type copy c:\windows\repair\software (instead of copy c:\windows\repair\system ), and then press ENTER.

You should receive a "One file copied" informational message. For additional information about how to use Recovery Console during startup, click the article number below to view the article in the Microsoft Knowledge Base:
Q307654 HOW TO: Install and Use the Recovery Console for Windows XP

IMPORTANT : If you encounter problems when you run the preceding commands, you may need to use the Change Directory command ( cd ) one folder at a time before you run the preceding commands. For example, type cd system32 , press ENTER, type cd config , and then press ENTER.

Type exit , and then press ENTER to quit Recovery Console and restart the computer.