Mini Kabibi Habibi

Current Path : C:/Windows/System32/drivers/en-US/
Upload File :
Current File : C:/Windows/System32/drivers/en-US/pmem.sys.mui

MZ����@���	�!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!B

`��@ �?8.rdata�@@.rsrc@ @@@D�t
T88D�t$��8.rdata8x.rdata$zzzdbg �.rsrc$01� �>.rsrc$02 [<��R��8��'�;ߖ���]�d�AD�t��(�@�X�p�����	�	�	�� ���!`:�\��MUI���{�f�$�fh�F�J��ņgZ�%�P[.�:�D�����MUIen-US,.�`!(�00PP ������e�f��i�m�P	�����
���������\�����
���� ����������2��<5�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.

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

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

(Hardware events

$Read request

$Write request

0Paging Read request

4Paging Write request

8Non-Read/Write request

@Device I/O control request

 PnP request

@IO Performance measurement

Info

Critical

Error

Warning

 Information

System

<Reported memory resource.

xMemory operation duration, in hundreds of nanoseconds.

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

@Dispatching a read request.

DDispatching a write request.

XCompleting an IO (read/write) request.

4Dispatching an IOCTL.

TCompleting a non-read/write request.

@Dispatching a PnP request.

<Completing a PnP request.

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

�Persistent memory disk %1 logged:

            %n

            %n %2

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

�Persistent memory disk %1 failed to start.

                   %nReason: %5

                   %nNTSTATUS code: %6

hPersistent memory disk %1 started successfully.

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.

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

                   %n

                   %nLook at the events logged by the physical NVDIMM driver for more details.

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

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

                   %nLook at the events logged by the physical NVDIMM driver for more details.

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

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

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

                   %n

                   %nLook at the events logged by the physical NVDIMM driver for more details.

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

            %n

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

            %n

            %nTo recover the disk, follow these steps:

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

            %n2. Create a registry key named 'ScmBus'. Inside it, create a new DWORD value named 'IgnoreLabels' and set it to 1.

            %n3. Restart your computer.

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

            %n5. Open the registry editor, navigate to the 'IgnoreLabels' value you created and set it to 0.

            %n6. Restart your computer.

            %n7. 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'.

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

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

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

\The driver encountered an internal error.

�The driver could not interpret the device's memory resources.

�The driver could not discover the device's interleaving settings.

tThe driver could not read the device's serial number.

�The driver could not discover whether boot-time operations, like save and restore, succeeded.

�The driver could not register to be notified of health-related events on the NVDIMM.

�The driver could not determine the health status of the persistent memory disk.

�There is an uncorrectable memory error in a critical region of the persistent memory disk.

unknown

unhealthy

warning

healthy

�4VS_VERSION_INFO��
aJ
aJ?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationZFileDescriptionPersistent memory driverh$FileVersion10.0.19041.1 (WinBuild.160101.0800)2	InternalNamepmem.sys�.LegalCopyright� Microsoft Corporation. All rights reserved.B
OriginalFilenamepmem.sys.muij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.19041.1DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING