????

Your IP : 18.223.172.41

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

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

$��<߱�R���R���R�U�����R�U�P���R�Rich��R�PEL�!R

p�L@ \N8.rdata�@@.rsrcP P@@��o�
T88��o�$��8.rdata8x.rdata$zzzdbg �.rsrc$01� �M.rsrc$02 nt�f
�E4B?5�җ���"�j%鶌o���(�@�X�p�����	�	�	�� ���!,I��j��MUI���Yt<��NWL�gSaS/�q�^	�;`"�A������MUIen-USPP���2�2�,����x�����/�0������`����4����L����`,�.�)1�1�7�����7���ECritical

Error

Warning

 Information

System

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

tNVDIMM %1 logged:

            %n

            %n %2

�The driver could not confirm that the NVDIMM %1 is healthy. Consider backing up your data to another disk.

8NVDIMM-N %1 has encountered %7 uncorrectable memory error(s). Uncorrectable memory errors can cause system instability and data loss. Consider replacing this NVDIMM-N.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

                   %n

                   %nThis NVDIMM-N can be located using the following information:

                   %n

                   %nSlot number: %3

                   %nManufacturer: %4

                   %nModel Number: %5

                   %nSerial Number: %6

                   %nLocation: %7

\The warning threshold for correctable memory errors on NVDIMM-N %1 has been exceeded. A large number of correctable memory errors increases the likelihood of an uncorrectable memory error in the future and reduces system performance. Contact your hardware vendor to determine if this NVDIMM-N needs to be replaced.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

                   %n

                   %nThis NVDIMM-N can be located using the following information:

                   %n

                   %nSlot number: %3

                   %nManufacturer: %4

                   %nModel Number: %5

                   %nSerial Number: %6

                   %nLocation: %7

�NVDIMM %1 encountered a serious problem. All data that was saved to this NVDIMM may be lost when the computer shuts down or restarts. Consider backing up your data to another disk.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

The problem with NVDIMM %1 was resolved. Data that was saved to this NVDIMM will not be lost when the computer shuts down or restarts.

�NVDIMM %1 encountered a serious problem. Data that was recently saved to this NVDIMM may be lost when the computer shuts down or restarts. Consider backing up your data to another disk.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

The problem with NVDIMM %1 was resolved. Data that was saved to this NVDIMM will not be lost when the computer shuts down or restarts.

,NVDIMM %1 encountered a critical problem. Windows may not be able to read or write to this NVDIMM.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

lThe critical problem with NVDIMM %1 was resolved.

dNVDIMM %1 is in a degraded health state and may soon encounter serious problems. Consider backing up your data to another disk.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

NVDIMM %1 is locked and you won't be able to access its contents. Contact your platform vendor to learn how you can unlock the NVDIMM.

DNVDIMM %1 failed to start. %3

HNVDIMM %1 started successfully.

�NVDIMM %1 encountered an error that may have caused data loss.

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

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

                   %n

                   %nThis NVDIMM may need to be replaced. It can be located using the following information:

                   %n

                   %nSlot number: %3

                   %nManufacturer: %4

                   %nModel Number: %5

                   %nSerial Number: %6

                   %nLocation: %7

@NVDIMM %1 encountered an error that makes it unable to save your data if your computer shuts down. Consider backing up your data to another disk.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

                   %n

                   %nThis NVDIMM may need to be replaced. It can be located using the following information:

                   %n

                   %nSlot number: %3

                   %nManufacturer: %4

                   %nModel Number: %5

                   %nSerial Number: %6

                   %nLocation: %7

�NVDIMM-N %1 encountered a serious problem that may cause data saved to this NVDIMM-N to be lost when the computer shuts down or restarts. Consider backing up your data to another disk.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

                   %n

                   %nThis NVDIMM-N may need to be replaced. It can be located using the following information:

                   %n

                   %nSlot number: %3

                   %nManufacturer: %4

                   %nModel Number: %5

                   %nSerial Number: %6

                   %nLocation: %7

DThe problem with NVDIMM-N %1 was resolved. Data saved to this NVDIMM-N is no longer at risk.

                   %n

                   %nThis NVDIMM-N may be located using the following information:

                   %n

                   %nSlot number: %3

                   %nManufacturer: %4

                   %nModel Number: %5

                   %nSerial Number: %6

                   %nLocation: %7

$NVDIMM-N %1 is in a degraded health state and may soon encounter serious problems. Consider backing up your data to another disk.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

                   %n

                   %nThis NVDIMM-N may need to be replaced. It can be located using the following information:

                   %n

                   %nSlot number: %3

                   %nManufacturer: %4

                   %nModel Number: %5

                   %nSerial Number: %6

                   %nLocation: %7

�NVDIMM %1 notified the driver that its health state changed. See the Details tab for more information.

PNVDIMM %1 is in a critically unhealthy state and your data may be lost. Consider backing up your data to another disk.

                  %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

`NVDIMM %1 is in a critically degraded state and may need to be replaced soon. Consider backing up your data to another disk.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

�NVDIMM %1's temperature is too high. To protect itself, the NVDIMM might be running slower than usual. If the temperature does not decrease, the system might shut down and some of your data may be lost.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

HNVDIMM %1 is in a degraded state and may need to be replaced soon. Consider backing up your data to another disk.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

HNVDIMM %1 is now healthy again.

�The energy source protecting NVDIMM %1 stopped working. The data saved to this NVDIMM may be lost when the computer shuts down or restarts. Consider backing up your data to another disk.

                   %n

                   %nIn PowerShell, run Get-PmemPhysicalDevice for more information and Get-PmemDisk to see which disks are affected by this problem.

�The energy source protecting NVDIMM %1 is working again. The data saved to this NVDIMM is no longer at risk.

\The driver encountered an internal error.

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

�The driver could not discover the device's unsafe shutdown count.

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

|The driver could not confirm that the NVDIMM is healthy.

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

�4VS_VERSION_INFO��
|O
|O?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationRFileDescriptionNVDIMM device driverh$FileVersion10.0.20348.1 (WinBuild.160101.0800)6InternalNamenvdimm.sys�.LegalCopyright� Microsoft Corporation. All rights reserved.FOriginalFilenamenvdimm.sys.muij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.20348.1DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD