| 0x12C | NVDIMM %1 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. |
NVDIMM %1 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. |
| 0x12D | NVDIMM %1 is no longer in read-only mode. |
NVDIMM %1 is no longer in read-only mode. |
| 0x12E | 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. |
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. |
| 0x10000002 | Hardware events |
Hardware events |
| 0x10000021 | Read request |
Read request |
| 0x10000022 | Write request |
Write request |
| 0x10000023 | Paging Read request |
Paging Read request |
| 0x10000024 | Paging Write request |
Paging Write request |
| 0x10000025 | Non-Read/Write request |
Non-Read/Write request |
| 0x10000026 | Device I/O control request |
Device I/O control request |
| 0x10000027 | PnP request |
PnP request |
| 0x10000028 | IO Performance measurement |
IO Performance measurement |
| 0x30000000 | Info |
Info |
| 0x50000001 | Critical |
Critical |
| 0x50000002 | Error |
Error |
| 0x50000003 | Warning |
Warning |
| 0x50000004 | Information |
Information |
| 0x90000001 | System |
System |
| 0xB0000001 | Reported memory resource. |
Reported memory resource. |
| 0xB0000002 | Memory operation duration, in hundreds of nanoseconds. |
Memory operation duration, in hundreds of nanoseconds. |
| 0xB0000003 | Request servicing time taken by lower driver stack(s). |
Request servicing time taken by lower driver stack(s). |
| 0xB0000065 | Dispatching a read request. |
Dispatching a read request. |
| 0xB0000066 | Dispatching a write request. |
Dispatching a write request. |
| 0xB0000069 | Completing an IO (read/write) request. |
Completing an IO (read/write) request. |
| 0xB000006A | Dispatching an IOCTL. |
Dispatching an IOCTL. |
| 0xB000006B | Completing a non-read/write request. |
Completing a non-read/write request. |
| 0xB000006C | Dispatching a PnP request. |
Dispatching a PnP request. |
| 0xB000006D | Completing a PnP request. |
Completing a PnP request. |
| 0xB00000C9 | Critical metadata on NVDIMM %1 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. %n %nConsider replacing the NVDIMM. %n %nThis NVDIMM may be located using the following information: %n %nSlot number: %2 %nManufacturer: %3 %nModel Number: %4 %nSerial Number: %5 |
Critical metadata on NVDIMM %1 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. %n %nConsider replacing the NVDIMM. %n %nThis NVDIMM may be located using the following information: %n %nSlot number: %2 %nManufacturer: %3 %nModel Number: %4 %nSerial Number: %5 |
| 0xB00000CA | NVDIMM %1 failed to start. %6 %n %nThis NVDIMM may be located using the following information: %n %nSlot number: %2 %nManufacturer: %3 %nModel Number: %4 %nSerial Number: %5 |
NVDIMM %1 failed to start. %6 %n %nThis NVDIMM may be located using the following information: %n %nSlot number: %2 %nManufacturer: %3 %nModel Number: %4 %nSerial Number: %5 |
| 0xB00000CB | NVDIMM %1 started successfully. |
NVDIMM %1 started successfully. |
| 0xB00000CC | One of the NVDIMMs that make up persistent memory disk %1 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. %n %nLook at the events logged by the physical NVDIMM driver for more details. |
One of the NVDIMMs that make up persistent memory disk %1 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. %n %nLook at the events logged by the physical NVDIMM driver for more details. |
| 0xB00000CD | During a previous boot session, one of the NVDIMMs that make up persistent memory disk %1 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. %n %nLook at the events logged by the physical NVDIMM driver for more details. |
During a previous boot session, one of the NVDIMMs that make up persistent memory disk %1 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. %n %nLook at the events logged by the physical NVDIMM driver for more details. |
| 0xB00000CE | NVDIMM %5 notified the persistent memory disk driver of a change in its health state. The NVDIMM now has the following health status: %7. %n %nThis NVDIMM is part of interleave set %1. |
NVDIMM %5 notified the persistent memory disk driver of a change in its health state. The NVDIMM now has the following health status: %7. %n %nThis NVDIMM is part of interleave set %1. |
| 0xB00000CF | One of the NVDIMMs that make up the persistent memory disk %1 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. %n %nUse the Get-PhysicalDisk command to get more information about the disk's health status. |
One of the NVDIMMs that make up the persistent memory disk %1 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. %n %nUse the Get-PhysicalDisk command to get more information about the disk's health status. |
| 0xB00000D0 | The driver could not confirm that the NVDIMM %1 is healthy. To protect your data, the NVDIMM is now in read-only mode. Consider backing up your data to another disk. %n %nThis NVDIMM may need to be replaced. It can be located using the following information: %n %nManufacturer: %2 %nModel Number: %3 %nSerial Number: %4 |
The driver could not confirm that the NVDIMM %1 is healthy. To protect your data, the NVDIMM is now in read-only mode. Consider backing up your data to another disk. %n %nThis NVDIMM may need to be replaced. It can be located using the following information: %n %nManufacturer: %2 %nModel Number: %3 %nSerial Number: %4 |
| 0xB00000D1 | The computer didn't assign any memory resources to NVDIMM %1. 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. %n %nThis NVDIMM may need to be replaced. It can be located using the following information: %n %nManufacturer: %2 %nModel Number: %3 %nSerial Number: %4 |
The computer didn't assign any memory resources to NVDIMM %1. 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. %n %nThis NVDIMM may need to be replaced. It can be located using the following information: %n %nManufacturer: %2 %nModel Number: %3 %nSerial Number: %4 |
| 0xB00000D2 | Some physical memory locations on NVDIMM %1 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. %n %nThis NVDIMM may need to be replaced. It can be located using the following information: %n %nManufacturer: %2 %nModel Number: %3 %nSerial Number: %4 |
Some physical memory locations on NVDIMM %1 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. %n %nThis NVDIMM may need to be replaced. It can be located using the following information: %n %nManufacturer: %2 %nModel Number: %3 %nSerial Number: %4 |
| 0xB00000D3 | The problem with the persistent memory disk %1 was resolved and it is now back in read-write mode. |
The problem with the persistent memory disk %1 was resolved and it is now back in read-write mode. |
| 0xB00000D4 | One of the NVDIMMs that make up the persistent memory disk %1 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. |
One of the NVDIMMs that make up the persistent memory disk %1 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. |
| 0xB00000D5 | NVDIMM %1 has encountered %5 uncorrectable memory error(s). Uncorrectable memory errors can cause system instability and data loss. Consider replacing this NVDIMM. %n %nThis NVDIMM can be located using the following information: %n %nManufacturer: %2 %nModel Number: %3 %nSerial Number: %4 |
NVDIMM %1 has encountered %5 uncorrectable memory error(s). Uncorrectable memory errors can cause system instability and data loss. Consider replacing this NVDIMM. %n %nThis NVDIMM can be located using the following information: %n %nManufacturer: %2 %nModel Number: %3 %nSerial Number: %4 |
| 0xB0000384 | NVDIMM %1 logged: %n %n %2 |
NVDIMM %1 logged: %n %n %2 |
| 0xD0000001 | The driver encountered an internal error. |
The driver encountered an internal error. |
| 0xD0000002 | The driver could not interpret the device's memory resources. |
The driver could not interpret the device's memory resources. |
| 0xD0000003 | The driver could not discover the device's interleaving settings. |
The driver could not discover the device's interleaving settings. |
| 0xD0000004 | The driver could not read the device's serial number. |
The driver could not read the device's serial number. |
| 0xD0000005 | The driver could not discover whether boot-time operations, like save and restore, succeeded. |
The driver could not discover whether boot-time operations, like save and restore, succeeded. |
| 0xD0000006 | The driver could not register to be notified of health-related events on the NVDIMM. |
The driver could not register to be notified of health-related events on the NVDIMM. |
| 0xD0000007 | The driver could not confirm that the NVDIMM is healthy. |
The driver could not confirm that the NVDIMM is healthy. |
| 0xD0000008 | unknown |
unknown |
| 0xD0000009 | unhealthy |
unhealthy |
| 0xD000000A | warning |
warning |
| 0xD000000B | healthy |
healthy |