Ntfs

5 events across 1 channel

Event	Title	Channel	Sample
55	A corruption was discovered in the file system structure on volume DriveName.	System	N
130	The file system structure on volume VolumeId has now been repaired.	System	Y
131	The file system structure on volume VolumeId cannot be corrected.	System	N
132	Too many repair events have occurred in a short period of time.	System	N
133	Skipped posting of TotalCount repair events.	System	N

Event ID 55: A corruption was discovered in the file system structure on volume DriveName.

Provider: Ntfs
Channel: System

Description

A corruption was discovered in the file system structure on volume DriveName.

Message #

A corruption was discovered in the file system structure on volume %1.

%8

Fields #

Name	Description
`DriveName` UnicodeString
`DeviceName` UnicodeString
`CorruptionState` HexInt32
`HeaderFlags` HexInt32
`Severity` UnicodeString
`Origin` UnicodeString
`Verb` UnicodeString
`Description` UnicodeString
`Signature` HexInt32
`Outcome` UnicodeString
`SampleLength` UInt16
`SampleData` Binary
`SourceFile` HexInt32
`SourceLine` UInt16
`SourceTag` UInt32
`AdditionalInfo` HexInt32
`CallStack` AnsiString

Event ID 130: The file system structure on volume VolumeId has now been repaired.

Provider: Ntfs
Channel: System
Level: Warning

Description

The file system structure on volume VolumeId has now been repaired.

Message #

The file system structure on volume %2 has now been repaired.

Fields #

Name	Description
`VolumeIdLength` UInt16
`VolumeId` UnicodeString
`RepairDetail` UnicodeString
`RepairDataLength` UInt16
`RepairData` Binary

Example Event #

{
  "system": {
    "provider": "Ntfs",
    "guid": "{DD70BC80-EF44-421B-8AC3-CD31DA613A4E}",
    "event_source_name": "",
    "event_id": 130,
    "version": 0,
    "level": 3,
    "task": 0,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-05-28T11:11:49.8428150+00:00",
    "event_record_id": 1821,
    "correlation": {},
    "execution": {
      "process_id": 4,
      "thread_id": 4368
    },
    "channel": "System",
    "computer": "telemetry-DC-d.cell-d.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "VolumeIdLength": "2",
    "VolumeId": "C:",
    "RepairDetail": "25008: Start repair on 05/28/2026 at 11:11:49:821\n\n25017: Processing repair verb IndexEntry: 0x10000000013df, \"$I30\", \"bb3a785178f443fda931098a5a9a306b.db.ses\"\nFlags: 0x32, 0x0\n26065: Deleting index entry bb3a785178f443fda931098a5a9a306b.db.ses in index 0x10000000013df of file 0x3000000010fae.\n25009: End repair on 05/28/2026 at 11:11:49:837\n",
    "RepairDataLength": "152",
    "RepairData": "0D000000FFFFFFFFFFFFFFFFE300170006000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
  },
  "message": "The file system structure on volume C: has now been repaired."
}

Event ID 131: The file system structure on volume VolumeId cannot be corrected.

Provider: Ntfs
Channel: System

Description

The file system structure on volume VolumeId cannot be corrected.

Message #

The file system structure on volume %2 cannot be corrected.
Please run the chkdsk utility on the volume %2.

Fields #

Name	Description
`VolumeIdLength` UInt16
`VolumeId` UnicodeString
`RepairDetail` UnicodeString
`RepairDataLength` UInt16
`RepairData` Binary

Event ID 132: Too many repair events have occurred in a short period of time.

Provider: Ntfs
Channel: System

Description

Too many repair events have occurred in a short period of time.

Message #

Too many repair events have occurred in a short period of time.
Temporarily suspending posting of further repair events.

Event ID 133: Skipped posting of TotalCount repair events.

Provider: Ntfs
Channel: System

Description

Skipped posting of TotalCount repair events. Repair event posting will now be resumed.

Message #

Skipped posting of %1 repair events.  Repair event posting will now be resumed.
 Here are the skipped posting repair events count by repair verbs:
 BadFRS: %2
 OrphanChildFRS: %3
 BadClusters: %4
 BadFreeClusters: %5
 CrossLink: %6
 SDEntry: %7
 InvalidSecurityId: %8
 IndexAttribute: %9
 IndexSubtree: %10
 IndexOffset: %11
 IndexEntry: %12
 IndexOrder: %13
 Connect: %14
 BreakCycle: %15
 FRSAllocate: %16
 Others: %17

Fields #

Name	Description
`TotalCount` UInt32
`BadFrsCount` UInt32
`OrphanChildFRSCount` UInt32
`BadClustersCount` UInt32
`BadFreeClustersCount` UInt32
`CrossLinkCount` UInt32
`SDEntryCount` UInt32
`InvalidSidCount` UInt32
`IndexAttributeCount` UInt32
`IndexSubtreeCount` UInt32
`IndexOffsetCount` UInt32
`IndexEntryCount` UInt32
`IndexOrderCount` UInt32
`ConnectCount` UInt32
`BreakCycleCount` UInt32
`FRSAllocateCount` UInt32
`OthersCount` UInt32

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 dd70bc80-ef44-421b-8ac3-cd31da613a4e

Defined in ntfs.sys, the binary that emits these events.

Observed on:

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

Downloads

Ntfs registered manifest XML (in the WS2022-20348.4893 manifest pack, 1.9 MB) manifest-xml
Ntfs registered manifest XML (in the Win11-26200.6584 manifest pack, 2.0 MB) manifest-xml

`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)

Ntfs

Event ID 55: A corruption was discovered in the file system structure on volume DriveName.

Description

Message #

Fields #

Event ID 130: The file system structure on volume VolumeId has now been repaired.

Description

Message #

Fields #

Example Event #

Event ID 131: The file system structure on volume VolumeId cannot be corrected.

Description

Message #

Fields #

Event ID 132: Too many repair events have occurred in a short period of time.

Description

Message #

Event ID 133: Skipped posting of TotalCount repair events.

Description

Message #

Fields #

Provenance

Downloads

Keyboard shortcuts

Search operators