Discussion Locked

The cause of reg hive becoming to large

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I've read Microsoft's articles re: recovery system.ced and what others have reported on TechRepublic, but do we know why this happens or what causes it. I support a trading floor and the image we use on our trading machines Win2k Pro is standard throughout. One user, however about every week or so, his system crashes and he gets this system.ced error so we swap out the machine using the same standard trading machine image -- it's faster than using recovery. We are driving ourselves crazy trying to determine the cause and why only one user gets this registry hive too large error. We've increased the Reg to max 128.

1 reply

by ann777

You'd need to describe your hardware in order for us to really be able to tell you why this keeps happening to your users.... but the below is taken from MSKB Q269075...

"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 much memory do you have in these computers? MHz? Intel? Do you use separate IDE controllers (the Promise ATA66 is mentioned in the above article as being a potential cause)?

If it's always the same user, then something maybe going on with his profile (especially if it has happened to him on multiple machines); have you tried recreating his profile? WHen you swap the machine, can you take his and see if it does the same thing when you log in?

This discussion is closed to new replies.