A Stop 0xc0000218 error message means that a necessary registry hive file could not be loaded. This error message can occur if the file is corrupt or missing. To resolve this issue, you can reinstall the operating system and restore the registry files from a backup. The registry files may have been corrupted because of hard disk corruption or some other hardware problem.
This error message can also occur if the driver has corrupted the registry data while loading into memory, or the memory where the registry is loading has a parity error. In the latter case, turn off the external cache and check the memory chips.
This error message can also occur if the driver has corrupted the registry data while loading into memory, or the memory where the registry is loading has a parity error. In the latter case, turn off the external cache and check the memory chips.
To resolve this issue, follow these steps:
-Start your computer by running the Recovery Console, run the chkdsk /p command on the drive, and then restart your computer. -Test to determine whether the issue is resolved. If the issue is resolved, do not complete the remaining steps. If the issue is not resolved, go to step 2.
-When Windows loads, press SPACE BAR when the "Load Last Known Good" message appears.
Complete a parallel installation, and restore the registry files from a tape backup. To do so:
- Reinstall Windows in a separate folder.
- Restore the damaged registry hive from backup. This procedure is specific to the backup application that you used to make a backup. Consult the documentation of your backup application or consult the vendor if you need assistance. Typically, this procedure requires you to restore a system state backup to an alternate location, and then copy the appropriate registry files to the %SYSTEMROOT%\System32\config folder of the damaged operating system.
If you do not have a tape backup, include the backup of network servers and production workstations.
NOTE: If Windows is stored on a FAT partition, you can restore the files by using another computer and by copying the registry hive files to the %SYSTEMROOT%\System32\Config subfolder.
If the Stop error message was caused by a hardware problem (for example, bad sectors on the hard drive), the drive may require a low-level format, repartition, reformat, and a restore of the entire system from a tape backup to clear up the problem. Although this would be the most drastic case, if the Stop error message was caused by a physically bad sector, the sector must be relocated with a low-level format.
-Start your computer by running the Recovery Console, run the chkdsk /p command on the drive, and then restart your computer. -Test to determine whether the issue is resolved. If the issue is resolved, do not complete the remaining steps. If the issue is not resolved, go to step 2.
-When Windows loads, press SPACE BAR when the "Load Last Known Good" message appears.
Complete a parallel installation, and restore the registry files from a tape backup. To do so:
- Reinstall Windows in a separate folder.
- Restore the damaged registry hive from backup. This procedure is specific to the backup application that you used to make a backup. Consult the documentation of your backup application or consult the vendor if you need assistance. Typically, this procedure requires you to restore a system state backup to an alternate location, and then copy the appropriate registry files to the %SYSTEMROOT%\System32\config folder of the damaged operating system.
If you do not have a tape backup, include the backup of network servers and production workstations.
NOTE: If Windows is stored on a FAT partition, you can restore the files by using another computer and by copying the registry hive files to the %SYSTEMROOT%\System32\Config subfolder.
If the Stop error message was caused by a hardware problem (for example, bad sectors on the hard drive), the drive may require a low-level format, repartition, reformat, and a restore of the entire system from a tape backup to clear up the problem. Although this would be the most drastic case, if the Stop error message was caused by a physically bad sector, the sector must be relocated with a low-level format.
No comments:
Post a Comment