Microsoft-Windows-PmemDisk

29 events across 4 channels

Event IDTitleChannel
1Reported memory resource.Analytic
2Memory operation duration; in hundreds of nanoseconds.Analytic
3Request servicing time taken by lower driver stack(s).Analytic
101Dispatching a read request.Diagnostic
102Dispatching a write request.Diagnostic
103Dispatching a read request.Diagnostic
104Dispatching a write request.Diagnostic
105Completing an IO (read/write) request.Diagnostic
106Dispatching an IOCTL.Diagnostic
107Completing a non-read/write request.Diagnostic
108Dispatching a PnP request.Diagnostic
109Completing a PnP request.Diagnostic
201Critical metadata on NVDIMM {PersistentMemoryDiskGuid} has been corrupted.Operational
202NVDIMM {PersistentMemoryDiskGuid} failed to start.Operational
203NVDIMM {PersistentMemoryDiskGuid} started successfully.Operational
204One of the NVDIMMs that make up persistent memory disk …Operational
205During a previous boot session; one of the NVDIMMs that make up persistent …Operational
206NVDIMM {PhysicalNvdimmGuid} notified the persistent memory disk driver of a …Operational
207One of the NVDIMMs that make up the persistent memory disk …Operational
208The driver could not confirm that the NVDIMM {PersistentMemoryDiskGuid} is …Operational
209The computer didn't assign any memory resources to NVDIMM …Operational
210Some physical memory locations on NVDIMM {PersistentMemoryDiskGuid} are corrupt.Operational
211The problem with the persistent memory disk {PersistentMemoryDiskGuid} was …Operational
212One of the NVDIMMs that make up the persistent memory disk …Operational
213NVDIMM {PersistentMemoryDiskGuid} has encountered {MemoryEventCount} …Operational
300NVDIMM {PersistentMemoryDiskGuid} is now in read-only mode.System
301NVDIMM {PersistentMemoryDiskGuid} is no longer in read-only mode.System
302Windows does not support this configuration: two or more NVDIMMs on this system …System
900NVDIMM {PersistentMemoryDiskGuid} logged: {Message}.Diagnostic

Event ID 1 — Reported memory resource.

Provider
Microsoft-Windows-PmemDisk
Channel
Analytic

Message

Reported memory resource.

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

Provider
Microsoft-Windows-PmemDisk
Channel
Analytic

Message

Memory operation duration; in hundreds of nanoseconds.

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

Provider
Microsoft-Windows-PmemDisk
Channel
Analytic

Message

Request servicing time taken by lower driver stack(s).

Event ID 101 — Dispatching a read request.

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

Dispatching a read request.

Event ID 102 — Dispatching a write request.

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

Dispatching a write request.

Event ID 103 — Dispatching a read request.

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

Dispatching a read request.

Event ID 104 — Dispatching a write request.

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

Dispatching a write request.

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

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

Completing an IO (read/write) request.

Event ID 106 — Dispatching an IOCTL.

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

Dispatching an IOCTL.

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

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

Completing a non-read/write request.

Event ID 108 — Dispatching a PnP request.

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

Dispatching a PnP request.

Event ID 109 — Completing a PnP request.

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

Completing a PnP request.

Event ID 201 — Critical metadata on NVDIMM {PersistentMemoryDiskGuid} has been corrupted.

Provider
Microsoft-Windows-PmemDisk
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.

Provider
Microsoft-Windows-PmemDisk
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
Status
VendorId
ProductId
SerialNumber
Reason

Event ID 203 — NVDIMM {PersistentMemoryDiskGuid} started successfully.

Provider
Microsoft-Windows-PmemDisk
Channel
Operational

Message

NVDIMM {PersistentMemoryDiskGuid} started successfully.

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...

Provider
Microsoft-Windows-PmemDisk
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...

Provider
Microsoft-Windows-PmemDisk
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.

Provider
Microsoft-Windows-PmemDisk
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...

Provider
Microsoft-Windows-PmemDisk
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.

Provider
Microsoft-Windows-PmemDisk
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}.

Provider
Microsoft-Windows-PmemDisk
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.

Provider
Microsoft-Windows-PmemDisk
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.

Provider
Microsoft-Windows-PmemDisk
Channel
Operational

Message

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

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 ...

Provider
Microsoft-Windows-PmemDisk
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).

Provider
Microsoft-Windows-PmemDisk
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.

Provider
Microsoft-Windows-PmemDisk
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.

Provider
Microsoft-Windows-PmemDisk
Channel
System

Message

NVDIMM {PersistentMemoryDiskGuid} is no longer in read-only mode.

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.

Provider
Microsoft-Windows-PmemDisk
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}.

Provider
Microsoft-Windows-PmemDisk
Channel
Diagnostic

Message

NVDIMM {PersistentMemoryDiskGuid} logged:                           {Message}

Fields

NameDescription
PersistentMemoryDiskGuid
Message