pmem.sys.mui Persistent memory driver 99c91e7d2d4e7ed485d9ab18fb598c87

File info

File name: pmem.sys.mui
Size: 15872 byte
MD5: 99c91e7d2d4e7ed485d9ab18fb598c87
SHA1: 33e4541ed3135b8551c902ff55635df9067d19a2
SHA256: 2e41791311d59386fbdf332762208615d12e1dba4f5acff12ec57f691a0b840e
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in Dutch language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id Dutch English
0x12CNVDIMM %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.
0x12DNVDIMM %1 is no longer in read-only mode. NVDIMM %1 is no longer in read-only mode.
0x12EWindows 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.
0x10000002Hardware events Hardware events
0x10000021Read request Read request
0x10000022Write request Write request
0x10000023Paging Read request Paging Read request
0x10000024Paging Write request Paging Write request
0x10000025Non-Read/Write request Non-Read/Write request
0x10000026Device I/O control request Device I/O control request
0x10000027PnP request PnP request
0x10000028IO Performance measurement IO Performance measurement
0x30000000Info Info
0x50000001Critical Critical
0x50000002Error Error
0x50000003Warning Warning
0x50000004Information Information
0x90000001System System
0xB0000001Reported memory resource. Reported memory resource.
0xB0000002Memory operation duration, in hundreds of nanoseconds. Memory operation duration, in hundreds of nanoseconds.
0xB0000003Request servicing time taken by lower driver stack(s). Request servicing time taken by lower driver stack(s).
0xB0000065Dispatching a read request. Dispatching a read request.
0xB0000066Dispatching a write request. Dispatching a write request.
0xB0000069Completing an IO (read/write) request. Completing an IO (read/write) request.
0xB000006ADispatching an IOCTL. Dispatching an IOCTL.
0xB000006BCompleting a non-read/write request. Completing a non-read/write request.
0xB000006CDispatching a PnP request. Dispatching a PnP request.
0xB000006DCompleting a PnP request. Completing a PnP request.
0xB00000C9Critical 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
0xB00000CANVDIMM %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
0xB00000CBNVDIMM %1 started successfully. NVDIMM %1 started successfully.
0xB00000CCOne 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.
0xB00000CDDuring 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.
0xB00000CENVDIMM %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.
0xB00000CFOne 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.
0xB00000D0The 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
0xB00000D1The 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
0xB00000D2Some 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
0xB00000D3The 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.
0xB00000D4One 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.
0xB00000D5NVDIMM %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
0xB0000384NVDIMM %1 logged: %n %n %2 NVDIMM %1 logged: %n %n %2
0xD0000001The driver encountered an internal error. The driver encountered an internal error.
0xD0000002The driver could not interpret the device's memory resources. The driver could not interpret the device's memory resources.
0xD0000003The driver could not discover the device's interleaving settings. The driver could not discover the device's interleaving settings.
0xD0000004The driver could not read the device's serial number. The driver could not read the device's serial number.
0xD0000005The 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.
0xD0000006The 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.
0xD0000007The driver could not confirm that the NVDIMM is healthy. The driver could not confirm that the NVDIMM is healthy.
0xD0000008unknown unknown
0xD0000009unhealthy unhealthy
0xD000000Awarning warning
0xD000000Bhealthy healthy

EXIF

File Name:pmem.sys.mui
Directory:%WINDIR%\WinSxS\amd64_pmem.inf.resources_31bf3856ad364e35_10.0.15063.0_nl-nl_2c4db4af8fa16e11\
File Size:16 kB
File Permissions:rw-rw-rw-
File Type:Win32 DLL
File Type Extension:dll
MIME Type:application/octet-stream
Machine Type:Intel 386 or later, and compatibles
Time Stamp:0000:00:00 00:00:00
PE Type:PE32
Linker Version:14.10
Code Size:0
Initialized Data Size:15360
Uninitialized Data Size:0
Entry Point:0x0000
OS Version:10.0
Image Version:10.0
Subsystem Version:6.0
Subsystem:Windows GUI
File Version Number:10.0.15063.0
Product Version Number:10.0.15063.0
File Flags Mask:0x003f
File Flags:(none)
File OS:Windows NT 32-bit
Object File Type:Dynamic link library
File Subtype:0
Language Code:Dutch
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:Persistent memory driver
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:pmem.sys
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:pmem.sys.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0

What is pmem.sys.mui?

pmem.sys.mui is Multilingual User Interface resource file that contain Dutch language for file pmem.sys (Persistent memory driver).

File version info

File Description:Persistent memory driver
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:pmem.sys
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original Filename:pmem.sys.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Translation:0x413, 1200