iologmsg.dll.mui IO Logging DLL 824052cc67d917fc860dbc6a2aa42730

File info

File name: iologmsg.dll.mui
Size: 42496 byte
MD5: 824052cc67d917fc860dbc6a2aa42730
SHA1: c35d88d58ab85679eacf76dd4b5c57a03b6c529e
SHA256: b215e9601596ef36d260eb875da905da63b2d1ee142af6dd1b337a236fc73507
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in English (U.S.) 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 English (U.S.) English
0x00040001A retry was successful on %1. A retry was successful on %1.
0x40040024A user hit their quota threshold on volume %2. A user hit their quota threshold on volume %2.
0x40040025A user hit their quota limit on volume %2. A user hit their quota limit on volume %2.
0x40040026The system has started rebuilding the user disk quota information ondevice %1 with label \"%2\". The system has started rebuilding the user disk quota information ondevice %1 with label \"%2\".
0x40040027The system has successfully rebuilt the user disk quota information ondevice %1 with label \"%2\". The system has successfully rebuilt the user disk quota information ondevice %1 with label \"%2\".
0x40040077The driver for device %1 delayed non-paging Io requests for %2 ms to recover from a low memory condition. The driver for device %1 delayed non-paging Io requests for %2 ms to recover from a low memory condition.
0x40040085Device %1 is locked for exclusive access. Device %1 is locked for exclusive access.
0x4004009FFirmware update for Disk %2 is completed. Firmware update for Disk %2 is completed.
0x400400A0Firmware update for Adapter %1 is completed. Firmware update for Adapter %1 is completed.
0x40050070Machine 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. 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.
0x40050073The 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. The 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.
0x40050074The 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 memory page at physical address %1 has encountered multiple corrected hardware error events. As a result it will no longer be used by Windows.
0x8004001AThe driver has detected that device %1 has old or out-of-date firmware.Reduced performance may result. The driver has detected that device %1 has old or out-of-date firmware.Reduced performance may result.
0x80040020The driver detected that the device %1 has its write cache enabled. Data corruptionmay occur. The driver detected that the device %1 has its write cache enabled. Data corruptionmay occur.
0x80040021Data was recovered using error correction code on device %1. Data was recovered using error correction code on device %1.
0x80040022The driver disabled the write cache on device %1. The driver disabled the write cache on device %1.
0x80040028The system has encounted an error rebuilding the user disk quotainformation on device %1 with label \"%2\". The system has encounted an error rebuilding the user disk quotainformation on device %1 with label \"%2\".
0x80040032{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. {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.
0x80040033An error was detected on device %1 during a paging operation. An error was detected on device %1 during a paging operation.
0x80040034The driver has detected that device %1 has predicted that it will fail.Immediately back up your data and replace your hard disk drive. A failuremay be imminent. The driver has detected that device %1 has predicted that it will fail.Immediately back up your data and replace your hard disk drive. A failuremay be imminent.
0x80040035A pending interrupt was detected on device %1 during a timeout operation. Alarge number of these warnings may indicate that the system is not correctlyreceiving or processing interrupts from the device. A pending interrupt was detected on device %1 during a timeout operation. Alarge number of these warnings may indicate that the system is not correctlyreceiving or processing interrupts from the device.
0x80040036An Io Request to the device %1 did not complete or canceled within thespecific timeout. This can occur if the device driver does not set acancel routine for a given IO request packet. An Io Request to the device %1 did not complete or canceled within thespecific timeout. This can occur if the device driver does not set acancel routine for a given IO request packet.
0x80040038The driver failed to allocate memory. The driver failed to allocate memory.
0x80040039The system failed to flush data to the transaction log. Corruption may occur. The system failed to flush data to the transaction log. Corruption may occur.
0x8004003AThe disk signature of disk %2 is equal to the disk signature of disk %3. The disk signature of disk %2 is equal to the disk signature of disk %3.
0x8004003BDisk %2 will not be used because it is a redundant path for disk %3. Disk %2 will not be used because it is a redundant path for disk %3.
0x80040076The driver for device %1 performed a bus reset upon request. The driver for device %1 performed a bus reset upon request.
0x80040081Reset to device, %1, was issued. Reset to device, %1, was issued.
0x80040084Device %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. 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.
0x8004008B{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 may be caused by network connectivity issues. Please try to save this file elsewhere.
0x8004008C{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 was returned by the server on which the file exists. Please try to save this file elsewhere.
0x8004008D{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. {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.
0x8004008EExtent %4 on disk %3 that is part of the fault-tolerant volume %2 is no longer accessible. Extent %4 on disk %3 that is part of the fault-tolerant volume %2 is no longer accessible.
0x8004008FThe storage device produced an internal dump. The storage device produced an internal dump.
0x80040090Disk %2 has crossed a capacity utilization threshold. Disk %2 has crossed a capacity utilization threshold.
0x80040091Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, there were %4 bytes of remaining capacity. Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, there were %4 bytes of remaining capacity.
0x80040092Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, the disk had %4 bytes of remaining capacity. Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, the disk had %4 bytes of remaining capacity.
0x80040093Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, the pool had %4 bytes of remaining capacity. Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, the pool had %4 bytes of remaining capacity.
0x80040094Disk %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. Disk %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.
0x80040095Disk %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. Disk %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.
0x80040097The capacity of Disk %2 has changed. The capacity of Disk %2 has changed.
0x80040098The logical block provisioning type for Disk %2 has changed. The logical block provisioning type for Disk %2 has changed.
0x80040099The 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 (PDO name: %4) was retried.
0x8004009BThe IO operation at logical block address %2 for Disk %3 took %4 milliseconds. This was longer than the maximum expected time of %5 milliseconds. 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.
0x8004009CCrash dump is disabled. Crash dump device is not present in the system. Crash dump is disabled. Crash dump device is not present in the system.
0x8004009DDisk %2 has been surprise removed. Disk %2 has been surprise removed.
0x8004009EDisk %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. 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.
0x8005003CMachine 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 Cache error reported to CPU %1. %2 additional error(s) are contained within the record.
0x8005003EMachine Check Event reported is a corrected level %3 translation Buffer 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.
0x80050040Machine 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 External/Internal bus error reported to CPU %1. %2 additional error(s) are contained within the record.
0x80050042Machine 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 internal CPU register access error reported to CPU %1. %2 additional error(s) are contained within the record.
0x80050044Machine Check Event reported is a corrected Micro Architecture Structure 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.
0x80050046Machine 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. Machine 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.
0x80050048Machine 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. Machine 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.
0x8005004AMachine 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 reported to CPU %1. %2 additional error(s) are contained within the record.
0x8005004CMachine 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 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.
0x8005004EMachine 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 System Event error reported to CPU %1. %2 additional error(s) are contained within the record.
0x80050050Machine 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 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.
0x80050052Machine 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 Parity error reported to CPU %1. %2 additional error(s) are contained within the record.
0x80050054Machine 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 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.
0x80050056Machine 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 SERR error reported to CPU %1. %2 additional error(s) are contained within the record.
0x80050058Machine 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. 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.
0x8005005AMachine 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 Master abort error reported to CPU %1. %2 additional error(s) are contained within the record.
0x8005005CMachine 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 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.
0x8005005EMachine 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 a corrected PCI bus Timeout error reported to CPU %1. %2 additional error(s) are contained within the record.
0x80050060Machine 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 an unknown corrected PCI bus error reported to CPU %1. %2 additional error(s) are contained within the record.
0x80050062Machine Check Event reported is a corrected PCI component 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.
0x80050064Machine 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 SMBIOS Device Type %3 error reported to CPU %1. %2 additional error(s) are contained within the record.
0x80050066Machine 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 Platform Specific error reported to CPU %1. %2 additional error(s) are contained within the record.
0x80050068Machine Check Event reported is a corrected error reported to CPU %1. Machine Check Event reported is a corrected error reported to CPU %1.
0x8005006AMachine Check Event reported is a corrected error. Machine Check Event reported is a corrected error.
0x8005006DCorrected Machine Check Interrupt threshold exceeded. Interrupt has been disabled. Polling mode has been enabled. Corrected Machine Check Interrupt threshold exceeded. Interrupt has been disabled. Polling mode has been enabled.
0x8005006ECorrected Platform Error 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.
0x8005006FMachine 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 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.
0x80050071Machine Check Event reported is a corrected CPU error reported from CPU %1. %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.
0xC0040002The driver could not allocate something necessary for the request for %1. The driver could not allocate something necessary for the request for %1.
0xC0040003Driver or device is incorrectly configured for %1. Driver or device is incorrectly configured for %1.
0xC0040004Driver detected an internal error in its data structures for %1. Driver detected an internal error in its data structures for %1.
0xC0040005A parity error was detected on %1. A parity error was detected on %1.
0xC0040006The device, %1, had a seek error. The device, %1, had a seek error.
0xC0040007The device, %1, has a bad block. The device, %1, has a bad block.
0xC0040008An overrun occurred on %1. An overrun occurred on %1.
0xC0040009The device, %1, did not respond within the timeout period. The device, %1, did not respond within the timeout period.
0xC004000AThe driver detected an unexpected sequence by the device, %1. The driver detected an unexpected sequence by the device, %1.
0xC004000BThe driver detected a controller error on %1. The driver detected a controller error on %1.
0xC004000CThe driver detected an internal driver error on %1. The driver detected an internal driver error on %1.
0xC004000DThe driver was configured with an incorrect interrupt for %1. The driver was configured with an incorrect interrupt for %1.
0xC004000EThe driver was configured with an invalid I/O base address for %1. The driver was configured with an invalid I/O base address for %1.
0xC004000FThe device, %1, is not ready for access yet. The device, %1, is not ready for access yet.
0xC0040010The request is incorrectly formatted for %1. The request is incorrectly formatted for %1.
0xC0040011The wrong version of the driver has been loaded. The wrong version of the driver has been loaded.
0xC0040012The driver beneath this one has failed in some way for %1. The driver beneath this one has failed in some way for %1.
0xC0040013The device, %1, has been reset. The device, %1, has been reset.
0xC0040014A transport driver received a frame which violated the protocol. A transport driver received a frame which violated the protocol.
0xC0040015A conflict has been detected between two drivers which claimed two overlappingmemory regions.Driver %2, with device , claimed a memory range with starting addressin data address 0x28 and 0x2c, and length in data address 0x30. A conflict has been detected between two drivers which claimed two overlappingmemory regions.Driver %2, with device , claimed a memory range with starting addressin data address 0x28 and 0x2c, and length in data address 0x30.
0xC0040016A conflict has been detected between two drivers which claimed two overlappingIo port regions.Driver %2, with device , claimed an IO port range with starting addressin data address 0x28 and 0x2c, and length in data address 0x30. A conflict has been detected between two drivers which claimed two overlappingIo port regions.Driver %2, with device , claimed an IO port range with starting addressin data address 0x28 and 0x2c, and length in data address 0x30.
0xC0040017A conflict has been detected between two drivers which claimed equivalent DMAchannels.Driver %2, with device , claimed the DMA Channel in data address 0x28, withoptinal port in data address 0x2c. A conflict has been detected between two drivers which claimed equivalent DMAchannels.Driver %2, with device , claimed the DMA Channel in data address 0x28, withoptinal port in data address 0x2c.
0xC0040018A conflict has been detected between two drivers which claimed equivalent IRQs.Driver %2, with device , claimed an interrupt with Level in data address0x28, vector in data address 0x2c and Affinity in data address 0x30. A conflict has been detected between two drivers which claimed equivalent IRQs.Driver %2, with device , claimed an interrupt with Level in data address0x28, vector in data address 0x2c and Affinity in data address 0x30.
0xC0040019The driver has detected a device with old or out-of-date firmware. Thedevice will not be used. The driver has detected a device with old or out-of-date firmware. Thedevice will not be used.
0xC004001BThe device could not allocate one or more required resources due to conflictswith other devices. The device DMA setting of '%2' could not besatisified due to a conflict with Driver '%3'. The device could not allocate one or more required resources due to conflictswith other devices. The device DMA setting of '%2' could not besatisified due to a conflict with Driver '%3'.
0xC004001CThe device could not allocate one or more required resources due to conflictswith other devices. The device interrupt setting of '%2' could not besatisified due to a conflict with Driver '%3'. The device could not allocate one or more required resources due to conflictswith other devices. The device interrupt setting of '%2' could not besatisified due to a conflict with Driver '%3'.
0xC004001DThe device could not allocate one or more required resources due to conflictswith other devices. The device memory setting of '%2' could not besatisified due to a conflict with Driver '%3'. The device could not allocate one or more required resources due to conflictswith other devices. The device memory setting of '%2' could not besatisified due to a conflict with Driver '%3'.
0xC004001EThe device could not allocate one or more required resources due to conflictswith other devices. The device port setting of '%2' could not besatisified due to a conflict with Driver '%3'. The device could not allocate one or more required resources due to conflictswith other devices. The device port setting of '%2' could not besatisified due to a conflict with Driver '%3'.
0xC004001FThe file %2 on device %1 contains a bad disk block. The file %2 on device %1 contains a bad disk block.
0xC0040029The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the device %1 with label \"%2\". The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the device %1 with label \"%2\".
0xC004002AThe user disk quota information is unusable.To ensure accuracy, the file system quota information on the device %1 with label \"%2\" willbe rebuilt. The user disk quota information is unusable.To ensure accuracy, the file system quota information on the device %1 with label \"%2\" willbe rebuilt.
0xC004002BThe system sleep operation failed The system sleep operation failed
0xC004002CThe system could not get file retrieval pointers for the dump file. The system could not get file retrieval pointers for the dump file.
0xC004002DThe system could not sucessfully load the crash dump driver. The system could not sucessfully load the crash dump driver.
0xC004002ECrash dump initialization failed! Crash dump initialization failed!
0xC004002FA valid crash dump was found in the paging file while trying to configurea direct dump. Direct dump is disabled! This occurs when the direct dumpoption is set in the registry but a stop error occured before configurationcompleted A valid crash dump was found in the paging file while trying to configurea direct dump. Direct dump is disabled! This occurs when the direct dumpoption is set in the registry but a stop error occured before configurationcompleted
0xC0040030Direct dump configuration failed. Validate the filename and make sure the target deviceis not a Fault Tolerant set member, remote, or floppy device. The failure maybe because there is not enough room on the dump device to create the dump file. Direct dump configuration failed. Validate the filename and make sure the target deviceis not a Fault Tolerant set member, remote, or floppy device. The failure maybe because there is not enough room on the dump device to create the dump file.
0xC0040031Configuring the Page file for crash dump failed. Make sure there is a pagefile on the boot partition and that is large enough to contain all physicalmemory. Configuring the Page file for crash dump failed. Make sure there is a pagefile on the boot partition and that is large enough to contain all physicalmemory.
0xC0040037The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the volume %2. The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the volume %2.
0xC004006CThe driver %3 for the %2 device %1 got stuck in an infinite loop. Thisusually indicates a problem with the device itself or with the devicedriver programming the hardware incorrectly. Please check with yourhardware device vendor for any driver updates. The driver %3 for the %2 device %1 got stuck in an infinite loop. Thisusually indicates a problem with the device itself or with the devicedriver programming the hardware incorrectly. Please check with yourhardware device vendor for any driver updates.
0xC0040075The driver for device %1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition. The driver for device %1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition.
0xC0040096Disk %2 has reached a logical block provisioning permanent resource exhaustion condition. Disk %2 has reached a logical block provisioning permanent resource exhaustion condition.
0xC004009AThe IO operation at logical block address %2 for Disk %3 (PDO name: %4) failed due to a hardware error. The IO operation at logical block address %2 for Disk %3 (PDO name: %4) failed due to a hardware error.
0xC00400A1Dump file creation failed due to error during dump creation. Dump file creation failed due to error during dump creation.
0xC005003DMachine Check Event reported is a fatal level %3 Cache error reported to CPU %1. %2 additional error(s) are contained within the record. Machine Check Event reported is a fatal level %3 Cache error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC005003FMachine 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 level %3 translation Buffer error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050041Machine Check Event reported is a fatal External/Internal bus 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.
0xC0050043Machine Check Event reported is a fatal internal CPU register access error reported to CPU %1. %2 additional error(s) are contained within the record. Machine Check Event reported is a fatal internal CPU register access error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050045Machine Check Event reported is a fatal Micro Architecture Structure error reported to CPU %1. %2 additional error(s) are contained within the record. Machine Check Event reported is a fatal Micro Architecture Structure error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050047Machine 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 an unknown physical address reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050049Machine 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. 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.
0xC005004BMachine 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 reported to CPU %1. %2 additional error(s) are contained within the record.
0xC005004DMachine 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 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.
0xC005004FMachine 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 System Event error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050051Machine 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 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.
0xC0050053Machine 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 Parity error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050055Machine 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 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.
0xC0050057Machine 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 SERR error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050059Machine 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 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.
0xC005005BMachine 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 Master abort error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC005005DMachine 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 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.
0xC005005FMachine 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 a fatal PCI bus Timeout error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050061Machine 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 an unknown fatal PCI bus error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050063Machine 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 PCI component error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050065Machine 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 SMBIOS Device Type %3 error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050067Machine 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 Platform Specific error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050069Machine Check Event reported is a fatal error reported to CPU %1. Machine Check Event reported is a fatal error reported to CPU %1.
0xC005006BMachine Check Event reported is a fatal error. Machine Check Event reported is a fatal error.
0xC0050072Machine Check Event reported is a fatal CPU error reported to CPU %1. %2 additional error(s) are contained within the record. Machine Check Event reported is a fatal CPU error reported to CPU %1. %2 additional error(s) are contained within the record.
0xC0050078Machine 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 memory hierarchy error.%r Trasaction Type: %1%r Memory Hierarchy Level: %2%r Request Type: %3%r Address: %4
0xC0050079Machine Check Event reported is a fatal TLB error.%r Transaction Type: %1%r Memory Hierarchy Level: %2%r Address: %3 Machine Check Event reported is a fatal TLB error.%r Transaction Type: %1%r Memory Hierarchy Level: %2%r Address: %3
0xC005007AMachine 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 Machine 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
0xC005007BMachine 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 Bus or Interconnect timeout error.%r Memory Hierarchy Level: %1%r Participation: %2%r Request Type: %3%r Memory/IO: %4%r Address: %5
0xC005007CMachine Check Event reported is a fatal internal watchdog timer error. Machine Check Event reported is a fatal internal watchdog timer error.
0xC005007EMachine Check Event reported is a fatal microsoft ROM parity error. Machine Check Event reported is a fatal microsoft ROM parity error.
0xC005007FMachine 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 condition. A processor received an external signal that an unrecoverable error has occurred.
0xC0050080Machine Check Event reported is a fatal functional redundancy check error. Machine Check Event reported is a fatal functional redundancy check error.

EXIF

File Name:iologmsg.dll.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-windows-iologgingdll.resources_31bf3856ad364e35_10.0.15063.0_en-us_061f079c1260dc88\
File Size:42 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:41984
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:English (U.S.)
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:IO Logging DLL
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:iologmsg.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:iologmsg.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Directory:%WINDIR%\WinSxS\x86_microsoft-windows-iologgingdll.resources_31bf3856ad364e35_10.0.15063.0_en-us_aa006c185a036b52\

What is iologmsg.dll.mui?

iologmsg.dll.mui is Multilingual User Interface resource file that contain English (U.S.) language for file iologmsg.dll (IO Logging DLL).

File version info

File Description:IO Logging DLL
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:iologmsg.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original Filename:iologmsg.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Translation:0x409, 1200