Question : Event ID 333 - Server 2003 SP2  I/O Error

I have three Server 2003 Terminal servers in my environment.  Last week, Term-B froze up on us.  On reboot there was this message repeated every 5-9 seconds in the event log until the server was forced to reboot.  Before reboot there was no keyboard/mouse response and remote stations were being rejected from connecting.

Event Type:      Error
Event Source:      Application Popup
Event Category:      None
Event ID:      333
Date:            6/28/2010
Time:            3:19:18 AM
User:            N/A
Computer:      TERM-B
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   ........

Today, Term-A has had the same issue, same error.  This happened over a week appart from eachother.

All servers are running SP2 on a Bladecenter.  They run Terminal services to serve up a simple application to thin clients on the production floor which has not changed in years.  The three servers are connected via session directory on a fourth box.  I have seen documents on this in other forums and sites without concrete solutions/cause and none of the other instances have Terminal Services running (so it would seem).

Any suggestions?

Answer : Event ID 333 - Server 2003 SP2  I/O Error

If its not working, microsoft seems to have a patch for this error.

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