Question : Keep geting lots of "The system failed to flush data to the transaction log. Corruption may occur" errors in Windows 7 Pro

Hi Experts,

In our Windows 7 Pro system (relatively new), we keep getting this error "The system failed to flush data to the transaction log. Corruption may occur." Google, Microsoft, and EE searches haven't yielded much help based on the details of the event. When it occurs, it will occurs SEVERAL times in a row for an hour or so. Then, it just stops for several hours, then starts again. We don't see much correlation as to what's happening at those times. Can anyone shed any light? Thx Here is the full code of the error below

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:

           
           
          Log Name:      System
Source:        Ntfs
Date:          5/12/2010 3:34:37 PM
Event ID:      57
Task Category: (2)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      mc1
Description:
The system failed to flush data to the transaction log. Corruption may occur.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Ntfs" />
    <EventID Qualifiers="32772">57</EventID>
    <Level>3</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-05-12T07:39:52.469080600Z" />
    <EventRecordID>9095</EventRecordID>
    <Channel>System</Channel>
    <Computer>mc1</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>0000000001000000020000003900048000000000100000C000000000000000000000000000000000</Binary>
  </EventData>
</Event>

           
         

Answer : Keep geting lots of "The system failed to flush data to the transaction log. Corruption may occur" errors in Windows 7 Pro

Event ID: 57
The system failed to flush data to the transaction log. Corruption may occur.
This issue may occur if the disk is "surprise removed." For example, this behavior may occur if you remove the disk without using the Safely Remove Hardware icon in the notification area to stop the disk first. This issue may occur even though the disk uses an interface that supports surprise removal, such as a universal serial bus (USB) interface or an IEEE 1394 interface.
http://support.microsoft.com/kb/938940/en-us