📄 ntiologc.h
字号:
// 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.
//
#define IO_ERR_IRQ_CONFLICT_DETECTED ((NTSTATUS)0xC0040018L)
//
// MessageId: IO_ERR_BAD_FIRMWARE
//
// MessageText:
//
// The driver has detected a device with old or out-of-date firmware. The
// device will not be used.
//
#define IO_ERR_BAD_FIRMWARE ((NTSTATUS)0xC0040019L)
//
// MessageId: IO_WRN_BAD_FIRMWARE
//
// MessageText:
//
// The driver has detected that device %1 has old or out-of-date firmware.
// Reduced performance may result.
//
#define IO_WRN_BAD_FIRMWARE ((NTSTATUS)0x8004001AL)
//
// MessageId: IO_ERR_DMA_RESOURCE_CONFLICT
//
// MessageText:
//
// 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'.
//
#define IO_ERR_DMA_RESOURCE_CONFLICT ((NTSTATUS)0xC004001BL)
//
// MessageId: IO_ERR_INTERRUPT_RESOURCE_CONFLICT
//
// MessageText:
//
// 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'.
//
#define IO_ERR_INTERRUPT_RESOURCE_CONFLICT ((NTSTATUS)0xC004001CL)
//
// MessageId: IO_ERR_MEMORY_RESOURCE_CONFLICT
//
// MessageText:
//
// 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'.
//
#define IO_ERR_MEMORY_RESOURCE_CONFLICT ((NTSTATUS)0xC004001DL)
//
// MessageId: IO_ERR_PORT_RESOURCE_CONFLICT
//
// MessageText:
//
// 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'.
//
#define IO_ERR_PORT_RESOURCE_CONFLICT ((NTSTATUS)0xC004001EL)
//
// MessageId: IO_BAD_BLOCK_WITH_NAME
//
// MessageText:
//
// The file %2 on device %1 contains a bad disk block.
//
#define IO_BAD_BLOCK_WITH_NAME ((NTSTATUS)0xC004001FL)
//
// MessageId: IO_WRITE_CACHE_ENABLED
//
// MessageText:
//
// The driver detected that the device %1 has its write cache enabled. Data corruption
// may occur.
//
#define IO_WRITE_CACHE_ENABLED ((NTSTATUS)0x80040020L)
//
// MessageId: IO_RECOVERED_VIA_ECC
//
// MessageText:
//
// Data was recovered using error correction code on device %1.
//
#define IO_RECOVERED_VIA_ECC ((NTSTATUS)0x80040021L)
//
// MessageId: IO_WRITE_CACHE_DISABLED
//
// MessageText:
//
// The driver disabled the write cache on device %1.
//
#define IO_WRITE_CACHE_DISABLED ((NTSTATUS)0x80040022L)
//
// MessageId: IO_FILE_QUOTA_THRESHOLD
//
// MessageText:
//
// A user hit their quota threshold on volume %2.
//
#define IO_FILE_QUOTA_THRESHOLD ((NTSTATUS)0x40040024L)
//
// MessageId: IO_FILE_QUOTA_LIMIT
//
// MessageText:
//
// A user hit their quota limit on volume %2.
//
#define IO_FILE_QUOTA_LIMIT ((NTSTATUS)0x40040025L)
//
// MessageId: IO_FILE_QUOTA_STARTED
//
// MessageText:
//
// The system has started rebuilding the user disk quota information on
// device %1 with label "%2".
//
#define IO_FILE_QUOTA_STARTED ((NTSTATUS)0x40040026L)
//
// MessageId: IO_FILE_QUOTA_SUCCEEDED
//
// MessageText:
//
// The system has successfully rebuilt the user disk quota information on
// device %1 with label "%2".
//
#define IO_FILE_QUOTA_SUCCEEDED ((NTSTATUS)0x40040027L)
//
// MessageId: IO_FILE_QUOTA_FAILED
//
// MessageText:
//
// The system has encounted an error rebuilding the user disk quota
// information on device %1 with label "%2".
//
#define IO_FILE_QUOTA_FAILED ((NTSTATUS)0x80040028L)
//
// MessageId: IO_FILE_SYSTEM_CORRUPT
//
// MessageText:
//
// The file system structure on the disk is corrupt and unusable.
// Please run the chkdsk utility on the device %1 with label "%2".
//
#define IO_FILE_SYSTEM_CORRUPT ((NTSTATUS)0xC0040029L)
//
// MessageId: IO_FILE_QUOTA_CORRUPT
//
// MessageText:
//
// 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.
//
#define IO_FILE_QUOTA_CORRUPT ((NTSTATUS)0xC004002AL)
//
// MessageId: IO_SYSTEM_SLEEP_FAILED
//
// MessageText:
//
// The system sleep operation failed
//
#define IO_SYSTEM_SLEEP_FAILED ((NTSTATUS)0xC004002BL)
//
// MessageId: IO_DUMP_POINTER_FAILURE
//
// MessageText:
//
// The system could not get file retrieval pointers for the dump file.
//
#define IO_DUMP_POINTER_FAILURE ((NTSTATUS)0xC004002CL)
//
// MessageId: IO_DUMP_DRIVER_LOAD_FAILURE
//
// MessageText:
//
// The system could not sucessfully load the crash dump driver.
//
#define IO_DUMP_DRIVER_LOAD_FAILURE ((NTSTATUS)0xC004002DL)
//
// MessageId: IO_DUMP_INITIALIZATION_FAILURE
//
// MessageText:
//
// Crash dump initialization failed!
//
#define IO_DUMP_INITIALIZATION_FAILURE ((NTSTATUS)0xC004002EL)
//
// MessageId: IO_DUMP_DUMPFILE_CONFLICT
//
// MessageText:
//
// 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
//
#define IO_DUMP_DUMPFILE_CONFLICT ((NTSTATUS)0xC004002FL)
//
// MessageId: IO_DUMP_DIRECT_CONFIG_FAILED
//
// MessageText:
//
// 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.
//
#define IO_DUMP_DIRECT_CONFIG_FAILED ((NTSTATUS)0xC0040030L)
//
// MessageId: IO_DUMP_PAGE_CONFIG_FAILED
//
// MessageText:
//
// 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.
//
#define IO_DUMP_PAGE_CONFIG_FAILED ((NTSTATUS)0xC0040031L)
//
// MessageId: IO_LOST_DELAYED_WRITE
//
// MessageText:
//
// {Lost Delayed-Write Data}
// The system was attempting to transfer file data from buffers to %1.
// The write operation failed, and only some of the data may have been
// written to the file.
//
#define IO_LOST_DELAYED_WRITE ((NTSTATUS)0x80040032L)
//
// MessageId: IO_WARNING_PAGING_FAILURE
//
// MessageText:
//
// An error was detected on device %1 during a paging operation.
//
#define IO_WARNING_PAGING_FAILURE ((NTSTATUS)0x80040033L)
//
// MessageId: IO_WRN_FAILURE_PREDICTED
//
// MessageText:
//
// 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.
//
#define IO_WRN_FAILURE_PREDICTED ((NTSTATUS)0x80040034L)
//
// MessageId: IO_WARNING_INTERRUPT_STILL_PENDING
//
// MessageText:
//
// 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.
//
#define IO_WARNING_INTERRUPT_STILL_PENDING ((NTSTATUS)0x80040035L)
//
// MessageId: IO_DRIVER_CANCEL_TIMEOUT
//
// MessageText:
//
// 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.
//
#define IO_DRIVER_CANCEL_TIMEOUT ((NTSTATUS)0x80040036L)
//
// MessageId: IO_FILE_SYSTEM_CORRUPT_WITH_NAME
//
// MessageText:
//
// The file system structure on the disk is corrupt and unusable.
// Please run the chkdsk utility on the volume %2.
//
#define IO_FILE_SYSTEM_CORRUPT_WITH_NAME ((NTSTATUS)0xC0040037L)
#endif /* _NTIOLOGC_ */
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -