D
David English
http://support.microsoft.com/default.aspx?scid=kb;en-us;269075
includes a procedure for reducing the size of the system hive.
If you are still faced with the problem after trying "everything" then
I offer this additional procedure for reducing the size.
When you restart your Microsoft Windows 2000-based computer, you may
receive the following error message:
Windows could not start because the following file is missing or
corrupt:\WINNT\SYSTEM32\CONFIG\SYSTEMced
Windows 2000 may be unable to load the registry if it is too large.
This issue can occur when a process writes too much data to the System
subkey in the registry. The System subkey is designed to contain only
the information that is necessary to boot the computer.
Computers that are based on Intel architecture or ARC (RISC)
architecture can only use 16 megabytes (MB) of memory at this stage of
the boot process. The System registry subkey has to share the 16 MB
with the loader, kernel, HAL, and boot drivers. In some instances, the
size of the System subkey may be 13 MB or larger.
How to Reduce the Size of the System Hive - last resort
WARNING: this procedure is time consuming and requires some experience
with the registry editor.
You will need a 2nd system OR a complete parallel installation.
Step 1 - check the size of the failing system hive using the repair
console, if it's less than 13MB this procedure is unlikely to help
you.
Step 2 - use regedt32 to load the failing system hive as (eg)
"BADSYSTEM" under HKEY_LOCAL_MACHINE on a working Windows 2000 / XP
system, which implies that you have available a 2nd system or a
parallel installation on the same disk.
Step 3 - determine the "Last Known Good" ControlSet from
HKEY_LOCAL_MACHINE\BADSYSTEM\Select
Step 4 - change "Current" and "Default" to match "Last Known Good" in
HKEY_LOCAL_MACHINE\BADSYSTEM\Select
Step 5 - do not delete the ControlSetxxx you have just identified, but
do delete all other ControlSets under the BADSYSTEM you loaded in Step
2. You will probably have to reset permissions to allow you to
complete this operation.
Step 6 - save BADSYSTEM, which you've just modified, under a different
name, eg SMALLSYS
Step 7 - verify that "SMALLSYS" is considerably smaller than the
failing "SYSTEM" file
Step 8 - unload the BADSYSTEM, rename SYSTEM to system.org and
SMALLSYS to SYSTEM
Step 9 - reboot with fingers crossed and if it works do step 10
Step 10 - use backup/restore to create an ERD and a current copy of
the system state in the repair folder
includes a procedure for reducing the size of the system hive.
If you are still faced with the problem after trying "everything" then
I offer this additional procedure for reducing the size.
When you restart your Microsoft Windows 2000-based computer, you may
receive the following error message:
Windows could not start because the following file is missing or
corrupt:\WINNT\SYSTEM32\CONFIG\SYSTEMced
Windows 2000 may be unable to load the registry if it is too large.
This issue can occur when a process writes too much data to the System
subkey in the registry. The System subkey is designed to contain only
the information that is necessary to boot the computer.
Computers that are based on Intel architecture or ARC (RISC)
architecture can only use 16 megabytes (MB) of memory at this stage of
the boot process. The System registry subkey has to share the 16 MB
with the loader, kernel, HAL, and boot drivers. In some instances, the
size of the System subkey may be 13 MB or larger.
How to Reduce the Size of the System Hive - last resort
WARNING: this procedure is time consuming and requires some experience
with the registry editor.
You will need a 2nd system OR a complete parallel installation.
Step 1 - check the size of the failing system hive using the repair
console, if it's less than 13MB this procedure is unlikely to help
you.
Step 2 - use regedt32 to load the failing system hive as (eg)
"BADSYSTEM" under HKEY_LOCAL_MACHINE on a working Windows 2000 / XP
system, which implies that you have available a 2nd system or a
parallel installation on the same disk.
Step 3 - determine the "Last Known Good" ControlSet from
HKEY_LOCAL_MACHINE\BADSYSTEM\Select
Step 4 - change "Current" and "Default" to match "Last Known Good" in
HKEY_LOCAL_MACHINE\BADSYSTEM\Select
Step 5 - do not delete the ControlSetxxx you have just identified, but
do delete all other ControlSets under the BADSYSTEM you loaded in Step
2. You will probably have to reset permissions to allow you to
complete this operation.
Step 6 - save BADSYSTEM, which you've just modified, under a different
name, eg SMALLSYS
Step 7 - verify that "SMALLSYS" is considerably smaller than the
failing "SYSTEM" file
Step 8 - unload the BADSYSTEM, rename SYSTEM to system.org and
SMALLSYS to SYSTEM
Step 9 - reboot with fingers crossed and if it works do step 10
Step 10 - use backup/restore to create an ERD and a current copy of
the system state in the repair folder