Hello, I agree with Sridharan. First you need to find out what issue you are running in to, is it a resource issue(most likely) or a disk issue. The instructions in Michael Morales article are a great start: These tools can assist in further diagnosing event ID 333 messages: Performance Monitor: The counters to track are the system, memory, disk, and process objects. Memory object: Look for a rise in nonpaged or paged memory.Process object: Look for continuous rises in a processs handles just prior to the event ID 333s being logged.System object: The %Registry Quota In Use counter can be useful in displaying how much of the allowed registry quota is being utilized. The higher the percentage, the more likely that the problem is related to a growing registry.Physical disk: Look for increases in the Avg Disk Queue Length counter, which tracks the average number of read and write requests to the selected disk. If this counter spikes during the problem, start investigating the filter drivers (i.e., antivirus or backup software) on your system. So first setup Perfmon to log to a file and add the above objects. Also, I would like to see a copy of this registry key if at all possible: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management We should verify that all of the settings are at the default setting before troubleshooting. Michael. [MSFT]

Excellent, can you export your Memory Management key and post it here? Also, let me know when you have the perfmon data gathered.Michael. [MSFT]

Thanks for the replies, will follow your steps to find out what is exactly causing to this issue. also i found bunch of error messages as bellow. this is seems like spreading all over the servers. first i had this for one server only now its spreading up to 4 servers. could be a patch update issue?? Event Type: Error Event Source: Application Popup Event Category: None Event ID: 333 Date: 10/02/2012 Time: 11:14:14 AM User: N/A Computer: SKH-TSBOW 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. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 01 00 6c 00 ......l. 0008: 00 00 00 00 4d 01 00 c0 ....M.. 0010: 00 00 00 00 4d 01 00 c0 ....M.. 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 58624

we are facing a problem that system is frozen some times. it happens atleast every onday and i found that there are bunch of error message as bellow. if the server freezes the following can /cant do cannot access the server via RDP SQL replication does not work can ping the server also client can access the database application. hard to find out. please help me on this. Event Type: Error Event Source: Application Popup Event Category: None Event ID: 333 Date: 8/02/2012 Time: 10:17:42 AM User: N/A Computer: BILDA-LAE-ELECT 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. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 01 00 6c 00 ......l. 0008: 00 00 00 00 4d 01 00 c0 ....M.. 0010: 00 00 00 00 4d 01 00 c0 ....M.. 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 58624

Hi, Thanks for posting here. May I know if there is any other warring or error in events viewer ? what OS is running on this server host ? It is hard to determine and narrow down this issue right now but will suggest to troubleshoot form the great article below: Troubleshooting Event ID 333 Errors http://blogs.technet.com/b/askperf/archive/2007/10/30/troubleshooting-event-id-333-errors.aspx Thanks. Tiger LiTiger Li TechNet Community Support

Hello, If Event id 333 ocurred because of system / Application Memory leak in the server. first you must determine which general category the error falls into. Also its useful to check the System event log for any other event IDs that accompany the 333 error, such as event ID 2020, which indicates a lack of paged pool memory, or event ID 2019, which indicates a leak in nonpaged pool memory. It's useful link for trouble shoot Event id 333. http://www.windowsitpro.com/article/registry2/troubleshooting-the-infamous-event-id-333-errors If you want any information / help kindly let me know :) All the best . Regards, Sridharan. M