Hacked By AnonymousFox

Current Path : C:/Windows/System32/en-US/
Upload File :
Current File : C:/Windows/System32/en-US/iologmsg.dll.mui

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

$<ߵRRRЫRЫPRRichRPEL!


@ 8.rdata@@.rsrc @@f
T88f$8.rdata8x.rdata$zzzdbg .rsrc$01 0.rsrc$02 H`kM"1|	yIkf(@Xp			 !ܚ|MUI>Jב~_d, +kK_PyMUIen-USP$@'@w@w@l@@H@@p@p@ds@t@(
 "
((8268;vvL()<<8->>\.@@/BB0DD2FFH3HH4JJ5LLX7NN8PP:RR;TT<VVT>XXt?ZZA\\DB^^C``Ebb(FddHGffxHhhIjj4JmoJqq4NDO|_)1$f774ollpuu,r\stt==tu??vAAwCCxEE$zGG\{II|KK}MMTOOQQSSUUWW(YY@[[؈]]__aacc̍eeggii,kkrr x|$~DA retry was successful on %1.

hA user hit their quota threshold on volume %2.

`A user hit their quota limit on volume %2.

The system has started rebuilding the user disk quota information on

device %1 with label "%2".

The system has successfully rebuilt the user disk quota information on

device %1 with label "%2".

The driver for device %1 delayed non-paging Io requests for %2 ms to recover from a low memory condition.

\Device %1 is locked for exclusive access.

\Firmware update for Disk %2 is completed.

dFirmware update for Adapter %1 is completed.

Machine Check Event reported is a CPU thermal throttling event reported from CPU %1. The CPU has dropped below the temperature limit and throttling has been removed. %2 additional error(s) are contained within the record.

LThe maximum number of Machine Check Event corrected error events that can be saved to the Event Log has been reached. Logging of these events has been disabled.

0The memory page at physical address %1 has encountered multiple corrected hardware error events. As a result it will no longer be used by Windows.

The driver has detected that device %1 has old or out-of-date firmware.

Reduced performance may result.

The driver detected that the device %1 has its write cache enabled. Data corruption

may occur.

Data was recovered using error correction code on device %1.

lThe driver disabled the write cache on device %1.

The system has encounted an error rebuilding the user disk quota

information on device %1 with label "%2".

{Delayed Write Failed}

Windows was unable to save all the data for the file %2. The data has been lost.

This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

An error was detected on device %1 during a paging operation.

TThe driver has detected that device %1 has predicted that it will fail.

Immediately back up your data and replace your hard disk drive. A failure

may be imminent.

A pending interrupt was detected on device %1 during a timeout operation.  A

large number of these warnings may indicate that the system is not correctly

receiving or processing interrupts from the device.

An Io Request to the device %1 did not complete or canceled within the

specific timeout. This can occur if the device driver does not set a

cancel routine for a given IO request packet.

TThe driver failed to allocate memory.

The system failed to flush data to the transaction log. Corruption may occur.

The disk signature of disk %2 is equal to the disk signature of disk %3.

Disk %2 will not be used because it is a redundant path for disk %3.

The driver for device %1 performed a bus reset upon request.

LReset to device, %1, was issued.

`Device %1 is not correctly processing some write requests. In Device Manager, ensure that the Write Cache option is disabled for this device or data corruption may occur.

{Delayed Write Failed}

Windows was unable to save all the data for the file %2; the data has been lost.

This error may be caused by network connectivity issues. Please try to save this file elsewhere.

{Delayed Write Failed}

Windows was unable to save all the data for the file %2; the data has been lost.

This error was returned by the server on which the file exists. Please try to save this file elsewhere.

{Delayed Write Failed}

Windows was unable to save all the data for the file %2; the data has been lost.

This error may be caused if the device has been removed or the media is write-protected.

Extent %4 on disk %3 that is part of the fault-tolerant volume %2 is no longer accessible.

dThe storage device produced an internal dump.

tDisk %2 has crossed a capacity utilization threshold.

0Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, there were %4 bytes of remaining capacity.

4Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, the disk had %4 bytes of remaining capacity.

4Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, the pool had %4 bytes of remaining capacity.

XDisk %2 has crossed a capacity utilization threshold. When the threshold was crossed, %3 bytes from the pool were used and the disk had %4 bytes of remaining capacity.

XDisk %2 has crossed a capacity utilization threshold. When the threshold was crossed, %3 bytes from the pool were used and the pool had %4 bytes of remaining capacity.

TThe capacity of Disk %2 has changed.

The logical block provisioning type for Disk %2 has changed.

The IO operation at logical block address %2 for Disk %3 (PDO name: %4) was retried.

,The IO operation at logical block address %2 for Disk %3 took %4 milliseconds. This was longer than the maximum expected time of %5 milliseconds.

Crash dump is disabled. Crash dump device is not present in the system.

PDisk %2 has been surprise removed.

Disk %2 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.

$Machine Check Event reported is a corrected level %3 Cache error reported to CPU %1. %2 additional error(s) are contained within the record.

<Machine Check Event reported is a corrected level %3 translation Buffer error reported to CPU %1. %2 additional error(s) are contained within the record.

0Machine Check Event reported is a corrected External/Internal bus error reported to CPU %1. %2 additional error(s) are contained within the record.

@Machine Check Event reported is a corrected internal CPU register access error reported to CPU %1. %2 additional error(s) are contained within the record.

@Machine Check Event reported is a corrected Micro Architecture Structure error reported to CPU %1. %2 additional error(s) are contained within the record.

XMachine Check Event reported is a corrected ECC memory error at an unknown physical address reported to CPU %1. %2 additional error(s) are contained within the record.

HMachine Check Event reported is a corrected ECC memory error at physical address %3 reported to CPU %1. %2 additional error(s) are contained within the record.

pMachine Check Event reported is a corrected ECC memory error at physical address %3 on memory module %4 reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a corrected ECC memory error at physical address %3 on memory module %4 on memory card %5 reported to CPU %1. %2 additional error(s) are contained within the record.

 Machine Check Event reported is a corrected System Event error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a corrected PCI bus Parity error during a transaction type %3 at address %4 on PCI bus %5 reported to CPU %1. %2 additional error(s) are contained within the record.

$Machine Check Event reported is a corrected PCI bus Parity error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a corrected PCI bus SERR error during a transaction type %3 at address %4 on PCI bus %5 reported to CPU %1. %2 additional error(s) are contained within the record.

 Machine Check Event reported is a corrected PCI bus SERR error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a corrected PCI bus Master abort error during a transaction type %3 at address %4 on PCI bus %5 reported to CPU %1. %2 additional error(s) are contained within the record.

0Machine Check Event reported is a corrected PCI bus Master abort error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a corrected PCI bus Timeout error during a transaction type %3 at address %4 on PCI bus %5 reported to CPU %1. %2 additional error(s) are contained within the record.

$Machine Check Event reported is a corrected PCI bus Timeout error reported to CPU %1. %2 additional error(s) are contained within the record.

(Machine Check Event reported is an unknown corrected PCI bus error reported to CPU %1. %2 additional error(s) are contained within the record.

 Machine Check Event reported is a corrected PCI component error reported to CPU %1. %2 additional error(s) are contained within the record.

0Machine Check Event reported is a corrected SMBIOS Device Type %3 error reported to CPU %1. %2 additional error(s) are contained within the record.

(Machine Check Event reported is a corrected Platform Specific error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a corrected error reported to CPU %1.

pMachine Check Event reported is a corrected error.

Corrected Machine Check Interrupt threshold exceeded. Interrupt has been disabled. Polling mode has been enabled.

Corrected Platform Error Interrupt threshold exceeded. Interrupt has been disabled. Polling mode has been enabled.

Machine Check Event reported is a CPU thermal throttling event reported from CPU %1. The CPU has exceeded the temperature limit and has been throttled down. %2 additional error(s) are contained within the record.

Machine Check Event reported is a corrected CPU error reported from CPU %1. %2 additional error(s) are contained within the record.

The driver could not allocate something necessary for the request for %1.

pDriver or device is incorrectly configured for %1.

Driver detected an internal error in its data structures for %1.

PA parity error was detected on %1.

LThe device, %1, had a seek error.

LThe device, %1, has a bad block.

@An overrun occurred on %1.

The device, %1, did not respond within the timeout period.

The driver detected an unexpected sequence by the device, %1.

dThe driver detected a controller error on %1.

pThe driver detected an internal driver error on %1.

The driver was configured with an incorrect interrupt for %1.

The driver was configured with an invalid I/O base address for %1.

dThe device, %1, is not ready for access yet.

dThe request is incorrectly formatted for %1.

lThe wrong version of the driver has been loaded.

The driver beneath this one has failed in some way for %1.

HThe device, %1, has been reset.

A transport driver received a frame which violated the protocol.

A conflict has been detected between two drivers which claimed two overlapping

memory regions.

Driver %2, with device {3>, claimed a memory range with starting address

in data address 0x28 and 0x2c, and length in data address 0x30.

A conflict has been detected between two drivers which claimed two overlapping

Io port regions.

Driver %2, with device {3>, claimed an IO port range with starting address

in data address 0x28 and 0x2c, and length in data address 0x30.

A conflict has been detected between two drivers which claimed equivalent DMA

channels.

Driver %2, with device {3>, claimed the DMA Channel in data address 0x28, with

optinal port in data address 0x2c.

A conflict has been detected between two drivers which claimed equivalent IRQs.

Driver %2, with device {3>, claimed an interrupt with Level in data address

0x28, vector in data address 0x2c and Affinity in data address 0x30.

The driver has detected a device with old or out-of-date firmware.  The

device will not be used.

The device could not allocate one or more required resources due to conflicts

with other devices.  The device DMA setting of '%2' could not be

satisified due to a conflict with Driver '%3'.

The device could not allocate one or more required resources due to conflicts

with other devices.  The device interrupt setting of '%2' could not be

satisified due to a conflict with Driver '%3'.

The device could not allocate one or more required resources due to conflicts

with other devices.  The device memory setting of '%2' could not be

satisified due to a conflict with Driver '%3'.

The device could not allocate one or more required resources due to conflicts

with other devices.  The device port setting of '%2' could not be

satisified due to a conflict with Driver '%3'.

pThe file %2 on device %1 contains a bad disk block.

The file system structure on the disk is corrupt and unusable.

Please run the chkdsk utility on the device %1 with label "%2".

8The user disk quota information is unusable.

To ensure accuracy, the file system quota information on the device %1 with label "%2" will

be rebuilt.

LThe system sleep operation failed

The system could not get file retrieval pointers for the dump file.

The system could not sucessfully load the crash dump driver.

LCrash dump initialization failed!

A valid crash dump was found in the paging file while trying to configure

a direct dump. Direct dump is disabled! This occurs when the direct dump

option is set in the registry but a stop error occured before configuration

completed

Direct dump configuration failed. Validate the filename and make sure the target device

is not a Fault Tolerant set member, remote, or floppy device. The failure may

be because there is not enough room on the dump device to create the dump file.

LConfiguring the Page file for crash dump failed. Make sure there is a page

file on the boot partition and that is large enough to contain all physical

memory.

The file system structure on the disk is corrupt and unusable.

Please run the chkdsk utility on the volume %2.

The driver %3 for the %2 device %1 got stuck in an infinite loop. This

usually indicates a problem with the device itself or with the device

driver programming the hardware incorrectly. Please check with your

hardware device vendor for any driver updates.

0The driver for device %1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition.

Disk %2 has reached a logical block provisioning permanent resource exhaustion condition.

The IO operation at logical block address %2 for Disk %3 (PDO name: %4) failed due to a hardware error.

Dump file creation failed due to error during dump creation.

Machine Check Event reported is a fatal level %3 Cache error reported to CPU %1. %2 additional error(s) are contained within the record.

4Machine Check Event reported is a fatal level %3 translation Buffer error reported to CPU %1. %2 additional error(s) are contained within the record.

(Machine Check Event reported is a fatal External/Internal bus error reported to CPU %1. %2 additional error(s) are contained within the record.

8Machine Check Event reported is a fatal internal CPU register access error reported to CPU %1. %2 additional error(s) are contained within the record.

8Machine Check Event reported is a fatal Micro Architecture Structure error reported to CPU %1. %2 additional error(s) are contained within the record.

PMachine Check Event reported is a fatal ECC memory error at an unknown physical address reported to CPU %1. %2 additional error(s) are contained within the record.

@Machine Check Event reported is a fatal ECC memory error at physical address %3 reported to CPU %1. %2 additional error(s) are contained within the record.

hMachine Check Event reported is a fatal ECC memory error at physical address %3 on memory module %4 reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal ECC memory error at physical address %3 on memory module %4 on memory card %5 reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal System Event error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal PCI bus Parity error during a transaction type %3 at address %4 on PCI bus %5 reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal PCI bus Parity error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal PCI bus SERR error during a transaction type %3 at address %4 on PCI bus %5 reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal PCI bus SERR error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal PCI bus Master abort error during a transaction type %3 at address %4 on PCI bus %5 reported to CPU %1. %2 additional error(s) are contained within the record.

(Machine Check Event reported is a fatal PCI bus Master abort error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal PCI bus Timeout error during a transaction type %3 at address %4 on PCI bus %5 reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal PCI bus Timeout error reported to CPU %1. %2 additional error(s) are contained within the record.

 Machine Check Event reported is an unknown fatal PCI bus error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal PCI component error reported to CPU %1. %2 additional error(s) are contained within the record.

(Machine Check Event reported is a fatal SMBIOS Device Type %3 error reported to CPU %1. %2 additional error(s) are contained within the record.

 Machine Check Event reported is a fatal Platform Specific error reported to CPU %1. %2 additional error(s) are contained within the record.

Machine Check Event reported is a fatal error reported to CPU %1.

hMachine Check Event reported is a fatal error.

Machine Check Event reported is a fatal CPU error reported to CPU %1. %2 additional error(s) are contained within the record.

0Machine Check Event reported is a fatal memory hierarchy error.%r Trasaction Type: %1%r Memory Hierarchy Level: %2%r Request Type: %3%r Address: %4

Machine Check Event reported is a fatal TLB error.%r Transaction Type: %1%r Memory Hierarchy Level: %2%r Address: %3

TMachine Check Event reported is a fatal Bus or Interconnect error.%r Memory Hierarchy Level: %1%r Participation: %2%r Request Type: %3%r Memory/IO: %4%r Address: %5

dMachine Check Event reported is a fatal Bus or Interconnect timeout error.%r Memory Hierarchy Level: %1%r Participation: %2%r Request Type: %3%r Memory/IO: %4%r Address: %5

Machine Check Event reported is a fatal internal watchdog timer error.

Machine Check Event reported is a fatal microsoft ROM parity error.

Machine Check Event reported is a fatal condition. A processor received an external signal that an unrecoverable error has occurred.

Machine Check Event reported is a fatal functional redundancy check error.

4VS_VERSION_INFO
cE
cE?StringFileInfo040904B0LCompanyNameMicrosoft CorporationFFileDescriptionIO Logging DLLh$FileVersion10.0.17763.1 (WinBuild.160101.0800):
InternalNameiologmsg.dll.LegalCopyright Microsoft Corporation. All rights reserved.JOriginalFilenameiologmsg.dll.muij%ProductNameMicrosoft Windows Operating System>
ProductVersion10.0.17763.1DVarFileInfo$Translation	PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX

Hacked By AnonymousFox1.0, Coded By AnonymousFox