Archived from groups: microsoft.public.win2000.general (
More info?)
Hi Head,
For Stop 0xC0000218 Error, please refer to the following KB article:
How to Troubleshoot a Stop 0xC0000218 Error Message
http://support.microsoft.com//kb/156640
Also copy related information here just for your convenience:
CAUSE
================
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.
NOTE:
***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. ***
RESOLUTION
================
To resolve this issue, follow these steps:
1. 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.
2. When Windows loads, press SPACE BAR when the "Load Last Known Good"
message appears.
3. 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.
Hope this helps!
Have a nice day!
Sincerely,
Tom Che
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Reply-To: "Head Hunter" <sevenredp@hotmail.com>
>From: "Head Hunter" <nospam@nospam.com>
>References: <eKtDyXZrFHA.1168@TK2MSFTNGP11.phx.gbl>
<#HL#ZbwsFHA.4072@TK2MSFTNGP09.phx.gbl>
<uSFkxi1sFHA.1032@TK2MSFTNGP12.phx.gbl>
>Subject: Re: Latest info
>Date: Wed, 7 Sep 2005 10:42:53 -0700
>Lines: 150
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>X-RFC2646: Format=Flowed; Original
>Message-ID: <#q0rTO9sFHA.3708@TK2MSFTNGP10.phx.gbl>
>Newsgroups: microsoft.public.win2000.general
>NNTP-Posting-Host: sb0-cf9a623c.dsl.impulse.net 207.154.98.60
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.general:62741
>X-Tomcat-NG: microsoft.public.win2000.general
>
>I didn't mention the hive problem because I hadn't done the parallel
install
>yet. Even then, it wasn't until I was looking through the resource guide
>that I found out I could access the old event files from the new
>installation. That is where I saw the stop error. It also mentioned the
>minidump file. That is where I saw the security file problem.
>
>"Dave Patrick" <DSPatrick@nOsPAM.gmail.com> wrote in message
>news:uSFkxi1sFHA.1032@TK2MSFTNGP12.phx.gbl...
>> 0xC0000218
>>
>> You didn't mention the hive. Assuming the system hive and you already
>> tried
>> LKG, It may be possible to rename the system hive found in
>> %windir%\system32\config\system
>> to system.old
>> then rename
>> %windir%\system32\config\system.alt
>> to
>> %windir%\system32\config\system
>>
>> You can also try using the most recent backup found in
>> %windir%\repair\regback
>>
>> If that fails you haven't much choice but to copy/ use the
>> original-as-installed system hive from
>> %windir%\repair\system
>> to
>> %windir%\system32\config\system
>> You'll need to reinstall the device drivers for any hardware added since
>> the
>> original OS install.
>>
>> If the software hive, it may be possible to rename the software hive
found
>> in;
>> %windir%\system32\config\software
>> to software.old
>> then copy the most recent backup found in
>> %windir%\repair\regback
>> as
>> %windir%\system32\config\software
>>
>> If that fails you can copy/ use the file
>> %windir%\repair\software
>> This file is an image of the hive at the time the OS was installed, so
>> you'd
>> have to reinstall all software. This being the case you might just as
well
>> blow it away and start a new install. (note: this would at least allow
you
>> to start the OS to make any necessary backups prior to wiping the drive.)
>>
>> To start the Recovery Console, start the computer from the Windows 2000
>> Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
>> floppy disks and your computer cannot start from the Windows 2000 Setup
>> CD,
>> use another Windows 2000-based computer to create the Setup floppy
disks.
>> At
>> the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
>> installation, and then press C to use the Recovery Console. The Recovery
>> Console then prompts you for the administrator password. If you do not
>> have
>> the correct password, Recovery Console does not allow access to the
>> computer. If an incorrect password is entered three times, the Recovery
>> Console quits and restarts the computer. Note If the registry is
corrupted
>> or missing or no valid installations are found, the Recovery Console
>> starts
>> in the root of the startup volume without requiring a password. You
cannot
>> access any folders, but you can carry out commands such as chkdsk,
>> fixboot,
>> and fixmbr for limited disk repairs. Once the password has been
validated,
>> you have full access to the Recovery Console, but limited access to the
>> hard
>> disk. You can only access the following folders on your computer: drive
>> root, %systemroot% or %windir%
>>
>> You can do the copy from your parallel install.
>>
>> --
>> Regards,
>>
>> Dave Patrick ....Please no email replies - reply in newsgroup.
>> Microsoft Certified Professional
>> Microsoft MVP [Windows]
>>
http://www.microsoft.com/protect
>>
>> "Head Hunter" wrote:
>> | OK. The Win2000 Resource Guide suggests install a duplicate copy of
>> Win2000
>> | and using it to scan the drives, theoretically fix the registry, etc.
>> | Looking at a mini-hex dump, it seemed to say it couldn't load the
>> security
>> | hive. I copied over the security, system, and software files from the
>> | original \repair folder into the \system32\config folder. I now get a
>> very
>> | fast blue screen, then the reboot. Loading the original installations
>> event
>> | viewer files into the second installation, I have a bugcheck showing
>> error
>> | 0xc000218. I googled for it, and the only hit I got was on the Spanish
>> | version of the MS Technet site which called it an UNKNOWN_HARD_ERROR.
>> | Unfortunately, I don't read Spanish. Also, this error is not in the
>> English
>> | Technet site, or listed in any of my Win2000 resource books. The link
>> is
>> |
>>
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/es/library/Se
rverHelp/fc8efbed-4ea6-4068-9f55-40801292ec6d.mspx
>> |
>> | I am pretty sure it is my hard drive, but I am still hoping.
>> |
>> | "Head Hunter" <nospam@nospam.com> wrote in message
>> | news:eKtDyXZrFHA.1168@TK2MSFTNGP11.phx.gbl...
>> | >I have a system that dual-boots Win98 and Win2000 on separate
>> partitions.
>> | >Both systems are fully current on updates and anti-virus. Everything
>> was
>> | >working fine on Saturday. Sunday morning, I was in Win98 and it was
>> fine.
>> | >I rebooted into Win2000, and that is when the fun started.
>> | >
>> | > First, I had a "missing or corrupt D:\WINNT\System32\Config\System
>> file".
>> | > Not a problem. My D-Drive is formatted as FAT32 for just this kind
of
>> | > problem, so I booted into Win98, and copied the file from the Repair
>> | > folder, and rebooted. Then, Win2000 had to perform a consistancy
>> check
>> on
>> | > my D: drive. Was taking forever (15 minutes to get to 17% with no
>> | > problems), so I went to watch TV. Came back, and saw the screen had
>> the
>> | > white and blue "Windows 2000 is starting" screen. Then, black screen
>> and
>> | > reboot. Now, I just get the white bar going across the bottom of the
>> | > screen, gets all the way across, then reboot. Safe Mode doesn't work
>> | > either, same problem.
>> | >
>> | > I am not getting a blue screen or any kind of error. It just keeps
>> | > rebooting. I really don't want to have to reinstall everything if I
>> don't
>> | > have to. Forunately, I can get to most of my data from Win98, but
>> there
>> | > is a partition on another physical hard drive that is NTFS, so I
can't
>> see
>> | > it.
>> | >
>> | > Any ideas, before I do the deed and reinstall???
>> | >
>> |
>> |
>>
>>
>
>
>