Microsoft-Windows-DataIntegrityScan

41 events across 2 channels

Event	Title	Channel	Sample
1	Started checking data integrity.	Admin	Y
4	Completed data integrity checks.	Admin	Y
11	Disk scan started on \\?	Admin	N
12	Disk scan completed on \\?	Admin	N
21	Volume scan started on FriendlyVolumeName (VolumeName) in \\?	Admin	N
22	Volume scan completed on FriendlyVolumeName (VolumeName).	Admin	N
23	Volume scan was partially completed on FriendlyVolumeName (VolumeName).	Admin	N
24	Files were skipped during the volume scan.	Admin	N
25	Volume scan completed on FriendlyVolumeName (VolumeName).	Admin	N
26	Volume scan was partially completed on FriendlyVolumeName (VolumeName).	Admin	N
27	Volume scan completion at PercentComplete% on FriendlyVolumeName (VolumeName).	Admin	N
54	File data inconsistency was detected and was repaired successfully.	Admin	N
55	File data scrub operation failed.	Admin	N
56	Volume metadata inconsistency was detected and was repaired successfully.	Admin	N
57	Volume metadata scrub operation failed.	Admin	N
58	File metadata inconsistency was detected and was repaired successfully.	Admin	N
59	File metadata scrub operation failed.	Admin	N
60	File data inconsistency was detected and the parity repair was scheduled at the …	Admin	N
61	Volume metadata inconsistency was detected and the parity repair was scheduled …	Admin	N
62	File metadata inconsistency was detected and the parity repair was scheduled at …	Admin	N
101	Started checking data integrity for crash recovery.	CrashRecovery	N
104	Completed data integrity checks for crash recovery.	CrashRecovery	N
111	Crash recovery disk scan started on \\?	CrashRecovery	N
112	Crash recovery disk scan completed on \\?	CrashRecovery	N
121	Crash recovery volume scan started on FriendlyVolumeName (VolumeName) in \\?	CrashRecovery	N
122	Crash recovery volume scan completed on FriendlyVolumeName (VolumeName).	CrashRecovery	N
123	Volume scan was partially completed on FriendlyVolumeName (VolumeName).	CrashRecovery	N
124	Files were skipped during the volume scan.	CrashRecovery	N
125	Crash recovery volume scan completed on FriendlyVolumeName (VolumeName).	CrashRecovery	N
126	Volume scan was partially completed on FriendlyVolumeName (VolumeName).	CrashRecovery	N
127	Drt clear completed on FriendlyVolumeNameLength (VolumeNameLength).	CrashRecovery	N
128	Drt clear completed on FriendlyVolumeNameLength (VolumeNameLength).	CrashRecovery	N
129	Crash recovery volume scan completion at PercentComplete% on FriendlyVolumeName …	CrashRecovery	N
154	File data inconsistency was detected and was repaired successfully.	CrashRecovery	N
155	File data scrub operation failed.	CrashRecovery	N
156	Volume metadata inconsistency was detected and was repaired successfully.	CrashRecovery	N
157	Volume metadata scrub operation failed.	CrashRecovery	N
158	File metadata inconsistency was detected and was repaired successfully.	CrashRecovery	N
159	File metadata scrub operation failed.	CrashRecovery	N
160	Parity repair completed.	Admin	N
161	Parity repair failed.	Admin	N

Event ID 1: Started checking data integrity.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Level: Informational
Opcode: Start

Description

Started checking data integrity.

Message #

Started checking data integrity.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-DataIntegrityScan",
    "guid": "{13BC4371-4E21-4E46-A84F-8C0FFB548CED}",
    "event_source_name": "",
    "event_id": 1,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 1,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T05:39:31.2827688+00:00",
    "event_record_id": 17,
    "correlation": {},
    "execution": {
      "process_id": 4328,
      "thread_id": 5744
    },
    "channel": "Microsoft-Windows-DataIntegrityScan/Admin",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {},
  "message": "Started checking data integrity."
}

Event ID 4: Completed data integrity checks.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Level: Informational
Opcode: Stop

Description

Completed data integrity checks.

Message #

Completed data integrity checks.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-DataIntegrityScan",
    "guid": "{13BC4371-4E21-4E46-A84F-8C0FFB548CED}",
    "event_source_name": "",
    "event_id": 4,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 2,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T05:39:31.4041810+00:00",
    "event_record_id": 18,
    "correlation": {},
    "execution": {
      "process_id": 4328,
      "thread_id": 5744
    },
    "channel": "Microsoft-Windows-DataIntegrityScan/Admin",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {},
  "message": "Completed data integrity checks."
}

Event ID 11: Disk scan started on \\?

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Start

Description

Disk scan started on \\?\PhysicalDriveDiskNumber (\\?\DiskDiskGuid).

Message #

Disk scan started on \\?\PhysicalDrive%1 (\\?\Disk%2)

Fields #

Name	Description
`DiskNumber` UInt32
`DiskGuid` GUID
`PortPoolId` GUID
`PortDiskId` GUID

Event ID 12: Disk scan completed on \\?

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Stop

Description

Disk scan completed on \\?\PhysicalDriveDiskNumber (\\?\DiskDiskGuid).

Message #

Disk scan completed on \\?\PhysicalDrive%1 (\\?\Disk%2)

Fields #

Name	Description
`DiskNumber` UInt32
`DiskGuid` GUID
`PortPoolId` GUID
`PortDiskId` GUID

Event ID 21: Volume scan started on FriendlyVolumeName (VolumeName) in \\?

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Start

Description

Volume scan started on FriendlyVolumeName (VolumeName) in \\?\PhysicalDriveVolumeGuid (\\?\DiskDiskNumber).

Message #

Volume scan started on %4 (%2) in \\?\PhysicalDrive%5 (\\?\Disk%6)

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`VolumeGuid` GUID
`DiskNumber` UInt32
`DiskGuid` GUID
`PortPoolId` GUID
`PortDiskId` GUID

Event ID 22: Volume scan completed on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Stop

Description

Volume scan completed on FriendlyVolumeName (VolumeName).

Message #

Volume scan completed on %4 (%2)
Bytes repaired: %11
Bytes not repaired: %12
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`TotalTimeTaken` UInt64
`VolumeGuid` GUID

Event ID 23: Volume scan was partially completed on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Stop

Description

Volume scan was partially completed on FriendlyVolumeName (VolumeName).

Message #

Volume scan was partially completed on %4 (%2)
Bytes repaired: %11
Bytes not repaired: %12
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`TotalTimeTaken` UInt64
`VolumeGuid` GUID

Event ID 24: Files were skipped during the volume scan.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

Files were skipped during the volume scan.

Message #

Files were skipped during the volume scan.
Files skipped: %6
Volume name: %4 (%2)
First skipped file name: %8
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`Count` UInt64
`FileNameLength` UInt16
`FileName` UnicodeString
`VolumeGuid` GUID

Event ID 25: Volume scan completed on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Stop

Description

Volume scan completed on FriendlyVolumeName (VolumeName).

Message #

Volume scan completed on %4 (%2)
Bytes repaired: %11
Bytes not repaired: %12
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`TotalTimeTaken` UInt64
`VolumeGuid` GUID

Event ID 26: Volume scan was partially completed on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Stop

Description

Volume scan was partially completed on FriendlyVolumeName (VolumeName).

Message #

Volume scan was partially completed on %4 (%2)
Bytes repaired: %11
Bytes not repaired: %12
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`TotalTimeTaken` UInt64
`VolumeGuid` GUID

Event ID 27: Volume scan completion at PercentComplete% on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

Volume scan completion at PercentComplete% on FriendlyVolumeName (VolumeName).

Message #

Volume scan completion at %25% on %4 (%2)
Bytes repaired: %10
Bytes not repaired: %11

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`TotalTimeTaken` UInt64
`PercentComplete` UInt16
`VolumeGuid` GUID

Event ID 54: File data inconsistency was detected and was repaired successfully.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

File data inconsistency was detected and was repaired successfully.

Message #

File data inconsistency was detected and was repaired successfully.
File name: %2
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 55: File data scrub operation failed.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

File data scrub operation failed.

Message #

File data scrub operation failed.
File name: %2
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Bytes not repaired: %7
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 56: Volume metadata inconsistency was detected and was repaired successfully.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

Volume metadata inconsistency was detected and was repaired successfully.

Message #

Volume metadata inconsistency was detected and was repaired successfully.
Volume name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 57: Volume metadata scrub operation failed.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

Volume metadata scrub operation failed.

Message #

Volume metadata scrub operation failed.
Volume name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Bytes not repaired: %7
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 58: File metadata inconsistency was detected and was repaired successfully.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

File metadata inconsistency was detected and was repaired successfully.

Message #

File metadata inconsistency was detected and was repaired successfully.
File name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 59: File metadata scrub operation failed.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

File metadata scrub operation failed.

Message #

File metadata scrub operation failed.
File name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Bytes not repaired: %7
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 60: File data inconsistency was detected and the parity repair was scheduled at the end of the task.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

File data inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.

Message #

File data inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.
File name: %2
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 61: Volume metadata inconsistency was detected and the parity repair was scheduled at the end of the task.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

Volume metadata inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.

Message #

Volume metadata inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.
Volume name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 62: File metadata inconsistency was detected and the parity repair was scheduled at the end of the task.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

File metadata inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.

Message #

File metadata inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.
File name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 101: Started checking data integrity for crash recovery.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Start

Description

Started checking data integrity for crash recovery.

Message #

Started checking data integrity for crash recovery.

Event ID 104: Completed data integrity checks for crash recovery.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Stop

Description

Completed data integrity checks for crash recovery.

Message #

Completed data integrity checks for crash recovery.

Event ID 111: Crash recovery disk scan started on \\?

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Start

Description

Crash recovery disk scan started on \\?\PhysicalDriveDiskNumber (\\?\DiskDiskGuid).

Message #

Crash recovery disk scan started on \\?\PhysicalDrive%1 (\\?\Disk%2)

Fields #

Name	Description
`DiskNumber` UInt32
`DiskGuid` GUID
`PortPoolId` GUID
`PortDiskId` GUID

Event ID 112: Crash recovery disk scan completed on \\?

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Stop

Description

Crash recovery disk scan completed on \\?\PhysicalDriveDiskNumber (\\?\DiskDiskGuid).

Message #

Crash recovery disk scan completed on \\?\PhysicalDrive%1 (\\?\Disk%2)

Fields #

Name	Description
`DiskNumber` UInt32
`DiskGuid` GUID
`PortPoolId` GUID
`PortDiskId` GUID

Event ID 121: Crash recovery volume scan started on FriendlyVolumeName (VolumeName) in \\?

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Start

Description

Crash recovery volume scan started on FriendlyVolumeName (VolumeName) in \\?\PhysicalDriveDiskNumber (\\?\DiskDiskGuid).

Message #

Crash recovery volume scan started on %4 (%2) in \\?\PhysicalDrive%5 (\\?\Disk%9)

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`DiskNumber` UInt32
`DiskOffset` HexInt64
`Length` HexInt64
`VolumeGuid` GUID
`DiskGuid` GUID
`PortPoolId` GUID
`PortDiskId` GUID

Event ID 122: Crash recovery volume scan completed on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Stop

Description

Crash recovery volume scan completed on FriendlyVolumeName (VolumeName).

Message #

Crash recovery volume scan completed on %4 (%2)
Bytes repaired: %11
Bytes not repaired: %12
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`ThreadCount` UInt32
`TotalTimeTaken` UInt64
`DiskNumber` UInt32
`DiskOffset` HexInt64
`Length` HexInt64
`VolumeGuid` GUID

Event ID 123: Volume scan was partially completed on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Stop

Description

Volume scan was partially completed on FriendlyVolumeName (VolumeName).

Message #

Volume scan was partially completed on %4 (%2)
Bytes repaired: %11
Bytes not repaired: %12
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`ThreadCount` UInt32
`TotalTimeTaken` UInt64
`DiskNumber` UInt32
`DiskOffset` HexInt64
`Length` HexInt64
`VolumeGuid` GUID

Event ID 124: Files were skipped during the volume scan.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

Files were skipped during the volume scan.

Message #

Files were skipped during the volume scan.
Files skipped: %6
Volume name: %4 (%2)
First skipped file name: %8
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`Count` UInt64
`FileNameLength` UInt16
`FileName` UnicodeString
`VolumeGuid` GUID

Event ID 125: Crash recovery volume scan completed on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Stop

Description

Crash recovery volume scan completed on FriendlyVolumeName (VolumeName).

Message #

Crash recovery volume scan completed on %4 (%2)
Bytes repaired: %11
Bytes not repaired: %12
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`ThreadCount` UInt32
`TotalTimeTaken` UInt64
`DiskNumber` UInt32
`DiskOffset` HexInt64
`Length` HexInt64
`VolumeGuid` GUID

Event ID 126: Volume scan was partially completed on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Stop

Description

Volume scan was partially completed on FriendlyVolumeName (VolumeName).

Message #

Volume scan was partially completed on %4 (%2)
Bytes repaired: %11
Bytes not repaired: %12
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`ThreadCount` UInt32
`TotalTimeTaken` UInt64
`DiskNumber` UInt32
`DiskOffset` HexInt64
`Length` HexInt64
`VolumeGuid` GUID

Event ID 127: Drt clear completed on FriendlyVolumeNameLength (VolumeNameLength).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

Drt clear completed on FriendlyVolumeNameLength (VolumeNameLength).

Message #

Drt clear completed on %4 (%2)
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DiskNumber` UInt32
`DiskOffset` HexInt64
`Length` HexInt64
`VolumeGuid` GUID
`DiskGuid` GUID
`PortPoolId` GUID
`PortDiskId` GUID

Event ID 128: Drt clear completed on FriendlyVolumeNameLength (VolumeNameLength).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

Drt clear completed on FriendlyVolumeNameLength (VolumeNameLength).

Message #

Drt clear completed on %4 (%2)
HResult: %5

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`HResult` Int32
`DiskNumber` UInt32
`DiskOffset` HexInt64
`Length` HexInt64
`VolumeGuid` GUID
`DiskGuid` GUID
`PortPoolId` GUID
`PortDiskId` GUID

Event ID 129: Crash recovery volume scan completion at PercentComplete% on FriendlyVolumeName (VolumeName).

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

Crash recovery volume scan completion at PercentComplete% on FriendlyVolumeName (VolumeName).

Message #

Crash recovery volume scan completion at %26% on %4 (%2)
Bytes repaired: %10
Bytes not repaired: %11

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`DirectoryCount` UInt64
`FileCount` UInt64
`StreamCount` UInt64
`DataCount` UInt64
`FsctlCount` UInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`BytesSkippedDueToNoAllocation` HexInt64
`BytesSkippedDueToInvalidRun` HexInt64
`BytesSkippedDueToIntegrityStream` HexInt64
`BytesSkippedDueToRegionBeingClean` HexInt64
`BytesSkippedDueToLockConflict` HexInt64
`BytesSkippedDueToNoScrubDataFlag` HexInt64
`BytesSkippedDueToNoScrubNonIntegrityStreamFlag` HexInt64
`DataBytesScrubbed` HexInt64
`MetadataBytesProcessed` HexInt64
`DataBytesProcessed` HexInt64
`TotalMetadataBytesInUse` HexInt64
`TotalDataBytesInUse` HexInt64
`MaxThreadCount` UInt32
`TotalTimeTaken` UInt64
`PercentComplete` UInt16
`DiskNumber` UInt32
`DiskOffset` HexInt64
`Length` HexInt64
`VolumeGuid` GUID

Event ID 154: File data inconsistency was detected and was repaired successfully.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

File data inconsistency was detected and was repaired successfully.

Message #

File data inconsistency was detected and was repaired successfully.
File name: %2
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 155: File data scrub operation failed.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

File data scrub operation failed.

Message #

File data scrub operation failed.
File name: %2
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Bytes not repaired: %7
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 156: Volume metadata inconsistency was detected and was repaired successfully.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

Volume metadata inconsistency was detected and was repaired successfully.

Message #

Volume metadata inconsistency was detected and was repaired successfully.
Volume name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 157: Volume metadata scrub operation failed.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

Volume metadata scrub operation failed.

Message #

Volume metadata scrub operation failed.
Volume name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Bytes not repaired: %7
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 158: File metadata inconsistency was detected and was repaired successfully.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

File metadata inconsistency was detected and was repaired successfully.

Message #

File metadata inconsistency was detected and was repaired successfully.
File name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 159: File metadata scrub operation failed.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: CrashRecovery
Opcode: Info

Description

File metadata scrub operation failed.

Message #

File metadata scrub operation failed.
File name: %2
Metadata reference: %3
Range offset: %4
Range length (in bytes): %5
Bytes repaired: %6
Bytes not repaired: %7
Status: %8

Fields #

Name	Description
`FileNameLength` UInt16
`FileName` UnicodeString
`InternalFileReference` HexInt64
`FileOffset` HexInt64
`Length` HexInt64
`BytesRepaired` HexInt64
`BytesFailed` HexInt64
`Status` HexInt32	NTSTATUS reference
`VolumeGuid` GUID

Event ID 160: Parity repair completed.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

Parity repair completed.

Message #

Parity repair completed.
Volume name: %4 (%2)
Extent count: %5
Length (in bytes): %6

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`ExtentCount` UInt64
`ExtentSize` UInt64
`HResult` Int32
`VolumeGuid` GUID

Event ID 161: Parity repair failed.

Provider: Microsoft-Windows-DataIntegrityScan
Channel: Admin
Opcode: Info

Description

Parity repair failed.

Message #

Parity repair failed.
Volume name: %4 (%2)
Extent count: %5
Length (in bytes): %6
HResult: %7

Fields #

Name	Description
`VolumeNameLength` UInt16
`VolumeName` UnicodeString
`FriendlyVolumeNameLength` UInt16
`FriendlyVolumeName` UnicodeString
`ExtentCount` UInt64
`ExtentSize` UInt64
`HResult` Int32
`VolumeGuid` GUID

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID 13bc4371-4e21-4e46-a84f-8c0ffb548ced

Defined in discan.dll, which carries the event manifest.

Observed on:

WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02
Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.1, captured 2026-06-02

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)