NdisWriteErrorLogEntry - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ndis.h
VOID NdisWriteErrorLogEntry(
[in] NDIS_HANDLE NdisAdapterHandle,
[in] NDIS_ERROR_CODE ErrorCode,
[in] ULONG NumberOfErrorValues,
...
);
View the official Windows Driver Kit DDI referenceNo description available.
NdisWriteErrorLogEntry writes an entry to the system I/O error log file.
NdisAdapterHandle [in]Specifies the handle representing the NIC that is the cause of the I/O error to be logged. This handle is an input parameter to MiniportInitializeEx.
ErrorCode [in]Specifies the NDIS_ERROR_CODE_XXX code that best describes the I/O error as one of the following values:
The driver could not access a required resource.
The hardware or driver ran out of resources.
The driver detected a hardware error.
The network adapter was not found.
The interrupt registration failed.
A driver failure occurred that does not match any of the other error conditions.
The driver detected a version mismatch.
A timeout expired.
A network address is invalid.
The requested driver configuration is not supported.
The network adapter hardware provided an invalid value.
A driver configuration parameter is missing in the registry.
The I/O base address for the network adapter hardware is invalid.
The amount of receive buffer memory that is available is too small to receive data.
The network adapter hardware is disabled.
NumberOfErrorValues [in]Specifies the number of ULONG values to follow this parameter.
...Specifies a variable-sized array of ULONGs associated with the error to be logged.
NdisWriteErrorLogEntry allocates an I/O error log record, fills in the record with the supplied information about the error, and then writes the record to the I/O error log file.
The system places a limit on the potential size of an error log record. For Windows 2000 and later versions, the limit is defined as ERROR_LOG_MAXIMUM_SIZE. The NumberOfErrorValues passed to NdisWriteErrorLogEntry therefore has a system-enforced limit, which is considerably less than the maximum possible value for a ULONG.
In practice, few callers of NdisWriteErrorLogEntry even approach the limit for NumberOfErrorValues because supplying many additional NDIS_STATUS_XXX values is not particularly helpful to the user or system administrator who later reads the error log, using the Win32 event viewer. Logging an I/O error at every possible opportunity is not particularly helpful to users either, so a miniport driver should log only critical I/O errors that can help a user or system administrator to debug a network failure for which the NIC is responsible on a particular machine or a configuration resource conflict discovered during driver initialization.
In general, a miniport driver calls NdisWriteErrorLogEntry during initialization from its MiniportInitializeEx function if it cannot initialize a NIC that it controls or cannot allocate the hardware resources it needs to carry out I/O operations on a NIC. A miniport driver also can call NdisWriteErrorLogEntry when a device-reset operation fails due to unrecoverable hardware error(s). Logging these kinds of I/O errors helps users or system administrators to identify a badly configured NIC or a NIC with failing hardware components.