MZ@ !L!This program cannot be run in DOS mode. $Rؕ3}3}3}H̴3}H̱3}Rich3}PEL!  |@0.rsrc@@( @Xp   MUI 9j#>+@@0-BB`.DD/FF0HH82JJ3LL4NN6PP7RR89TT\:VV;XX =ZZ>\\?^^tA``BbbCddDffFhh8GjjGmo, 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. 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@%@%?StringFileInfo040904B0LCompanyNameMicrosoft CorporationFFileDescriptionIO Logging DLLr)FileVersion6.3.9600.16384 (winblue_rtm.130821-1623): InternalNameiologmsg.dll.LegalCopyright Microsoft Corporation. All rights reserved.JOriginalFilenameiologmsg.dll.muij%ProductNameMicrosoft Windows Operating SystemBProductVersion6.3.9600.16384DVarFileInfo$Translation PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING