| Event Id | 57 |
| Source | ftdisk |
| Description | The system failed to flush data to the transaction log. Corruption may occur. |
| Event Information | Explanation : NTFS could not write data to the transaction log. This could affect the ability of NTFS to stop or roll back the operations for which the transaction data could not be written. NTFS could not write data because of one or more of the following reasons: I/O requests issued by the file system to the disk subsystem might not have been completed successfully. User Action : If this message appears frequently, run Chkdsk to repair the file system. To repair the file system : Save any unsaved data and close any open programs. Restart the computer. The volume is automatically checked and repaired when you restart the computer. Alternatively, you can run the Chckdsk tool from the command prompt without shutting down the computer first. Click Start, click Run, and then type cmd At the command prompt, type chkdsk /R /X Drive: Chkdsk runs and automatically repairs the volume. Repeat step 2 for each volume on the disk. If the following message appears, type Y. “Cannot lock current drive. Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?” The next time the computer is started, Chkdsk will automatically run. |
| Reference Links | Event ID 57 and event ID 55 may be logged when you use Windows Cluster on Windows Server 2003 Event ID 50, 26, or 57 is logged when you use HP SecurePath on a computer that is running Windows Server 2003 Service Pack 1 (SP1) or an x64 edition of Windows |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.