Windows / Modules / pmem.sys

pmem.sys

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0x12c1011Persistent 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.
0x12d1011Persistent memory disk %1 is no longer in read-only mode.
0x12e1011Windows 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.
0x100000021011Hardware events
0x100000211011Read request
0x100000221011Write request
0x100000231011Paging Read request
0x100000241011Paging Write request
0x100000251011Non-Read/Write request
0x100000261011Device I/O control request
0x100000271011PnP request
0x100000281011IO Performance measurement
0x300000001011Info
0x500000011011Critical
0x500000021011Error
0x500000031011Warning
0x500000041011Information
0x900000011011System
0xb00000011011Reported memory resource.
0xb00000021011Memory operation duration, in hundreds of nanoseconds.
0xb00000031011Request servicing time taken by lower driver stack(s).
0xb00000651011Dispatching a read request.
0xb00000661011Dispatching a write request.
0xb00000691011Completing an IO (read/write) request.
0xb000006a1011Dispatching an IOCTL.
0xb000006b1011Completing a non-read/write request.
0xb000006c1011Dispatching a PnP request.
0xb000006d1011Completing a PnP request.
0xb00000d810The driver couldn't configure the dump stack on persistent memory disk %1, which may cause hibernation or memory dump generation to fail.
0xb00003841011Persistent memory disk %1 logged: %2
0xb00100d71011The 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.
0xb00200ca10Persistent memory disk %1 failed to start. Reason: %5 NTSTATUS code: %6
0xb00200cb1011Persistent memory disk %1 started successfully.
0xb00200cc1011One 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.
0xb00200cd1011During 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.
0xb00200ce1011NVDIMM %5 notified persistent memory disk %1 of a change in its health state. The NVDIMM now has the following health status: %7.
0xb00200cf1011One 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.
0xb00200d11011The 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.
0xb00200d31011The problem with the persistent memory disk %1 was resolved and it is now back in read-write mode.
0xb00200d41011One 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.
0xb00200d51011The 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\\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.
0xb00200d61011The 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.
0xb00300d21011Some 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.
0xd00000011011The driver encountered an internal error.
0xd00000021011The driver could not interpret the device's memory resources.
0xd00000031011The driver could not discover the device's interleaving settings.
0xd00000041011The driver could not read the device's serial number.
0xd00000051011The driver could not discover whether boot-time operations, like save and restore, succeeded.
0xd00000061011The driver could not register to be notified of health-related events on the NVDIMM.
0xd00000071011The driver could not determine the health status of the persistent memory disk.
0xd00000081011There is an uncorrectable memory error in a critical region of the persistent memory disk.
0xd00000091011unknown
0xd000000a1011unhealthy
0xd000000b1011warning
0xd000000c1011healthy
0xb00100d811The driver couldn't configure the dump stack on persistent memory disk %1, which may cause hibernation or memory dump generation to fail.
0xb00100d911The persistent memory disk %1 changed its powerfail persistence mode to %2. (0 is PerformanceMode, 1 is DurabilityMode)
0xb00200ca11Persistent memory disk %1 failed to start. Reason: %7 NTSTATUS code: %8
58 entries