Message

Reported memory resource.

Fields

Message

Memory operation duration, in hundreds of nanoseconds.

Fields

Message

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

Fields

Message

Dispatching a read request.

Fields

Message

Dispatching a write request.

Fields

Message

Dispatching a read request.

Fields

Message

Dispatching a write request.

Fields

Message

Completing an IO (read/write) request.

Fields

Message

Dispatching an IOCTL.

Fields

Message

Completing a non-read/write request.

Fields

Message

Dispatching a PnP request.

Fields

Message

Completing a PnP request.

Fields

Message

Persistent memory disk %1 failed to start.                    
Reason: %7                    
NTSTATUS code: %8

Fields

Message

Persistent memory disk %1 started successfully.

Fields

Message

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. If this is a data disk, it is now in read-only mode as a precaution. If you want to keep using it, run the Reset-PhysicalDisk command to make it writeable again. If this is the system disk, it will remain writeable but will appear as Unhealthy until you run the Reset-PhysicalDisk command in PowerShell.                    
                    
Look at the events logged by the physical NVDIMM driver for more details.

Fields

Message

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. If this is a data disk, it is now in read-only mode as a precaution. If you want to keep using it, run the Reset-PhysicalDisk command to make it writeable again. If this is the system disk, it will remain writeable but will appear as Unhealthy until you run the Reset-PhysicalDisk command in PowerShell.                    
                    
Look at the events logged by the physical NVDIMM driver for more details.

Fields

Message

NVDIMM %5 notified persistent memory disk %1 of a change in its health state. The NVDIMM now has the following health status: %7.

Fields

Message

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.                    
                    
Use the Get-PhysicalDisk command to get more information about the disk's health status.                    
Look at the events logged by the physical NVDIMM driver for more details.

Fields

Message

The computer didn't assign any memory resources to persistent memory disk %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.

Fields

Message

Some physical memory locations on persistent memory disk %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.

Fields

Message

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

Fields

Message

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.                    
                    
Look at the events logged by the physical NVDIMM driver for more details.

Fields

Message

The physical devices that make up persistent memory disk %1 have an atomicity setting that is incompatible with the data on the disk. Windows didn't start the disk to prevent data loss.             
             
This type of problem can happen when you update your computer's firmware, or when you upgrade from a version of Windows that doesn't look at atomicity settings to one that does.             
             
To recover the disk, follow these steps:             
1. Open the registry editor (regedit) and navigate to 'Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\ACPI0012\<instance ID>\Device Parameters'. There will only be one instance ID key.             
2. Create a registry key named 'ScmBus'. Inside it, create a new DWORD value named 'IgnoreLabels' and set it to 1.             
3. Restart your computer.             
4. When Windows starts again, your persistent memory disks will be accessible. Back up **all the data** on **all of them** to a different disk. NOTE: these recovery steps will clear all persistent memory disks, even the ones that aren't affected by this problem, so it's important to back up all your data.             
5. Open the registry editor, navigate to the 'IgnoreLabels' value you created and set it to 0.             
6. Restart your computer.             
7. The persistent memory disk will be inaccessible again. To use it, you will have to reinitialize all physical persistent memory devices on the system. Open an elevated PowerShell window and run 'Get-PmemPhysicalDevice | Initialize-PmemPhysicalDevice'.             
8. The last step is to recreate the persistent memory disks. You can do that in the elevated PowerShell window by running 'Get-PmemUnusedRegion | New-PmemDisk'. Look at the help content for 'New-PmemDisk' to learn how to specify the disks' atomicity modes.

Fields

Message

The persistent memory disk %1 is inaccessible because at least one of its NVDIMMs are locked. Contact your hardware vendor for instructions on how to unlock the NVDIMMs.

Fields

Message

The driver for persistent memory disk %1 encountered an internal error. The information in the Details tab might help Microsoft or your platform vendor to diagnose the problem.

Fields

Message

The driver couldn't configure the dump stack on persistent memory disk %1, which may cause hibernation or memory dump generation to fail.

Fields

Message

The persistent memory disk %1 changed its powerfail persistence mode to %2. (0 is PerformanceMode, 1 is DurabilityMode)

Fields

Message

Persistent memory disk %1 is now in read-only mode.  Use the Get-PhysicalDisk command to get the device?s health status.  The Microsoft-Windows-PersistentMemory-PmemDisk/Operational event log may also contain more information.

Fields

Message

Persistent memory disk %1 is no longer in read-only mode.

Fields

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.

Fields

Message

Persistent memory disk %1 logged:             
             
 %2

Fields