333 Event Id Error
Contents |
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample windows event id 333 report Custom views/filters Servers list, organized in groups Integration with EventID.Net event id 333 in windows 2003 Consolidated view for all logs Free for subscribers Event ID: 333 Source: Application Popup Source:
Event Id 333 Application Popup
Application Popup Type: Error 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
Event Id 333 Server 2003
files that contain the system's image of the Registry. English: This information is only available to subscribers. An example of English, please! Concepts to understand: What are the registry files? What is an I/O operation? When does an I/O operation fail unrecoverably? Our approach: This information is only available to subscribers. An example of event id 333 microsoft Our approach Comments: Anonymous I had this problem in some server on LUN network, when the storage was moved to other site. To solve this, I removed the iSCSI parameters and Volume mount point device and after that I rebooted the system. When the system came back I reconfigured the iSCSI and re-scanned the device volume. x 7 Johannes Froemter Had this event on dozens of W2K3 SP2. Turned out to be caused by a service that allocated handles without properly releasing them. After a couple of days uptime other services crashed and event id 333 was written to the system log twice a minute. In our case the culprit was gpamon.exe (Beta 48 Tracker) from Beta Systems. To find the process causing the problem, enable the Handle Count column in Task Manager (process tab) and check the process(es) with the highest number(s). If you cannot logon to the server anymore, try pslist \\servername (from Sysinternals, now part of Microsoft).
identifying the cause of Event ID 333 Issue: Event ID 333 is logged in the System event log when performance related issues arise such as paged pool, nonpaged pool or physical
Event Id 222
memory depletion. Event ID 2019 and Event ID 2020 are sometimes logged event id 999 indicating a nonpaged pool memory depletion or paged pool depletion respectively. Often times a stop error occurs as event id 1111 a result. Solution: 1. Review the System event logs for Event ID 2019 and Event ID 2020. Often times the source of the paged or nonpaged pool memory leak is http://www.eventid.net/display-eventid-333-source-Application%20Popup-eventno-5757-phase-1.htm identified in the Event ID. Contact the software vendor of the identified software application or driver if identified. 2. If a stop error occurs the memory dump file can be used to determine the paged pool and nonpaged pool consumption. It can also identify paged and nonpaged pool tags consuming excessive amounts of memory. Follow the steps in the Additional Information http://www.dell.com/support/article/us/en/04/SLN290484 section to determine if there is a memory leak. 3. Review the free physical RAM to determine if it is depleted. Often times free physical RAM is depleted because an application is configured to utilize all available memory on the server or the application may have a memory leak. Applications such as Microsoft SQL Server can be configured to consume all available memory causing performance issues and resource depletion. Instructions about setting the SQL Server Maximum Memory Setting can be found here. 4. Review the processes in Windows Task Manager to determine if an application or process is consuming too many file handles indicating a memory leak. Information about using Windows Task Manager to identify these issues can be found here. 5. Add additional physical RAM to the server especially if the operating system is 32-bit. 32-bit versions of Windows are allocated smaller pools of paged and nonpaged pool memory thus increasing the chances of pool depletion. Smaller amounts of pool memory may be allocated depending on the version of the operating system and whether it is 32-bit or 64-bit. 6.
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://serverfault.com/questions/56121/an-i-o-operation-initiated-by-the-registry-failed-unrecoverably Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top event id An I/O operation initiated by the Registry failed unrecoverably up vote 2 down vote favorite 4 Every 10 seconds or so, both our web servers (windows server 2003, running iis6), report the same errors in the event log. > Event Type: Error Event > Source: Application Popup Event > Category: None Event ID: 333 > Date: 2009-08-18 Time: 22:04:06 > User: N/A Computer: DFS273 > Description: An I/O operation > initiated event id 333 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 > ........ I can't find any information as to what could cause these kinds of errors. The CPU is quite busy at 90-100% but there is almost 1 GB of unused RAM. windows-server-2003 iis iis-6 windows-registry low-memory share|improve this question asked Aug 19 '09 at 14:55 windyjonas 133117 add a comment| 5 Answers 5 active oldest votes up vote 1 down vote accepted Disk/controller/RAID hardware? Take the machine down and run chkdsk c: /v /f (and also on any other partitions you have.). I know you said the problem happened on two machines, but perhaps they both have disks from a bad batch. Or your disk is fine