Microsoft-Windows-PmemDisk

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 {PersistentMemoryDiskGuid} has been corrupted.OperationalNN
202NVDIMM {PersistentMemoryDiskGuid} failed to start.OperationalNN
203NVDIMM {PersistentMemoryDiskGuid} started successfully.OperationalNN
204One of the NVDIMMs that make up persistent memory disk …OperationalNN
205During a previous boot session; one of the NVDIMMs that make up persistent …OperationalNN
206NVDIMM {PhysicalNvdimmGuid} notified the persistent memory disk driver of a …OperationalNN
207One of the NVDIMMs that make up the persistent memory disk …OperationalNN
208The driver could not confirm that the NVDIMM {PersistentMemoryDiskGuid} is …OperationalNN
209The computer didn't assign any memory resources to NVDIMM …OperationalNN
210Some physical memory locations on NVDIMM {PersistentMemoryDiskGuid} are corrupt.OperationalNN
211The problem with the persistent memory disk {PersistentMemoryDiskGuid} was …OperationalNN
212One of the NVDIMMs that make up the persistent memory disk …OperationalNN
213NVDIMM {PersistentMemoryDiskGuid} has encountered {MemoryEventCount} …OperationalNN
300NVDIMM {PersistentMemoryDiskGuid} is now in read-only mode.SystemNN
301NVDIMM {PersistentMemoryDiskGuid} is no longer in read-only mode.SystemNN
302Windows does not support this configuration: two or more NVDIMMs on this system …SystemNN
900NVDIMM {PersistentMemoryDiskGuid} 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 {PersistentMemoryDiskGuid} has been corrupted.

#
Channel
Operational

Message #

Critical metadata on NVDIMM {PersistentMemoryDiskGuid} 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: {VendorId}                    Manufacturer: {ProductId}                    Model Number: {SerialNumber}                    Serial Number: {BinaryDataSize}

Fields #

NameDescription
PersistentMemoryDiskGuid
VendorId
ProductId
SerialNumber
BinaryDataSize

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

#
Channel
Operational

Message #

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

Fields #

NameDescription
PersistentMemoryDiskGuid
StatusNTSTATUS reference
VendorId
ProductId
SerialNumber
Reason

Event ID 203: NVDIMM {PersistentMemoryDiskGuid} started successfully.

#
Channel
Operational

Fields #

NameDescription
PersistentMemoryDiskGuid

Event ID 204: One of the NVDIMMs that make up persistent memory disk {PersistentMemoryDiskGuid} encountered an error while transferring your data to or from pers...

#
Channel
Operational

Message #

One of the NVDIMMs that make up persistent memory disk {PersistentMemoryDiskGuid} 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 persistent memory disk is now in read-only mode. If you want to keep using it; run the Reset-PhysicalDisk command to make it writeable again.                                        Look at the events logged by the physical NVDIMM driver for more details.

Fields #

NameDescription
PersistentMemoryDiskGuid

Event ID 205: During a previous boot session; one of the NVDIMMs that make up persistent memory disk {PersistentMemoryDiskGuid} encountered an error while transf...

#
Channel
Operational

Message #

During a previous boot session; one of the NVDIMMs that make up persistent memory disk {PersistentMemoryDiskGuid} 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 persistent memory disk temporarily read-only. If you want to keep using this persistent memory disk; use the Reset-PhysicalDisk command to make it writeable again.                                        Look at the events logged by the physical NVDIMM driver for more details.

Fields #

NameDescription
PersistentMemoryDiskGuid

Event ID 206: NVDIMM {PhysicalNvdimmGuid} notified the persistent memory disk driver of a change in its health state.

#
Channel
Operational

Message #

NVDIMM {PhysicalNvdimmGuid} notified the persistent memory disk driver of a change in its health state. The NVDIMM now has the following health status: {NvdimmHealthStatus}.                          This NVDIMM is part of interleave set {LogicalPersistentMemoryDiskGuid}.

Fields #

NameDescription
PhysicalNvdimmGuid
NvdimmHealthStatus
LogicalPersistentMemoryDiskGuid

Event ID 207: One of the NVDIMMs that make up the persistent memory disk {PersistentMemoryDiskGuid} encountered a serious problem and the disk is now in read-onl...

#
Channel
Operational

Message #

One of the NVDIMMs that make up the persistent memory disk {PersistentMemoryDiskGuid} encountered a serious problem and the disk is now in read-only mode. Data that was saved to this disk 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 disk's health status.

Fields #

NameDescription
PersistentMemoryDiskGuid

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

#
Channel
Operational

Message #

The driver could not confirm that the NVDIMM {PersistentMemoryDiskGuid} 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:                                        Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
PersistentMemoryDiskGuid
VendorId
ProductId
SerialNumber

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

#
Channel
Operational

Message #

The computer didn't assign any memory resources to NVDIMM {PersistentMemoryDiskGuid}. 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:                                        Manufacturer: {VendorId}                    Model Number: {ProductId}                    Serial Number: {SerialNumber}

Fields #

NameDescription
PersistentMemoryDiskGuid
VendorId
ProductId
SerialNumber

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

#
Channel
Operational

Message #

Some physical memory locations on NVDIMM {PersistentMemoryDiskGuid} 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:                          Manufacturer: {VendorId}             Model Number: {ProductId}             Serial Number: {SerialNumber}

Fields #

NameDescription
PersistentMemoryDiskGuid
VendorId
ProductId
SerialNumber

Event ID 211: The problem with the persistent memory disk {PersistentMemoryDiskGuid} was resolved and it is now back in read-write mode.

#
Channel
Operational

Fields #

NameDescription
PersistentMemoryDiskGuid

Event ID 212: One of the NVDIMMs that make up the persistent memory disk {PersistentMemoryDiskGuid} is in a degraded health state and may soon encounter serious ...

#
Channel
Operational

Message #

One of the NVDIMMs that make up the persistent memory disk {PersistentMemoryDiskGuid} 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.

Fields #

NameDescription
PersistentMemoryDiskGuid

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

#
Channel
Operational

Message #

NVDIMM {PersistentMemoryDiskGuid} 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:                          Manufacturer: {VendorId}             Model Number: {ProductId}             Serial Number: {SerialNumber}

Fields #

NameDescription
PersistentMemoryDiskGuid
MemoryEventCount
VendorId
ProductId
SerialNumber

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

#
Channel
System

Message #

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

Fields #

NameDescription
PersistentMemoryDiskGuid

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

#
Channel
System

Fields #

NameDescription
PersistentMemoryDiskGuid

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 {PersistentMemoryDiskGuid} logged: {Message}.

#
Channel
Diagnostic

Message #

NVDIMM {PersistentMemoryDiskGuid} logged:                           {Message}

Fields #

NameDescription
PersistentMemoryDiskGuid
Message