Damaged Registry Repair and Recovery in Windows XP (318159)



The information in this article applies to:

  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional

This article was previously published under Q318159

SYMPTOMS

When a registry hive becomes damaged, your computer may become unbootable, and you may receive one of the following Stop error messages on a blue screen:
  • Unexpected Shutdown
  • Stop:0xc0000135

CAUSE

Registry damage often occurs when programs with access to the registry do not cleanly remove temporary items that they store in the registry. This problem may also be caused if a program is terminated or experiences a user-mode fault.

RESOLUTION

NOTE: The hotfix that is described in this article automatically repairs the registry during startup, but does not display any notification of this process. If you import a damaged registry hive, you may receive a notification, and the recovery of the registry hive takes place as it imports.

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to Obtain the Latest Windows XP Service Pack

The English version of this fix should have the following file attributes or later:
   Date         Time   Version      Size       File name
   --------------------------------------------------------
   28-Feb-2002  10:13  5.1.2600.29  1,846,272  Ntkrnlmp.exe
   28-Feb-2002  10:14  5.1.2600.29  1,901,568  Ntkrnlpa.exe
   28-Feb-2002  10:14  5.1.2600.29  1,874,432  Ntkrpamp.exe
   28-Feb-2002  10:13  5.1.2600.29  1,879,168  Ntoskrnl.exe
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.

Modification Type:MinorLast Reviewed:10/10/2006
Keywords:kbHotfixServer kbQFE kbbug kbenv kbfix kbOSWin2000fix kbWinXPsp1fix KB318159