iologmsg.dll
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x40001 | 78.11011 | A retry was successful on %1. |
| 0x40040024 | 78.11011 | A user hit their quota threshold on volume %2. |
| 0x40040025 | 78.11011 | A user hit their quota limit on volume %2. |
| 0x40040026 | 78.11011 | The system has started rebuilding the user disk quota information on device %1 with label "%2". |
| 0x40040027 | 78.11011 | The system has successfully rebuilt the user disk quota information on device %1 with label "%2". |
| 0x40040077 | 78.11011 | The driver for device %1 delayed non-paging Io requests for %2 ms to recover from a low memory condition. |
| 0x40040085 | 78.11011 | Device %1 is locked for exclusive access. |
| 0x4004009f | 1011 | Firmware update for Disk %2 is completed. |
| 0x400400a0 | 1011 | Firmware update for Adapter %1 is completed. |
| 0x40050070 | 78.11011 | 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. |
| 0x40050073 | 78.11011 | 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. |
| 0x40050074 | 78.11011 | 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. |
| 0x8004001a | 78.11011 | The driver has detected that device %1 has old or out-of-date firmware. Reduced performance may result. |
| 0x80040020 | 78.11011 | The driver detected that the device %1 has its write cache enabled. Data corruption may occur. |
| 0x80040021 | 78.11011 | Data was recovered using error correction code on device %1. |
| 0x80040022 | 78.11011 | The driver disabled the write cache on device %1. |
| 0x80040028 | 78.11011 | The system has encounted an error rebuilding the user disk quota information on device %1 with label "%2". |
| 0x80040032 | 78.11011 | {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. |
| 0x80040033 | 78.11011 | An error was detected on device %1 during a paging operation. |
| 0x80040034 | 78.11011 | 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 failure may be imminent. |
| 0x80040035 | 78.11011 | 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. |
| 0x80040036 | 78.11011 | 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. |
| 0x80040038 | 78.11011 | The driver failed to allocate memory. |
| 0x80040039 | 78.11011 | The system failed to flush data to the transaction log. Corruption may occur. |
| 0x8004003a | 78.11011 | The disk signature of disk %2 is equal to the disk signature of disk %3. |
| 0x8004003b | 78.11011 | Disk %2 will not be used because it is a redundant path for disk %3. |
| 0x80040076 | 78.11011 | The driver for device %1 performed a bus reset upon request. |
| 0x80040081 | 78.11011 | Reset to device, %1, was issued. |
| 0x80040084 | 78.11011 | 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 | 8.11011 | {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 | 8.11011 | {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 | 8.11011 | {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. |
| 0x8004008e | 8.11011 | Extent %4 on disk %3 that is part of the fault-tolerant volume %2 is no longer accessible. |
| 0x8004008f | 8.11011 | The storage device produced an internal dump. |
| 0x80040090 | 8.11011 | Disk %2 has crossed a capacity utilization threshold. |
| 0x80040091 | 8.11011 | Disk %2 has crossed a capacity utilization threshold and used %3 bytes. When the threshold was crossed, there were %4 bytes of remaining capacity. |
| 0x80040092 | 8.11011 | 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. |
| 0x80040093 | 8.11011 | 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. |
| 0x80040094 | 8.11011 | 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. |
| 0x80040095 | 8.11011 | 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. |
| 0x80040097 | 8.11011 | The capacity of Disk %2 has changed. |
| 0x80040098 | 8.11011 | The logical block provisioning type for Disk %2 has changed. |
| 0x80040099 | 8.11011 | The IO operation at logical block address %2 for Disk %3 (PDO name: %4) was retried. |
| 0x8004009b | 8.11011 | 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. |
| 0x8004009c | 8.11011 | Crash dump is disabled. Crash dump device is not present in the system. |
| 0x8004009d | 8.11011 | Disk %2 has been surprise removed. |
| 0x8004009e | 1011 | 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. |
| 0x8005003c | 78.11011 | Machine Check Event reported is a corrected level %3 Cache error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x8005003e | 78.11011 | 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. |
| 0x80050040 | 78.11011 | Machine Check Event reported is a corrected External/Internal bus error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x80050042 | 78.11011 | 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. |
| 0x80050044 | 78.11011 | Machine Check Event reported is a corrected Micro Architecture Structure error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x80050046 | 78.11011 | 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. |
| 0x80050048 | 78.11011 | 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. |
| 0x8005004a | 78.11011 | 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. |
| 0x8005004c | 78.11011 | 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. |
| 0x8005004e | 78.11011 | Machine Check Event reported is a corrected System Event error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x80050050 | 78.11011 | 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. |
| 0x80050052 | 78.11011 | Machine Check Event reported is a corrected PCI bus Parity error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x80050054 | 78.11011 | 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. |
| 0x80050056 | 78.11011 | Machine Check Event reported is a corrected PCI bus SERR error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x80050058 | 78.11011 | 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. |
| 0x8005005a | 78.11011 | 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. |
| 0x8005005c | 78.11011 | 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. |
| 0x8005005e | 78.11011 | Machine Check Event reported is a corrected PCI bus Timeout error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x80050060 | 78.11011 | Machine Check Event reported is an unknown corrected PCI bus error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x80050062 | 78.11011 | Machine Check Event reported is a corrected PCI component error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x80050064 | 78.11011 | 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. |
| 0x80050066 | 78.11011 | Machine Check Event reported is a corrected Platform Specific error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0x80050068 | 78.11011 | Machine Check Event reported is a corrected error reported to CPU %1. |
| 0x8005006a | 78.11011 | Machine Check Event reported is a corrected error. |
| 0x8005006d | 78.11011 | Corrected Machine Check Interrupt threshold exceeded. Interrupt has been disabled. Polling mode has been enabled. |
| 0x8005006e | 78.11011 | Corrected Platform Error Interrupt threshold exceeded. Interrupt has been disabled. Polling mode has been enabled. |
| 0x8005006f | 78.11011 | 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. |
| 0x80050071 | 78.11011 | Machine Check Event reported is a corrected CPU error reported from CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0040002 | 78.11011 | The driver could not allocate something necessary for the request for %1. |
| 0xc0040003 | 78.11011 | Driver or device is incorrectly configured for %1. |
| 0xc0040004 | 78.11011 | Driver detected an internal error in its data structures for %1. |
| 0xc0040005 | 78.11011 | A parity error was detected on %1. |
| 0xc0040006 | 78.11011 | The device, %1, had a seek error. |
| 0xc0040007 | 78.11011 | The device, %1, has a bad block. |
| 0xc0040008 | 78.11011 | An overrun occurred on %1. |
| 0xc0040009 | 78.11011 | The device, %1, did not respond within the timeout period. |
| 0xc004000a | 78.11011 | The driver detected an unexpected sequence by the device, %1. |
| 0xc004000b | 78.11011 | The driver detected a controller error on %1. |
| 0xc004000c | 78.11011 | The driver detected an internal driver error on %1. |
| 0xc004000d | 78.11011 | The driver was configured with an incorrect interrupt for %1. |
| 0xc004000e | 78.11011 | The driver was configured with an invalid I/O base address for %1. |
| 0xc004000f | 78.11011 | The device, %1, is not ready for access yet. |
| 0xc0040010 | 78.11011 | The request is incorrectly formatted for %1. |
| 0xc0040011 | 78.11011 | The wrong version of the driver has been loaded. |
| 0xc0040012 | 78.11011 | The driver beneath this one has failed in some way for %1. |
| 0xc0040013 | 78.11011 | The device, %1, has been reset. |
| 0xc0040014 | 78.11011 | A transport driver received a frame which violated the protocol. |
| 0xc0040015 | 78.11011 | 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. |
| 0xc0040016 | 78.11011 | 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. |
| 0xc0040017 | 78.11011 | 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. |
| 0xc0040018 | 78.11011 | 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. |
| 0xc0040019 | 78.11011 | The driver has detected a device with old or out-of-date firmware. The device will not be used. |
| 0xc004001b | 78.11011 | 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'. |
| 0xc004001c | 78.11011 | 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'. |
| 0xc004001d | 78.11011 | 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'. |
| 0xc004001e | 78.11011 | 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'. |
| 0xc004001f | 78.11011 | The file %2 on device %1 contains a bad disk block. |
| 0xc0040029 | 78.11011 | The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the device %1 with label "%2". |
| 0xc004002a | 78.11011 | The user disk quota information is unusable. To ensure accuracy, the file system quota information on the device %1 with label "%2" will be rebuilt. |
| 0xc004002b | 78.11011 | The system sleep operation failed |
| 0xc004002c | 78.11011 | The system could not get file retrieval pointers for the dump file. |
| 0xc004002d | 78.11011 | The system could not sucessfully load the crash dump driver. |
| 0xc004002e | 78.11011 | Crash dump initialization failed! |
| 0xc004002f | 78.11011 | 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 |
| 0xc0040030 | 78.11011 | 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. |
| 0xc0040031 | 78.11011 | Configuring 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. |
| 0xc0040037 | 78.11011 | The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume %2. |
| 0xc004006c | 78.11011 | 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. |
| 0xc0040075 | 78.11011 | 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. |
| 0xc0040096 | 8.11011 | Disk %2 has reached a logical block provisioning permanent resource exhaustion condition. |
| 0xc004009a | 8.11011 | The IO operation at logical block address %2 for Disk %3 (PDO name: %4) failed due to a hardware error. |
| 0xc00400a1 | 10 | Dump file creation failed due to error during dump creation. |
| 0xc005003d | 78.11011 | Machine Check Event reported is a fatal level %3 Cache error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc005003f | 78.11011 | 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. |
| 0xc0050041 | 78.11011 | Machine Check Event reported is a fatal External/Internal bus error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050043 | 78.11011 | 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. |
| 0xc0050045 | 78.11011 | Machine Check Event reported is a fatal Micro Architecture Structure error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050047 | 78.11011 | 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. |
| 0xc0050049 | 78.11011 | 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. |
| 0xc005004b | 78.11011 | 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. |
| 0xc005004d | 78.11011 | 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. |
| 0xc005004f | 78.11011 | Machine Check Event reported is a fatal System Event error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050051 | 78.11011 | 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. |
| 0xc0050053 | 78.11011 | Machine Check Event reported is a fatal PCI bus Parity error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050055 | 78.11011 | 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. |
| 0xc0050057 | 78.11011 | Machine Check Event reported is a fatal PCI bus SERR error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050059 | 78.11011 | 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. |
| 0xc005005b | 78.11011 | 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. |
| 0xc005005d | 78.11011 | 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. |
| 0xc005005f | 78.11011 | Machine Check Event reported is a fatal PCI bus Timeout error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050061 | 78.11011 | Machine Check Event reported is an unknown fatal PCI bus error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050063 | 78.11011 | Machine Check Event reported is a fatal PCI component error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050065 | 78.11011 | 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. |
| 0xc0050067 | 78.11011 | Machine Check Event reported is a fatal Platform Specific error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050069 | 78.11011 | Machine Check Event reported is a fatal error reported to CPU %1. |
| 0xc005006b | 78.11011 | Machine Check Event reported is a fatal error. |
| 0xc0050072 | 78.11011 | Machine Check Event reported is a fatal CPU error reported to CPU %1. %2 additional error(s) are contained within the record. |
| 0xc0050078 | 78.11011 | Machine Check Event reported is a fatal memory hierarchy error. Trasaction Type: %1 Memory Hierarchy Level: %2 Request Type: %3 Address: %4 |
| 0xc0050079 | 78.11011 | Machine Check Event reported is a fatal TLB error. Transaction Type: %1 Memory Hierarchy Level: %2 Address: %3 |
| 0xc005007a | 78.11011 | Machine Check Event reported is a fatal Bus or Interconnect error. Memory Hierarchy Level: %1 Participation: %2 Request Type: %3 Memory/IO: %4 Address: %5 |
| 0xc005007b | 78.11011 | Machine Check Event reported is a fatal Bus or Interconnect timeout error. Memory Hierarchy Level: %1 Participation: %2 Request Type: %3 Memory/IO: %4 Address: %5 |
| 0xc005007c | 78.11011 | Machine Check Event reported is a fatal internal watchdog timer error. |
| 0xc005007e | 78.11011 | Machine Check Event reported is a fatal microsoft ROM parity error. |
| 0xc005007f | 78.11011 | Machine Check Event reported is a fatal condition. A processor received an external signal that an unrecoverable error has occurred. |
| 0xc0050080 | 78.11011 | Machine Check Event reported is a fatal functional redundancy check error. |
| 0x400a2 | 11 | Dump file generation succeded. |
| 0x80380001 | 11 | There was an error validating KSR data - operation %2 status %3. |
| 0x80380002 | 11 | Failed to read KSR data - disk %2 sector %3 operation %4 status %5. |
| 0x80380003 | 11 | A %2 operation took place during KSR - disk %3 offset %4. |
| 0xc00400a1 | 11 | Dump file creation failed due to error during dump creation. BugCheckProgress was: %2 |
| 0xc00400a3 | 11 | A callback exception was logged during dump. See DumpStack.log for details. |
| 0xc00400a4 | 11 | Configuring the dedicated dump for crash dump failed. Make sure the dedicated dump file path is set correctly, or the disk has enough space to create the dump file. |
| 0x80040082 | 7 | The file system structure on volume %2 has now been repaired. |
| 0x80040086 | 7 | The transaction resource manager on volume %2 encountered an error during recovery. The resource manager will continue recovery. |
| 0x80040088 | 7 | The default transaction resource manager on volume %2 encountered an error while starting and its metadata was reset. The data contains the error code. |
| 0x8004008b | 7 | {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 | 7 | {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 | 7 | {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. |
| 0xc0040083 | 7 | The file system structure on volume %2 cannot be corrected. Please run the chkdsk utility on the volume %2. |
| 0xc0040087 | 7 | The transaction resource manager on volume %2 was unable to create free space in its log due to a non-retryable error. The data contains the error code. |
| 0xc0040089 | 7 | The default transaction resource manager on volume %2 encountered a non-retryable error and could not start. The data contains the error code. |
| 0xc004008a | 7 | The transaction resource manager at %2%3 encountered a fatal error and was shut down. The data contains the error code. |
| 169 entries | ||