Unrecoverable error repair method for I/O operation caused by registry _win server

This problem occurs with the server:
Many users who use the Windows Server 2003 system will receive the following error:
Event Type: Error
Event Source: Application Popup
Event Type: None
Event id:333
Date: 2007-8-11
Event: 8:48:03
Users: N/A
Computer: Lz_yq
Describe:
An unrecoverable error occurred with the I/O operation caused by the registry. The registry will not be able to read, write, or refresh one of the files that contains the registry system image.
The system then loses its response and requires a reboot.
The event ID is 333, and the English log is
Event Type:error
Event source:application Popup
Event Category:none
Event id:333
Date:date
Time:time
user:n/a
Computer:computer Name
Description:an I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the "files" that contain the system ' s image of the Registry.
The reason for this error is that this problem may occur temporarily in non-paged memory or in a paged pool with insufficient memory. The system retains recording class events until the computer restarts or the associated hive is unloaded, even if the temporary memory insufficiency stops.
Refer to KB below, because the patch is in beta, so you need to download the corresponding patch via mail:
http://support.microsoft.com/kb/970054
This problem is primarily a problem with memory exhaustion, please increase memory or look for memory-consuming culprits


The server began to stage the panic state. You can't connect for a while. After reboot normal, after a period of time is the same problem.

There are a lot of the same errors in Event Viewer:
Event id:2020
Description: The server cannot be allocated through the system page share because the shared area is currently empty.

Event id:333
Description: An unrecoverable error occurred with the I/O operation caused by the registry. The registry will not be able to read, write, or refresh one of the files that contains the registry system image.

The effect remains to be seen in trying to solve the problem with the following methods:
1, start the Registry Editor (start-> run->regedt32.exe).
2. Locate and click the following registry key in the registry:
Hkey_local_machine\system\currentcontrolset\control\sessionmanager\memory Management
3. On the Edit menu, click Add Value, and then add the following registry value (if the following registry value already exists, adjust it according to the following reference values):
(1), Numerical name: Poolusagemaximum
Data type: REG_DWORD
Cardinality: Decimal
Value data: 40
Setting this value to 40 notifies the memory manager to begin the trimming process when it reaches the PagedPoolMax 40% instead of the default setting of 80%.

(2), numerical name: PagedPoolSize
Data type: REG_DWORD
Cardinality: Hexadecimal
Value data: 0xFFFFFFFF
Setting the PagedPoolSize to 0xFFFFFFFF (-1) assigns the computer the largest paged pool to replace other resources.

4, exit Registry Editor.

PostScript (July 28, 2011):
According to the above adjustment, in the morning of the next day, the server will still appear panic condition. Suspect is not the server poisoned, to search for poison, found that the server poisoned, cleaning up the virus, after the database of the reload.

PostScript (July 30, 2011):
The server is hung up again, the Internet has checked 333 problems, try to follow the http://support.microsoft.com/kb/970054 to deal with.
Step one: Download the install patch to apply this hotfix, the computer must have Windows Server 2003 Service Pack 1 or Service Pack 2 installed.

Microsoft Official Download 378286_chs_i386_zip.exe

Download this site 378286_chs_i386_zip

Step two: To enable this hotfix, add the following registry key, and then set the value to 1 or 2.
Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Name: Registryflusherrorsubside
Type: REG_DWORD
Value: 1 or 2
If you set the value of the Registryflusherrorsubside registry key to 1, the system only logs a 333 event when there is not enough temporary memory. If the value is set to 2, the system triggers a Stop error for diagnostics.

PostScript (August 1, 2011):
The final solution is also the most helpless and most effective way to solve the problem. Tried n way, can not solve, before good, doubt is not the system upgrades what patch caused the problem, rage, the June after the system patch deleted a clean, the result of the world quiet, the server also does not crash.