What does Windows error code 6851 (ERROR_VOLUME_DIRTY) mean?

 
Previous Next
ERROR_COMPRESSION_NOT_ALLOWED_IN_TRANSACTION ERROR_NO_LINK_TRACKING_IN_TRANSACTION

ERROR_VOLUME_DIRTY

The operation could not be completed because the volume is dirty. Please run chkdsk and try again.

ERROR_VOLUME_DIRTY is Win32 error 6851 (0x00001AC3) in Windows file-system and storage integrity handling.

Where the result appears

  • mounting or servicing a volume after an unclean shutdown.
  • performing an operation that requires a clean NTFS state.
  • starting backup, resize, or repair work.
  • accessing removable or virtual media after interrupted writes.

What to verify

Verify whether the file system has completed required consistency checking and cleared the dirty state. Check fsutil dirty query result, chkdsk scan or repair output, and System log disk and NTFS events.

Likely causes

  • the system lost power during file-system updates.
  • Windows detected metadata inconsistency.
  • a previous chkdsk or repair did not complete.
  • the storage path disappeared while writes were pending.
  • the dirty bit was set for a scheduled consistency check.

Troubleshooting steps

  1. Collect fsutil dirty query result.
  2. Record chkdsk scan or repair output.
  3. Correlate System log disk and NTFS events with the Windows System log, NTFS/ReFS events, storage-controller diagnostics, application integrity checks, and backup or replica logs.

Handling, retry, and recovery

Schedule and complete the appropriate chkdsk mode, correct underlying storage faults, reboot when the volume cannot be repaired online, and verify that the dirty bit is cleared.

Related errors

ERROR_BAD_CLUSTERS identifies damaged allocation units; a dirty volume may be healthy physically but still require consistency verification.

Example

A maintenance tool refuses to resize a data volume after an unexpected host reset. An online scan identifies metadata work that requires an offline repair; after reboot and chkdsk, the dirty bit clears and resize succeeds.

Developer and administrator guidance

Administrators should prioritize data preservation and hardware evidence before repair. Developers should separate structural file-system success from application-level integrity, because a readable or repaired file can still be semantically incomplete.

References

Looking for a different code? Search another status or error code.