APPLIES TO

x86 Windows Server 2003 Service Pack 2

x64 Windows Server 2003 Service Pack 2

IA64 Windows Server 2003 Service Pack 2

INTRODUCTION

This blog describes how to troubleshoot “Event ID 333” on Windows Server 2003.

My team has written a blog regarding this issue:

Troubleshooting Event ID 333 Errors

http://blogs.technet.com/askperf/archive/2007/10/30/troubleshooting-event-id-333-errors.aspx

and

Michael Morales has written a nice article for Windows IT Pro about this issue.

Troubleshooting the Infamous Event ID 333 Errors

http://windowsitpro.com/Articles/ArticleID/101059/pg/1/1.html

SYMPTOMS

Event Type: Error
Event Source: Application Popup
Event Category: None
Event ID: 333
Date: MM/DD/YEAR
Time: HH:MM:SS
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.

Troubleshooting:

------------------

I wanted to bring to you this new item to your arsenal of tools to get to the bottom of this issue.

1)  You want to make sure to have the following kernel hotfix or a newer version is installed:

970054 Many events with ID 333 are added to the System log on a Windows Server 2003-based computer

http://support.microsoft.com/kb/970054

Updates Ntoskrnl.exe 5.2.3790.4497

2)  You want to setup the tools for gathering data for memory issues as described in:

http://blogs.technet.com/yongrhee/archive/2009/10/14/how-to-troubleshoot-the-use-of-paged-pool-kernel-memory-event-id-2020-in-windows-server-2003.aspx