Microsoft-Windows-ScmDisk0101

EventTitleChannelSampleRule
1Reported memory resource.AnalyticNN
2Memory operation duration; in hundreds of nanoseconds.AnalyticNN
3Request servicing time taken by lower driver stack(s).AnalyticNN
101Dispatching a read request.DiagnosticNN
102Dispatching a write request.DiagnosticNN
103Dispatching a read request.DiagnosticNN
104Dispatching a write request.DiagnosticNN
105Completing an IO (read/write) request.DiagnosticNN
106Dispatching an IOCTL.DiagnosticNN
107Completing a non-read/write request.DiagnosticNN
108Dispatching a PnP request.DiagnosticNN
109Completing a PnP request.DiagnosticNN
201Critical metadata on NVDIMM {DeviceGuid} has been corrupted.OperationalNN
202NVDIMM {DeviceGuid} failed to start.OperationalNN
203NVDIMM {DeviceGuid} started successfully.OperationalNN
204NVDIMM {DeviceGuid} encountered an error while transferring your data to or from …OperationalNN
205During a previous boot session; the NVDIMM {DeviceGuid} encountered an error …OperationalNN
206NVDIMM {DeviceGuid} notified the driver that its health state changed.OperationalNN
207NVDIMM {DeviceGuid} encountered a serious problem and is now in read-only mode.OperationalNN
208The driver could not confirm that the NVDIMM {DeviceGuid} is healthy.OperationalNN
209The computer didn't assign any memory resources to NVDIMM {DeviceGuid}.OperationalNN
210Some physical memory locations on NVDIMM {DeviceGuid} are corrupt.OperationalNN
211The problem with NVDIMM {DeviceGuid} was resolved and it is now back in …OperationalNN
212NVDIMM {DeviceGuid} is in a degraded health state and may soon encounter serious …OperationalNN
213NVDIMM {DeviceGuid} has encountered {MemoryEventCount} uncorrectable memory …OperationalNN
214The warning threshold for correctable memory errors on NVDIMM {DeviceGuid} has …OperationalNN
300NVDIMM {DeviceGuid} is now in read-only mode.SystemNN
301NVDIMM {DeviceGuid} is no longer in read-only mode.SystemNN
302Windows does not support this configuration: two or more NVDIMMs on this system …SystemNN
900NVDIMM {DeviceGuid} logged: {Message}.DiagnosticNN

Event ID 1: Reported memory resource.

#
Channel
Analytic

Event ID 2: Memory operation duration; in hundreds of nanoseconds.

#
Channel
Analytic

Event ID 3: Request servicing time taken by lower driver stack(s).

#
Channel
Analytic

Event ID 101: Dispatching a read request.

#
Channel
Diagnostic

Event ID 102: Dispatching a write request.

#
Channel
Diagnostic

Event ID 103: Dispatching a read request.

#
Channel
Diagnostic

Event ID 104: Dispatching a write request.

#
Channel
Diagnostic

Event ID 105: Completing an IO (read/write) request.

#
Channel
Diagnostic

Event ID 106: Dispatching an IOCTL.

#
Channel
Diagnostic

Event ID 107: Completing a non-read/write request.

#
Channel
Diagnostic

Event ID 108: Dispatching a PnP request.

#
Channel
Diagnostic

Event ID 109: Completing a PnP request.

#
Channel
Diagnostic

Event ID 201: Critical metadata on NVDIMM {DeviceGuid} has been corrupted.

#
Channel
Operational

Message #

Critical metadata on NVDIMM {DeviceGuid} has been corrupted. Windows needs this metadata to start the NVDIMM correctly; so we had to reinitialize it. The data on that NVDIMM may have been lost.                                        Consider replacing the NVDIMM.                                        This NVDIMM may be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 202: NVDIMM {DeviceGuid} failed to start.

#
Channel
Operational

Message #

NVDIMM {DeviceGuid} failed to start. {Reason}                                        This NVDIMM may be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
Reason
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 203: NVDIMM {DeviceGuid} started successfully.

#
Channel
Operational

Fields #

NameDescription
DeviceGuid

Event ID 204: NVDIMM {DeviceGuid} encountered an error while transferring your data to or from persistent media (see the Details tab for more information).

#
Channel
Operational

Message #

NVDIMM {DeviceGuid} encountered an error while transferring your data to or from persistent media (see the Details tab for more information). Some of your data may have been lost. As a precaution; this NVDIMM is now in read-only mode. If you want to keep using this NVDIMM; use the Reset-PhysicalDisk command to make it writeable again.                                        This NVDIMM may need to be replaced. It can be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 205: During a previous boot session; the NVDIMM {DeviceGuid} encountered an error while transferring your data to or from persistent media.

#
Channel
Operational

Message #

During a previous boot session; the NVDIMM {DeviceGuid} encountered an error while transferring your data to or from persistent media. Some of your data may have been lost then. As a precaution; Windows made this NVDIMM temporarily read-only. If you want to keep using this NVDIMM; use the Reset-PhysicalDisk command to make it writeable again.                                        This NVDIMM may need to be replaced. It can be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 206: NVDIMM {DeviceGuid} notified the driver that its health state changed.

#
Channel
Operational

Message #

NVDIMM {DeviceGuid} notified the driver that its health state changed.                                        This NVDIMM may be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 207: NVDIMM {DeviceGuid} encountered a serious problem and is now in read-only mode.

#
Channel
Operational

Message #

NVDIMM {DeviceGuid} encountered a serious problem and is now in read-only mode. Data that was saved to this NVDIMM may be lost when the computer shuts down or restarts. Consider backing up your data to another disk.                                        Use the Get-PhysicalDisk command to get more information about the device’s health status.                                        This NVDIMM may need to be replaced. It can be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 208: The driver could not confirm that the NVDIMM {DeviceGuid} is healthy.

#
Channel
Operational

Message #

The driver could not confirm that the NVDIMM {DeviceGuid} is healthy. To protect your data; the NVDIMM is now in read-only mode. Consider backing up your data to another disk.                                        This NVDIMM may need to be replaced. It can be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 209: The computer didn't assign any memory resources to NVDIMM {DeviceGuid}.

#
Channel
Operational

Message #

The computer didn't assign any memory resources to NVDIMM {DeviceGuid}. You won't be able to access the data on the device; but you can still query its health status by using the Get-PhysicalDisk command.                                        This NVDIMM may need to be replaced. It can be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 210: Some physical memory locations on NVDIMM {DeviceGuid} are corrupt.

#
Channel
Operational

Message #

Some physical memory locations on NVDIMM {DeviceGuid} are corrupt. In order to protect your computer; Windows will not access those locations and you may see failures trying to read or write to your data. Contact your hardware vendor to learn what recovery steps are available.                          This NVDIMM may need to be replaced. It can be located using the following information:                          Slot number: {SlotNumber}             Manufacturer: {VendorId}             Model Number: {ProductId}             Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 211: The problem with NVDIMM {DeviceGuid} was resolved and it is now back in read-write mode.

#
Channel
Operational

Message #

The problem with NVDIMM {DeviceGuid} was resolved and it is now back in read-write mode.                                        This NVDIMM may be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 212: NVDIMM {DeviceGuid} is in a degraded health state and may soon encounter serious problems.

#
Channel
Operational

Message #

NVDIMM {DeviceGuid} is in a degraded health state and may soon encounter serious problems. Consider backing up your data to another disk. Use the Get-PhysicalDisk command to see more information.                                        This NVDIMM may need to be replaced. It can be located using the following information:                                        Slot number: {SlotNumber}                    Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 213: NVDIMM {DeviceGuid} has encountered {MemoryEventCount} uncorrectable memory error(s).

#
Channel
Operational

Message #

NVDIMM {DeviceGuid} has encountered {MemoryEventCount} uncorrectable memory error(s). Uncorrectable memory errors can cause system instability and data loss. Consider replacing this NVDIMM.                          This NVDIMM can be located using the following information:                          Slot number: {SlotNumber}             Manufacturer: {VendorId}             Model Number: {ProductId}             Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
MemoryEventCount
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 214: The warning threshold for correctable memory errors on NVDIMM {DeviceGuid} has been exceeded.

#
Channel
Operational

Message #

The warning threshold for correctable memory errors on NVDIMM {DeviceGuid} has been exceeded. A large number of correctable memory errors increases the likelihood of an uncorrectable memory error in the future and reduces system performance. Contact your hardware vendor to determine if this NVDIMM needs to be replaced.                          This NVDIMM can be located using the following information:                          Slot number: {SlotNumber}             Manufacturer: {VendorId}             Model Number: {ProductId}             Serial Number: {SerialNumber}

Fields #

NameDescription
DeviceGuid
SlotNumber
VendorId
ProductId
SerialNumber

Event ID 300: NVDIMM {DeviceGuid} is now in read-only mode.

#
Channel
System

Message #

NVDIMM {DeviceGuid} is now in read-only mode.  Use the Get-PhysicalDisk command to get the device’s health status.  The Microsoft-Windows-ScmDisk0101/Operational event log may also contain more information.

Fields #

NameDescription
DeviceGuid

Event ID 301: NVDIMM {DeviceGuid} is no longer in read-only mode.

#
Channel
System

Fields #

NameDescription
DeviceGuid

Event ID 302: Windows does not support this configuration: two or more NVDIMMs on this system are part of an interleaved set.

#
Channel
System

Message #

Windows does not support this configuration: two or more NVDIMMs on this system are part of an interleaved set. Back up the data on the interleaved set to a different drive and then break up the interleaved set. Consider using Storage Spaces if NVDIMM capacity needs to be aggregated.

Event ID 900: NVDIMM {DeviceGuid} logged: {Message}.

#
Channel
Diagnostic

Message #

NVDIMM {DeviceGuid} logged:                           {Message}

Fields #

NameDescription
DeviceGuid
Message