3

To be precise

System has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored.

WinXP/64 running fine for 2 years (no /3Gb switch), just started happening. I used ntregopt and the problem went away at least temporarily. However, looking before and after in Windows\System32\Config I see that my System file was reduced only by 10% and is still 170+ Mb. According to my rather extensive research with Google, this is "huge" and should be more like 10-20Mb. The system runs fine. There is a System.bak that is only 11Mb and has the date when I ran ntregopt.

That's what I know. Now my question: Is there anything I can do to reduce or rebuild the System registry hive given the above info?

Bob Denny
  • 303

3 Answers3

3

This article seems to have some information that may help. It does go over some steps you may have already tried (ntregopt), but it includes a link to a tool you may have yet to try to clean your registry of dead entries: vxscrub.

I'm not big on these registry cleaners, but some people rave about ccleaner, which contains a module that also cleans your registry of dead entries.

Personally, I would opt for a data backup and an operating system re-install for a more stable system. That depends on your environment and available time, though.

I found this post which seems to imply that this error is caused by a corrupted swap file. Since you've already tried the first suggestion in the post, I would try the second, added recommendation (cross posted here for easy reference):

The page file needs to be overwritten as it has been corrupted. Follow the following steps:

  1. Enter System in control panel (classic view)
  2. Click on the Advanced tab
  3. Click the settings button under "performance"
  4. Click the Advanced tab in Performance Settings
  5. Click Change virtual settings
  6. Choose No paging file on the settings and click Set
  7. Exit and restart the computer.
  8. Repeat the first five steps of these instructions.
  9. Choose System managed size on the settings and click Set
  10. When you exit you will be asked if you want to overwrite the previous page file. Allow this action.
  11. Restart your computer. You will be rid of the error message. Also, your programs may run better.

I still think it could be a corrupted swap file. Have a look at this document, which outlines the procedure a lot more. Are you sure you removed the swap file, rebooted, then re-created it?

You might also want to try the User Profile Hive Cleanup Service. Some people have reported success with that.

If indeed the size of the system part of the local machine hive has filled up, then I don't think there is a solution other than removing some software and running a second machine - be it virtual or physical. This would be really interesting to see; in all my professional career I have never seen a legitimately filled registry.

Community
  • 1
Cypher
  • 343
  • 2
  • 12
1

This is so strange... As I pointed out in comments, I decided that the message was false. I have now used the system for a week doing heavy development, including testing a complex installer that registers a bunch of old VB6 and newer .NET based COM objects repeatedly. I'm very careful that I don't change GUIDs thus creating a bunch of dead registry entries, by the way! Success for all this time, no problems with the registry.

Anyway, I ran into a separate bizarre problem last night, where I decided to use System Restore (which I've only used one other time in several years). The System Restore failed, saying it could not restore to that checkpoint and that nothing was changed.

On a lark, I decided to have a look at that \config\system file (system hive) and WHAT??? It had shrunk from 196Mb to 7Mb! the error on boot was gone! Something in the last few days, which included a few reboots for the other unrelated problem, caused the system hive to shrink back down to where it should be.

So this isn't an "answer" as such, it's just a war story which ends in a mysterious "self correction" of the original problem. I have no idea what fixed it.

Bob Denny
  • 303
0

The registry may have "dead" entries, if there were applications and hardware changes. There are a number of online resources available by searching against "registry cleaner" as the search term.